18 Aug
2011
18 Aug
'11
11:28 p.m.
On 08/18/2011 05:04 PM, rosea grammostola wrote:
On 08/18/2011 05:33 PM, Rui Nuno Capela wrote:
Ok thanks. Basic transport functionality in Qtractor seems to work, but
not recording. How do you assign a knob in qmidictl to a knob in qtractor?
the usual way: right-click on any qtractor slider, select "MIDI
Controller...", exercise some button or slider on qmidictl, a midi
channel controller event should be detected and exposed on the qtractor
midi controller dialog, hit ok. that's it (ie. midi controller learn
feature on qtractor side)
the other way is assigning a permanent controller map to each qtractor
mixer track strip. a bit more complicated to explain here, but you
should get right away with this file:
http://www.rncbc.org/datahub/usx2y.qtc
after importing it into the View/Controllers... configuration dialog
--that's the default mapping for qmidictl track sliders (following an
old jlcooper control surfaces, found in some tascam ones too, if you wish)
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Hi,
Is it possible to use qmidictl from a n900 to qtractor or ardour? Is
there a howto somewhere, or can someone explain it?
of course you can use qmidictl to control qtractor, ardour or whatever
midi controlled program you might think of.
by default most controls are plain mmc which qtractor and ardour does
respond if configured properly. all qmidictl widgets (buttons, sliders
or knobs) are configurable to transmit/recognize any other midi channel
event type, besides mmc (cf. Configure...)
if not obvious already, you'll need a gateway device on the same machine
you run the daw. yours trully qmidinet is a good choice ; it does
alsa-midi and/or jack-midi, so that you can connect the provided in/out
ports to and from the designated control ports of qtractor, ardour, w/e.
cheers