Love the smart fade feature, but I wasn’t able to get the flat curve working as intended. On playback, I’m hearing track A be volume-faded out and end earlier than expected when track B starts. I have smart fade enabled, the fade-out set to flat and the duration at 16 seconds.
That’s the thing. I’m using smart fades. It’s enabled and the timing of it is engaging when it’s expected, just not how it’s expected. With fade out curve set to flat and fade in curve disabled, I shouldn’t be hearing a volume fade on either track when it triggers, yet I am.
Ok. I follow what you’re saying. I assumed because the curve settings were directly beneath smart fades in the UI that they affected the smart fades system.
In that case this is less of a bug report and more of a feature request. If smart fades correctly decides the timing then the curve used shouldn’t matter much. I personally would prefer it to not volume fade at all and just overlap the quiet transition points like it otherwise does.
Sure, but I have a counterpoint in the form of Plexamp’s “sweet fades” and Foobar’s foo_dsp_crossmix component. Both do the same thing of intelligently finding the Crossfade point between two songs but not engaging any volume fading at all. After all, if at least one of both tracks are very quiet at the threshold the smart fade says it’s time to overlap, why is a volume fade needed?
Why do you compare apples and oranges, the function is called Smart FADES so it fades because it was built exactly for that purpose and do that very well …
The fact that PlexAmp use the wrong naming is irrelevant here.
If you want another specific function you make a proper feature requests, but you probably should avoid trying to lecture me and use a single example that does not cover all the millions crossing that can happen