"Start to zero" command sometimes works and sometimes does not depending on the file

I’m recording an audiobook with a number of tracks in each file. Each file is a chapter with a number of sections in it. I have to split the individual files up. After deleting the first few tracks I’ve been hitting “ctrl+A” then Tracks> Align Tracks > Start To Zero. This works sometimes to realign all the tracks to the beginning, but then other times it does not. Specifically in the files that it does work “ctrl+A” only selects starting where the first track begins, whereas when it does not work, “ctrl+A” selects starting from 0, with all the empty space too.

It seems to be something that I did while I was recording in the files, as the command works just fine in some files and not in others. Any ideas on how to fix this?


Can I rewrite that a bit? “I have to split the individual sections up into files?” I read the original three times and couldn’t bring it home.

That’s the part I think I experienced. I had a multi-track show. I drag-selected a portion of one track.

File > Export > Export Selected Audio. What I actually got was my selection plus everything else Audacity thought I might want. I can’t sort what Audacity was thinking about. It was way too complicated to get what I actually wanted.

Waiting for other elves to comment.


Hey there tech-savvy community!

I’ve recently been diving into some software intricacies, and I came across an interesting quirk that I thought I’d share with all of you. Have you ever used the “Start to Zero” command and found that it’s a hit-or-miss situation depending on the file you’re working with? Well, join the club!

I’ve noticed that the “Start to Zero” command, which seems pretty straightforward, doesn’t always perform as expected across different files. This got me scratching my head for a bit until I stumbled upon a crucial piece of the puzzle – file dependency.

It turns out that the success of the “Start to Zero” command can be influenced by the file’s complexity and its connections with other files. If the file you’re applying the command to has intricate dependencies or relies on data from other files, there’s a chance that the command might not work seamlessly.

After some experimentation and discussions with fellow developers, it seems that ensuring all necessary dependencies are correctly linked and loaded before executing the “Start to Zero” command can make a world of difference. This involves checking if all required libraries, modules, and data sources are in sync and available.

Furthermore, the order in which you execute the command can also play a role. Sometimes, starting the process in a specific sequence – like loading dependencies first and then initiating the “Start to Zero” command – can lead to more consistent results.

Of course, this doesn’t mean the “Start to Zero” command is flawed. It’s just a reminder that even seemingly simple commands can have underlying complexities. So, next time you encounter issues with the command, take a step back and consider the dependencies and execution sequence. It might just be the missing piece of the puzzle you needed.

Has anyone else encountered this phenomenon? What strategies have you adopted to ensure a smoother experience with the “Start to Zero” command? Let’s share our insights and help each other navigate these little intricacies in the world of coding. :desktop_computer::computer:

1 Like

Yeah I was wondering if it was something I did while recording somehow… But I’m pretty sure I did the same stuff each file? It’s interesting that essentially “cut and paste” could become broken like this, bother!

This topic was automatically closed after 30 days. New replies are no longer allowed.