Nuendo midi notes not recording ontime
which version do you have?
nuendo 2 had that prob, and nuendo 3 worked perfectly.
well.
almost everybody says not to use emulated midi.
in my case only with emulated midi i had a system that could record midi perfect.
when i used non emulated midi, the recording of midi was ok in the beggining and after minutes it started to record behind, and it became worse and worse.
i fixed it with emulated midi.
well in your case i do not really know what is going to fix your problem.
just try both.
in order to have the ability to use emulated midi ports, the file IgnorePortFilter must be in the folder "Midi Port Enabler" which is in nuendo folder.
if you want non-emulated midi, you have to put the file "ignoreportfilter" out of the folder "midi port enabler", and let it be in nuendo folder just by moving with mouse, and leaving the folder "midi port enabler" empty.
try both by recording midi for many minutes.
nuendo 2 had that prob, and nuendo 3 worked perfectly.
well.
almost everybody says not to use emulated midi.
in my case only with emulated midi i had a system that could record midi perfect.
when i used non emulated midi, the recording of midi was ok in the beggining and after minutes it started to record behind, and it became worse and worse.
i fixed it with emulated midi.
well in your case i do not really know what is going to fix your problem.
just try both.
in order to have the ability to use emulated midi ports, the file IgnorePortFilter must be in the folder "Midi Port Enabler" which is in nuendo folder.
if you want non-emulated midi, you have to put the file "ignoreportfilter" out of the folder "midi port enabler", and let it be in nuendo folder just by moving with mouse, and leaving the folder "midi port enabler" empty.
try both by recording midi for many minutes.
thankx for the help, i just 'enabled all" in the midi preferences page (in nuendo) and the midi seems normal, still having a hard time to get logic to see the creamware i/o tho. it seems to me logic has better internal filters for audio processing than nuendo, you can judge it simply by converting some vst audio into nuendo audio, and the clarity's gone, logic sounds excellent tho.
many have noticed that the audio of logic is better than steinberg. the filters are better, but there are always the "cannot continue, audio...blah, blah" blues of operating in logic, i wish i had the audio quality of logic and the gui of nuendo. Once i had a stylus loop which sounded great in stylus, then when i converted it to audio via the mixdown feature in nuendo, it sounded terrible ,i think its the same idea when you take an akai loop and convert it via cdextract for the audio , something is lost audiowise, my techy friends say its the filters , probably in the design
logic should work really well.
off line rendering is never as good as realtime audio in any of the apps i've seen. record the track as audio. logic works just fine with scope, i use it all the time. it does help to set the priority of logic to "above normal" in the task manager.
i don't think that it's "filters that determine the audio quality of software. a filter is a physical thing(emulated in software). more likely, it's algorithms. these are the mathmatical representations of the uncertainty of the real world.....the sound of the app makes a difference, but mostly in the way that signals are combined, called summing..well, and in rendering.
since i sum in scope and i don't render, but record to a new track in real time, i just use either my clients format; or since i prefer the editing there, in cubase and it sounds about as good as it needs to regardless of the sequencer...
actually, i do like the stock logic plugins better than the sonar, samplitude or cubase sx plugins...
off line rendering is never as good as realtime audio in any of the apps i've seen. record the track as audio. logic works just fine with scope, i use it all the time. it does help to set the priority of logic to "above normal" in the task manager.
i don't think that it's "filters that determine the audio quality of software. a filter is a physical thing(emulated in software). more likely, it's algorithms. these are the mathmatical representations of the uncertainty of the real world.....the sound of the app makes a difference, but mostly in the way that signals are combined, called summing..well, and in rendering.
since i sum in scope and i don't render, but record to a new track in real time, i just use either my clients format; or since i prefer the editing there, in cubase and it sounds about as good as it needs to regardless of the sequencer...
actually, i do like the stock logic plugins better than the sonar, samplitude or cubase sx plugins...
summing and seperation sound 'wider' in logic, take a stereo perc loop and logic gets huge width with the scope mixer left,right, and big bottom frame drums get more depth, i guess its the alogorithims, thats why logic crashes easier than nuendo probably.. ..A good example is opening a reason synth vs a scope one, you can add 20 reason synths at 40note polyphony, while a 4 note synth in scope will blow it away.
If you try that priority setting trick (i.e. set the Logic priority at "above normal"), those "Audio Engine Overload" messages should disappear completely for non-really-loaded-up-project use.
You can also turn off the displaying of the messages, so that it just stops playing without opening up a little dialog.
You can also turn off the displaying of the messages, so that it just stops playing without opening up a little dialog.
just my opinion and experience, but logic doesn't crash normally. setting priority WILL eliminate the message you refer to. don't use summing in ANY sequencer if you have scope, sum in scope(for your "serious" mixes).....really, you shouldn't have any problems...
<font size=-1>[ This Message was edited by: garyb on 2006-01-30 21:31 ]</font>
<font size=-1>[ This Message was edited by: garyb on 2006-01-30 21:31 ]</font>