Another way to put it, “Ignore/Don’t bounce Incomplete Cross-Fade Selections”
When bouncing a selection of events that are within more events that aren’t selected, but all are crossfaded, you lose the crossfader at the start and end, and are left with overlapped events:
This might not even need to be a preference, and rather just a change of behaviour… But perhaps there are use cases where the current behaviour are needed (?), so I’m suggesting it as a preference.
The “problem” is that when you bounce the fade gets baked into the file, so an automatic new crossfade won’t sound the same. You would get the crossfade “twice” for just the one file. That may obviously still be fine, but it’s different, so if you want it to sound the same you have to tweak it regardless.
Do you think this has any purpose?
Sorry, I’m not following. Do I think what has a purpose?
The crossfades behaving this way when bounced… Or could Steinberg alter this behaviour without being aggravated by the chang?
I think it’s probably better to have an auto-crossfade instead of the way it works right now, but maybe leave it optional.
Right so it does render the non-selected cross-fade as a fade on the one side.
The proposed behavior concept I guess, is for bounce to “Ignore/Don’t bounce Incomplete Cross-Fade Selections”
I can’t really see any need for it to be the way it is currently and if anything could result in a user not noticing a bad cross/fade if it’s small enough.
One of those little things that has always been this way, but could probably be tweaked in modern times (?)
edit
Also I’ll add, changing the behaviour so that it functions similar to how “Make Extension Permanent” does. This will create more of a expected and symmetrical program behaviour between the two functions: