Thank you all for your extraordinary engagement and for following the rules in this thread. Our team has already started looking into some of the issues that you have reported. The next step involves assessing the feasibility of implementation in relation to the availability of resources. It goes without saying that we cannot fix all issues at once.
To focus on the issues reported so far, I’m temporarily closing this thread. Once the analysis is complete, I’ll post some of the results here. After that, this thread will be reopened. In the meantime, we’re of course happy to continue the discussion in other threads.
All the best,
Timo
Dear all,
Thank you again for your engagement. I’m opening this thread in order to gain a better overview on early feedback related to Nuendo 15 and possible issues. In order to make it manageable for us, I kindly ask you to accept 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
only post issues, that have been CONFIRMED by other users in separate threads.
please only 1 post per issue, with a description of what it is and how it can be reproduced
please don’t start discussing bugs or reports in this thread
in case you find a bug report very important, please make use of the little “heart” symbol and vote for it, this will help prioritizing
We’re going to collect these issues now for 2 weeks and will then have an interim review. We won’t be able to comment on everything though as the analysis will take some time. Afterwards, we will continue with this approach.
This first, ongoing initiative should also be understood as a response to the recent criticism we received for insufficient communication. I would like to improve this clearly, but need your support.
When using transpose/time-stretch/warp in the project manager with the elastique algorithm, sometimes pops or crackles will play back in the audio. If this clip is then rendered in place the pops will be present in the render. This has been reported for a very long time in Cubase & Nuendo and is still present in N15.
NB: I am happy to create a fresh video demonstrating this bug in N15 if that is useful, or demonstrate it on a video call…whatever you need, I’d love to squash this one!
Repro steps:
Insert audio event on timeline
Set Algorithm to any Elastique Pro - Time
Timestretch using tool, or change transpose/finetune value
Begin playback from just before event - pop/glitch may be present, if not then change stretch/tranpose value and repeat
If pop/glitch can be heard, use Render in Place on event
Can’t drag in region from mediabay into timeline anymore.
Steps to repo:
Open up mediabay and an session timeline
select specific region range within the file in media bay
normally I would drag in the file and I would get just that region on the timeline (as well as handles for the rest of the file) - Now it doesn’t work at all and just copies the whole file over without the specific region.
Offline process : so long !! buggs one the graph of plugins as FabFilter taking full screen and impossible to have on little gaphic presentation. And so much ressources than v14 … please correct it !
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 it 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.
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.
When automating parameters in N15 with activated “Fill Loop” option, Nuendo does not write the parameters exactly into the loop, but creates small ramps at the beginning and end of the loop. This leads to audible EQ sweeps for example. This means you can’t have immediate parameter-changes on one track and you need to checkerboard events over multiple tracks if you don’t want to correct every single automation point by hand.
I have en issue with unreliable Midi Remote integration, multiple greyed out instances of controllers showing up. Was hoping it would be solved in N15, but not yet.
When I activate edit-in place on an Instrument-track, the right pan-handle of the panning control becomes cut off, it´s accessible, but still this seems to be a bug.
Alt-tab handling in Windows and inconsistent window design
(@TimoWildenhain Is it worth making this entire thread a pinned sticky at the top for maximum visibility? I noticed it had dropped off the front page)
Nuendo requires 2 alt-tabs to switch away to another program if an overlay window is present, even though that window doesn’t appear in the Task Switcher:
To summarise:
When an overlay window is present (and focused) it requires 2 alt-tabs to switch away, even though it only presents 1 window to the Task Switcher.
When an overlay window is present but the project manager is focused then it takes 1x alt-tab to switch away, but when alt-tabbing back the overlay window retakes focus so then it takes another 2 alt-tabs to switch away again.
I think if an overlay is not being presented to Windows as its own window, then it should not be able to interfere with the alt-tab switching logic as this is quite counterintuitive (not to mention frustrating when you’re trying to work quickly!)
The second issue is that the way Nuendo presents overlays vs independent windows (can be alt-tabbed) is inconsistent.
For example:
Syncstation Status & OSKeybord are overlays, don’t have a titlebar, and don’t come up in the alt-tab switcher:
So you’d assume that things with a titlebar will act as independent windows, but that’s not the case, for example Time Display has a titlebar but does not come up in the alt-tab switcher:
Issue: The timeline keeps the time format from the last opened project, regardless of the time format settings of the current project.
When switching between projects with different time formats (for example one with “Timecode” and one with “Beats/Bars”), the projects do load the correct saved time format in the background, but the timeline remains in the last used time format (including grid/nudge). You have to first switch to a different time format and back again to the wanted one, to get the timeline in the correct time format.
Subject: Nuendo 15 Freeze During Export / Render In Place (Timecode Keeps Running)
Hello,
User shoon0312 and I are experiencing the same issue in Nuendo 15.
Nuendo freezes when performing an Export or Render In Place. The timecode continues running endlessly, but the application becomes completely unresponsive and the process never completes.
This issue does not occur in every project, but it consistently happens in projects that include:
Video tracks
Tempo changes
A mix of Linear and Musical mode tracks
Important point:
On the same computer, with the exact same plugins and configuration, Nuendo 14 works perfectly and completes these operations without any issue.
However, Nuendo 15 fails every time under the same conditions.
This strongly suggests a regression in Nuendo 15.
This function is essential for professional workflows, so we kindly ask you to investigate and fix this issue as soon as possible. For me now, Nuendo 15 is unusable/useless.
When you apply an ARA process (such as Spectralayers) to an audio event, moving the event in the timeline or changing its duration is updated in the ARA Editor. So far, so good.
However, if I move an event (i.e., position it earlier or later on the same track in the timeline) and undo that move (Ctrl+Z), the undo is not reflected in the ARA Editor. It remains in the old position in the ARA editor and can no longer be played at all. It remains silent, both at the correct timeline position and at the “ghost position” in the ARA Editor. Strangely enough, however, length changes are indeed transferred correctly to the ARA Editor when I press Ctrl+Z.
This isn’t a Spectralayers issue either, happens with every ARA effect.
