Post
by Amaury » Mon May 25, 2009 12:36 pm
Hi,
I think there is a confusion. The original thread talks about a bug that prints a fade in the beginning of consolidated and rendered files, even when there is no user fade. So, in you scenario, delete the fade by hand so that its length is equal to 0, consolidate the clip, and you'll see that a fade has been applied. This bug is now filed and will be worked on.
If there were any user fade, of any length (which you can see if the Fade view is visible, or via the shaded area on the clip box itself, it would be expected that a fade is printed into the consolidated or rendered file, because the user fade is also consolidated or rendered.
Now, you are describing here a situation where the Preference "create fades on clip edges" seems to have no influence. Indeed, as you expect, if the pref is OFF, Reset Fades should set the fade to 0ms. If ON, Reset Fades should create 4ms fades.
But, I can't reproduce the problem, following your steps.
- The "drag image", when dragging a sample from the Browser to the Live set, always shows you the original sample, so, the waveform is as the original.
- When you drop the sample into the Arranger, there can be two reasons why there is a fade: either the "create fades on clip edges" is ON, or, there is a fade saved with the .asd file. To make sure, you can rename the .asd file from the sample, then turn the pref OFF, and drag the sample. It should be fade-free.
- Last, for me, when I change the Preference while the clip is already in the Arranger, the "Reset Fades" command changes behaviour accordingly. That would be the bug you're describing, but here it seems to work well, using 8.0.3.
Kind regards,
Amaury
Ableton Product Team
