Studio fade out bug

Hi… I was hoping that the new release would cure the studio fade out tool sometimes splitting the audio, but it’s still there…

I was working on two projects this morning… On the first one studio fade out worked first time…

On the second one it split the audio… Usually by moving the cursor and trying again it works but this time it just kept splitting the audio… In the end I just used fade out…

It’s not the end of the world, just a bit annoying…

Moving on…

This bug should be fixed in the current release version (Audacity 3.7.3)

@steve

I doesn’t seem to be - this is with 3.7.3 on W10

Peter

Indeed… I was using 3.7.3 and it’s still there…

You’re right. There was a different (worse) bug that has been fixed, but the issue that you describe still exists.

The behaviour that I’m seeing is that if the selection starts or ends on a clip boundary, then the other end of the selection is split. This appears to happen consistently across all Nyquist effects, so it “may” be an intended (but undocumented) change of behaviour, or a bug.

@steve @ChrisWood1955

Testing shows this is indeed a recent regression on 3.7.1

I have logged this regression bug on Muse’s Githug issue tracker:

Peter

@ChrisWood1955

Hi Chris,

you may be pleased to know that this looks like to be fixed for the upcoming 3.7.4 release.

It has been fixed in the Audacity3 “master” (I just tested it) - but has not yet made it to a 3.7.4 alpha or beta - but I fully expect it to be in the 3.7.4 release.

Testing all this has made me notice a couple of oddball effects *Repeat and Reverse) that do still produce splits - and I can’t see the point of that, in particular it makes them inconsistent with all the other effects.

Both are very old regressions as the earliest Audacity versions did not do this - so I will later be logging regression issues for these.

Thanks for flagging this original issue, much appreciated :sunglasses:

Peter

UPDATE

@ChrisWood1955 @steve

From looking at the recent bug list on Muse’s Github. it looks like this is not properly fixed for Studio Fade Out - where it remains a moonphase bug (one that on;y happens every now and again, but not consistently).

See:

Peter

I have logged this two regression bugs this morning: