You are here

Home › Midi keyboard controller mapping

Add new comment

26 August, 2010 - 08:17 — rncbc
rncbc's picture

Yes, since qtractor-0.4.6.49+ (svn trunk of course) that the MIDI controllers mapping was refactored to support some other MIDI event types than just CC# (Controller) ones. It is still on experimental status so things might break loose.

However, it should read and convert previous control maps seamlessly (retro-compatible) , unless I missed something terrible :)

I'll try to explain the (new) control map fields in a hurry:

Type
This is the type of MIDI event being mapped; options are Note On, Note Off, Key Press, Controller, Chan Press or Pitch Bend; default is Controller (CC#) as before.
Channel
This is the MIDI channel being mapped; it can be one of literally addressable channel numbers (1..16) or set to * (asterisk) which means that the command will be mapped to the same track number (1..16); same as before.
Parameter
Depending on the selected MIDI event Type, this the precise event parameter value that is being mapped; it may be described by its corresponding note/pitch name (as for Note On, Note Off and Key Press event types) or controller names (as for Controller event type, obviously).
Track
This check-box flags whether the previous Parameter value is to be considered as the base track index; when turned on the command will be mapped to track numbers given by consecutive parameter values; eg. if Parameter value is set to 64, track 1 will be mapped to parameter value 64, track 2 to 65 and so on.
Command
This is obviously the command action to be mapped (Track Gain, Track Panning, Track Monitor, Track Record, Track Mute, Track Solo); same as before.
Feedback
This check-box flags whether the corresponding MIDI event should be sent out in response to respective command action; it is made specially useful for control surfaces that keep their own state (eg. motorized faders, lights and LEDs, etc.); same as before.

HTH

If things keep failing on your side, please consider showing here your (original) controllers .qtc file and explain as best as you can what are you trying to achieve. Given the experimental status of this new controllers facility, it might just be a little difficult to succeed at first time. You can blame on me, for a while ;)

Cheers

Copyright (C) 2006-2024 rncbc aka Rui Nuno Capela. All rights reserved.
Powered by Drupal