Add new comment

Now that's one can of worms that is being opened. Qtractor doesn't have to embed Hydrogen, one way or the other, nor the other way around.

What we should think about is how the two can sync each-other in face and despite the presence of a tempo/time-signature map, which should be shared between the two applications but that's not the point, I think. Yeah, things might just go wrong sometimes; take loops, MIDI clock or MIDI song position protocol in particular. That is, if applications fail to share the very same tempo map, there will be a point, sooner or later, when they will be severely but systematically out of sync.

However, given this is an open implementation hiatus, so to speak, hydrogen and qtractor do reference absolute time. Basically they're both sequencers, one specialized as a drum/percussion sampler (h2) and the other a generic audio/MIDI sequencer. Also, it is no coincidence that both are JACK transport aware. I strongly suspect there must be this potential problem which seems related to both competing as JACK transport timebase masters. I know I have not dealt with this thoroughly, if at all, mostly because I don't use H2 that often ;)

Anyway, this is indeed open for discussion at large, and I surely appreciate all ideas, use cases and what not, to let qtractor and hydrogen inter-operate seamlessly to the least. The most the better :)

Cheers.