Hi,
I’m trying to use a nanoKontrol 2 on Waveform PRO, MacOS. I have set the midi channels of sliders to CC 102 - 109 to make sure they don’t interfere with something else. I could map the controls of an instrument to sliders with Midi Learn, but I can’t record them. You can see on the attached image that the pitch and modulation wheels of my keyboard are recorded, but not the channels. Anyone knows how I could record the midi channels from the nanoKontrol?
Thanks!
Record MIDI channels from nanoKontrol 2
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
From the Nano, what channel are the controls being sent? Any chance those same controls are being filtered on the MIDI channel filter for that track? Some MIDI devices actually send "control information" on another MIDI device, and it could be you've got to record that as well (??).
The other thing is that these are being intercepted/treated as a control surface within Waveform, and as such may not be recorded as "standard track data" as such. What might work is to record the incoming controls as automation, not as track midi data.
The other thing is that these are being intercepted/treated as a control surface within Waveform, and as such may not be recorded as "standard track data" as such. What might work is to record the incoming controls as automation, not as track midi data.
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRer
- Topic Starter
- 4 posts since 6 Mar, 2022
Hi Peter,
First, the nanoKontrol is not set to control surface. I made this error the first time I used the nano, before I figured out it must be disabled for midi control...
I think that the MIDI of the nano is not rooted to another MIDI device. Could be wrong...
Then, if I understand well, there is a channel from which MIDI is sent, which is the channel set for the slider of the nanoKontrol. I did a factory reset, and the first slider is at its default value : channel 0.
And there is another channel where the midi is received by the DAW? I checked on the instrument (Spitfire LABS): it seems that it's channel 11.
Sadly, neither channels 0 and 11 are recorded in Waveform. One thing I couldn't test is if the channel is filtered. How can I check that?
Note that the answer could be easy : I'm new to MIDI recording.
Thanks for the help!
First, the nanoKontrol is not set to control surface. I made this error the first time I used the nano, before I figured out it must be disabled for midi control...
I think that the MIDI of the nano is not rooted to another MIDI device. Could be wrong...Then, if I understand well, there is a channel from which MIDI is sent, which is the channel set for the slider of the nanoKontrol. I did a factory reset, and the first slider is at its default value : channel 0.
And there is another channel where the midi is received by the DAW? I checked on the instrument (Spitfire LABS): it seems that it's channel 11.
Sadly, neither channels 0 and 11 are recorded in Waveform. One thing I couldn't test is if the channel is filtered. How can I check that?
Note that the answer could be easy : I'm new to MIDI recording.
Thanks for the help!
You do not have the required permissions to view the files attached to this post.
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
There are 2 MIDI monitoring tools which can be quite useful - in different contexts.
Waveform has a MIDI monitor, which allows you to see track events within Waveform. Use it as any other VST, and place it as the first VST in the chain on the right. It may NOT show all events as they may be filtered elsewhere, but DOES allow you to see everything that would be hitting your instrument VST. In some instances (like a MIDI arpegiator) you may want to place it between the arpegiator and the VST, so you see the OUTPUT of the arp VST, rather than the keyboard input.
The second is MIDI-Ox. You must shut down Waveform to use it. It has a whole set of tools (Sysex capture and MIDI monitor are the ones I use), that allow you to see EVERYTHING (MIDI) sent from your midi device. Note it MAY be possible to use with Waveform, but in my trials the MIDI would only go to one OR the other, not both.
Waveform has a MIDI monitor, which allows you to see track events within Waveform. Use it as any other VST, and place it as the first VST in the chain on the right. It may NOT show all events as they may be filtered elsewhere, but DOES allow you to see everything that would be hitting your instrument VST. In some instances (like a MIDI arpegiator) you may want to place it between the arpegiator and the VST, so you see the OUTPUT of the arp VST, rather than the keyboard input.
The second is MIDI-Ox. You must shut down Waveform to use it. It has a whole set of tools (Sysex capture and MIDI monitor are the ones I use), that allow you to see EVERYTHING (MIDI) sent from your midi device. Note it MAY be possible to use with Waveform, but in my trials the MIDI would only go to one OR the other, not both.
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRer
- Topic Starter
- 4 posts since 6 Mar, 2022
AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
MIDI-Ox is Windows only, so I tried another app (MIDI monitor). MIDI monitor shows the signals of both the Xkey (C2) and the nano (the two sliders on the left).Code: Select all (#)
13:04:04.049 From Xkey37 Note On 1 C2 119
13:04:04.168 From Xkey37 Aftertouch 1 C2 119
13:04:04.202 From Xkey37 Aftertouch 1 C2 120
13:04:04.218 From Xkey37 Aftertouch 1 C2 121
13:04:04.233 From Xkey37 Aftertouch 1 C2 123
13:04:04.249 From Xkey37 Aftertouch 1 C2 127
13:04:05.868 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 11
13:04:05.919 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 12
13:04:05.956 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 13
13:04:05.984 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 14
13:04:06.004 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 15
13:04:06.022 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 16
13:04:06.034 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 17
13:04:06.048 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 18
13:04:06.060 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 19
13:04:06.078 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 20
13:04:06.085 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 21
13:04:06.096 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 22
13:04:06.109 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 23
13:04:06.123 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 24
13:04:06.138 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 25
13:04:06.153 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 26
13:04:06.182 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 27
13:04:06.187 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 28
13:04:06.211 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 29
13:04:06.241 From nanoKONTROL2 SLIDER/KNOB Control 1 Bank Select 30
13:04:08.804 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 74
13:04:08.823 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 73
13:04:08.844 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 72
13:04:08.867 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 71
13:04:08.888 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 70
13:04:08.921 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 69
13:04:08.921 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 68
13:04:08.939 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 67
13:04:08.954 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 66
13:04:08.978 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 65
13:04:08.995 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 64
13:04:09.023 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 63
13:04:09.026 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 62
13:04:09.049 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 61
13:04:09.091 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 60
13:04:09.139 From nanoKONTROL2 SLIDER/KNOB Control 1 Modulation Wheel (coarse) 59
13:04:09.822 From Xkey37 Aftertouch 1 C2 126
13:04:09.843 From Xkey37 Aftertouch 1 C2 125
13:04:09.858 From Xkey37 Aftertouch 1 C2 119
13:04:09.873 From Xkey37 Aftertouch 1 C2 97
13:04:09.889 From Xkey37 Aftertouch 1 C2 42
13:04:09.902 From Xkey37 Aftertouch 1 C2 0
13:04:09.904 From Xkey37 Note Off 1 C2 0I moved the nano to Channel 2, but the only way I could record from the nano is to set i as input device. If I do this, the keyboard is obviously not recorded...
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
You can actually have multiple inputs to a track... Where you normally select the input device (the dropdown), at the bottom there is an entry for "select the number of input devices" and bump up by one. You can then actually have both MIDI devices at the same time.
Not sure what the end effect will be. Normally INTERNALLY Waveform strips out the MIDI channel number, and then (if needed) you select the MIDI channel again on output (i.e. if sending back to a real external MIDI device). I'm guessing here that with 2 MIDI devices they're all going to show up as though they came from the same device, so you could, say, pitchbend from a different device than you're playing keys on.
Now, for what you WANT, check to see that the channel controllers show up in the clip being recorded. However, depending on HOW you use the controller data may be the issue. Not sure if you can actually use a recorded/continuous controller to tweak knobs on the VST the same way you can as a controller. You probably COULD, on the other hand, use those controls as pressure or wind or modulation IN the VST as a normal input.
As I indicated previously, you may be able to "record automation" of knobs and controls being input from the controller; just not out of "track data events".
Not sure what the end effect will be. Normally INTERNALLY Waveform strips out the MIDI channel number, and then (if needed) you select the MIDI channel again on output (i.e. if sending back to a real external MIDI device). I'm guessing here that with 2 MIDI devices they're all going to show up as though they came from the same device, so you could, say, pitchbend from a different device than you're playing keys on.
Now, for what you WANT, check to see that the channel controllers show up in the clip being recorded. However, depending on HOW you use the controller data may be the issue. Not sure if you can actually use a recorded/continuous controller to tweak knobs on the VST the same way you can as a controller. You probably COULD, on the other hand, use those controls as pressure or wind or modulation IN the VST as a normal input.
As I indicated previously, you may be able to "record automation" of knobs and controls being input from the controller; just not out of "track data events".
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRer
- Topic Starter
- 4 posts since 6 Mar, 2022
Hi Peter,
I gave it a try by adding a second input on the track. I selected two, then I could enable both the Xkey37 and the nanoKontrol. After activating both in recording, I pushed record and magic happened. Both inputs were recorded. Problem solved! Thanks a lot for the help. My piece has much more expression now.
I gave it a try by adding a second input on the track. I selected two, then I could enable both the Xkey37 and the nanoKontrol. After activating both in recording, I pushed record and magic happened. Both inputs were recorded. Problem solved! Thanks a lot for the help. My piece has much more expression now.