Background: I record a podcast using Audacity and our sessions run about 1.5-2 hours long. I then save the file for later editing. I use a Seagate External Hard-drive (D:)
I recently downloaded the Audacity 3.0.0 and since then it will not save data in the files or will not read them correctly. I can open a previous AUP file from the external hd, and I can save that same file under an alternative name, such as name_edit1, however, when I close the program and go to open that new file, it tells me that it cannot read the file in D:.
Also, when I edit the original file, and attempt to save it or back it up, it tells me that D: is not write-able or is full. It is not full. It is a brand new 2TB hd. So i have been stubbornly doing all of my edits, and then exporting it as an MP3 in order to save the audio file.
What am I doing wrong. Is the hard -drive not formatted correctly? Is there a bug in 3.0.0? Help please.
when I follow your directions, after opening disk management, it is listed next to the drive that the file system is exFAT. when you right click the drive and go to properties/volumes, it says that the partition style is MBR. Does that help in any way?
I can save .txt files to the harddrive with no problem.
To answer the other questions, yes i could run .aup files from C:\ but i don’t have the room on that drive to maintain so many files, and i got the download from the audacity website, not a third-party site.
When i attempt to open the app permissions, it does not give any options other than to uninstall.
How long is the USB cable? These are some of the same symptoms that Audacity exhibits when it tries to manage cloud drives with notoriously sloppy access.
What was the drive before this one?
Is it spinning metal and not Solid State? Does it try to “go to sleep” periodically during operation? That can cause access problems.
The advice for Cloud Drives is do all the work on an internal drive and do all the transfers on and off the “drive” outside of Audacity. Only use the services for archive and long storage, not second-by-second editing.
Avoid doing production in MP3. MP3 creates sound damage and it gets worse as you edit. You can’t stop it.
i could run .aup files from C:\ but i don’t have the room on that drive to maintain so many files
If you can’t edit an hour show on your internal drive, you may have just posted the real problem.
The drive specifications have the RPM as “Other” and it’s powered from the USB cable, so it’s probably an SSD and that’s not it.
I think it’s the Party Line that you upgrade to 3.0.2. It fixed a lot of problems in 3.0.0. If that still doesn’t work, it’s possible go back to 2.4.2 from the posted archives if you didn’t keep the installer.
Are you following digital hygiene? Be able to point to two separate places that have your valuable work? Internal Drive, External Drive, Cloud Backup and Flash Drives all count as one. Two folders on your internal drive doesn’t count. I recently rescued some valuable work from a large Windows machine because I had copied the work to a second internal hard drive. The main hard drive went into the dirt, but I got the work from the second drive.
Oddly, three or more doesn’t count, either. Nobody keeps three drives current.
the photos on C:\ are backed up to a different external than the one I am currently trying to use for the podcast. I haven’t tried moving my podcast files to the photo external hdd to see if it has the same problem.
but I did re-download 2.4.2 to work with my original files for now.