If I have Sync-Lock Tracks turned on and I insert some audio into a track, the last label on the label track gets inserted into the corresponding spot in the label track. It only seems to happen if the inserted audio is inserted before the position of the last label.
If you follow these steps, you should be able to re-produce it:
turn on sync lock tracks
generate an tone track
add a few labels, one at start, one at middle, and one at end.
copy a section of the tone track and paste it into another spot in the track prior to the last label
the last label is duplicated at that point where the audio was inserted
I then selected 30 seconds between Label1 and Label2 and did Ctrl-C. Then I placed the cursor at 6Min and did a Ctrl-V. Below is what I ended up with.
Not sure if that helps or not. I have “Type to Create a Label” turned on, but I also tested it with it turned off and got the same result. If I turn off Sync-Lock or if I paste after the last label, it does not happen.
I’ve tested with Audacity 2.4.1 on both Linux and Windows 10, and I’m not able to reproduce the issue.
You could try resetting Audacity Preferences to see if that “fixes” it. If it does, then reinstate your normal preferences one at a time to check if the problem returns.
The easiest way to reset Preferences is to reinstall Audacity and enable the option to reset preferences during the installation.
I re-installed and added my preferences one-by-one. The problem showed up after I selected “Retain labels if selection snaps to a label” under Interface. It’s not that critical of a selection for me so I will uncheck it. But the description of that selection doesn’t seem to indicate that inserting audio would be impacted by that selection. So something is weird.
OOH so it does - I tested this on W10 on 2.41
a) no label added at step 5 when using default settings of “Retain labels if selection snaps to a label” turned off
b) but when I turn that setting “on” - then ideed I get the spurious label.
So this is a bug in 2.4.1
However I also tested this on the latest alpha test build I have for the soon to be upcoming 2.4.2 - and somewhat mysteriously this bug has disappeared, I can’t reproduce it there. So presumably it got “fixed” by something else we fixed for 2.4.2.
On this basis I don’t think I need to log this in our bug-tracker (unless Steve thinks I should for trackability).
But many thanks for the bug report Mike - and many thanks for the clear steps to reproduce, that is very much appreciated
I have been using labels quite a bit as I edit audio that comes from 1:30 minute seminars and then send the audio to an audio reviewer - so labels help me organize my processing and are very useful for the reviewer to locate problem areas.
