Just a quick report to suggest Tempo changes are no longer being persisted across sessions. Feel free to let me know what additional information is needed.
Bah, it's gone again and I may have misreported success when I last updated this thread. I just opened the session this morning and while I see all 3 entries, the 2nd contains a meter of '4/4' when it should contain a meter of '6/4'. Rui, did you happen to change the meter when you last tested?
The problem is probably midiClock+modeIncludingSlave.
If not, check if the error occurs when saving or loading.
To do this, monitor the session file in a text editor when you save. The data is stored in the "tempo-map" tag.
If it saves correctly but Qtractor indicates something different when opened, it's a "Jack" session problem (for example midiClock+modeIncludingSlave).
PS
I haven't been able to reproduce the problem with any configuration.
Reset options again?
The tempo change appears to be loading correctly now although I didn't do anything different in terms of steps or workflow. Seems to happen on an intermittent basis and I'm not sure I could imagine how to reproduce. Something I'll keep an eye on...
Happened again. It may have something to do with saving the session once a new track has been added. I'll keep poking around and reporting what I find. There's something here... just can't understand what conditions trigger the behavior.
re. Meter/tempo changes...
hi,
there's no evidence that's the case: tempo, time-signature map and markers are here still being saved and reloaded fine...
some more details are certainly needed to assess that claim or suggestion.
thanks
I may need to fault user…
I may need to fault user error here as I just fired up my session and saw the programmed meter change was intact.
Bah, it's gone again and I…
Bah, it's gone again and I may have misreported success when I last updated this thread. I just opened the session this morning and while I see all 3 entries, the 2nd contains a meter of '4/4' when it should contain a meter of '6/4'. Rui, did you happen to change the meter when you last tested?
re. Meter/tempo changes...
yes.
Ah, this is happening again…
Ah, this is happening again. I'll set the meter change, save the session only to find it didn't persist when opening the session next time.
After saving and re-opening...
It looks like this
https://github.com/rncbc/qtractor/issues/500
The problem is probably midiClock+modeIncludingSlave.
If not, check if the error occurs when saving or loading.
To do this, monitor the session file in a text editor when you save. The data is stored in the "tempo-map" tag.
If it saves correctly but Qtractor indicates something different when opened, it's a "Jack" session problem (for example midiClock+modeIncludingSlave).
PS
I haven't been able to reproduce the problem with any configuration.
Reset options again?
The tempo change appears to…
The tempo change appears to be loading correctly now although I didn't do anything different in terms of steps or workflow. Seems to happen on an intermittent basis and I'm not sure I could imagine how to reproduce. Something I'll keep an eye on...
MIDI loop?
Is Qtractor both master and slave for MIDI clock and receives its own MIDI clock in its MIDI input?
I guess? I just set it to…
I guess? I just set it to Master since I'm not using any external MIDI stuff.
re. The tempo change appears to…
one question: are you running it on pipewire(-jack) or is it the real mccoy/genuine jackd(bus) ?
pipewire-jack
pipewire-jack
re. pipewire-jack...
then turn off all jack-transport input for x sake.
keep it at all times as "master" or even "none" and only, never "slave" nor "full".
pipewire jack-transport implementation is still quite unreliable to say the least.
hth.
huh? I have no idea what…
huh? I have no idea what jack-transport is and most likely am not running it. I'll google and stuff...
View->Options->General
Transport Mode: None
or Transport > Mode > ...
... "Master" or "None" (as @bluebell suggested), and nothing else.
Happened again. It may have…
Happened again. It may have something to do with saving the session once a new track has been added. I'll keep poking around and reporting what I find. There's something here... just can't understand what conditions trigger the behavior.
Add new comment