Forced drive type

Feedback and bug reports for the latest alpha version.

Discussions posted here will be archived in the Audacity 3.x Feedback and Reviews archive.
Forum rules
This forum is only for feedback and bug reports for the most recent Audacity alpha version.

All bug reports must include the following information:
  • Exact version number of Audacity
  • Operating system version
  • Brief description of the problem
  • Detailed, step by step instructions for how to reproduce the problem
Bug reports that do not include the above information will be deleted

Additional information and / or screenshots should be included as necessary to adequately describe the problem.
Site Admin
Posts: 81964
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Forced drive type

Post by steve » Tue Apr 13, 2021 4:05 pm

DJ_CoolBreeze wrote:
Tue Apr 13, 2021 3:42 pm
now downloadable on the 'Net (free) in Version 3.01.02:
Please note than "Audacity 3.0.2 rc01" is not an official release.
Please also note that downloading software from unofficial sources is potentially dangerous and definitely NOT recommended.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

Posts: 1
Joined: Mon May 10, 2021 4:28 pm
Operating System: Windows 10

Re: Forced drive type

Post by Digitalblacksmith » Mon May 10, 2021 4:37 pm

Found this thread after bashing my head on this problem.
As a business I have a weekly podcast and we use google drive (filestream) and I collect wav files from hosts. It is an easy way for my team members to share to a common folder. My finished projects run between 400-700MB. This puts me WELL under the FAT limit. However, thanks to this nice 'check' I am forced to quit the software or find a new working directory.

I get the fat check...but make it a warning rather than a hard error. I am happy to work within the limitations. But this should be my choice, not the dev choice.

This may be the breaking point for my use of audacity if it is not fixed. I really don't want to have to create yet another volume, it will be far easier for me to just start using audition instead.

Site Admin
Posts: 81964
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Forced drive type

Post by steve » Mon May 10, 2021 11:57 pm

Here's the issue re. FAT formatted drives:

For Audacity 3.x, a new single file project format was developed.
Why? Because it is heartbreaking to see inexperienced or less technical Audacity users permanently losing their work because they haven't understood the concept of a multi-file project format. Week after week on this forum we would see users that had inadvertently destroyed their own work, sometimes valuable, never to be repeated recordings. In one sad case it was the final words of a relative.

The technical challenge: how to modify data in the middle of a long track without having to write the entire track data (which could be several gigabytes).
The original solution was to split the track data into small "block files" (the ".au" files in the _data folder), but how to do that with a single file format? It is not possible to just write data in the middle of a normal computer file.

The answer was to use a kind of database - SQLite
As with other databases, it is possible to access chunks of data, read them, modify them and write them back to disk. Unlike other databases, SQLite manages to achieve this yet still use a single file format for the database.

After many years of thinking, discussing, and considering very many possible solutions, SQLite looked like the best answer. Two of top developers began working on developing a "Unitary Project Format", based on the SQLite database.

Unfortunately, a snag was discovered:
One one of the platforms that Audacity supports, there is an ancient (44 years old, which is an aeon in computer technology) disk format called FAT, which is still used today. By today's standards, the FAT file system and is very primitive. Among it's many limitations, it does not support file locking, which is required by SQLite in order to perform secure transactions.

There were two choices; either abandon the work, or drop support for FAT. An executive decision was made to drop support for FAT. In this case it was decided that the needs of the many outweighed the needs of the few.

Since Audacity 3.x has been available, the number of cases that we've seen on this forum, of people losing / destroying their projects, has reduced very noticeably. Of the few cases that we have seen recently, most if not all have been using older (2.4.2 or earlier) versions of Audacity, with the old "pile of files" project format.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

Post Reply