I suspect the the Track align commands were never designed to work with Label tracks.
For example if you have a couple of audio tracks and a label track, select all and then use Align End to End - then only the audio tracks get moved the label track is left alone unmoved.
I also tried:
Audio Track1
Label Track-1
Audio Track2
Label Track-2
(to simulate a pair of Sync-locked track groups) - and selecting all of that and using Align End to End also aligned just the audio tracks and left the label tracks alone.
@Vishnu what precisely is your use case fir having the two label tracks, just the two label tracks?
Having said that Audacity should never crash so I will log an issue on Muse’s Github bug-tracker using your STRs (Steps To Reproduce) - but I will wait until I hear back from you about your use case.
As far as I remember, aligning label tracks has never been implemented. The Align commands should work with Audio tracks and Note tracks.
I do see some possible (but rare) use cases for aligning label tracks, but also practical implementation problems. In my opinion, Label tracks (and Time tracks) should be ignored by the Align commands, and the documentation should explicitly state that the Align commands operate (only) on Audio track and Note tracks.
Thanks for your response. We’ve noticed that when we select both Audio and Label tracks and use the “Align Track End to End” feature, everything works fine. However, if we select only Label tracks and use the same feature, the application crashes instead of showing a pop-up message instructing us to select one or more audio tracks, similar to how the Time Track feature works.
We are reporting this as a stability issue to prevent data loss due to crashes. While we understand that data can be recovered upon relaunching the application, it would be beneficial to fix this crash issue and provide an appropriate pop-up message to guide users in selecting the correct track combinations.
And yes I did do some furter testing yesterday (after @steve 's comments in this thread) and observed, as you say, that the Time Track behaves much better in this regard.
I will log this on Muse’s Github later today.
UPDATE
Further testing shows that this is a regression on Audacity 2.3.0, introduced in 2.3.1 which was released on 18Nov22 - so we have had this bug for over two years now.