Actually I’m not going to bother as Muse are closing suchlike trivial 3.x bugs as they transition to 4.x with it’s new framework and architecture.
Peter
Actually I’m not going to bother as Muse are closing suchlike trivial 3.x bugs as they transition to 4.x with it’s new framework and architecture.
Peter
If they’re that close to 4.x, I agree that the workaround, although cumbersome, is good enough for now. Do you have any idea if they are addressing these glaring issues for 4.x?
Don’t hold your breath, it’s not that close. They are just switching their ongoing focus to working on 4.x
Good
Sorry no, I am not part of the Muse team so not party to such design decisions.
Peter
From what I can tell of 4.x, the Muse take-over of Audacity will be be a radical departure from the traditional Audacity. Further, there is no doubt, in my mind, that the take-over will, sooner or later, lead to a server-based service requiring annual subscription. It seems very likely that I’ll be living with 3.6.4 for a very long time …unless there is a alternative option to Audacity. With that in mind, and given your depth of expertise, what alternatives to Audacity are you familiar enough with to recommend?
This is what the under developmemt 4.0 looks like at the moment:
Quite a similar look&feel I’m thinking.
Peter.
Thanks. I was seeing something similar, as well. My bigger concern is that Muse does not exist to be a non-profit and I’m watching as the drift does seem to be toward a server/cloud-based service. This whole undo-redo issue is something that makes me believe this. It didn’t exist in previous releases and seems to point to a move away from computer-based software, which is fine for the provider and a heavy, consistent, user of the software, but not for the casual user.
I have just compiled and run release 3.7.0 on windows and from a couple of tests this problem seems to be fixed. I will try a direct comparison test with 3.6.4 and confirm after a longer trial.
That would be great. If you would like me to test it, point me in the direction of the executable. I import about 20-30 half-hour long audio files and process them all in a single session. The session files, for such sessions, typically are in the 35-45 GB area. So, I could quickly see any improvement in the 30-45 minute “Discarding undo/redo history” process.
Further testing of 3.7.0 on a lower specification windows system seems to confirm that exit is clean and the message doesn’t appear.
DeannaAudio - This version source is available on github
https://github.com/audacity/audacity/tree/release-3.7.0
But I had to download it as a zip file. Because of the confusion with muse its possible that it won’t be released officially and I can’t let you have my ASIO version. If the powers that be are not going to release it maybe they will sanction me letting you have a non-ASIO ( windows 11 64-bit only )?
Thanks for putting in the effort, but I don’t quite know what to do with the files in that zip container. Should I just add them all to the Audacity program folder, replacing any preexisting versions?
Incidentally, I’m using Win10 pro, not Win11 …if it matters.
3.7 is now released and available for download - problem solved!
The files available from github are the source code from which, with suitable tools, an executable Audacity program may be built by compiling and linking as set out in the instructions in the file build.md. This can be done on your windows 10 machine but you may feel it is a bigger task than you want to tackle. An easier alternative may be to try one of the previous versions of audacity which are available for download and did not have the current undo/redo function.
Thanks for the effort, but previous versions don’t have the new compressor and limiter. The legacy compressor is wrapped with a noise removal filter and, even with that minimized, does not seem to behave like a pure compressor and I’d prefer to address noise and compression separately.
This topic was automatically closed after 30 days. New replies are no longer allowed.