Studio Pro doesn't ship a script for the Novation Launchkey MK4, so I made one. It's free and open source (MIT):

https://github.com/miraer/launchkey-mk4-studio-pro

What it does:

• Transport buttons with their Shift functions (play from loop start, return to zero, autopunch, precount, redo...). The LEDs follow Studio Pro.
• Faders 1-8 and master on the Remote Bank. The buttons under the faders select or arm tracks and light up in the track colours. Shift + Track < > pages through the channels.
• Encoders in all of the Launchkey's DAW modes: Control Link for the focused plugin, mixer volume/pan, sends, and a transport mode (position, zoom, loop, markers, tracks, arranger sections, tempo).
• Pads: clip launcher (2 lanes x 8 scenes, or 16 scenes) or a Mute/Solo page.
• Screen: selected track, parameter names and values, and which channels are on the faders after paging the bank. The Launchkey's own font is ASCII-only, so track names in Cyrillic are drawn by the script.
• The keys and the drum pads keep working as a normal MIDI keyboard.

Install: copy one folder into Studio Pro's "User Devices" folder, restart and add Novation > Launchkey MK4 DAW on the keyboard's DAW ports. Step-by-step instructions and the full control map are in the README.

Tested with Studio Pro 8.1.2 on Windows 11 and a Launchkey 49 MK4. The 25/37/61 use the same protocol and should work too, but I couldn't test them, nor macOS or Studio One 6/7. If you try it, I'd love to hear how it goes - bug reports and pull requests are welcome on GitHub.

Hey everyone, BEEN 48 HOURS WITH THIS PROBLEM

I'm in the middle of mixing an album in Studio One, and suddenly my VST plugins stopped working after I accidentally changed something in the settings.

I was having an issue with Melodyne, so I went into the settings to try to fix/reset something. I honestly don't remember what I clicked, but at one point I noticed that all my VST plugins were showing up in red.

Now Studio One doesn't detect Fresh Air by Slate Digital, and I'm worried about the rest of my plugins.

Everything works perfectly fine in FL Studio. All my VSTs are detected there, and both DAWs use the same plugin folder locations. I haven't installed or updated anything. Studio One was working fine yesterday, and this started immediately after I changed those settings.

I've already checked the VST folder paths, checked the scanning settings, and tried resetting the blacklist, but nothing has fixed it.

Is there a way to force Studio One to rescan all plugins or rebuild its plugin database? Has anyone experienced this after accidentally changing a setting?

I'm in the middle of an album mix, so I really need to fix this without reinstalling all my plugins, losing my settings, or risking my existing sessions.

I'm running Studio 6.0.0.8 One on Windows 10. Any help would be greatly appreciated.

Hi all, I'm fairly new to Studio Pro 8.1, and I'm having an issue where if I manipulate the controls of a plugin during playback, the GUI of the plugin stutters and occasionally glitches out on me. For example, when moving around a band on an EQ, it will be super laggy, and occasionally it will grab other bands and start moving them instead, etc. This happens on stock plugins and 3rd party, I've tried messing with direct monitor, my interface buffer size, dropout protection, plugin nap, high dpi mode, and nothing has fixed the issue. Does anyone else have this problem or know how to fix it?

Interface is a Tascam US-4x4 HR Windows 10 22H2 Computer specs: Ryzen 5 3600 RTX 3080ti 64GB Ram

If you started on Cubase on the Atari ST and switched DAWs since: this converts the old .ARR and .ALL files to DAWproject, which Bitwig (5.0.9+) and Studio One (6.5+) import, with tracks, parts and tempo changes in place. I've tested the import in Cubase; if you try it in Bitwig or Studio One, please tell me how it went. Free, in the browser, nothing uploaded. Link in teh comments. Happy converting!