Just loaded 3.7.2 on windows 11.
Editing a track to delete a small section using “Delete” key puts in a split in the track and if one tries to join the sections it deletes the part before the split.
This make things unusable . Any one else seeing the same problem ?
4 Likes
Yep - same issue on Mac.
Rolling back to previous version now.
3 Likes
Im having the same issue can you tell me how i can move back to the old version?
How do you roll back to the previous version? This is a disaster!
This appears to be new behavior introduced in 3.7.2 (the latest release) - and I presume an intentional design decision by Muse.
Personally I can see that the separate clips may well be useful in helping identify precisely where the deletion took place. The separate clips make no difference to how the audio plays or is exported.
To remove the clip lines and consolidate the audio, just select the audio to be consolidated and use:
Edit > Audio Clips > Join or its shortcut Ctrl + J
If you do this a lot you could create a macro that makes the deletion, the selection and the join - and then create a custom shortcut to invoke that macro.
Peter
Joining has a bug, please avoid using it. I recommend staying on 3.7.1 for the moment.
3 Likes
Tried the “Join” when I first saw it splitting the track but all it does is to delete the section before. Just revert to 3.7.1 until all the various reported problems are sorted.
1 Like
Yeah, when I join after editing the cut it’s moving the clip backwards to fill the time … thereby throwing off the whole sequence. Very weird!
1 Like
Thanks for the assistance! I’ve taken your advice. 
1 Like
Delete also has a bug. gone back to 3.7.1 and it works brilliantly again.
3.7.1 still crashes on saving with a fault report that wont send. Does recover on request and then saves OK frustrating.
1 Like
Be careful about reloading older versions if you are using Windows. 3.7.1 is still dodgy. I have reloaded it for the time being because 3.5 would not give me access to months of work done in 3.7.1. This is not entirely audacity’s fault because I’m sure you’re aware that Windows has a nasty (and stupid) habit of changing the status of any files that one has merely accessed as “last modified” (and therefore processed in 3.7.1). As a result, microsoft and audacity combined to temporarily corrupt (now resolved) archival files from a decade ago. Someone please help Microsoft understand that merely opening archival or recent files is NOT “modifying” them.
Yes I’m having the same problem, it’s driving me mad. 'Any solution found yet?
Rolling back now, thanks all
Thanks. I found the previous version on my laptop.