Problemas ao abrir e recuperar arquivos na versão 3.3.3 (Flatpak)

Audacity 3 Help Forum
1

OS Ubuntu Studio 22.04

I currently use Audacity 3.3.3 via Flatpak and I can’t open the files (even though they are aup3) directly. I need to open the program first and click on the “Open” option or generate “CTRL+O”, which is more annoying because it is less accurate and faster.

Another problem is that when closing the AUP3 file, it takes hours to close and warnings appear that it is “compiling” the data (for more than half an hour). If you close the program while the process is running, it corrupts the AUP3 that was being saved. I would like to know if it is an update issue of this Audacity flatpak package or if it is a FFMPEG related issue.

I generated some logs to try to better highlight this problem.

LOG 1

06:17:47: Audacity 3.3.3
06:17:47: sqlite3 message: (1) no such table: project in “SELECT 1 FROM project LIMIT 1;”
06:17:47: FFmpeg libraries loaded successfully from: /app/lib/codecs/lib/libavformat.so.60.3.100

LOG 2

06:17:47: Audacity 3.3.3
06:17:47: sqlite3 message: (1) no such table: project in “SELECT 1 FROM project LIMIT 1;”
06:17:47: FFmpeg libraries loaded successfully from: /app/lib/codecs/lib/libavformat.so.60.3.100

As for the corrupt file issue:

LOG 1

08:05:26: Audacity 3.3.3
08:05:26: sqlite3 message: (1) no such table: project in “SELECT 1 FROM project LIMIT 1;”
08:05:26: FFmpeg libraries loaded successfully from: /app/lib/codecs/lib/libavformat.so.60.3.100
08:05:30: sqlite3 message: (11) database corruption at line 67916 of [a26b6597e3]
08:05:30: sqlite3 message: (11) database disk image is malformed in “SELECT 1 FROM project LIMIT 1;”
08:06:32: sqlite3 message: (11) database corruption at line 66588 of [a26b6597e3]
08:06:32: sqlite3 message: (11) database corruption at line 66738 of [a26b6597e3]
08:06:32: sqlite3 message: (11) statement aborts at 10: [INSERT INTO vacuum_db.‘sampleblocks’ SELECT*FROM"main".‘sampleblocks’] database disk image is malformed
08:06:32: sqlite3 message: (11) statement aborts at 1: [VACUUM;] database disk image is malformed
08:06:32: Failed to set mode on /media/pseudoproducer/Reserva/03_-PRODUÇÃO AUDIOVISUAL/Production Fonográfica/UTAU Bancos de voz/Amai/Colônia/Colônia MULTICV.aup3
Error: database disk image is malformed
SQL: PRAGMA main.page_size = 65536;VACUUM;
08:06:32: DBConnection SetDBError
ErrorCode: 11
LastError: Failed to set page size for database /media/pseudoproducer/Reserva/03-_PRODUÇÃO AUDIOVISUAL/Produtora Fonográfica/UTAU Bancos de voz/Amai/Colônia/Colônia MULTICV.aup3
LibraryError: database disk image is malformed
08:06:32: DBConnection SetError
ErrorCode: 11
LastError: Failed to open database file:

/media/pseudoproducer/Reserva/03_-_PRODUÇÃO AUDIOVISUAL/Phonographic Production/UTAU Voice Banks/Amai/Colônia/Colônia MULTICV.aup3
LibraryError: (11): database disk image is malformed

LOG 2

08:26:06: Audacity 3.3.3
08:26:06: sqlite3 message: (1) no such table: project in “SELECT 1 FROM project LIMIT 1;”
08:26:06: FFmpeg libraries loaded successfully from: /app/lib/codecs/lib/libavformat.so.60.3.100
08:26:31: sqlite3 message: (283) recovered 9 frames from WAL file /var/tmp/audacity-pseudoproducer/New Project 2023-06-24 08-24-32 N-2.aup3unsaved-wal
08:26:38: sqlite3 message: (1) no such table: project in “SELECT 1 FROM project LIMIT 1;”
08:26:38: sqlite3 message: (283) recovered 2 frames from WAL file /var/tmp/audacity-pseudoproducer/New Project 2023-06-24 08-18-22 N-1.aup3unsaved-wal
08:26:38: Loaded 65 string 2.539062 Kb in size
08:26:38: Project loaded in 20 ms
08:27:23: sqlite3 message: (1) no such table: project in “SELECT 1 FROM project LIMIT 1;”
08:27:35: sqlite3 message: (11) database corruption at line 67916 of [a26b6597e3]
08:27:35: sqlite3 message: (11) database disk image is malformed in “SELECT 1 FROM project LIMIT 1;”
08:27:39: sqlite3 message: (11) database corruption at line 66588 of [a26b6597e3]
08:27:39: sqlite3 message: (11) database corruption at line 66738 of [a26b6597e3]
08:27:39: sqlite3 message: (11) statement aborts at 10: [INSERT INTO vacuum_db.‘sampleblocks’ SELECT*FROM"main".‘sampleblocks’] database disk image is malformed
08:27:39: sqlite3 message: (11) statement aborts at 1: [VACUUM;] database disk image is malformed
08:27:39: Failed to set mode on /media/pseudoproducer/Reserva/03_-PRODUÇÃO AUDIOVISUAL/Production Fonográfica/UTAU Bancos de voz/Amai/Colônia/Colônia MULTICV.aup3
Error: database disk image is malformed
SQL: PRAGMA main.page_size = 65536;VACUUM;
08:27:39: DBConnection SetDBError
ErrorCode: 11
LastError: Failed to set page size for database /media/pseudoproducer/Reserva/03-_PRODUÇÃO AUDIOVISUAL/Produtora Fonográfica/UTAU Bancos de voz/Amai/Colônia/Colônia MULTICV.aup3
LibraryError: database disk image is malformed
08:27:39: DBConnection SetError
ErrorCode: 11
LastError: Failed to open database file:

/media/pseudoproducer/Reserva/03_-_PRODUÇÃO AUDIOVISUAL/Phonographic Production/UTAU Banco

2

No - the first two log files are the same as everyone gets. These are solely informational.

Well that would be compacting. As you edit your Audacity project, Audacity keeps track of everything you have done and maintains an undo buffer so that any and all of the work you have done can be “undone”. As you continue your edits, the undo buffer gets larger and larger. When you are finally happy with the results and close the project, Audacity compacts the database and discards all of that temporary data. Yes you are right - this can take a while.

I usually take frequent breaks and close my .aup3 project database, probably at least once an hour and generally more often.

Yes - as you have learned - do NOT try to abort the database cleanup phase. It can lead to those error 11 = corrupt database errors. Also, see: Corrupt or Otherwise Broken Audacity Project Recovery

3

Thank you for the provided and detailed information. I was taken by surprise because I’ve been using the AUP compression method for many years and I think that because it has a separate folder, the way it processed large files seemed to me to be safer and faster. Thanks for passing the link on how to deal with corrupted files, I’ll look into reading that.

4

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