No products in the cart.
This is pretty maddening. I’m unsure what the heck is happening but my midi keyboard (novation impulse) works perfectly in Standalone mode, but when I open pro tools its like it doesn’t exist…and GUESS WHAT?? The select a midi device option disappears when you’re not in Standalone mode so theres no recourse. I’m so annoyed right now… My midi keyboard works fine on all the other channels, all the settings are as they always were and used to work fine within pro tools and SD3. I’m away to go and waste time in standalone mode back and forth, closing the session each time (face palm) …sad emoji..
Uh… I guess it’s not a problem due to SD3 Standalone or Pro Tools. It must be a problem with the driver (under Windows 10 you do not have to install a separate driver – it’s just “plug and play”). I also own a Novation Impulse 61 keyboard and I use Cockos Reaper. Normally I do not use anything but Reaper. But if by any chance I open ANY other programme which makes use of MIDI input… if I try to open Reaper again, the keyboard is not recognized. I have to go through a long process of unplugging my Impulse Keyboard, and then going to Reaper’s “Preferences” > “MIDI Devices”, then right click on all the “Impulse” input and output instances and choose “forget device”. Click OK and exit. Rebooting windows is advisable. Then, I connect my Impulse keyboard again. After that, I open Reaper and I have to go back again to “Preferences” > “MIDI Devices”, then right click on all the “Impulse” instances and NOW choose “Enable” for all of the “Impulse” input and output instances. Then click on “Apply” and “OK” and then the keyboard will work fine within Reaper again.
If I only use Reaper with my Impulse keyboard, it works fine every time I start my computer. BUT the moment I use a different programme which makes use of the “Impulse” driver, it won’t work with Reaper again unless I go through the long process I have just described.
Perhaps we should think about complaining to Novation and ask them to fix this up. You say you use Pro Tools. Windows or Mac? If you use it under Windows, we have the same problem.
Its all pretty weird. I never had an issue until I had to reinstall my apollo quad firewire the other day. I’m not sure if I had to delete some preferences or something else, but it has definitely messed with my setup with SD3. I used to be able to use my novation impulse 61 inside SD3 inside Pro tools with zero issues, just a few days ago even. Now the keyboard works perfectly in Standalone mode only. I have everything selected in SD3 that I should. I never noticed until today that you can’t choose a midi device in the midi in menu when you’re not in standalone mode, the button simply doesn’t exist when in slave mode. I might have to do the dreaded reinstall of SD3, hopefully I can do it without reinstalling the libraries.
I’m on a mac running high sierra and the most current pro tools and SD3
I hope TT decides to make the midi input settings able to be changed when inside a DAW in the next version release.
I got my track done, but it hurt a lot… almost threw my computer into the sea lol
In this case, PT is responsible for your midi input and not SD3. This is why there is no midi set up in SD when instantiated as a plug-in. This goes for all plug-ins. I would suggest creating a instrument track with another software instrument and if it is not responding to your keyboard, then you need to check on novations support site in regards to ProTools.
jord
Its all pretty weird. I never had an issue until I had to reinstall my apollo quad firewire the other day. I’m not sure if I had to delete some preferences or something else, but it has definitely messed with my setup with SD3. I used to be able to use my novation impulse 61 inside SD3 inside Pro tools with zero issues, just a few days ago even. Now the keyboard works perfectly in Standalone mode only. I have everything selected in SD3 that I should. I never noticed until today that you can’t choose a midi device in the midi in menu when you’re not in standalone mode, the button simply doesn’t exist when in slave mode. I might have to do the dreaded reinstall of SD3, hopefully I can do it without reinstalling the libraries.
I’m on a mac running high sierra and the most current pro tools and SD3
I hope TT decides to make the midi input settings able to be changed when inside a DAW in the next version release.
I got my track done, but it hurt a lot… almost threw my computer into the sea lol
Is your MIDI controller working with other virtual instruments in Pro Tools. Putting MIDI input settings in a VI AAX plug-in wouldn’t accomplish anything as the I/O is managed by the DAW itself. Which version of Pro Tools are you using?
Have you set “first selected MIDI track” in the Pro Tools preferences Setup > Preferences > MIDI?
What device do you have set for your MIDI input selector (at the very top the track with SD3 inserted on it). Mine is to all.
Also your MIDI output selector (Underneath the MIDI input selector) needs to be set to Superior Drummer.
Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)
No products in the cart.