Command palette for Cubase 15 (MacOS Only) built on MIDI Remote

Cubase
, ,
1

Hi all, I’m the dev of a small free tool I’ve been using daily and wanted to share.

Studio Launcher is a menu-bar command palette for Cubase 15 on macOS 14+. Press Cmd+Shift+P, type, hit Enter. It goes beyond the macOS Help menu search: it reads your key commands and plug-in cache, so you can trigger any key command, run PLE presets and macros, or drop a plug-in into the next free insert slot.

The interesting bit is how it talks to Cubase: it uses a small MIDI Remote script, so it can actually drive Cubase (inserting plug-ins, running PLE presets, etc.) instead of just sending keystrokes.

It’s free, with no account and no analytics: Studio Launcher, a command palette for Cubase on the Mac | DLT.ad

Happy to answer questions about the MIDI Remote side, and feedback or feature ideas are very welcome.

palette-results-dark
palette-results-dark1360×714 48.9 KB

palette-slot-picker-dark
palette-slot-picker-dark1360×1002 51.9 KB

2

In the next version I’m thinking of adding a few things people actually want. If you use Studio Launcher (or tried it), what’s one feature you’d love to see next?

3

Looks like a neat tool.

Hi all, I’m the dev of a small free tool I’ve been using daily and wanted to share.

But I have a hard time with that statement. Babysitting agents doesn’t make one a developer. I know. I have been a developer/engineer for decades, and now I babysit agents. It’s not really the same thing.

Not sure what to call it yet, but “dev” doesn’t feel right. I feel the same way when folks say they “created” something that their agents created. It’s like your manager taking credit for all your work.

That’s not to take away for the coolness of a tool. Just…I’m seeing a lot of “I developed” and “I created” lately, when it’s a lot of prompt iteration.

Also, on the web site, if you don’t create a LOT of guidance for your agent, the language always ends up the same. Same in the apps. It’s not really how humans write. It uses phrases where it should use simple nouns or adjectives, for example. I recently had Copilot/Claude go through and clean that up in the MIDI apps, so it knows how to do it if you point out that the language has an “AI Smell” to it :slight_smile:

Pete
Microsoft

4

Thanks for the note, Pete. Really appreciate the feedback.

Fair point on the wording. English isn’t my first language (I’m Spanish), so I used AI to help with the site copy. Happy to own that, and I’ll clean up anything that still smells like LLM filler.

If you’d rather dig into credentials offline, I can send you my CV privately. No pressure, just if it’s useful. And if you’re up for it, I’d genuinely welcome a DM pointing at which phrases read as AI slop so I can fix them.

Glad the tool itself still looks neat.

5

The easiest thing to do is have your agent do a review of the app user-facing labels and the website.

I started with this prompt for the review

Update phrasing for fields/labels in the Sequencer, MIDI Patchbay, and MIDI Glass apps

Many of the field labels have an “AI smell” to them. They are not the types of labels one would normally use in a human-authored app, which would tend towards a single domain-specific term/noun in most cases. This puts off users who are anti-AI, and it just reads strangely compared to other apps.

We’ve discussed this before so there may be language in your writing guidelines already. Please summarize your findings in a table for each app, and propose new clear and succinct language replacements.

If any of this is unclear, ask first. If you have general questions about what some common thing should be titled, also please ask.

It found this rule it had missed:

The rule exists: labels are nouns or known app terms, sentence case, never phrases. Now inventorying the current UI strings in all three apps.

In case it helps your agent, here’s the markdown file it produced with all the candidate problem labels, (these apps are all localizable so the strings are all in resource tables), the original labels and the candidate replacements. I tweaked some things it missed.

label-rename-proposal.zip (11.7 KB)

Once you start seeing the Claude-isms (or GPT, or whatever you are using) in the wording, you’ll really start noticing them everywhere, likely in Spanish as well. :slight_smile:

Pete
Microsoft

6

Thanks Pete, that’s really useful. I’ll run a pass like that on the app labels and the site this week. Appreciate you sharing the prompt and the file.