Generate silence and sync-lock tracks [SOLVED]

Help for Audacity on Windows.
Forum rules
ImageThis forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Locked
SUMTech5
Posts: 2
Joined: Tue Jun 14, 2016 3:10 am
Operating System: Windows 7

Generate silence and sync-lock tracks [SOLVED]

Post by SUMTech5 » Tue Jun 14, 2016 10:08 pm

I often need to generate silence into an audio track. When I do this, however, the labels track gets thrown off, even with "Sync-lock Tracks" turned on. For example, if I generate 1.5 seconds of silence, my labels are 1.5 seconds off. My work-around is to generate the silence in an empty track and then paste that silence into my main audio track. The Paste command does not mess up the labels and everything stays sync-locked as it should. It would be really nice to be able to generate silence into a track and keep the labels sync-locked with the audio track. Other generate commands, such as "Generate Noise," exhibit this same behavior.

OS: Windows 7 64-bit
Audacity version: 2.1.2

Thank you!

kozikowski
Forum Staff
Posts: 69384
Joined: Thu Aug 02, 2007 5:57 pm
Operating System: macOS 10.13 High Sierra

Re: Generate silence and sync-lock tracks

Post by kozikowski » Wed Jun 15, 2016 2:24 am

So in general, "Generate" has this problem.

Koz

steve
Site Admin
Posts: 81653
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Generate silence and sync-lock tracks [SOLVED]

Post by steve » Wed Jun 15, 2016 11:45 am

SUMTech5 wrote:I often need to generate silence into an audio track. When I do this, however, the labels track gets thrown off, even with "Sync-lock Tracks" turned on.
This has been fixed in the current development code, so the fix will be in the next release.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

Locked