Hello team,
first at all, thank you for everything you do! You’re fantastic!!
I want to report you an issue I noticed since I installed the last version 3.7.7:
program crashes very often when I try to undo some effect by pressing ctrl-z (or by menu) after applying some effect (time change, fade out and so on).
When I try to recover the unsaved project, the last modified part is missing!
I tried to send the bug report but it always fails so I copied the text and I attached it here in a txt file.
Thank you for your support
Tiziano
bug report.txt (182.5 KB)
Do you know the last version you used that was well behaved? It’s not unusual for us to recommend you step back to that version to get your shows out the door. Have you ever done that? There’s some tricks to it.
I don’t know that there is a successful pathway for Bug Reports and the Audacity Developers don’t reliably frequent the forum.
There is a technique to install a “Portable” version of Audacity and that can allow different versions and updates to co-exist. I’m investigating this as 3.7.7 and 3.6.2 (my day-to-day app) prevent me from investigating forum complaints.
I’m just now paying attention. Windows NT? I remember WinNT. How old is your system? We should remember that Audacity tries to run on all three major platforms. That makes software error detection and correction super entertaining.
Don’t push the “Bug” button. To do that you will need to find a couple of hundred different people with the exact same problem on different machines. This has happened. The forum lights up with postings that all say basically the same thing.
Koz
Hello and thank you for replying!
I use windows 11 on a modern machine. I don’t know why it appears WinNT.
I often have to reopen old projects so it’s a bit annoying doing a downgrade because after that it will be impossible to open projects made by a newer version of the program.
For the moment I will keep using the last version, trying to avoid to use the undo fonction.
I suppose that the corrupted part is just the inner table where the program registers all the events, to make the undo possible.
I understand that it’s very complicated to correctly save all the operations on a big multitrack project with lots of effects applied on every track…
Problem is that this same issue never occurred before, until I updated the program to the current release.
Another very annoying problem is that after saving a project, when I reopen it, some (apparently) random parts of one or more tracks are missing! I suppose that it could be connected to the other issue : probably those disappeared parts would have caused a crash if I attempted to undo my last operation on them…
I found a way to avoid this problem. After saving a project “X” , I save it again with a different name “Y” then I reopen in a new window the first one X. If I notice some missing part in X, I can copy all the tracks from the Y project. Copying and pasting the tracks to a new empty project, I can have a full working project, where the undo table has been reset. Obviously I don’t use the smart copy. This resets the undo table but keeps all the real time effects in place!
Audacity is wonderful but using it can be stressful
See:
I don’t have any stressful problems with Audacity. I do have constant use of some very old Audacity versions on mature machines and 3.6.2 is my day-to-day version. I Do Not update at the first whiff of a new version available and I absolutely, positively, no question don’t change anything in the middle of a production.
Koz
I like new releases and I use new functions, and I like to solve problems going forward, not going back to the past. Thank you for your time but I don’t think that “please don’t update” and “don’t change anything in the middle of a production” can be called “useful”.
I make a lot of changes, I apply a lot of effects on a lot of tracks and old versions on old machines run too slowly for me. I adore the current version and I look forward for new releases to correct these bugs.
It depends on your goals. I’m happy never having lost a paid job.
Koz