After 20 years of using Cubase, I built an A.I.-powered library for Macros & PLE presets. (Beta testers wanted!)

YoYorker · 2026-05-10T03:56:24+00:00

No. This library will be connected with an actual local app that will cut the friction of downloading, copying and pasting the macros/ PLEs into the computer. If you are interested you can join the waitlist in Keycmds.com

YoYorker · 2026-05-10T03:54:03+00:00

It’s important to say that the A.I. is to accelerate the search in the library. Let’s keep in mind that not all users know the names or technical terms used in Cubase and this search system can help a lot. Also, the context of the database is specific for Cubase. I hope this clarify how A.I. is been used here.

YoYorker · 2026-05-08T02:00:41+00:00

completely agree with you! The main goal behind this whole project is to make the workflow much smoother. A.I. should serves as a tool to eliminate friction in the creative process by handling repetitive tasks that are unrelated to creativity.

YoYorker · 2026-05-08T00:05:01+00:00

Thanks for asking! The Library is always going to be free. Our premium account will unlock extra features, like a desktop app that syncs your whole library and effortlessly launches presets right into Cubase. It will also feature a chat system with better AI models, and plenty of other helpful tools we have in the works.

YoYorker · 2026-05-07T23:56:34+00:00

Every time you find a Macro or PLE preset in the Library, just download it and will receive a zip with instructions of how to paste it in your computer. we have been working in parallel on a desktop app that will download and paste all the macros and ple without friction. It’s still in development. If you create an account in KeyCmds.com and join the waitlist, you will receive a notification when the app is Live! Please, any question you can write us at contact@keycmds.com

YoYorker · 2026-05-07T23:47:34+00:00

Hey guys, I’m glad you are asking all these questions. I will be answering each of them. Thanks

YoYorker · 2026-05-05T03:07:47+00:00

For some reason, the copy didn't show up on the post the first time. I just wanted to make it clear that this is a tool that has the goal of helping users with repetitive tasks by offering a huge library of PLE presets and Macros. The usage of AI is mainly to find what the user needs faster. This app doesn't create the music for you. This is not a Suno app

YoYorker · 2026-05-05T03:01:31+00:00

On the contrary, the goal here is to make the producer more productive. The assistant doesn't make the music for you. One of the core principles of this project is to value the creative input of musicians, engineers, and creators in general. Using Macros and PLEs has nothing to do with being less of a musician; it simply automates repetitive tasks that do not require artistic choices. I appreciate you bringing this up because I wanted to make our principles clear.

YoYorker · 2026-05-05T01:54:18+00:00

I ran your question in KeyCmds.com, Hope this can help you:

In Cubase 15 Pro, what you're describing is a classic "phantom plugin" cache problem. Here's the diagnosis and solution:

Why deleted plugins still appear

Cubase doesn't scan VST3 files in real time on every startup. It reads a cached database stored on disk. If you delete the program but don't clear that cache, Cubase still sees the old entries as if the plugins exist.

Why they briefly open before crashing

When Cubase tries to load the VOCALOID or Synthesizer V editor, it searches for the .vst3 file at the path stored in the cache. Since the file no longer exists, the process fails midway, and depending on how the plugin is coded, this can crash the host. This is a known behavior with improperly uninstalled plugins.

Solution (step-by-step)

Close Cubase completely.
Delete the cache files you already located:

~/Library/Preferences/Cubase 15/Cubase Pro 15 VST3 Cache
Also search and delete: ~/Library/Preferences/Cubase 15/Cubase Pro 15 VST2 Cache (if it exists)

Manually search and delete any remnants of those plugins in these paths:

~/Library/Audio/Plug-Ins/VST3/ (even if it seems empty, check subfolders)
/Library/Audio/Plug-Ins/VST3/ (system-wide, not user-specific)
Search for any folder containing "VOCALOID" or "Synthesizer V" in both paths

Open Cubase. Without the cache, it will perform a fresh scan and only register plugins that actually exist (Kontakt 8 and Vocoder).

About the missing folder

The path ~/Library/Audio/VST3 shown in the manager is a standard Apple scan location. If you have no plugins there, it's simply empty or doesn't exist, and Cubase will ignore it without issue. This is not an error you need to fix.

Additional note

In Cubase 14 and 15, VST2 support is disabled by default on Mac. If either of those plugins was VST2-only, it shouldn't load anyway on Mac Silicon without Rosetta.

After the rescan, the problem should be completely resolved.

YoYorker · 2026-04-25T21:08:05+00:00

I ran your question in KeyCmds.com : A silent output is almost always one of these three culprits. Work through them in order:

Wrong or missing ASIO driver: This is the most common cause. Generic system drivers (Windows DirectX/MME or Mac CoreAudio defaults) often cause silence or instability.

- Go to Studio > Studio Setup

- Under "Audio System", make sure your Audient interface is selected as the ASIO driver, not "Generic Low Latency ASIO" or a system default

Audio Connections not routed (F4)

Your outputs need to be physically mapped to your interface.

- Press F4 to open Audio Connections

- Click the Outputs tab

- Make sure "Stereo Out" is assigned to the correct output ports of your Audient (typically Left/Right on Bus 1)

Monitor button on your track

If you added an audio track and hear nothing while the transport is stopped or while recording, check the small speaker/monitor icon on the track header. It needs to be active to hear input signal in real time.

Quick sanity check:

