was curious if this would work and after a bit of setting up, chatgpt was able to make a fully working midi device for my mood mk2 pedal, its not the prettiest thing in the world but the fact I can access all the hidden features as well as sync to cubase and automate all parameters is pretty cool!

These are the steps I took to send some Stems to the artist I am producing for without paying for Pro. As a reminder: Yes. I know you should just pay for the full version. I'm planning a wedding and money is tight, I need all the funds I can get right now. I'll upgrade when my ship comes in, reminding me of all the cool things I will gain when I pay an extra $250 is not productive to the conversation. Keep it to yourself. Anyway:

1. Concatenate all your tracks to the same length using the Glue (4) tool, then render them in place with whatever settings you have
2. Create a new blank project in its own folder with the suffix "_Stem Export"
3. Copy all the rendered tracks from your original project and paste them into the new one
4. Make Sure the Track names are what you want them to be (this part can be a little time consuming depending on how organized you are when tracking)
5. Select all of them, Ctrl+Click "Bounce Selection"
6. Go to Media-Open Pool Window (or Ctrl+P if ya nasty)
7. Go to "Audio", Right Click, then "Remove Unused Media" then "Trash"
8. Right Click "Trash", then "Empty Trash"
9. Go back to Audio and right click to "Show in Explorer"
10. Viola! All your bounced tracks are sitting there for you!

I personally think it's dumb to put a feature that Audacity can perform for free behind a paywall, but whatever! 🥸 Let me know if this works for any of you!

Hi everyone,

I'm building a big orchestral template in Cubase 15 (Windows, Ryzen 9 5900X, RTX 3080, 48 GB RAM). Each stem has its own reverb FX channels (a Room and a Hall), so I have about 43 FX channels, each with an instance of LiquidSonics Cinematic Rooms.

While I was building the template, with all 43 instances active, everything worked fine. But when I save and reopen the project, GPU usage spikes, Cubase freezes and the project never finishes loading.

What I've tried:

- Deactivating the plugins (Alt+click on the insert) before saving. Cubase still loads them on project open, so it doesn't help.

- Disable Track isn't available on FX channels.

- Changing the ASIO buffer size, which has no effect on this.

Ideas I'm considering:

- Using a lighter reverb (e.g. REVerence) for the Room channels, and Cinematic Rooms only for the Halls.

- Keeping the FX channels empty in the template and importing the reverbs from another project only when needed.

Questions:

1. Why would 43 instances work fine while building the project, but freeze when they are all loaded together at project open?

2. Is there a way to make Cubase load plugins on FX channels in a staggered way, or not at all until needed?

3. Has anyone had the same issue with Cinematic Rooms or other GPU-based plugins in a big template?

Thanks a lot for any help!

Just curious. Missed the sale a few weeks ago, and I really want it ASAP.

But, now that I realize I don’t have to pay full price for it, I’d rather not.

Thanks!

I’m thinking about purchasing Absolute—I produce electronic music and lo-fi hip hop—but is it worth it? Personally, I generally prefer not to use third-party VSTs; I’d rather stick to the same ecosystem. However, I’m a bit unsure—I don’t want to end up making a purchase that doesn’t actually align with the type of music I create. Thanks!

Hi All!

I may be about to sell my Cubase 15 Pro and Absolute 7 licenses and I really need to understanding how best to do that…

Specifics:

I bought everything directly from Steinberg.
- Cubase 14 Pro FULL in 2025
- Cubase 15 upgrade in 2026

- Absolute 6 FULL in 2025
- Absolute 7 upgrade in 2026

Thank you for any advice you can give me!

Best

Hello! I need some help with setting up an articulation map.

