Not an official bug, but I can nearly can not read the text in the EQ1. White text at bright blue background is not great. Other developers do this well.
Still the Hub does NOT show the latest projects. This works just in the file menu, but not in the Hub. Never did. Just after closing Nuendo.
When I make timecode changes in the project settings or use the âSet Timecode to Position Pointerâ function in the Project menu, the ruler unit changes. This should not happen.
Edit â Move events to selected track: Does not work when âDivide Tracklistâ is enabled and one track is at the top and the other at the bottom.
If I save multiple settings for the arrangement or mixer in the Visibility Agent, newly added tracks are still added there because they are not âlockedâ. This makes this function unusable for me.
No linear crossfade âconstant amplitudeâ / âequal gainâ.
In Mediabay, volume should not only be adjustable after an audio file has been selected.
When importing audio files, always place the grid point at the beginning, not somewhere else.
File â Import â Tracks from Project: Automations are imported, but NOT whether a track has been switched to READ.
Issue: Render in Place (Dry - transfer Channel Settings) with multichannel VSTi only transfers Automation from VSTi Main-Output
Itâs an old bug (I already found it in C13) but itâs still present in N15 and discussed/confirmed here.
When performing a Render in Place from a VSTi with multiple outputs (e.g. Groove Agent) and select âDry (transfer Channel Settings)â, Nuendo transfers all inserts of the different channels (as it should), but only the automation data of the main output channel is kept (and then copied to all other channels), which is quite nonsense.
Screenshot (yellow = Volume automation of the main output that was copied by nuendo on all other tracks, red = automation on the "Out 3â that disappeared after the RIP process)
Issue: Linked send panners do not follow the main panner
Discussed and confirmed for example here.
All send panners use their own automation data, even when the âLink Pannersâ option is enabled. This means that panning automations written only for the main panner are not executed by the send panners. When the âLink Pannersâ option is enabled, the send panners should be independent of their own automation tracks and simply follow the main panner. Otherwise, this option is useless, because the panners arenât actually linked after all.
Another visual issue in this context: With multiple panners, itâs not immediately clear which panner corresponds to which automation track, because theyâre all labeled âPan left/right,â and you only see whether itâs a Send Panner or the Main Panner when you hover over them. This gets exspecially problematic because the new âshow last touched parameter on topâ in the automation panel doesnât always show the main panner on top when touching the panner in the channel but sometimes randomly one of the send panners.
Issue: âbounce selectionâ removes muted object if there are crossfades