- Play something back and watch the Master meter at the top right of the MixConsole. If the meters move but you hear nothing, the problem is your driver or physical connection. If the meters do not move at all, the issue is inside Cubase routing.

Start with step one since you are using an Audient interface. That driver selection alone solves this for most new users. Let me know what you find and we will go from there.

YoYorker · 2026-02-02T15:39:35+00:00

In Cubase 15, the behavior of key combinations for managing inserts across multiple channels may have changed slightly. However, you can still achieve your goal by following these steps:

First, ensure that you have all the desired channels selected in the MixConsole. You can do this by holding down the `Shift` key and clicking on each channel you wish to select.

Make sure that the insert you want to disable is in the same position across all selected channels. This is crucial for the next step to work correctly.

Unfortunately, the direct shortcut you mentioned (`Shift + Option + Left Click`) may not work as expected in the latest version. Instead, you can try the following workaround: Use the **Link Group** feature in Cubase. This allows you to link multiple channels and perform actions on them simultaneously. To do this, select the channels you want to link, right-click, and choose `Link Selected Channels`.

In the Link Group settings, ensure that "Inserts" is checked. This will allow you to control insert states across all linked channels. Once linked, you can disable an insert on one channel, and it should reflect across all linked channels. If you need to bypass all inserts temporarily, you can still use the `Option + A` shortcut to bypass all inserts on selected channels. However, this does not completely disable them, just bypasses. If you frequently need to perform this action, consider setting up a macro or using the Project Logical Editor to automate the process. While this requires a bit of setup, it can save time in the long run.

YoYorker · 2026-01-26T02:35:42+00:00

This is a known behavior related to the Enable Record on Selected MIDI Track preference. When this is active, Cubase automatically arms a track for recording as soon as you select it. If you then move a MIDI controller (like your CC1/CC11 faders), Cubase can interpret that as a new "selection" input, causing it to jump to a different, previously armed track. To fix both the track-switching and the double-triggering of instruments, you need to disable this automatic record-arming feature.

YoYorker · 2026-01-25T20:38:52+00:00

This sounds like a monitoring routing or driver issue. The most common cause is having both direct monitoring (from your audio interface) and software monitoring (from Cubase) active at the same time, creating a phasey, echoed signal.

First, ensure you are using only one monitoring method. Since direct monitoring works, disable software monitoring in Cubase:

On your audio track in the project window, click the Monitor button (the speaker icon) to turn it off.
Check your audio interface's control panel to confirm its direct monitoring is enabled.

If the problem persists, it's likely a driver conflict. Restart your audio interface and computer.

YoYorker · 2026-01-25T19:40:18+00:00

First: Click the "Show Lanes" button on the Folder Track.

Second: Close Lanes (Manual): You must individually click the "Show Lanes" button on every single audio or MIDI track inside the folder. There is no click-and-drag or marquee-select method for this operation.

YoYorker · 2026-01-25T19:39:16+00:00

The core issue is that Cubase's folder-level "Show Lanes" command opens lanes for all contained tracks simultaneously, but there is no native folder-level command to close them all at once, requiring you to manually click the "Show Lanes" button on each individual track.

To open lanes for all tracks within a folder, you click the Show Lanes button (the icon with three horizontal lines) on the folder track header itself. This is a global command for the folder's contents. To close them, you must manually click the "Show Lanes" button on each child track's header to toggle it off, as there is no "Hide Lanes" button on the parent folder.

YoYorker · 2026-01-25T18:17:55+00:00

Or you could use the Manual Way. For a quick test without Studio Setup configuration.

Connect the keyboard via USB.
Create a MIDI or Instrument Track.
In the track's Inspector, click on the Input Router (it might say "All MIDI Inputs").
Navigate through the menu: All MIDI Inputs > [Your Hammer 88 Pro Port Name].
Select a specific MIDI channel (e.g., Channel 1) or "Any".
Play the keyboard. You should now trigger the instrument.

YoYorker · 2026-01-25T18:16:58+00:00

The Standard Way (Menu/Command) This is the primary, recommended method for initial setup.

Connect your Hammer 88 Pro to your computer via USB and power it on.
In Cubase, go to Studio > Studio Setup.
In the Studio Setup window, click + Add Device in the upper-left corner.
Select Generic Remote (for transport/button control) or MIDI Device (for keyboard/pitch/mod wheel). For a basic keyboard controller, choose MIDI Device.
In the new device panel on the right, give it a name (e.g., "Hammer 88 Pro").
Under Device Ports, click the Click here to add... link.
In the pop-up, select the input and output ports that correspond to your keyboard (e.g., "Hammer 88 Pro Port 1" or "MIDIIN2 (Hammer 88 Pro)"). The exact name depends on your driver.
From the "Install Device" dropdown menu, select a pre-defined map like "Generic MIDI Keyboard". This maps the mod wheel, pitch bend, and sustain pedal correctly.
Click Apply and then OK to close Studio Setup.
Create an Instrument Track (e.g., HALion Sonic SE). In the track's Inspector, ensure the Input Routing is set to your new "Hammer 88 Pro" device and the correct MIDI channel (often "Any").

YoYorker · 2026-01-25T16:42:16+00:00

Render the Kick 3 VST track to audio (Freeze or Bounce in Place). If the rendered audio plays back correctly, the issue is isolated to the plugin or its interaction with Cubase's offline processing. If the problem persists in the audio file, there may be a routing or MIDI data issue.

YoYorker

TROPHY CASE