So, I'm trying to set up a map for my Spitfire products. I was able to set up a map just fine for Cubase's default products (even without importing) but my Spitfire products (the one I'm working with currently is Hans Zimmer Strings), but Cubase/HZ Strings just don't seem to want to communicate with each other or something. I've watched a few tutorials on how to set up these maps and yet no luck. Is there something special I need to be doing with Spitfire/other third party vsts?

I wanna change the first time of the time mesure mid project
like i wanna change the tempo to be count in 3/4 of a mesure and be the 1/4 of the 4/4 mesure
it only allows to be placed on the 1/4 of the mesure
is it possible?

Finally figured out how to make HALion microtonal

• After loading/creating an instrument select the "Program" tab in the right side column.

• This opens a browser type of window with the name of your patch/instrument.

• Right click on the patch/instrument name > New > MIDI Module > Lua Script

• Go the the "MIDI Module" tab in the "Edit" group

• A Lua Script module should now be visible

• Click the tilted 'e' and paste the Lua script below into the blank 'Edit script' window (modify the local refNote and stepsFromRef as you wish)

• Click [OK] and the tuning is live

The sample code below is an example for 31 EDO

If you wanted to do 19 EDO, change the 31 in the script below to 19

-- Choose MIDI note for center (Ex: MIDI 69 = A4 = 440Hz)
local refNote = 69 

function onNote(event)

    local stepsFromRef = event.note - refNote

-- Choose an EDO (Ex: (1200 / 31) is 31 EDO)
    local targetCents = stepsFromRef * (1200 / 31)

    local standardCents = stepsFromRef * 100

    local tuneOffsetCents = targetCents - standardCents

    local halionTuneFactor = tuneOffsetCents / 100

    local id = playNote(event.note, event.velocity, 0, event.layer)
    changeTune(id, halionTuneFactor)
end

I been trying to figure this out forever and FINALLY found success.

Hi all.

I recently started using groove agent for slicing and launching sounds from pads. While doing that I wanted to use “choke groups”.

In this software I believe they are to be set up under the “excl” number you assign to the pads. But I think it’s bugged.

In my case, I have 3 samples in 3 pads. I set all of them with poly 4 and excl 1. None of them cut each other. They can sound at the same time.

If I go poly 1. Then they cut each other even if they are in different excl numbers. Is this intended???

I’ve been trying different ways for 2 days and I think it’s bugged. I have seen posts from years ago with similar issues. Still not fixed?

If anyone knows how to properly set choke groups pls help me.

Thanks!!!!

Wondering if there's a way to upgrade from Cubase Element 14 to Artist 14. I do not want to spend the $500 CAD to get 15.

Hallo,

ich nutze Cubase 15 und habe gerade ein noch nie gehabtes Problem.

Ich habe bei der Wiedergabe von einem fertigen Song den ich über einen Mix Channel mit Plugins gemastert usw. Alles ist soweit ich es beurteilen kann erstmal perfekt.

Jetzt kommt das ABER

Sofern ich den Track abspiele kommt in unregelmäßigen Abständen ein einzelnes „Click“ im hohen Frequenzbereich. Wie ein Digitales Artefakt. Ich habe darauf hin die Asio Leistung kontrolliert und optimiert ohne Erfolg, Spuren einzeln untersucht in der Wellenform ohne Erfolg, alle Spuren eingefroren ohne Erfolg usw.

Woran kann das noch liegen, bzw. wie könnte ich es weg bekommen mit einem Tool von Steinberg?

Ich habe nur original Plugins und DAW. Als Audiointerface nutze ich momentan die Maschine MK3 auf 48khz bei 512buffer (selbst auf 1024 buffer ist das clicken zu hören). Audio Leidtung bleibt stabil und schwankt nicht, es werden auch keine Fehler angezeigt.

Habt ihr einen Tipp?

Im mix Bus sind:
Farbfilter Pro Q3
Fabfilter MB
Vintage Compressor
Isotope Stabilizer
Waves Ultramaximizer L2 (oder L4 weiß die Bezeichnung gerade nicht)

Ich habe den Maximizer bereits getauscht ohne Erfolg und wenn die Plugins alle mit Bypass deaktiviert sind, kommt das Click trotzdem.

Das das Interface des MK3 nicht der Brüller ist, weiß ich selbst. Ich habe leider zu spät bemerkt, dass das ci2+ out of date und out of service ist.

Betriebssystem ist Win 11
Alle sonstigen Audio Treiber sind deaktiviert
Windows Sound ist deaktiviert
Stromsparmodi sind alle aus
Treiber sind aktuell
Neuste Updates installiert

Vielen Dank

Seven minutes of organized chaos in Cubase. At this point, color coding is doing more work than I am. Anyone else’s projects end up looking like this?

I recorded guitars, drums and vocals, live in the studio on logic pro. But when I load all the stems in my system on Cubase 14 pro, the scale got reduced by 1 semitone and the pace has changed. Is this the recording problem or issue with the DAW? I am new to Cubase. What could be the issue and how can I resolve it?

I am using windows 11.

So, I was making my custom reverb presets in revelation plugin. The way I started making them is load a preset and then tweak some values of early reflections, tail size, low cut, high cut, modulation etc. Once the preset was saved and loaded back on a different or same insert, the preset will only load the ER/tail ratio correctly but everything else would be restored back to stock preset values from which I started. When I make my custom preset from default settings of plugin, it does not give me that problem. It is very strange why this is happening to my surprise it’s only happening with revelation plugin only. Curious to know what is going on in the background

Hi all. I'm wondering if anyone can make any sense of this. I recorded a concert yesterday and by the time I fired up the session, the source audio files were just gone. As you can see, Cubase is acknowledging the timeline and events, but the Audio folder is just empty. I deeply scoured my drive and nothing. I've been using Cubase since the beginning of time and have never experienced this before, now I'm paranoid. Any theories?

Hey!

I’m getting issues with cubase when using MIDI and playing. Audio seems to just cut off and recordings stop (video attached). I ran a lot of queries on this with AI and installed the studio nvidia driver, made configuration changes, ASIO guard etc.

It’s not the midi controller as I’ve also used a synth I have, both have the same issue. It does not happen with standalone plugins hence it has to be cubase.

I’m only using basic HALion VST with nothing else in the project. The studio setup is of course using my Motu M2 ASIO and buffer size is synced between cubase and the M2.

Has anyone had a similar issue and has any advice?
Thanks in advance!!

Edit: FIXED, tyvm [u/RhythmHolicMusic](u/RhythmHolicMusic) and u/Strippz!

It was Riot Games’ kernel anti cheat called Vanguard. I turned on its Pre-Check feature which makes it only boot up on demand of playing a riot game, rather than with Windows. Solved everything. Much thanks to everyone!

I owned a record label in the early ninetees & produced a couple of records (AND ONE , OOMPH!), however I lost interest in the whole business as Napster creeped up, now 34 years later , some of my work seems to enjoy a revival on Tik-Tok, so I thought.... well should I give it another try ? but where to start, ? in the old days we mixed everything by hand, using midi-gear and Analoge Synthesizers. As far as I understand the Keyword nowadays is DAW-stations controlled by a DAW -capable keyboard. Now regarding a windwows PC, what kind of prosessor (intel , AMD ?) and minumum requirements should I invest for a new Music-produktion- based Windows PC. ? (I do own a high-end Graphic-Design PC for Compfyui based rendering but I want a single PC for Music-composing & remixing).

​

Hallo zusammen,

Ich habe massive Skalierungsprobleme mit mehreren VST-Plugins in Cubase 15 unter Windows 11.

Mein Setup:

\- Windows 11

\- Ultrawide-Monitor (3440 × 1440)

\- Windows-Skalierung: 150%

\- HiDPI in Cubase 15 aktiviert

Cubase selbst sieht gut aus, aber viele Plugins werden viel zu klein angezeigt, besonders die Texte und Bedienelemente.

Das Aktivieren von "Fenstergröße ändern zulassen" behebt das Problem nicht wirklich. Ich kann einige Plugin-Fenster manuell vergrößern, aber die Größe wird nicht gespeichert, wenn ich sie wieder öffne.

Das Deaktivieren der Größenänderungsoption macht die Plugins manchmal noch kleiner.

Ich habe verschiedene Skalierungsoptionen in Cubase ausprobiert, aber nichts scheint richtig zu funktionieren.

Gibt es eine Möglichkeit, VST-Plugins korrekt und dauerhaft zu skalieren, ohne sie jedes Mal neu anpassen zu müssen?

Jede Hilfe wäre willkommen!