Support
Looper's Delight
|
Support |
|
|
For a year now I've been using my EDP with Sonar running on a Windows XP machine and have been experiencing inconsistent behavior from it. I have sent a lot of mails to the list describing various problems I have had and either bored, or stumped everyone into mostly silence. I do a one-man-band thing with sequenced backing tracks which include EDP control commands written into them to record and playback parts of the song which I "play in." No matter what I would do, the commands written into the sequencer would never work the same twice. Or, if they did twice, they wouldn't a third time. If Quantize was ON, sometimes it would quantize to the bar, sometimes it would quantize to a beat after, sometimes it would be a bar late. If Quantize was OFF, sometimes it would trigger on time with the sequencer, sometimes it would trigger late, and sometimes it would trigger early. I found it weird that to get commands to sound "on the beat" I would have to turn Quantize off, and then move the trigger note to the "a" (1e&a) of beat four. Anyway, there was a recent discussion on the list about Mac vs. PC regarding audio and MIDI latency which got me thinking... The timing master in Sonar is set to my main audio interface's digitial audio driver. QUESTION(S): Is the sequencer (Sonar) sending MIDI data late or early to make up for latency of the audio tracks in a sequence? Is this lateness/earliness variable, or a fixed amount of time? Could this be causing the seemingly erratic behavior of sequenced EDP commands? In the Mac/PC discussion on latency there was some discussion about Windows inducing another level of latency to MIDI data, which Macs somehow bypass. Is there any way of measuring this latency?