Audacity Passes a Huge File Test
Posted: Thu Feb 16, 2012 6:23 am
All,
I wasn't deliberately intending to test Audacity*, but this is the second time in recent months that I've tried to use it to edit a rather large MP3 file.
By the way, my reason for writing is NOT to report a problem, but rather to report that it works like a charm, even with an extraordinarily large file. In a previous project from last year, the forum seemed surprised that I had been working with an imported MP3 recording that was 12 hours long. I was kind of surprised, too, but perhaps you folks responsible for developing Audacity already knew this was possible.
This time, though, I had a bigger project to work on. The MP3 file was just over 380 MBytes -- yes, you read that correctly -- and the length of the recording is -- get this -- 35 hours, 31 minutes long. I kid you not! When I opened the file for the first time, since I had no info regarding the time/length of the recording, I opened it for the first time using VLC Media Player. I didn't believe what I was seeing, so I also tried to open this huge MP3 file in Sony Sound Forge, Audacity, and WinAmp, but all these programs indicated the same 35-hour-plus length.
My suggestion: Don't edit files this big with just 2 GBytes of RAM. Although I made just one modest edit, I decided to save the project just to be sure it would work; it took 6 minutes to save the project, but by saying that, I'm surely not complaining. Interestingly, although the MP3 file I imported was 380 MBytes, after the one minor test edit I made, I observed that the AUP file was 900 KBytes with a Data directory having the following properties: 5,861 files in 24 sub-directories, consuming 5.8 GBytes of disk space. Is that normal? Does that surprise Audacity's developers?
Closing this project was easy/fast and re-opening it took just a second or so. I happily noticed the project opened with Audacity displaying the portion of the time-line where I had last been working on the project, and the display had zoomed-in just as I had been when I closed the project.
Simply beautiful! I think it's time to make another donation. I really like using Audacity and expressing my appreciation is the least I can do. Thank you all very much!
Tony M.
* System Info: I'm using version 1.3.14-beta (build date Dec 8, 2011) on a Windows Vista Home Premium system with 2 GBytes of RAM
I wasn't deliberately intending to test Audacity*, but this is the second time in recent months that I've tried to use it to edit a rather large MP3 file.
By the way, my reason for writing is NOT to report a problem, but rather to report that it works like a charm, even with an extraordinarily large file. In a previous project from last year, the forum seemed surprised that I had been working with an imported MP3 recording that was 12 hours long. I was kind of surprised, too, but perhaps you folks responsible for developing Audacity already knew this was possible.
This time, though, I had a bigger project to work on. The MP3 file was just over 380 MBytes -- yes, you read that correctly -- and the length of the recording is -- get this -- 35 hours, 31 minutes long. I kid you not! When I opened the file for the first time, since I had no info regarding the time/length of the recording, I opened it for the first time using VLC Media Player. I didn't believe what I was seeing, so I also tried to open this huge MP3 file in Sony Sound Forge, Audacity, and WinAmp, but all these programs indicated the same 35-hour-plus length.
My suggestion: Don't edit files this big with just 2 GBytes of RAM. Although I made just one modest edit, I decided to save the project just to be sure it would work; it took 6 minutes to save the project, but by saying that, I'm surely not complaining. Interestingly, although the MP3 file I imported was 380 MBytes, after the one minor test edit I made, I observed that the AUP file was 900 KBytes with a Data directory having the following properties: 5,861 files in 24 sub-directories, consuming 5.8 GBytes of disk space. Is that normal? Does that surprise Audacity's developers?
Closing this project was easy/fast and re-opening it took just a second or so. I happily noticed the project opened with Audacity displaying the portion of the time-line where I had last been working on the project, and the display had zoomed-in just as I had been when I closed the project.
Simply beautiful! I think it's time to make another donation. I really like using Audacity and expressing my appreciation is the least I can do. Thank you all very much!
Tony M.
* System Info: I'm using version 1.3.14-beta (build date Dec 8, 2011) on a Windows Vista Home Premium system with 2 GBytes of RAM