Nuendo 15.0.30 - Bug Collection Thread - June 2026 | OPEN for posting

[TimoWildenhain]

Dear all,

Thank you for your engagement in reporting issues! I’m opening this thread in order to gain feedback related to the latest update, which is Nuendo 15.0.30.

In order to make it manageable for us, I kindly ask you to consider the following procedure. It makes it way more likely that we can actually fix those issues with the next maintenance update.

So, in this thread, please follow this procedure

1. only post issues, that have been CONFIRMED by other users in separate threads.
2. please mention if a bug has newly appeared in the current update or stems from older versions.
3. please only 1 post per issue, with a description of what it is and how it can be reproduced
4. please don’t start discussing bugs or reports in this thread
5. in case you find a bug report very important, please use the “heart” symbol for voting

We’re going to collect these issues now for 4 weeks and will then have an interim review. We won’t be able to comment on everything, but we will provide responses regarding the status of reported issues, insofar as resources and information allow.

Thank you again,

Timo

[GreyboxAudio]

Dear Timo,

I have already submitted a Support Ticket #768906 regarding functional & visual issues with the surround panner. It’s been 3 weeks and I’m still stuck with L1 support. I also opened a thread recently but so far no one has chimed in to confirm the issue Dolby Atmos Send-Pan broken since N14?

In a Dolby Atmos project in N13 I can click+drag on the panner for any send and it will instantly move the position. The pop-out panner closes as soon as I let go.
In N14&N15 click+drag will only pop out the small panning window, then I need to click+drag again to move the position and then I need to click outside of the window to close it. I can reproduce the behaviour on macOS (apple silicon), Windows x64 & Windows arm64.

I’m aware that I’m disobeying Rule No1, but I’m pretty confident that this is a bug and with my current support experience I’m not willing to wait another 2 weeks for someone to hopefully confirm the issue.

Best

Robert

[mart]

BUG / Feature needing improvement : IMPORT TRACKS FROM PROEJCT

-- issue with feature since it first appeared in the software

-- confirmed by many users on the forum

'Import Tracks from Project' loses input assignments

When I “Import Tracks from Project” I lose the input assignments of the imported tracks, even when importing from projects that used the same template etc. What’s going on here? Surely it should retain the inputs!

Import Tracks from Project BROKEN Nuendo 13 (and Cubase)

This part of Nuendo is a constant source of dissatisfaction: …this is how it should be in late 2024:

"Import Tracks From Project" is buggy

First this problem: Now your observation. Steinberg should really pay attention to this feature. Things like the one you described above are easy to overlook, and then you have the problem. This is simply not supposed to happen with professional software! (Does no one check this before releasing such a function? )

Issue - when importing tracks from another project any Input and Output hardware assignments are lost and set to default.

In pro studio software this is a huge issue - example recording a 20 mic strings setup or 24 input band live tracking session - going from the first song and going to the next song in the session slows the session down because if I use Import Tracks from Project I have to set all hardware inputs and outputs manually again

[henrique_staino]

Hi Timo, first of all thank you and congratulations for the comprehensive list of fixes in 15.0.30! And also for keeping this initiative of official bug collecting going on. This is very significant, so thank you sincerely.

Now, on to the bug:

The problem is that ARA extensions cause clip gain lines to be applied twice - once before the extension (you can see the gain changes in Spectralayers spectrogram, for example) - and once again before being monitored. Also, this first stage of gain is then rendered into the file when you make the extension permanent, while the gain line remains active after the deal.

What is expected is for the gain line to behave as other clip gains/event volumes do: affecting the signal only once and being after the extension in the signal chain. They should never be rendered with extensions.

This has been confirmed by other users in separate threads and It has been present at least since N11 as we can see by the posts below:

ARA2 Extension clip gain-problems

