Main menu
You are here
Probs with multiple qtr instances
Hi Rui!
I have a MIDI file that is pseudo tempo-less in that its tempo is set to 120bpm when loaded but its contents are actually being played at about 175bpm so I want to transcribe and clean it up into a proper, clean 175bpm MIDI file.
I was hoping I would be able to do this using two simultaneous instances of qtractor - one set at 120bpm with the effectively tempo-less file open for reference and then another qtr instance open with a fresh session set to 175bpm but it looks like I'll have to find another MIDI editor/viewer to be the reference player, at least for the moment, due to a couple of issues:
1 - Changing the tempo under one instance of qtractor changes it for both (all?) open instances of qtractor
2 - When I hit space to play, I only want the instance of qtractor that is currently in focus to play but both instances start playing.
It would be nice if multiple instances of qtractor could be controlled independently - I hope this isn't a big issue!?
Play prob solved
I had qtr set to 'Full' JACK transport mode. After setting it to 'master' instead I can now play each instance individually - I should've known better there!
I think that changing JACK transport mode has somehow fixed my tempo problem too - hopefully I've not spoken too soon on that!
Re. Probs with multiple qtr instances
i see.
i'm glad you found the solution as is: when jack-transport mode is set to "Full" or "Slave", session tempo follows the current jack-transport rolling state; if you change that setting it takes immediate effect on the current instance where you've changed it but all others will take effect only when they get restarted.
i guess you just tripped on it but there's an old leftover that dates back to the time when jack-session was introduced and multiple qtractor instances were allowed, is that the jack-transport mode setting is a global application configuration option and not a per session/instance one.
among other global options that may eligible, making the jack-transport mode setting a session property has been left in a coma. i even dare to say you just tripped on its life-support wires :))
byee
Add new comment