On Mon, Aug 08, 2011 at 05:30:08PM +0200, Florian Paul Schmidt wrote: the problem is that seq24 is registering a jack_sync callback. this is not correct. and i pretty much said that this was going to happen. a quick fix would be to register an empty process_callback() this would retain the old behaviour. however, this is still wrong. seq24 is not a slowsync client. you should probably do what is done in the sync callback from inside the process cb. the process_cb is called always, and not only when the transport starts, so one needs to go through a few hoops to obtain the same behaviour. i remember, that i tried to fix this, but i dont find the patch, and reading through archives, i might have hit a few problems, when i tried to fix it. -- torben Hohn