• Hi and welcome to the Studio One & Studio Pro User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!

Midi Learn Inserts and Send FX Busses in Studio Pro 8.x

N

NoBadMojo

New member
I have a confusing problem. I really enjoy Studio Pro but for some reason I can not midi learn FX plugins in inserts and busses and such. I;m just getting back to Studio One after an absence. I don't have this issue in Bitwig...I just dump an insert on a track and midi learn away. This does not work in Studio One. I remember I had to create a second track way back then to midi assign Amplitube 5 to a VST guitar and reroute things. Is that just a function of Amplitube or all FX vst's? I can midi assign Ujam instruments but not UJam Finisher effects vst's. I cant just use the T6 as a straight up generic midi because Nektar buries their whack into everything

I am hoping the problem is not inherent to Studio One. I am using a Nektar T6 keyboard..Their studio one script hijacks the Control Link and blocks it from my use and takes away the ability to use the FX vst's midi learn...or? If that is the problem I will just buy a new keyboard..If it is the way Studio One routes things and handles midi I am back to Bitwig I guess. I don't want to throw money at a new keyboard and have the same issues

Any help pls? Thx.
 
Do you have Nektarine installed? That may be hijacking the Midi Learn process - though I have a T6 and Nektarine on my sitting-room setup and I haven't noticed any issues with Midi Learn. However, it's not a function I use much. I'll have a play later and see if I can add anything useful!

Edit: you can of course delete the T6 and then re-add it as a generic keyboard/controller. That will remove the specific Nektar scripts that may interrupt things. However, Studio One/Pro FX busses don't accept Midi input routing in the same way instrument VSTs do, so I think you may be unlucky in trying to reproduce the Bitwig behaviour.
 
Last edited:
Hey Tim thx for the response. I think I have this all figured out. I tried a couple times to use the T6 in internal mode and to also set it up as a generic midi keyboard, but the Nektar script is really baked into the cake and both were a fail. I think you are right about how the Studio Pro routes midi input with inserts and sends compared to other DAW's

I;ve been fighting this keyboard for a while now, but have found a solution. I have a little midi-usb box coming today to plug the expression pedal and sustain pedal into because those were misbehaving plugged into the T6. I have setup a custom page in my Launchpad x to midi learn buttons and such because it isn't possible to convert the pads to midi cc in the T6 and that is working with inserts ..this should take care of things....I hope
 
Deleting the T6 and adding it as a generic keyboard/controller should remove any Nektar scripts (but you can do that manually too). Google AI may help you set up your workaround, but it's probably worth having a go with Nektarine as you can set up any number of FX chains and control maps in that software.
 
Aye I thought that too. Ran into all kinds of issues just trying to make it generic..after clearing every instance of Nektar/Panorama/T6 in the system. That was all over my hard drive. I think using Windows did not help either and AI mostly gave me wrong info and sent me down rabbit holes. I also had a Nektar LX25mk3 and that created all kinds of conflicts so I sent it back. I like the T6...I just don't think the Nektar script was a good idea..it locks you in to working how they think you should work and AI and I and Nektar support could not make it work right as a generic. if this doesn't work I;ll be looking for a new keyboard..The T6 is flawless in Bitwig, but I like using Studio Pro better
 
That’s a shame. I do like the T6 and find that it works well within Studio Pro for my purposes. I use a Nektar Aruba too, and together they’re excellent - and the Aruba can pick up some of the control mapping from the CS-12, as I understand it, though I haven’t pursued that. I had the Impact LX61+ and I managed to get that working with the NKS update meant for the Mk3 which did make it more useful, but the keyboard itself was cheap and nasty compared to the T6. It’s worth looking into using Nektarine as well - that is phenomenally powerful once you get your head round it!

If you do decide to move on from the T6, I’d look at the Arturia Keylab 61 Mk3 as probably the most capable replacement.
 
I agree, It's a quality under the radar board. I just don't like being locked in to the Studio One script like that and not be presented with an easy option to go generic. I took the Nektarine out for a brief dance...it does a lot to go along with the learning curve..I;m trying to spend my time making music rather than trying to fix things. There aren't many keyboards out there w. aftertouch and expression pedal ports to choose from. If this latest thing doesn't work out for me, I;m thinking about the Nektar gxp61 because I wouldn't be hosed by their script and it is really inexpensive. thx for your help
 
Nektar is one of the few hardware manufacturers that PreSonus/Fender have allowed into the script system to properly integrate their kit. From your original post, I'm pretty sure that the problem you're running into is a Studio Pro issue, not a Nektar issue. The setting up a separate track method is a recognised way around the problem. The T6 hasn't got the most intuitive display and menu system, but I personally think it's a lot better at controlling Studio Pro than any other brand. I do think it's worth persevering with - the GXP is very basic by comparison. But whatever gets you to the place you want to be! Good luck!
 
aye, in my case I think it is both a Nektar issue and an SP issue, maybe with a midi issue and windows issue thrown in as well :)

I do think it is dumb that Nektar only allows you to play notes with the pads. Other devices make it easy to customize pads and turn them into on/off's. But the hardware is great for the money and we cant have everything we want in a keyboard.

yes, I;ve been using the double track thing around the Studio One routing (Stratus guitar and Amplitube 5). I have lots of stuff like Amplitube..it's a very awkward/cumbersome way to do things.. Studio Pro seems antiquated with the routing, but I think other DAW's still operate that way..would be real hard to fix I guess
 
You must log in or register to reply here.
Back
Top