How to be sure project is saved?

[dgpretzel]

Thank you.

I tried it, but got error messages from foobar200.

It's OK, I just started over.

Thank you for your help.

DG

[kozikowski]

They are usually playable in Windows Media Player.

error messages from foobar200.

I'm foggy why we went out to external music players. The AU files open and play individually in Audacity, right? Unless, of course, they're broken.

Could it have created orphan files

I don't think you created anything. My favorite Conspiracy Theory has the Audacity Project format stressing the computer. I don't know of any other program that makes a storage system manage thousands of individual, tiny files in sequence like this. This is different from saving large files. I can imagine a hard drive armature getting warm and starting to miss, particularly if the drive is partially fragmented and there are no continuous, empty spaces available. If I was going to design a drive stress test, this would be it. Not everybody's machine survives. Other than pulling the plug before a save was completed, I know of no other reason for a project to fail—yet they do.

Can you imagine if bookkeeping or spreadsheets randomly turned up broken? Accounting files may be large and complicated, but they're not a blizzard of small files. Projects are unique that way and sometimes they're unique into the bin.

Koz

[kozikowski]

Do you have any idea how hard it is to buy tin foil these days? If you try it on-line you get not so subtly redirected.

Tin Foil > > > Reynolds Wrap Heavy Duty Aluminum Foil.

Aluminum foil is not nearly so good with the, you know, rays.

Koz

[waxcylinder]

My favorite Conspiracy Theory has the Audacity Project format stressing the computer. I don't know of any other program that makes a storage system manage thousands of individual, tiny files in sequence like this. This is different from saving large files. I can imagine a hard drive armature getting warm and starting to miss, particularly if the drive is partially fragmented and there are no continuous, empty spaces available. If I was going to design a drive stress test, this would be it. Not everybody's machine survives. Other than pulling the plug before a save was completed, I know of no other reason for a project to fail—yet they do.

Can you imagine if bookkeeping or spreadsheets randomly turned up broken? Accounting files may be large and complicated, but they're not a blizzard of small files. Projects are unique that way and sometimes they're unique into the bin.

Which is precisely why the next major development project we are about to work on is a Unified Project format - a single file container for the whole project. No more itty-bitty 6-second files.

Works is due to start on this as soon as the soon to be upcoming version 2.4.2 release is our the door. the initial planning and thinking is already underway.

Peter.

[steve]

I don't know of any other program that makes a storage system manage thousands of individual, tiny files in sequence like this.

Despite the drawbacks, it is an (almost) unique stroke of genius. It's because of the thousands of individual "blockfiles" that you can delete or modify a couple of seconds in the middle of a massively long track, and the waveform is updated almost instantly (rather than having to wait, possibly minutes, for the modification to be written to disk. Without using blockfiles, it would be necessary to read and write the entire track for every edit. With blockfiles a small edit may require reading / writing only 6 seconds of audio.

Accounting files may be large and complicated, but they're not a blizzard of small files.

That's a good analogy, and very relevant to how the new single file project format will work. Spreadsheets typically store many fragments of data within a single database-like structure that allows random access to the fragments. In the case of Audacity, those "fragments of data" are small blocks of audio. The new part of the new format is the database-like structure that contains all of those fragments in a single file, while still allowing fast access to any block anywhere in the file.

[dgpretzel]

Do you have any idea how hard it is to buy tin foil these days? If you try it on-line you get not so subtly redirected.

Tin Foil > > > Reynolds Wrap Heavy Duty Aluminum Foil.

Aluminum foil is not nearly so good with the, you know, rays.

Koz

ROTFLOL



DG

[dgpretzel]

I don't know of any other program that makes a storage system manage thousands of individual, tiny files in sequence like this.

Despite the drawbacks, it is an (almost) unique stroke of genius. It's because of the thousands of individual "blockfiles" that you can delete or modify a couple of seconds in the middle of a massively long track, and the waveform is updated almost instantly (rather than having to wait, possibly minutes, for the modification to be written to disk. Without using blockfiles, it would be necessary to read and write the entire track for every edit. With blockfiles a small edit may require reading / writing only 6 seconds of audio.

Accounting files may be large and complicated, but they're not a blizzard of small files.

That's a good analogy, and very relevant to how the new single file project format will work. Spreadsheets typically store many fragments of data within a single database-like structure that allows random access to the fragments. In the case of Audacity, those "fragments of data" are small blocks of audio. The new part of the new format is the database-like structure that contains all of those fragments in a single file, while still allowing fast access to any block anywhere in the file.

Thank you for the preview of future strategy.

DG