Hi! I’m having issues with Extensions on Nuendo version 11.0.30 Build 419. So far I have used Melodyne and Vocalign Project in my session. When I apply either one to a clip and continue to edit the clip (create crossfade for example), clip’s gain changes dramatically: either it boosts up, or turns down so much, that I have to re-adjust the clip’s gain. When i’m done and I edit other clips in the same audio-track, it affects the gain of the clip where I have the extension. This clearly is a bug.…

ARA2 Bug, clip gain calculated twice when using crossfade

I already posted this a while ago, did not Tag it, do not know ho to add Tags to old Posts, so once again as I now know it is reproducable on several machines. Repro: -Use Clip gain on Audio Part, for example -10 dB -cut Part in half -use spectral Layers on second part (and actually edit with it) -create crossfade between the parts RESULT: ARA part is now playing with -20dB clip gain. The clip gain is calculated twice when crossfading into an ARA-Part. Cheers, Dirx

Event volume envelope Renders With SL/"Make Extension Permanent" but still shows Line Gain

(Cubase 14 because my 15 trial ran out) Hi, I just realized that if you have Event Line Gain, open an instance of Spectralayers, and then ‘Make Extension Permanent’ it seems to render the event line gain, but still shows the event line gain but I believe it is actually inactive, as if you bounce the event it doesn’t double down on the gain process. here you see Event Line Gain → ARA2 SL → Make Extension Permanent → Event Bounce → Then I edit undo the steps: I was hoping to be able to o…

15.0.30 is out

I just tested the doubled clip gain as it happened on my side before, and it is still a problem. In my example if I crossfade a non Ara Clip with an Ara Clip, the clip gain of the ARA Clip is applied twice. Remove Fade, normal clip gain, crossfade again, double clipgain again.

Now to possibly help troubleshooting, I’d like to note that in N15.0.30 the behavior regarding ARA extensions and gain/volume seem to have changed, even though there is nothing about it in the release notes.

See, parallel to the doubled clip gain issue, we also had issues with huge POPs when the boundaries of events with active extensions were crossed, and in the last testing I’ve done, this didn’t seem to happen.

Also, I’ve noticed that in at least one session, if there were no other extensions active in other clips, the “double gain” problem did not occur! Spectralayers didn’t show the gain changes in it’s spectrogram, and I could’n hear them either. But this also meant that while the extension was active NO clip gain could be heard, as if the clip gain line was disabled completely (though this is already much better than having it doubled IMO).

As soon as there were other events with active extensions in the session, the problem came back, and not only that, but at least once the maximum drawn gain value was applied to the whole event, as if the clip gain line was simply a flat boost throughout it (which is not what normally happens).

If you need more details, tests, or anything else I can do to help, please feel free to reach out. I’d be more than willing to help solve this.

Thanks again and I hope this issue can finally be fixed.

EDIT TO ADD:

I was just using Spectralayers normally in a session and suddenly in one of the events I applied the extension, the event volume, (not a drawn gain line) was doubled. With a twist that this only happened in monitoring, it was not doubled in the processed clip with either “make permanent” or bounce. I believe this is a first. And also a bit disconcerting to use. My tests show me the whole deal is very inconsistent and unpredictable! I think I’ll go back to N14 for the time being. There the bugs at least are familiar already.

EDIT TO ADD 2: well now this has ported back to N14 when I opened the project there. Tragedy!

[Electriks]

Issue: Automation Parameter box in Project Window only shows last 5 parameters.

Repro: Click on the Automation Parameter selection box on a track in the Project Window. It always used to show a long list of automated parameters on the selected track so you could easily/instantly select what you want to adjust, and in N15.0.30 it still only shows five, regardless of whether you have Last Touched enabled or disabled. Compared to previous versions it’s extremely time-consuming to find and select an automated parameter when you have more than five.

Link to thread with many confirmations: C15: When selecting automation in the Project Window, I can’t see which ones are being used - Cubase - Steinberg Forums

The fix: When “Last Touched” is disabled in Preferences, restore the former behavior of seeing the first 15 automated parameters in the Select Parameter box for automation in track headers. Or, even better, always show the large list of used automation parameters like it used to, underneath the 5 last touched, if Last Touched is enabled.

