Re: [seq24-users] Sync Problem using Sooperlooper as jack master and seq24 as slave
Brought to you by:
rcbuse
|
From: Aurelien <tyr...@fr...> - 2009-07-02 17:23:32
|
Hello again, I've found today the reason of all this these troubles. It was pure "hasard". I'm using netjack with this machine. The fact is that the script runs jack_netsource on the master machine even if the slave machine is not there. If the slave machine is not connected, I get this weird latency, when it's connected, everything turns back well. Couldn't say why, but if someone has the same problem, here is a way to explain it. On Thu, Jul 02, 2009 at 10:12:29AM +0200, Aurelien wrote : > Hello > (First of all, sorry, I didn't find the time to write my patch files and > send them here) > > I'm exepriencing some troubles, quite weird and not so reproductible, > with MIDI synchronization between seq24 and other stuffs. > > I've got to describe a bit my setup to make this mail understandable. > > So, I use Sooperlooper as Jack Timebase Master, and as a live-looper, of > course. > I then use seq24 as a a sequencer controlling several instances of > AlsaModularSynth, and one of Tapeutape (a sampler), and also Q Light > Controller (a light controller package). > > I've made some patches in seq24 so that I can bind a MIDI control to > start and stop playback. > > Now, here is the problem: > Sometimes, all work fine, when I hit the playback MIDI binding or the > space key, sequences begin to play with tempo given by SooperLooper. I > can change SooperLooper tempo, it works really fine. > I mean, starting playback is "instantaneous" (as much as possible) with > the MIDI Signal. > > Some other times, it's not the same. When I hit the playback MIDI > binding, there is a really big delay (like 5-10s) before it begins to > start playback. > > One important thing is that everything is launched using a bash script, > so that the init sequence is the very same each time I power up the > computer. The only thing changing from one session to another is the > time when I've to unplug/plug my MIDISPORT interface as it's not > detected by udev when plugged at boot. > Another important thing is that when it doesn't work, it doesn't work > until I powercycle the COMPUTER!!! > > I know you probably cannot give me a solution or answer with so > "etheral" informations, but I first would like to know in which > direction I should look. I'm not very used with MIDI synchro, and > perhaps it's a really basic error, but I cannot figure out what it deals > with. > > Thanks a lot. > Aurélien > > -- > Aurélien > > ------------------------------------------------------------------------------ > _______________________________________________ > seq24-users mailing list > seq...@li... > https://lists.sourceforge.net/lists/listinfo/seq24-users > -- Aurélien |