What am I missing? 
PS: I’m aware that when activated the fades are not visible (no idea what’s the reasoning behind since if there’s a fade I want to see it) but they’re not x fading in playback
Any tip is much appreciated
Auto Fades in Nuendo is a separate function and only works when events meet IF they are not overlapped nor manually crossfaded.
Auto Fades also apply fade-ins and fade-outs, but they are overruled if you apply a manual fade.
They don’t show simply because that is would clutter things unnecessarily, because if active there will ALWAYS be a fade in/out/cross whenever events start/end/meet as long as they don’t overlap and there are no manual fades.
It’s meant to be used as an easy way to avoid pops and clicks in editing without having to do a manual fade every time.
What you want in the case of your image is the Crossfade panel. Just press X and the overlap between the selected event and the one below it will turn into a crossfade with the same length of the overlap. Press X again and the panel will pop up for further adjusting.
1 Like
Thanks Henrique
not sure what this means
only works when events meet IF they are not overlapped nor manually crossfaded.
tbh I cannot imagine a situation where an auto crossfade that’s not done manually??? (big head scratch)
I already setup a control in my streamdeck to apply x-fade but I’m wondering if that can be set by default like, what happens in Logic: you need to overlap 2 audio events, drag them manually, x-fade is created automatically.
Also so that you can audition the fade in real time and adjust if necessary.
having to do apply it just to check if it’s x-fading nicely or not seems quite time consuming to me
What I mean is that the way Auto Fades work in Nuendo is not what you are aiming for, this “overlap events and they will automatically crossfade”.
It works in the way I described: if you have it enabled, everytime an event either starts, ends or meets another event, it will have the auto fades setting applied to it, silently and invisibly in the background. But if you apply a manual fade/crossfade then those will prevail.
I don’t know, in Nuendo, of a way of doing what you say, so that the x-fade is created automatically when overlaps occur. I for one wouldn’t enable such a feature if it existed, cause I like my overlaps to hide the event below unless I specifically crossfade them. For me just pressing X is pretty straightforward and I don’t event think about it.
If you want a different approach than this, you can use the Range tool, then you select a range to the same area where you would drag the events if you were in logic, then press X. They will be trimmed automatically and crossfade within the selected range.
Or you can also activate “delete overlaps” in Preferences>Editing, and then events will always meet with no overlaps, and then X will apply your chosen default crossfade length. Then you can set your key commands for Play crossfade and increment/decrement fades sizes and adjust to taste without having to look at any windows or clicking anywhere.
There are many ways to work fast in Nuendo. You have to choose yours and do it until it becomes second nature… By then the way logic does it will matter no more.
1 Like
Thanks a bunch Henrique
I’ll just stick to the streamdeck command.
Not sure what I’m missing here: Logic is way more streamlined so not sure what you mean with “by then it will matter no more”:
Logic:
1- you just drag events onto each other
2- audition the x-fade
if it doesn’t sound good just keep dragging and auditioning. Fades will adjust automatically.
VS
Nuendo:
1- you drag events onto each other
2- click “x-fade” command
3- click the rightmost event to start playback and audition x-fade
and in case it doesn’t sound good (in my case is super common when doing SFX)
1- undo x-fade
2- reposition the events
3- click “x-fade” command
4- click the rightmost event to start playback and audition x-fade
and so on until you nail the positioning
In a nutshell:
- Logic: drag
- Nuendo: drag + 2 extra actions to perform the same thing
not to mention Nuendo doesn’t allow you to resize the event that’s underneath even if it’s selected. which means that, you need to remove the other event out of the way, and start the positioning/auditioning from scratch, adding 3 more actions to the list in the very common need to reposition events.
Sorry but which is more efficient is a no brainer in my books.
But appreciated stopping by and sharing 
At least I know it’s not possible and I’ll just adapt to it.
1 Like
N13 has added very useful key commands that allow resizing faded events. An auto x-fade could be nice, since the window management on nuendo for fades is inconsistent and cumbersome.
Nah. Just drag an event to overlap another event, and press X. Now move whichever even you want, resize the xfade area by dragging either edge, slip audio within the crosfade etc. It’s all there.
2 Likes
What I mean is that I think you need is to get to know the tools and ways in Nuendo better, instead of wanting it to behave like something else.
You don’t need to do all those steps you mentioned. You definitely don’t need to undo the crossfade to adjust it dude, c’mon, that’s basic stuff.
You can simply drag each event border, drag the crossfade itself, or simply press X and go to the Crossfade editor window and do all the adjustments there.
And you can assign all kinds of key commands to have an absolutely streamlined workflow regarding crossfades - and whatever else. For example, you can have a key command for “play crossfade” and another pair for nudging the crossfade around. So you need ZERO clicks to adjust your crossfade.
And yeah, Nuendo won’t let you resize the event below, but you can simply press “delete overlaps”, or you can press “bring to front” and adjust, or you can - again, select a range and make both events conform to that range while crossfading them at the same time… and I’m sure there are other ways to go about this too.
Try to dive deeper into key commands, macros and the Project Logical Editor. They are key to using Nuendo efficiently.
1 Like
Thanks Henrique (and Graveley)
Unfortunately due to work reasons I had to switch to Windows and I’m stuck with Nuendo so I’ll deffo deep dive into it with time.
My issue with Steinberg in general is that, compared to Logic, it always takes so many more steps to accomplish the same exact things.
And to me that will always be inefficient design. No matter what.
Another example, render events with a reverb tail:
Nuendo has a separate window that you need to open first and set all sort of parameters (if you want bar or seconds etc…) also the length of the tail itself
In Logic there is one single check box: Add Tail.
Or naming events with increasing numbers:
Nuendo: shortcut “name selected events” open naming window - type name - enter - press enter again to confirm and close the window
Logic: shortcut “name selected events” - type name_01 - enter
(no unnecessary separated windows or separated boxes for text, numer etc…)
If we’re talking about UI design and user experience, this is just objectively better designed. No matter if I get super fast with Nuendo’s worflow with time.
Having a lot of options to me is always a red flag of unefficient design.
Reaper is king on this but at least is fully scriptable.
But I work in games and I’m uber sensible with UI experience and making sure is as streamlined as possible
And that’s an Art by itself.
But yeah, I’m using Nuendo from now on so I’ll just stick to it and fine.
Thanks again for chiming in!
That’s what I’m telling ya, you are complaining without even knowing what you are talking about. There are two ways of rendering in place. One is “render with current settings” and the other is setting up and then rendering. So if you have your settings the way you want, just press the shortcut and render immediately just as in Logic. If you want to adjust your settings first, do that and then render. Are you suggesting that having no way to adjust your settings is somehow better?
Also
No double enter here. Just press the shortcut, type new name, press enter. That’s it. Less steps would require mind reading by Nuendo.
I simply disagree. To me, having lots of ways to do the same task simply allows for more flexible and adaptable workflows.
I’m sorry but I’ve been working in this environment (Cubase/Nuendo) for a becade already, and there are a LOT of issues with them, but none of them are what you pointed out. =D
Yup I’m aware there is “Render with current settings” and it’s just one click away but I’ll give a quite recurring example for me
This is a quite common task when doing SFXs.
I have 5 tracks with 10 sfxs events and a custom reverb tail length setting for each track.
Track1: 3 seconds
Track2: 6 seconds
Track3: 2 seconds
Track4: 10 seconds
Track5: 1 second
Don’t you have to open the render settings video 5 times to setup the respective tail lenght before rendering each track?
Now I’m curious
for the records, in Logic you don’t need to specify anything: 1 click and it renders each event as soon as the amplitude reaches - inf. That’s it.
No need to specify the tail length. And why would you want to input that manually anyway?
This is a simple taks with one simple goal: render an event where entire tail is included.
A software that does it automatically for me is just more efficient than a software where I have to manually do it myself.
This goes beyond personal workflow preferences. It’s just common sense.
AHHH ok.
You could have said that from the beginning hehe!
I really don’t know if that’s possible, cause I don’t use it like that, but I will definitely look into it!
I know yeah, it’s typical game audio stuff and that’s why I invested in Nuendo since it was marketed also for game audio and as of today the specific game audio tools and workflows, in my experience, are just pretty juvenile and not that useful. Especially with Reaper around which is getting more & more efficient thanks to its scriptability.
Fun fact: Logic isn’t marketed as game audio by any means but believe it or not, I switched to Logic 16 years ago because of that “add tail” function alone. (I was on Live and happy with it).
I worked on a game with a poopies ton of procedural audio and had to render literally thousands of short musical clips (in the end they were over 9000) multiple times and with Live (or Nuendo or even Reaper back then) it would have taken me months just for this single task if I had to set it up manually for each.
But nuff about Logic 
I really hope N14 brings some solid improvements. There are quite few things where Nuendo wins hands down compared to any other DAW I’ve used and C14 has some really cool new features, workflow wise I know I’ll use a lot.
Yeah, it seems Nuendo can’t set an autotail and set the render size to -inf automatically. =(
But a possible workaround is just setting up a long tail, longer than anything you’ll have, and then just trimming off silence out of everything, in a batch process.
I agree it must be a terrible miss when you need it.
But the other points still stand! 