[Tajika]

The “track focus behaviour issue in mixconsole” as described in this thread is still unresolved. It was reproduced by other users and Steinberg support in 2024, however it’s still unresolved in Nuendo 15.0.30.

It’s a nasty bug when working with keycommands and midi controllers in mixconsole.

The track focus behaviour is different between project view and mixconsole

The track focus behaviour is different between project view and mixconsole and misleading in mixconsole 1 create new project 2 create 2 audio tracks 3 in project view select the first track 4 in project view click the second’s track mute button → track focus stays on the first track 5 now hit the key command for mute (m) → the first track is muted - which makes sense, since trackfocus is still on the first track now do the same thing in mixconsole: 1 in mixconsole select first track 2 in…

[Tajika]

There’s one DOP related bug left, as described towards the end of this thread: https://forums.steinberg.net/t/dop-processes-multiplied-and-never-end/1006202/33

I reported it in 2024 and support confirmed the issue. It’s still there in Nuendo 15.0.30.

[Joe-TimelineAudio]

Divide Track List Selection sticks - Nuendo keeps track or event selected even when focus is lost and selection is made on the other Tracklist side. I don’t think this behaviour is helpful and as far as I’ve seen on the forum most agree with the consensus. Another example listed below is not knowing which one is in focus when both are selected in this way.

** updating for rules - been around at least for the last few versions of Nuendo - 12 to 15

Divide Track list - bugs

Hi, When using Divide Track List and having selected clips in both the upper and lower sections, there’s no visual indication of which section is currently focused. This makes it unclear which clips will be affected by editing actions. The Select None function only works in the currently focused section. (This might not be a bug, but as a user, when I choose “Select None”, I expect nothing to be selected in either section.) While using Divide Track List and trying to change the color of…

Hi,

1. When using Divide Track List and having selected clips in both the upper and lower sections, there’s no visual indication of which section is currently focused. This makes it unclear which clips will be affected by editing actions.

2. The Select None function only works in the currently focused section. (This might not be a bug, but as a user, when I choose “Select None”, I expect nothing to be selected in either section.)

3. While using Divide Track List and trying to change the color of clips, the selected clips in both the upper and lower sections change color. However, other functions (like nudge edit, delete, change clip volume, etc.) only affect elements in the last focused section.This is confusing and inconsistent.

Martin

[italian_noise]

This is confirmed by others, Nuendo 15.0.30, 15.0.2 for Win10.

Project Logical Editor, can not toggle (open/close) on a group folder that is in another folder

BUG:N15 PLE, can not toggle (open/close) on a group folder that is in another folder

Summary: Project Logical Editor, can not toggle (open/close) on a group folder that is in another folder: Result: The PLE will not toggle =sub folder as expected, if I create a PLE that targets ~MAIN, that works Setup: I have a very simple project that has 2 Folder tracks enabled as group tracks ~MAIN =sub Audio 01 PLE Command: Target Filters: container type equals Folder and Name equals =sub Event Transform Options: Track Operation Folder Toggle Transform Environment: Nuendo 15…

[TimoWildenhain]

Hi everyone,

Thank you for posting issues found with 15.0.30 - much appreciated.

We’d like to evaluate and fix as many issues as possible, so may I kindly remind

on the 5 rules stated at the beginning of this thread. Only if the information is

available in this format will we be able to look into this issue within the limits of our resources.

Many thanks for your cooperation!

Kind Regards,

Timo

[tonbuero21]

Nuendo 15.0.30 crashes while finishing Audio Mixdown/Quick Loudness Analysis.
As discussed in this thread Nuendo 15 crashes on audio export

The export process starts and one can see the timecode running. Near 100% it stops and nothing happens (spinning beachball). I can still move the windows around, but the cancel button and everything else is unresponsive. Then have to force quit.
Unfortunately the muting of the videotrack (as suggested in the thread) does not solve the problem for me.