If the controller is not defined as a keyboard, you won't be able to select it as an input device. Other than not being able to see what I'm setting, I like the rest of it More than anything else, my hatred for AT5 is the difficulty reading the interface controls. Good to go.Įxcept when it forgets what it learned and has to be retrained. It has to be defined as a keyboard and controls mapped via Control Link will never get thru.
Track setup with the controller as the input device. The 'trick' for Guitar Rig and Amplitube is to have an Inst. A bit of experimentation taught me that GR6 doesn't remember learned MIDI per component, which would be nice, but instead stores per preset. I'm guessing that Studio One may be intercepting the control messages.Īre you saving your S1 project after you establish MIDI learn, or are you just depending on the plugin preset to retain your MIDI learn mapping?īobF wroteSaved project and preset. So I am truly stumped as to how you managed to get as far as you did.
Whenever I activated MIDI learn on any FX plugin, it would just continue to wait for a signal that never got there, even as I was twisting knobs and faders. I tested Guitar Rig 6 in standalone mode and MIDI learn works fine with my controller.Īlso the MIDI learn would work fine on the virtual instrument itself, but it appears as if the MIDI CCs are never reaching the FX insert. But had no luck at all getting MIDI learn to work with any FX plugin, including Guitar Rig 6. Well I tried Guitar Rig 6 as an FX insert on an instrument track. Again, the routing appears to be correct because everything readily learns again. When I come back to the preset a few days later, the previously learned MIDI assignments are gone like they never happened. I verify by changing, then reloading the preset. I go thru the process and save the preset. I think I have routing correct as the initial learning works fine. BobF wroteWin10 Pro, Studio One 6 Pro, X-Touch MINI.
0 kommentar(er)
