MIDI Learn Undo?

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hi all. I'm using Waveform Version 11.5.18 (Built: 12 July 2021) (64-bit), Win 12 OS.

My Midi controller & surface controller is the Keylab Essential 49.

On one project only, the surface controllers weren't responding, so I used Midi Learn to map the encoder knobs and sliders. However, the knobs and sliders don't move smoothly, if at all.

I reset the Keyboard, and checked other projects. Everything is working fine.

I deleted all my edits in the project, thinking, removing the edits would remove any Midi Learn data. No go.

So, is there a way to make WF "forget" what I did through Midi Learn? Again, it's on this one track only, and happens to be the only track I really want to work on after a 15 month break from any recording, and I was just learning how to record with midi.

Any help would be appreciated. TIA.

Post

Hmmm... depends on what you intended to do. Personally I haven't used MIDI learn from the front page, but set up custom controllers from within the Settings - Controllers section.

Custom controllers become "system settings" across all projects, not tied to a single project or edit.

1. Create a new custom controller with a new name. Set IT as getting the input from that device. The other one will then be "ignored".
2. Go back to that controller, and the Edit Control Mappings. Delete the ones you don't like.
3. Export settings on the controller. Save it to a file and you CAN make a copy, and edit out the ones you don't like. Go back and import it as a new controller.
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1

Post

Peter Widdicombe wrote: Thu Jan 27, 2022 2:12 amHmmm... depends on what you intended to do.
I'd like to get the controller to work on this one project, as it does for all my other projects.
Peter Widdicombe wrote: Thu Jan 27, 2022 2:12 am 1. Create a new custom controller with a new name. Set IT as getting the input from that device. The other one will then be "ignored".
2. Go back to that controller, and the Edit Control Mappings. Delete the ones you don't like.
3. Export settings on the controller. Save it to a file and you CAN make a copy, and edit out the ones you don't like. Go back and import it as a new controller.
Quote frankly, that seems barely worth the effort, in this instance. I'd essentially be expending the time/effort duplicating what my controller already does. I think it would be easier if I copy/pasted all the midi data from the project I'm working on, and start a new project.

Aside from that, after this long break, nothing is intuitive enough for me to do much of anything, but I did start the custom controller, but when I go to Edit, there's nothing there to edit.

The other odd thing is, I can't move all the sliders with my mouse on this particular project.

I appreciate your input. You helped me with a Traction problem 2 years ago, when Tracktion didn't recognize any midi input devices at all. I was really getting into recording, but Covid came.

Post

Not sure if this is what you are trying to do but I use a Keylab Essential 61 MIDI controller with Waveform 11.5. I use it as a control surface which means I can control faders and pans. The Keylab uses Mackie standard so there is no need to make any custom mappings. In Settings-Control Surfaces, set your MIDI controller to Mackie Control Universal and it should work straight away.

Post

Yeah, it does really depend on your particular controller and desire to customize (and sometimes finding the RIGHT combination on keyboard settings and selection within Waveform). If you FIND one that works, it's easier.

Actually, if you find a close one, can you then add "MIDI learn" to customize it? On the Setup Controllers page itself it appears not to let you either copy one of the standard ones "as a template" for your own, and have to start from scratch.

(i.e. I'd like to use the MCU as a starting point, and add or modify some of the controls - i.e. to use fader 8 as master volume. This I did with a custom controller definition; but the track select and arm I defined don't work "well"... )
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1

Post

No, unfortunately the standard interfaces such as MCU are 'read only' and can't even be copied and amended. I had the same thought and asked Tracktion support. Although not ideal (there are some buttons and controls on my KeyLab that aren't mapped at all) the basic transport controls (stop/play/record/rewind) do work so I'm sticking with the MCU standard for now

Post

Dark Lane wrote: Thu Jan 27, 2022 9:29 am Not sure if this is what you are trying to do but I use a Keylab Essential 61 MIDI controller with Waveform 11.5. I use it as a control surface which means I can control faders and pans.
Yes, this, exactly. The encoders and sliders don't work as expected on ONE project only.

I thought I could fix things by using Midi Learn, and why I asked if there was an "undo" button of some kind. I've since learned the sliders don't respond to the mouse very well either.

Post

Peter Widdicombe wrote: Thu Jan 27, 2022 1:06 pmYeah, it does really depend on your particular controller and desire to customize
At this point, my desire to customize is zero. I just want the transport and surface controllers to work.

My recording abilities were limited to recording my guitar via an interface, because, going back to T4, I couldn't get Tracktion/WF to recognize my midi keyboard. Almost exactly 2 years ago, you helped me solve that problem by telling me how to delete the tracktion.settings file. That was a problem that spanned about TEN years.

Appreciate your input. I'll abandon this one project, and go back to learning how to use WF, and my mixing/mastering skills.

Post Reply

Return to “Tracktion”