Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some effects delete Envelope Control Points, or do not move them when timeline changes #1500

Open
crsib opened this issue Aug 18, 2021 · 5 comments
Labels
bug An error, undesired behaviour, or missed functionality Effects P3 Medium Priority bugs
Projects

Comments

@crsib
Copy link
Member

crsib commented Aug 18, 2021

Describe the bug

Effect using ClearAndPaste, as well as Equalization (which is not) do not preserve Envelope points. This issue is reintroduced after reverting:

However, it is considered to have much lower priority

To Reproduce
Steps to reproduce the behavior:

  1. Create an envelope.
  2. Use ONE of these effects:

a. Change Speed/Pitch/Tempo
b. An EQ effect (see bug 1686)
c. Noise Removal
d. Nyquist Prompt
e. Sliding Time Scale/Pitch Shift
f. Copy-paste

Envelope points are deleted.

Expected behavior
Envelope points should not be deleted. Discontinuities should not be added for effects, only when copying

@crsib crsib added bug An error, undesired behaviour, or missed functionality P3 Medium Priority bugs labels Aug 18, 2021
@crsib crsib added this to To do (Dev) in Release 3.1 via automation Aug 18, 2021
@Paul-Licameli
Copy link
Member

Paul-Licameli commented Aug 18, 2021

Actually, rather than reversion, what happens if the calls to Envelope::Insert() are instead made to Envelope::InsertOrReplace()? I think this will preserve the bug fix, and also not corrupt the envelope because points will remain properly sorted.

@crsib
Copy link
Member Author

crsib commented Aug 18, 2021

The behavior will be still buggy because Clear introduces discontinuities, that are totally not expected when applying the effect. I believe that (10 years) old buggy behavior is preferred to new buggy behavior, with the consequences not known so well.

Also, the new behavior will still introduce 4 new points for each effect usage.

@Paul-Licameli
Copy link
Member

Paul-Licameli commented Aug 18, 2021

How four, not two? You mean, in a stereo track, not mono.

Paul-Licameli pushed a commit to Paul-Licameli/audacity that referenced this issue Aug 18, 2021
@crsib
Copy link
Member Author

crsib commented Aug 18, 2021

How four, not two? You mean, in a stereo track, not mono.

Sure, two, you are right

@Paul-Licameli
Copy link
Member

Paul-Licameli commented Aug 18, 2021

Of course we mean two discontinuities, four points.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An error, undesired behaviour, or missed functionality Effects P3 Medium Priority bugs
Projects
No open projects
Release 3.1
  
To do (Dev)
Development

No branches or pull requests

3 participants