Main menu
You are here
Can't adjust volume of midi tracks in mixer?
29 June, 2013 - 20:23 — nobody (not verified)
I have midi tracks with Calf Monosynth and Calf Organ on them. Everything seems to work just fine until I adjust the volume slider on the tracks in the mixer window. Nothing happens. What am I doing wrong?
Forums:
re. Can't adjust volume of midi tracks in mixer?
the MIDI volume (and panning) slider on MIDI track mixer strips act specifically as dedicated MIDI channel controllers CC#7 for volume (and CC#10 for panning), so their effect actually depend on the receiving MIDI instrument or plugin implementation.
that said, it all depends whether Calf Monosynth or Calf Organ recognizes and reacts itself to each of the MIDI channel controllers just mentioned (CC#7 or CC#10).
i can't confirm it atm. but not all MIDI instruments or plugins have that controller mapping set by design or default, so that you won't see any response or effect while changing the volume sliders on the MIDI track / channel they're inserted into.
hth.
cheers
looks like midi bus mixer
looks like midi bus mixer strips sends sysex messages, not CC (#7/#10)
re. looks like midi bus mixer
that's right. since day one, MIDI output buses do send GM master volume or panning messages, which are sysex messages indeed (aka. GM System Universal messages).
cheers
But it worked fine before..!?
I tried fiddling with the "MIDI controller" menu of the track (|( I only want the volume fader of the track to actually control the volume of the instrument) but while I know what QTractor (0.5.7.3) sends, I have no clue about what Monosynth (calf-plugins 0.0.19) receives. And franckly I cannot imagine that Calf decided to change the parameter numbers their plugins receive.
I made a lot of songs using Monosynth tracks in Qtractor and never experience that PB ; what could have happened to either of those entities (Qtractor, Monosynth, and I) ?
I'm very sad at the idea of not using calf Monosynth anymore... The other plugins I tried seem to work (but ONE misbehaving strip on the console, and the whole mixing experience is ruined).
Very loosely related : Does anybody know how to use Qtractor on Unity and still see the toggle status of the track controls ? (Record / Mute / Solo)
re. Qtractor on Unity
maybe not related to Unity on itself but to the general qt4 widget style in use on gtk based environments.
try the
qtractor -style -plastiqueyou'll get better results, i hope. it's also the recommended workaround when midi input inexplicably stops to work usually after you're opening any of the common file browser dialogs. so that, as they say, you kill two rabbits with just one stick :)
cheers
Workaround
You can use the "Learn Midi Assignement" in the volume knob of your plugin, and then playing the QTractor channel fader. It will work great for Helm, for example, but also the Calf instruments as well.
Thank you very much for your
Thank you very much for your quick answer, Rui. The plastique style option does indeed solve all the graphical issues. But the volume faders continue to ignore what I'm telling them to do. I just open the session using "open last..." avoiding the file dialogs. I'm going to investigate further.
Has anyone got this to work
Has anyone got this to work with Calf plugins? I am also experiencing the same issue with a DSSI VST synth. Would love to work on getting this resolved since I am currently mixing with the plugin volume knobs!
re. Has anyone got this to work
as posted before, if the Calf plugin you're using doesn't recognize MIDI CC#7 for volume (CC#10 for panning) as from elder GM standard, then yes, you're left with proper plugin controls as you say. qtractor's midi track sliders won't do a thing for you. sorry.
byee
Thanks for the reply. Suppose
Thanks for the reply. Suppose that the plugin did expose some interface that allowed you to assign CC numbers to various knobs/sliders. In theory, would this allow the slider to work?
re. Suppose that the plugin
re. Suppose that the plugin did expose some interface that allowed you to assign CC numbers to various knobs/sliders. In theory, would this allow the slider to work?
yes. correct.
Workaround with dedicated audio bus
Hi there,
Got the same problem with calf organ loaded as lv2 plugin (is lv2 plugins volume controlled by midi cc ? I would have thought it would be somewhat more low level) : volume of calf organ would not be controlled by its midi track volume fader.
I managed to work around it by creating a dedicated audio bus :
1. go to `view / buses ...`
2. select master bus
3. change its name to something else
4. press "create" button (this creates the new bus, "update" button would have overwritten master bus)
5. open mixer
6. right click calf plugin
7. in "audio" submenu, select your new bus
You now have a new bus in mixer (just next "master" output) which you can use to control calf plugin volume.
Any changes regarding this issue in latest qtractor versions?
Hi there,
the qtractor changelog says (among other things) the following about version 0.9.14:
LV2 Plug-in Patch parameter/properties automation and MIDI
Controller assignment/learn are now a possibility.
Shouldn't that allow to assign those MIDI events sent by the mixer strips to any of the plug-in parameters displayed in the plugin properties dialog? (I've had no luck, though, to find any (context) menu option to initiate MIDI learning on the plugin properties widgets in version 0.9.15.)
It would really provide a much smoother mastering experience if it was possible to adjust the volume of e.g. calf synth tracks through the mixer instead of always having to open the plugin GUIs...
Cheers --
re. Any changes regarding this issue in latest qtractor versions
re. LV2 Plug-in Patch parameter/properties automation and MIDI Controller assignment/learn are now a possibility.
this are not the least related to your question: it's a LV2 specific thing (LV2 Patch properties) that were not automate-able before.
re. if it was possible to adjust the volume of e.g. calf synth tracks through the mixer instead of always having to open the plugin GUIs...
you can set one of those plugin parameters as in so called "direct-access" mode: on that a little slider will overlay the plugin list entry so that you'll have, yes, direct access to that plugin control right from the mixer strip, without having to open the plugin's own GUI (plugin > Edit); you can set once this "direct access" from the plugin's context menu (plugin > Direct Accesss > ...) or from the generic plugin's GUI (plugin > Properties...).
hth.
cheers
Direct access rules!
this are not the least related to your question
Ah, sorry, this apparently was a misunderstanding on my side. Although having used Linux as main OS for over 15 years, I'm still pretty new to Linux-based MIDI and audio processing. Last time I did some computer music was with Cakewalk 3 on Windows 98... ;)
you can set one of those plugin parameters as in so called "direct-access" mode: on that a little slider will overlay the plugin list entry so that you'll have, yes, direct access to that plugin control right from the mixer strip
That's cool, thanks for the advice!
Cheers --
Add new comment