Originally Posted by JSt0rm
The innerclock plug in is going to be delayed with everything else in the system via delay compensation. Its accurate. Most everything has automatic delay compensation and while yes things can go wrong here with plug ins not reporting correctly or something that isnt a problem with any of these systems we are talking about. And you would still have this problem working with usb midi.
Im confused as to your argument as of course midi clock over usb is sloppy as all hell. I thought you were referring to your audio being jitttery. Thats what these products solve - sloppy usb/firewire midi. They solve it by using a audio signal, something that daws are very good at keeping in sync.
Have you used one of these systems?
No I haven't used any of these software CV that's why I asked because I could be interested
Well, yes midi is very sloppy using USB and even certain firewire interfaces, my argument was because I noticed random delays even in audio in certain cases and even with very expensive interfaces, have you ever tried looping back stuff, using like 8 channels at time and then trying to null? Doing that I found my converter is very silent (meaning it nulls a lot) but after a while boom! I had the volume quite loud and I found a part of the audio file was not nulled at all... I zoom to see the waveform and I've seen it didn't null because the audio was shifted compared to the other track... both tracks tracked simultaneously..
Since then I've done that more frequently and I've seen that it happens... not that often to be noticed, but happens... so, considering when I do tests I'm just using 8 tracks and no processing at all... I imagine these things happen much more frequently when you are producing or mixing... and probably we don't notice that because we are making music not tests, but still happen and if that audio clocks stuff could be a problem
But, well... I'll try it out one day