after recorded a trak with arpeg and inferno,the following playback has not good sync.i have quantize,but sometimes the sync is incorrect.
i use logic audio and pulsar2 and scope srb.
thank you
bad sync with arpeg 01 and inferno synt
MIDI as clock sync always has issues it seems - I see this exact thing mentioned on the Waldorf list all the time. I will usually set the BPM manually myself in the CW environment, and record the MIDI data, you can then use tools in your sequencer to adjust it slightly.
There are so many possible things than can cause bad sync, here are a few things to try:
1) Do not send MIDI clock to all midi ports in your sequencer: For me, Logic was sending clock to every port in my system, including the "ALL ports" (maybe I did this, not sure), but removing "ALL ports" caused the MIDI loop I created to vanish and the sync was much better.
2) If you're also sending a bunch of automation(CC) data to the device, thin it out or disable it until after you've recorded the MIDI notes.
3) Avoid MIDI loop back devices like Hubis, these do cause timing issues (for me, even with my external equipment). Took a little tracking down to find it, but removing this solved it.
4) Understand the limitations of MIDI... it wasn't made to be sample accurate or really, to even have an accurate clocking mechanism, unfortunately.
5) If possible, use the CW hardware midi ports rather than the software ports.
6) Check for midi feedback loops. These cause wild MIDI timing fluctuations.
7) Check for other devices in your midi chain which may be sending clock. Sometimes, if you are using a "MIDI through" configuration, the clock may not show up on your midi monitor because it gets "caught" by another device before you can monitor it. But it can still cause problems that can be tricky to track down.
FWIW, I've used these devices without problems in finished songs, but I also am not anal about sample-accurateness, I like a tiny bit of loose-ness. It should be pretty close, so if it's not, carefully go through the check list, I guess.
There are so many possible things than can cause bad sync, here are a few things to try:
1) Do not send MIDI clock to all midi ports in your sequencer: For me, Logic was sending clock to every port in my system, including the "ALL ports" (maybe I did this, not sure), but removing "ALL ports" caused the MIDI loop I created to vanish and the sync was much better.
2) If you're also sending a bunch of automation(CC) data to the device, thin it out or disable it until after you've recorded the MIDI notes.
3) Avoid MIDI loop back devices like Hubis, these do cause timing issues (for me, even with my external equipment). Took a little tracking down to find it, but removing this solved it.
4) Understand the limitations of MIDI... it wasn't made to be sample accurate or really, to even have an accurate clocking mechanism, unfortunately.
5) If possible, use the CW hardware midi ports rather than the software ports.
6) Check for midi feedback loops. These cause wild MIDI timing fluctuations.
7) Check for other devices in your midi chain which may be sending clock. Sometimes, if you are using a "MIDI through" configuration, the clock may not show up on your midi monitor because it gets "caught" by another device before you can monitor it. But it can still cause problems that can be tricky to track down.
FWIW, I've used these devices without problems in finished songs, but I also am not anal about sample-accurateness, I like a tiny bit of loose-ness. It should be pretty close, so if it's not, carefully go through the check list, I guess.