Reset Fades (ctrl+del) shows up in the context menu (and will work as a shortcut) only if at least one of the selected clip has faders already resetted.
I think this is a bug rather than a "feature"
[5088] [5089] reset fades does not always work as expected
Re: [amo] reset fades does not always work as expected
Hi,
I don't quite understand. Can you explain in a more detailed manner, what you do, what you expect, and what you get? A step by step instruction is always helpful.
Regards,
Amaury
I don't quite understand. Can you explain in a more detailed manner, what you do, what you expect, and what you get? A step by step instruction is always helpful.
Regards,
Amaury
Ableton Product Team
Re: [amo] reset fades does not always work as expected
assume i have the preference create fades on clip edge activated.
create an audio track, drop 2 clips -> both clips will have short fades
right click on one of the two clip, check that there's no menu entry "Reset Fades CTRL DEL"
click on one fade handle, delete one single fade (so the clip will still have the other one)
right click, check that now there's a new menu entry "Reset Fades CTRL DEL"
from now on i can use "reset fades" on the selected clip, or on any combination of clips selection that includes this clip.
double check: right click the other clip with two faders, if it's the only one selected you won't see the menu entry, if both are selected you will.
i got into this while trying to remove all fades created automaticcaly on an old project, and thought "where the fuck is this command??? i swear i have seen it once..."
create an audio track, drop 2 clips -> both clips will have short fades
right click on one of the two clip, check that there's no menu entry "Reset Fades CTRL DEL"
click on one fade handle, delete one single fade (so the clip will still have the other one)
right click, check that now there's a new menu entry "Reset Fades CTRL DEL"
from now on i can use "reset fades" on the selected clip, or on any combination of clips selection that includes this clip.
double check: right click the other clip with two faders, if it's the only one selected you won't see the menu entry, if both are selected you will.
i got into this while trying to remove all fades created automaticcaly on an old project, and thought "where the fuck is this command??? i swear i have seen it once..."
Re: [amo] reset fades does not always work as expected
Hi,
That's how it's supposed to work: if there is at least one fade to reset in the selection, then the command is available, and resets what can be reset.
Regards,
Amaury
That's how it's supposed to work: if there is at least one fade to reset in the selection, then the command is available, and resets what can be reset.
Regards,
Amaury
Ableton Product Team
Re: [amo] reset fades does not always work as expected
uhm, maybe my explanation wasn0t clear enough: what i say is that it works only if there's a fader already reset in the selection. are you sure this is how it's supposed to work?
from what you wrote i understand that two fades on a clip means "there's nothing to reset"
from what you wrote i understand that two fades on a clip means "there's nothing to reset"
Re: [amo] reset fades does not always work as expected
Hi,
Reset, in that case, doesn't mean "length = 0". It all depends on the Preference. If "Create fades at clip edges" in ON, resetting a fade means creating a fade that is 4ms, if it's OFF, reset fades means "make all fades lenght = 0".
Now, in your case, the preference is ON, all fades are the default short fade but one. Because of that one, the command is available. For the clip that already have 2 short default fades, the command is not available, because the fades are already reset, meaning they are the short default fades. If you change the Preference, then the command will be available for that clip, because reset will mean "set fade length to 0".
Is that clear enough?
Regards,
Amaury
Reset, in that case, doesn't mean "length = 0". It all depends on the Preference. If "Create fades at clip edges" in ON, resetting a fade means creating a fade that is 4ms, if it's OFF, reset fades means "make all fades lenght = 0".
Now, in your case, the preference is ON, all fades are the default short fade but one. Because of that one, the command is available. For the clip that already have 2 short default fades, the command is not available, because the fades are already reset, meaning they are the short default fades. If you change the Preference, then the command will be available for that clip, because reset will mean "set fade length to 0".
Is that clear enough?
Regards,
Amaury
Ableton Product Team
Re: [amo] reset fades does not always work as expected
many many thanks for the explanation, now it's all bright and clear 
i actually understood how to report the bug correctly (yes, i still think there's a glitch):
"Reset Fades" visualization is not completely consistent with the Preference "Create fades at clip edges"
->> it always show like if the pref is switched on (but the action upon pressing is consistent with the pref)
before we go on talking, this is a screenshot to make sure we are talking about the same thing:
here's a step by step:
- set the pref on
- drop a new clip (make sure it has never been analysed, since i noticed this can add some troubles)
- set the pref off
- "Reset Fades" is not showing up (and it won't show even after reopening the saved set)
this in not a big deal, but the pain is that it does apply also to sets and clips created with the pref = on and then opened at a second time with pref = off (that was exactly the use case i didn't report correctly in first instance)
another (way less disturbing) glitch is this one:
- set the pref off
- drop a new clip
- "Reset Fades" is always showing up, no matter fades are resetted or not. the only way to hide it, is to set the pref on, then click "reset fades".
seeing these combined, now you can figure out why my approach was a bit confused in illustrating the problem:
i always had the pref set off, but started to work on a friend's set which was generated with pref on, so i was faced to a behaviour which was not consistent with the one i have always experienced before.
many many thanks for your time and your attention
i actually understood how to report the bug correctly (yes, i still think there's a glitch):
"Reset Fades" visualization is not completely consistent with the Preference "Create fades at clip edges"
->> it always show like if the pref is switched on (but the action upon pressing is consistent with the pref)
before we go on talking, this is a screenshot to make sure we are talking about the same thing:
here's a step by step:
- set the pref on
- drop a new clip (make sure it has never been analysed, since i noticed this can add some troubles)
- set the pref off
- "Reset Fades" is not showing up (and it won't show even after reopening the saved set)
this in not a big deal, but the pain is that it does apply also to sets and clips created with the pref = on and then opened at a second time with pref = off (that was exactly the use case i didn't report correctly in first instance)
another (way less disturbing) glitch is this one:
- set the pref off
- drop a new clip
- "Reset Fades" is always showing up, no matter fades are resetted or not. the only way to hide it, is to set the pref on, then click "reset fades".
seeing these combined, now you can figure out why my approach was a bit confused in illustrating the problem:
i always had the pref set off, but started to work on a friend's set which was generated with pref on, so i was faced to a behaviour which was not consistent with the one i have always experienced before.
many many thanks for your time and your attention
Re: [5088] [5089] reset fades does not always work as expected
Hi,
Now we're talking bugs! Thanks for bringing these to our attention. They are indeed two different bugs, and are now filed.
Regards,
Amaury
Now we're talking bugs!
Thanks for bringing these to our attention. They are indeed two different bugs, and are now filed.Regards,
Amaury
Ableton Product Team
Re: [5088] [5089] reset fades does not always work as expected
these two looks fixed with beta17
quick job guys
quick job guys