Forums
While playing around with mididings and a script that gets midi information from Robin Gareus' jack_midi_clock I noticed a little flaw with Qtractor as a JACK transport master:
-
Start Qtractor
-
Load a song, playhead is at 1.1.000 after loading in this example
-
play a few bars
-
stop playback
-
End Qtractor
-
Start Qtractor again
-
Load the same song, playhead is at 1.1.000 after loading
-
play (song starts at 1.1.000 as it should)
Now transport position as displayed in Qjackctl resumes at the old position and doesn't get reset to 1.1.000 -
stop
Now transport position is set to the correct position. From this point on everything works as expected.
It looks as if at first play after loading the transport position is not correctly synced to the playhead position.
re. Incorrect initial JACK transport song position...
check if there isn't any other application playing JACK timebase master around (allegedly not jack_midi_clock)
there can only be one (timebase master) at any one time, otherwise the symptoms you report may arise randomly.
seeya
ps. I assume you're into genuine jackd, not pipewire-jack.
checked, genuine jack2
Killing jack_midi_clock doesn't change anything.
Although the song starts at 1.1.000 its position on Qjackctl is displayed from the old position 2.3.102 on.
When repositioning the playhead after loading and before playing then the correct position is sent (not done in the video).
Only when playing immediately after loading then the initial position is not or not correctly sent.
strange system of mine
I tested the same on another machine, where the playhead doesn't jump to 1.1.000 after loading a song file.
Then the problem I described doesn't manifest.
I have to find out first why on one system the playhead jumps to 1.1.000 after loading a song and on another system it doesn't.
Add new comment