You are here

Weird Midi controller problem


first I want to say thanks for qtractor, it seems just to be made for my workflow. I found instrument definition files for both of my keyboards and imported them successfully. The template creation is perfect for my different setups. Visiting a home recording workshop showed that everything I need is possible with qtractor, too. Today I tried to use qtractor with controller functions:

My Workstation allows me to use 8 trigger pads and i assigned them to control the transport. Every function (forward, fast forward, backward etc.) works fine, but play/pause does not.

The problem is that sometimes it works and then several times in a row, but most of the time (90%) the playhead moves a little bit and then jumps back, stopping. Holding the button plays the project as long as the pad is pressed.

- Switching to another trigger pad does not work, same problem
- Switching to a key from the keyboard works!?
- Hitting the space bar works as always

Midi sniffing shows that the trigger pad sends note on/note off as the key does, but the pad has no velocity (only 127 and 0)

As I said, every other transport function works using the trigger pads, so I am a little desperated :-) Has anyone assigned the play/pause function to a midi controller (not a key)? Can anyone confirm this behavior or is my workstation to blame?


rncbc's picture

have you check whether Transport > Continue Past End is playing you tricks?


Hi Rui,

thanks for the quick reply, I tried:
- Turning off "Continue past end"
- Deactivating a2jmidid
- Turning off "Auto backward"
The latter moved the playhead without setting it backward, which is IMHO the desired behavior.
If nobody else has this problem, I put the blame on my workstation and use the space bar to play/pause.

Could you please explain the "Latch" option when assigning midi shortcuts, I did not find it in the documentation?

Thanks for your help


rncbc's picture

Could you please explain the "Latch" option when assigning midi shortcuts, I did not find it in the documentation?

the "Latch" option is only applicable to on/off toggle subjects and relates to "latch" vs. "momentary" (opposite) modes of switches--latch=OFF is same as momentary=ON and vice versa--and applies mostly to foot-switches (or pedal controllers) mode of operation.

latch (=on) mode is the default setting for most controllers, but when you have a midi controller that operates in "momentary" mode, it usually sends an event when you press (0->1) and another one when you depress (1->0)--that's why it is said "momentary": the switch state is only signaled momentarily on while you keep the switch pressed, returning to its former state when you depress it.

setting the "Latch" option to OFF for these later cases, will simulate a toggle switch, meaning that the target subject state will only change to ON _or_ OFF when the switch is _either_ being pressed _or_ depressed, respectively.


Add new comment