Hi all. I’m new to the vst live journey and have just purchased a nano controller 2. I’ve got it all set up with the right mapping and have used the VST Live ‘Learn’ function to map what I need - all good. My issue is that from cold laptop boot, vst live is not triggering the nano, I see from the transport bar that the Nano is transmitting messages, but Live is not reacting in any way. I then close Live, boot Cubase, Cubase sees it perfectly and works without adjustment. I then restart Live and it all works perfectly, again no changes in config. It’s the boot to cubase that seems to kick everything into life. Has anyone got any guidance on this. It feels like Live is not initiating drivers properly, but that Cubase is, and not sure what to do to get Live working without the help of Cubase as in interim step…thanks all…
Hi @martyn.whitlam,
I guess we need some information. This descriptions sounds a bit familiar. But let me ask some more …
. Which version of VST Live are you running?
. Which OS are you working with?
. Or more MIDI devices attached? Are they working?
. Do you close Cubase before you start VST Live?
Thank you,
Michael.
Hi. Thanks for replies. Running latest Windows 11 25h2 Cubase 15.0.20, vst live 3.0.30.157. from boot up, I have to start Cubase 15, create an empty song, it automatically recognizes the nano. I close cubase and then open vst live. When I look at the settings in Cubase, it’s properly set up as a midi controller as nano with both input and outputs sets properly. I’ve replicated this in vst live.
I’ve got inputs as nano, yc series (Yamaha yc73), virtual midi, and loopbe midi.
I’ve found what was causing it as I write this. I’ve firstly deleted all midi inputs. Then, I’ve made sure the nano is number 1, then made sure other midi ports aren’t clashing as the vm auto reinstalled after deleting as also as port 1. Moving this to port 3 fully resolved it. Hope my learnings help others, thanks to the community for offering support …