Audacity Forum

Great catch Mike

I have logged this as P1 Bug #2687
https://bugzilla.audacityteam.org/show_bug.cgi?id=2687
Compressor with selection to end of track can cause corruption

Many thanks for the testing and the report.

Peter.

As James inferred earlier - your second screenshot shows that that tack is already fully amplified up to 0dB - that's why there's no further amplification suggested.

You can force it to Amplify more by checking on the "Allow Clipping" - but you will get a badly clipped distorted result.

Peter.

@waxcylinder: Thanks for the double-click reminder. This works well when I am trying to select the part covered by a single label. Is there something similar I can use when selecting the track between two "point" labels (i.e., zero-length) ... Sorry there isn't - but you're not the first person t0 ...

Please see: https://manual.audacityteam.org/man/timer_record.html

WC

@Corvinus,

Do you realize you can accurately select the audio associated with a label by simply double-clicking in the label ?

Peter.

Our free official download can be obtained here: https://www.audacityteam.org/download/

I followed the steps in the bug report and here is the video of me inserting silence - the scale doesn't change. I also tried my original live project and the scale did not change in that either. I'm minded to agree - if you look in the bug report I tested that as Ok on W10 (following the Steps to ...

mafg1953 wrote: ↑

Mon Mar 01, 2021 2:09 pm

Looks like RC04 fixed the issue. Thanks!

This puzzles me because Steve tested this and did not pass it as "FIXED"
https://bugzilla.audacityteam.org/show_bug.cgi?id=2680

Peter.

The issue here appears to be with Snap-to and not the label a) With Snap-to set off  sample-grained labels in a re-opened projects do get the yellow snap guide-lines. b) but if you turn Snap-to on in a re-opened project you do NOT get the yellow snap guidelines. Tested for this in both 2.4.2 and 3.0...

(I use hh:mm:ss + samples at 44.1kHz) because snap-to was set to nearest and never changed. Corvinus, is there any particular reason you need sample-level accuracy ? If you use the Audacity default setting of hh:mm:ss + milliseconds this problem does not occur. (I just tested this with 2.4.2 and th...