Project file size is too big

Hi,
I created a project, saved the file (say, as v001) and then performed some operations, like amplify, and fade in and out. Then I saved this as a v002.
The first file (v001) is 250 mg, the second one (v002) is 5 GIGs and a half.

I “suppose” it’s because of the History of what I did but, why, when opening the v002, the History is empty, even though the file still weight 5 GIGs?
Is there any ways to get rid of this? (I save versions, I don’t want to keep this History)

I tried what someone suggested, that is: select all, copy, create new project, paste and select “do not copy smart clip”. First of all, I do not get a popup giving me the opportunity to “not copy smart clip” AND, the option in Preferences: “Ask me each time” IS checked. The project file is still huge.

Anyone can help me with this? How can I get ride of the History (well, funny thing is, there is no History and the file is still huge) and regain small size project files?

Oh and I just updated Audacity 30m ago (in case someone tells me that the recent version has corrected this)

Thanx

Stephane

Do you still have the first (v001) version?

If you do, make a backup copy of it, then try applying the same operations and see if it does it again. Make a note (pen and paper) of each operation as you go, and check the project size each time.

Is there a particular operation that causes the bloat?

When you close the project, the project size should go down as the undo history is removed from the project. If there is a lot of undo data, it could take several minutes for the undo data to be properly removed (you may see a message saying “Compacting” or something similar while this is happening).

Hi Steve,

today, I started another project. Imported a WAV file that makes 300 MG. I added 5 or 6 other very small WAV files under the main 300 MG WAV file. The total of the other small WAV files doesn’t even totalize 50 MG. I performed some fade-ins and fade-outs on the smaller WAV files. Anyway, long story short, the undo said this will now be 700 MG (which in my mind doesn’t quite make sense…unless there’s something I reeeeally don’t get in this process, shouldn’t it weight the addition of all the WAV files, ish?) I do not get any “Compressing” when I close the project. What I did is: Save Project, Exit (no compression occurred), the project size was 700 megs like the undo said it would, and then reopened it, no undo anymore, project file still big.

Then, I tried something else: brand new project (empty), imported the 300 MG WAV file again ONLY, didn’t perform any other tasks, then went in the Undo History right away, and then (you can watch my attached image)


.

How come it doubles the size right from the start?

Thanx

Stephane

What format does the drive have where you want to save the project? If it is FAT32, the maximum file size is around 4 GB. Format your drive to NTFS (Windows) or HFS+ (Mac).

There’s two things happening right at the top. A sound file in Audacity is larger than you think it should be because it’s held in a super high quality format. It does this so you can temporarily cause overload and clipping and then easily recover with zero sound damage. Audiobook Mastering Macro sometimes works this way. So just looking at the file outside of Audacity doesn’t tell you the whole story.

But the truly startling process is UNDO. When you, for example, add a tiny sound file to your production, Audacity makes a clean protection copy of the whole show. If you need to UNDO, Audacity doesn’t try to untangle the tiny sound file, it just plays you the show before you added it. That clean show has to come from somewhere.

Koz

Thanx Koz.

I’ve been in situations where MGs became GIGs very fast. This so called “Compacting”, mentioned in the Help Manual, does it work?

This has never worked for me.

Stephane

oh: what version of Audacity does not have the undo History and does not have this “way” of working with the files? …if that still exists… (not stuff I want to deal with anymore)

There was a forum discussion recently about a process of intentionally flushing the UNDO system to keep a show from outgrowing the machine and “going up in a ball of flame.” Yes, I’m clear that means your UNDO goes away, but I’m good with that if it means my show is likely to stay alive.

Apparently, the program fathers didn’t like the idea and we’re not sure why. My assumption is they’ve never had a large, difficult, valuable show Hindenburg.

I advocated a compromise process where Audacity warns the user about an impending explosion. Surprises are not welcome.

Koz

This started to be a serious problem in Audacity 3.5. I advocated staying on 3.4.2 until they got this resolved.

Koz

Thanx again Koz, will check the 3.4.2 or below :+1:

Stephane

This topic was automatically closed after 30 days. New replies are no longer allowed.