Inaccuracy in XTC Mode when using midi automation.

suvak · Post by **suvak** » Wed Nov 30, 2005 4:06 am

Hi there!

I own a Pulsar I and an XTC card, and use(trying to use) my cards in XTC mode.
Everything works fine except one thing I experienced yesterday.
I made a MIDI track in Nuendo3 with periodically repeated notes. The output of the midi track is for example the Inferno XTC synth. I play the track, it's OK the sound is accurate. Now I assign cc21 to the filter cutoff and draw a CC-curve in the midi track. I play again and the sound is inaccurate! The notes play very unslided. Why? Is it because of the high number of CC21 data? It's very frustrating. Does anyone experienced this???

Zajos

voidar · Post by **voidar** » Fri Dec 02, 2005 6:34 pm

Can't you use regular automation instead?

suvak · Post by **suvak** » Mon Dec 05, 2005 5:07 am

I did not try that.
But I use external midi keyboard with controllers and the simplest way to work is to screw out a good filter or something curve. One more thing:When I "just" play on my external keyboard and turn the controllers and Nuendo is NOT in play mode then does not come this error. (Technical info:When Nuendo does not play then it resets all incoming midi inputs sample offset to 0 in an audio buffer). When Nuendo is in play mode (eg:I try to record my playings) then comes this thing. (Technical info:When Nuendo plays (or records) then it does not set the incoming midi data sample offset (VstMidiEvent.DeltaFrames) in an audio buffer). So I think VST SFP devices has a problem handling input VST midi data arrives with different DeltaFrames.

Suvak