MIDI automation question
-
- KVRist
- 237 posts since 9 Dec, 2016 from Grand Rapids, Michigan USA
I am setting up for some MIDI automation, learning the moves here. So, I have a slider on a MIDI device that I have set up to control the volume of one track. After I get that set and I want to adjust the volume on another different track, how can I turn the MIDI control OFF on the first track, so I can move to another?
When I set the volume slider on my device to control MIDI volume on the first track, and then do the same on the next track, my MIDI slider moves the volume plug in on BOTH tracks, I can't figure out how to disable MIDI control on the first track. I hope that's clear! I know there must be an easy thing that I am missing here, thanks!
When I set the volume slider on my device to control MIDI volume on the first track, and then do the same on the next track, my MIDI slider moves the volume plug in on BOTH tracks, I can't figure out how to disable MIDI control on the first track. I hope that's clear! I know there must be an easy thing that I am missing here, thanks!
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
Does the device have multiple sliders, or are you expecting to select another track, and the same slider controls the SELECTED one?
I have an MPK261 with 9 faders, and they were each set to control individual tracks; and that works well. However, each slider then becomes DEDICATED to a track number, no matter what is selected.
There's probably a better way with a little coding/customization, but that's where I left off... and it works well. 9 faders, last one is master volume; but I'm limited to 8 tracks, unless I select another bank on the keyboard, and the MIDI keyboard then sends info on a NEW set of 9 "input channels" to control what you want there.
From within the controller file that gets imported/exported...
<MAPPING id="65556" addr="" channel="1" function="1800" note="-1"/>
<MAPPING id="65557" addr="" channel="1" function="1801" note="-1"/>
<MAPPING id="65558" addr="" channel="1" function="1802" note="-1"/>
<MAPPING id="65559" addr="" channel="1" function="1803" note="-1"/>
<MAPPING id="65560" addr="" channel="1" function="1804" note="-1"/>
<MAPPING id="65561" addr="" channel="1" function="1805" note="-1"/>
<MAPPING id="65562" addr="" channel="1" function="1809" note="-1"/>
for faders. Not sure if the keyboard sends the 65xxx and function is a combination of function and channel...
I think these are buttons that I mapped using MIDI learn, for the standard rewind, FF, stop, record, and play
<MAPPING id="65653" addr="" channel="1" function="2" note="-1"/>
<MAPPING id="65654" addr="" channel="1" function="1" note="-1"/>
<MAPPING id="65655" addr="" channel="1" function="3" note="-1"/>
<MAPPING id="65651" addr="" channel="1" function="4" note="-1"/>
<MAPPING id="65652" addr="" channel="1" function="13" note="-1"/>
I did get a new computer, installed a newer version of Waveform, and re-imported that same little text file above, and was pleasantly surprised that it all worked properly.
I guess I didn't spend enough time to figure out if I could do it the OTHER way, where i could use up/down keys to change tracks, and from THAT use buttons to mute/unmute/arm for record/ and use a single slider for volume, and another for PAN, etc. I tried for arm alone, and it SORT of worked, but I had to toggle twice for it to change state, for whatever reason.
I have an MPK261 with 9 faders, and they were each set to control individual tracks; and that works well. However, each slider then becomes DEDICATED to a track number, no matter what is selected.
There's probably a better way with a little coding/customization, but that's where I left off... and it works well. 9 faders, last one is master volume; but I'm limited to 8 tracks, unless I select another bank on the keyboard, and the MIDI keyboard then sends info on a NEW set of 9 "input channels" to control what you want there.
From within the controller file that gets imported/exported...
<MAPPING id="65556" addr="" channel="1" function="1800" note="-1"/>
<MAPPING id="65557" addr="" channel="1" function="1801" note="-1"/>
<MAPPING id="65558" addr="" channel="1" function="1802" note="-1"/>
<MAPPING id="65559" addr="" channel="1" function="1803" note="-1"/>
<MAPPING id="65560" addr="" channel="1" function="1804" note="-1"/>
<MAPPING id="65561" addr="" channel="1" function="1805" note="-1"/>
<MAPPING id="65562" addr="" channel="1" function="1809" note="-1"/>
for faders. Not sure if the keyboard sends the 65xxx and function is a combination of function and channel...
I think these are buttons that I mapped using MIDI learn, for the standard rewind, FF, stop, record, and play
<MAPPING id="65653" addr="" channel="1" function="2" note="-1"/>
<MAPPING id="65654" addr="" channel="1" function="1" note="-1"/>
<MAPPING id="65655" addr="" channel="1" function="3" note="-1"/>
<MAPPING id="65651" addr="" channel="1" function="4" note="-1"/>
<MAPPING id="65652" addr="" channel="1" function="13" note="-1"/>
I did get a new computer, installed a newer version of Waveform, and re-imported that same little text file above, and was pleasantly surprised that it all worked properly.
I guess I didn't spend enough time to figure out if I could do it the OTHER way, where i could use up/down keys to change tracks, and from THAT use buttons to mute/unmute/arm for record/ and use a single slider for volume, and another for PAN, etc. I tried for arm alone, and it SORT of worked, but I had to toggle twice for it to change state, for whatever reason.
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRist
- Topic Starter
- 237 posts since 9 Dec, 2016 from Grand Rapids, Michigan USA
Thank you for taking the time to help me out. This is a bit much for what I need, all I want to do is use one slider to record automation for volume on one track, and when that is done move to another track. When I use MIDI learn to set up the same slider with the next track it still remains connected to the first track and now I find I am controlling BOTH of the volume plug ins. There must be a simple command that turns OFF MIDI control for any given parameter. I can't believe that doesn't exist.
- KVRAF
- 4890 posts since 3 Jan, 2003 from Vancouver
Theoretically a shift-click on something somewhere. I've tried it and it seems to be buggy.
viewtopic.php?t=435835
viewtopic.php?t=435835
Surely there must be consensus by now...
-
- KVRian
- 500 posts since 3 Dec, 2021
From memory, select the plugin that you want to 'unlearn'. Go to the controls panel, find the tab with the midi learnt assignment and shift click the assignment you want to clear.
- KVRAF
- 4890 posts since 3 Jan, 2003 from Vancouver
Yes, but I've found that it's flaky. There is supposed to be an assignment number thing but it doesn't seem to show up for me. Also, after the first couple of times the assignment doesn't show up at all, even though the slider on my MIDI device still controls the plugin parameter. At this point any assignment I make is un-delete-able because there is nothing to shift-click on. The assignments are all ghost assignments. I even made a brand new Edit to test.dysjoint wrote: Wed Jan 07, 2026 2:18 pm From memory, select the plugin that you want to 'unlearn'. Go to the controls panel, find the tab with the midi learnt assignment and shift click the assignment you want to clear.
I've been trying to find where the assignment happens in the project files. I thought it would be in the Edit file, but I'm not seeing it there. I hoped it was XML and you could just delete it.
EDIT: I think this has been complicated for me because the device in question was already set up to be a Control Surface. I think MIDI learn is something different. Since I have no idea how any of this is really supposed to work, I'm going to stop trying. Hopefully the above instructions work for the OP. And hopefully TSC will work on a more obvious method.
Surely there must be consensus by now...
-
- KVRist
- Topic Starter
- 237 posts since 9 Dec, 2016 from Grand Rapids, Michigan USA
Thanks everyone for your help so far. I hope the TSC folks will see this and make a fix.
For the meantime, I have found a quick turn that does work, at least for some things. I find that if I right click the "volume" plug in and delete it, and then just put a new volume plug in its place that it will no longer be connected. That works for that, but if I have automated a parameter in some other plug in, that would not work.
For the meantime, I have found a quick turn that does work, at least for some things. I find that if I right click the "volume" plug in and delete it, and then just put a new volume plug in its place that it will no longer be connected. That works for that, but if I have automated a parameter in some other plug in, that would not work.
-
- KVRist
- 374 posts since 18 Nov, 2023
To my knowledge they are not monitoring this forum. This is a user-to-user forum.
You would need to report any issue via the support form directly to Tracktion. The chat bot on their support page will give you the address of the support form.
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
-
- KVRian
- 500 posts since 3 Dec, 2021
I double checked the standard method as I wrote above in case something has changed and it seems ok here. I am using a Nektar LX61+ in 'user preset' mode, so there are definitely no conflicts, just straight midi learn assignments.
I'm pretty simple in my use of it though. Make an assignment using midi learn. Record some automation. Delete the assignment by: clicking on the plugin, opening the controls panel, going to the 'Midi Controller mappings' tab and shift clicking on the 'far right edge' (important) of the assignment I want to delete. Nothing more complicated than that.
I'm pretty simple in my use of it though. Make an assignment using midi learn. Record some automation. Delete the assignment by: clicking on the plugin, opening the controls panel, going to the 'Midi Controller mappings' tab and shift clicking on the 'far right edge' (important) of the assignment I want to delete. Nothing more complicated than that.
