Hi guys, I was looking into the transport code (because I was having sync. issues with another app), and here's how I understand it:
* When Hydrogen is the timebase master, it supplies the B:B:T info based on info supplied by the Hydrogen instance. * When Hydrogen is the timebase slave, it ignores the B:B:T info supplied by the timebase master. Instead, it only looks for changes in jack_position_t::beats_per_minute and calculates frame offsets from that. (It also looks for a couple of relocate events.) * The info supplied by jack_position_t is communicated to the Hydrogen instance through a TransportInfo object. This object only contains status, a frame offset, the tick size, and the current tempo. * It doesn't look like Hydrogen has any way to recover the downbeat if the BPM calculations drift. Is this the current state of things? If so -- I have a few problems with that, but I'll hold my comments until I understand what is happening. Peace, Gabriel ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
