So far so good as in test conditions 0.1 left the audacity picture on and it didn’t even load the screen saver Norton or crash out to both at all however it is prone to having 1 dropout still on a 2 hour straight recording even on the modern standard of 8GB + RAM and an Intel i7 which is old enough to not work with Windows 11 but not old enough to crash it to make it have these dropouts so it just shouldn’t be happening but it’s better than the white text screen of death it going back to how it was working like for ages anyway I guess.
Taking off half the graphics and turning classic skin mode back to on leaving me with controls and times only like classic versions which didn’t do dropouts at all stripping me to the basic look skin doesn’t stop getting 1 or 2 dropouts in 2 hours of recording yet and would be great if that was ironed out in Windows 10 OEM Home i7 3.60mhz Quad Core 8GB RAM mode as it’s not like I don’t have a powerful enough config to handle not getting a dropout at all. I meet the config to not get dropouts yet since modern versions which give dropout warnings started I’ve always had at least 1 in a long recording.
What’s good in the baby steps in fixing all recording issues out though is in a 2 hour test run this morning as I needed to test it the behaviour in 3.6.1 left the picture of the Audacity on the screen and didn’t go to screen saver and Norton didn’t even start up neither and no crash log seen yet although we shall see if it does the same in real conditions later.
But what needs to be done now is trying to iron out the recording glitch which gives at least one dropout on a 8GB RAM i7 system way higher than the minimums.
But test conditions isn’t the real conditions of recording at 13:50 - 15:50 though the original DAB Countywide Community Radio airing of The Heritage Chart if it’s the correct one on whilst racing is on again plus Olympics as well.
I am having trouble with 3.61 randomly crashing when recording a stereo track of a live event. I also experienced this last week with 3.6. This is being done on a standalone Windows 10 computer with no other work being done on it, so there shouldn’t be anything else competing for resources or conflicting with Audacity. I am not importing or exporting anything when the crash occurs, just recording live audio. Similar to other users, the crash report fails to send.
Audacity and crashing are synonymous. In my developer days nobody wanted to solve the bread-and-butter issues, much preferring to work on the cherries of new features. It seems nothing’s changed.
Well it lasted for one show then when it came to the next in a chain of 2 it did crash to the .00 rubbish once but the other show hadn’t started to be fair and I just rushed it on a bootup after the first so I did get to reboot the file to try it again when the show actually started.
So I had one successful live event recording in 0.1 and that was with leaving it alone but leaving it a second time it went.
Brian get back into development just to fix these recording things mate then leave again I think we need your expertise in frustration to a recording app that doesn’t record with a 100% track record.
I’ve had at least 2 hits on test and proper runs before I striked out for the first time in 01 though better than 0.0 100% miss rate.
Heritage Chart worked thats all that mattered I’m here live for Legacy this race day.
If LW can’t bring us back to a real working Audacity on 3.60MHz Quad Core i7 8GB RAM setups which should handle a non crashing and also non dropouts recording easily please somebody else take his place for my sanity using this otherwise other than beta level coding on a final version which shouldn’t be allowed to be even released yet great program.
If the developer can’t handle fixing bread and butter recording and sleep mode and norton crashes time for it to switch hands again because the coding is just not good enough for our needs for this program trying my best way to say it without insulting our developers skillsets in frustration of a poor product in it’s main feature recording which comes before edition but everything else 3rd in line.
Has anybody been having issues with exporting to M4A? I was trying to export a song I’ve been trying to combine into one, only to get an “Crash reason: EXCEPTION_ACCESS_VIOLATION_READ” error, with it refusing to send the report as well. I figured it was possibly the song size (being that it’s an hour long in seven parts), however it was able to convert as an MP3. I tried it with another song that was shorter and again as an M4A, only for Audacity to crash.
Hi, I’m totally new to Audacity. Just downloaded 3.6 from audacityteam.org on my Mac running Sonoma 14.5.
It’s kind of a weird issue…there’s no menu at the top of the app, and the controls seem to be quite limited vs what I see on the instructional video? Did I mess up the download somehow?
In 3.6.1 on Windows 11, I save a file. Then, when I click on the file’s Audacity icon, a window opens that says I must restore the file, which one can select from the new window menu. When I select the file to restore it, a sign appears that says the file was saved improperly. The recording window opens and is empty. However, if I try to open the saved file using Audacity’s Open command after starting the Audacity program, the file will open. This problem does not seem to occur in the Mac version of Audacity. This bug needs to be fixed asap.
But when is recording going to be fixed to Goldwave, Magix Audio Cleaning Lab and Classic Audacity level standards where on 8GB of ram you don’t get crash logs on a screensaver on anytime like for example this version fixed a single time recording but if you recorded again after it just crashes and does bring black screen sleep screensavers up and the second issue of getting dropouts when you leave it too.
A recorder should be able to handle 2 hours of recording followed by a second file of 2 hours of recording in multitasking on 8GB of ram not getting anything ruining your recording dropouts just shouldn’t happen not even one even when Norton turns on whilst leaving it on 8GB of RAM 4 times the minimum.
Ok, for single usage it records a file and even stops the screensaver coming on in this version but when you start a new recording straight away you are screwed after 45 minutes unless you get back in time it’s white and black text screen of impending doom and death to your show capture.
Recording needs to go back to the classic code where dropouts wasn’t a thing.
You are forgetting your bread and butter devs and that is being able to edit and save files flawlessly in all formats with no crashes and to record with no dropouts or crashes for extended length periods with your PC screen off even being able to handle your recording still working in this sleep mode with no crash.
I cannot replicate thsison my W11 laptop, works fine for me.
Clicking on the icon for a saved Audacity project on my desktop properly opens the project in 3.6.1 - I get no messages abot restoring or improperly saved file.
What you are describing sounds like Audacity’s recovery which comes into effect when you next launch Audacity after a crash.
I’m still unimpressed with recording had another crash on a 3.60 Mhz Quad Core and 8GB RAM leaving it whilst out today on the 01.
Why did they release this garbage it’s alpha quality because beta and proper quality doesn’t crash on the recording only other things in beta but not bread and butter and the proper version should be stable this isn’t stable it’s like it’s built by a jobber that doesn’t know how to program and how good it has to be before a stable release.
I’ve had to resort to having Magix Audio Cleaning Lab on as an additional simultaneous recording app.
The developer won’t even reply to me bollocking their programming being poor in this version.
As it’s open source which is what is good about it someone else have a go at reprogramming the recording which is making people crazy in anger and rage make it super lightweight so it doesn’t crash on a pretty powerful system like mine.
In addition to this problem … After using the envelope tool, the visual glitch shows the reduced waveform only, even if we want to manually fade something up … we are not seeing the actual waveform. This sample is actually at full volume after the fade-up, but you’d never know from looking at it.
HELP!!! I just updated and my mic is no longer coming through. It was working perfectly on the previous addition.
Set up hasn’t changed - AT4033 into Scarlette into iMac
I made sure the scarlette was selected as Audio input
Any suggestions?
I need to record tonight!
Thank you!
