Unitary Project - issue tracking
|This page is to track the early issues with Unitary Project.
- UP-1 initial launch
- UP-2 Save Project grayed-out
- UP-3 Drag&Drop - OK on Win and Linux, not working on Mac
- UP-4 more on Save Project
- UP-5 Amplify crashes
- UP-6 Save location and name
- UP-7 new project save name and location
- UP-8 last-used location not remembered
- UP-9 error opening empty project
- UP-10 timing tests - an ongoing activity
- UP-11 MIDI
- UP-12 recent files list
- UP-13 Move and Rename a closed project () UP-13a Move after Closing
- UP-14 Recovery - On W10 is this just the way it is? Fails on Mac
- UP-15 cannot update a project
- UP-16 Nyquist EGATs crash
- UP-17 Projects can be larger on UP-3.0.0 - an ongoing activity
- UP-18 Closing Audacity is slower with UP-3.0.0 - an ongoing activity
- UP-19 Easier opening and deleting
- UP-20 Aliased Projects - Bugs 2188 & 2187 - works fine on Win - yet to be tested on Mac and Linux
- UP-21 Backup command
- UP-22 Import .aup projects - wooks fine on W10 and Linux - just needs testing on Mac
- UP-23 Macro commands: Save Copy and Save Project2
- UP-24 Timer Record
- UP-25 Test disk-space exhaustion
- UP-26 Stress Tests- an ongoing activity
- UP-27 Deleting, Moving renaming active project files - OK on Win, untested on Mac, fails on Linux
- UP-28 Use of OS to create a copy project
- UP-29 Save Project does not propagate project name to Audacity window - OK on Win, untested on Mac or Linux
- UP-30 On Mac second use of Save Project as has bad name/location
- UP-31 X-platform compatibility of AUP3 project files
- UP-32 Backup Projects show error on opening
- UP-33 History window shows misleading "space used"
- UP-34 Dirty Project-1 Corrupted unopenable project
- UP-35 Dirty Project-2 bloat retention
- UP-36 Failure to Save new empty project
On initial launch I got a message asking if I wanted to associate .aup3 files with Audacity to click on for launch.
I never normally see such a message with any new versions. I don't get this on Mac Catalina. Leland says that this is expected behavior.
This was a regression on 2.4.2 and earlier.
- Drag&Drop of an .aup3 file onto an audacity.exe in Windows Explorer or a desktop shortcut icon for it
- Drag&Drop of an .aup3 file onto an open Audacity Window adds that project to the open project.
- Drag&Drop of an .aup file onto an open Audacity Window succeeds (it adds to the open project)
- Drag&Drop of an .aup3 file onto an Audacity app in Finder or the Audacity icon in the apps bar
Bill 17Jul2020: This behaviour is the same as 242 on Catalina. Drag&drop an AUP or audio file onto the Dock icon or Application icon when Audacity is not running (in 242) works. Do the same when Audacity is running and it does not work. Same now in 300. So it looks like we need to address the underlying issue on Catalina. This is bug 2347.
- Drag&Drop of an .aup3 file onto an open Audacity Window fails
Bill 17Jul2020: This now kind of works. Drag&drop an AUP3 into an empty Audacity window results in the project opening, but the project remains "untitled" (window title bar still reads "Audacity"). Closing the project window results in a "Save changes?" dialog. Surely this should just open the project, the same as File > Open.
- Drag&Drop of an .aup file onto an open Audacity Window -
behaviour unknown for now
Bill 17Jul2020: Again, this kind of works. Drag&drop an AUP file into an empty project window and the AUP is imported, but the project window remains "Audacity". Seems to me the project name and window title should become the name of the AUP project that was imported. However you can drag&drop an AUP file into a non-empty project window and the AUP project will be imported into new tracks. So perhaps the project should remain untitled in these cases.
I imported a file with drag&drop from my desktop, when I went to Save the Project I was offered
a) a very unsuitable location "Session Data" folder - should be last used save location or default location if first ever save
b) a rather oddly constructed name ...
BUT on Mac it's always Documents after relaunching Audacity. While Audacity remains open the last-used location is remembered, bur is lost when Audacity is closed. See UP-08 below.
If I Save a project to a folder location while I have Audacity open and do Save As - I get offered that location
But if I close and reopen Audacity the the offered location is "Session Data" again and not the last-used location from previous use of Audacity.
UP-3.0.0 is a little slower than 2.4.2 right now 0 except for MP3 export which seems bang on the money.
Amplify takes more than double the time though.
Test file is a 3-hour stereo audio file
- Import 3-hour WAV 1:31
- Amplify 3-hour audio 2:07
- Export 3-hour WAV 2:16
- Export as 3-hour MP3 4:36
- Import 3-hour MP3 2:07
- Import 3-hour WAV 0:50
- Amplify 3-hour audio 0.50
- Export 3-hour WAV 1:30
- Export as 3-hour MP3 4:35
- Import 3-hour MP3 1:12
Peter 15Jul20: I did some further timing tests on my Zurich PC today. Also an i7 256 SSD machine, but it seems faster than the HP Envy I have in Manchester for the 2.4.2 tests.
- Import 3-hour WAV 0:35
- Amplify 3-hour audio 0:44
- Export 3-hour WAV 1:12
- Export as 3-hour MP3 3:37
- Import 3-hour MP3 1:03
- Import 3-hour WAV 0:15
- Amplify 3-hour audio 0.18
- Export 3-hour WAV 1:07
- Export as 3-hour MP3 3:40
- Import 3-hour MP3 0:45
On both W10 and macOS Catalina I can
- import MIDI files
- play MIDI tracks
On Mac the Recent Files list is a bit iffy (Steve said the same about Linux)
Also seems iffy on Windows
Leland 07Jul20 Temporary filenames are showing up in the file history. Haven't looked into why as yet.
On W10 and mcOS Catalina I can:
- rename a .aup3 file
- move a .aup3 file to a different folder
and in both cases Audacity successfully opens it.
This is GREAT - as this is a tangle with old projects where losers could trip up and lose/damage their projects.
It's unclear if this is a bug or desired behaviour. It will go away if we clear the clipboard on closing a project. Paul is very very keen on keeping the clipboard around after closing the Audacity project.
Paul 07Jul20 I'm no longer very keen: I wanted to keep old behavior if it was not difficult to do safely, but now I have been persuaded that there are enough hidden difficulties.
And Paul has now fixed this. RM is fine with the tiny 'regression', that you can close a project and lose a clipboard that previously would have hung around until you close Audacity (and that caused all sorts of problems).
Testing with a simulated crash.
But I can successfully reopen the project and it tells me its recovered to the last snapshot.
Is this the "new form or recovery" ?
- Peter 06Jul20: I'm thinking yes it is
- Most users will realize that Audacity has crashed and can then just go and re-open their project (just as they would with Excel and Word). And for any user that just abandons a crashed project and comes back to it many months later and it will still tell 'em it's recovered to the last snapshot.
If I try to re-open the project I get:
>Error Opening Project
>Unable to parse project information.
> Unable to parse project information.
Phase-1 On Windows and Mac most shipped Nyquist effects, generators, analyzers and tools crash Audacity.
The only three that work are
- Rhythm track
Initially Projects in UP-3.0.0 could be much larger than the equivalent project in 2.4.3
Projects are slightly larger as they develop on 3.0.0 than 2.4.2 - but on exiting Audacity 2.4.2 releases space whereas 3.0.0 does not. "Vacuuming" is what is needed, but when and with what trigger(s)
testing on Audacity 3.0.0 6c2cd20 - the bloat-space is released on exit from Audacity (it is slow though seeUP-18)
Testing with a 5 hour mono chirp
- Audacity 3.0.0 0fbabb0 the .aup3 file occupies 3.134GB
- Audacity 2.4.2 the ,aup and data folder occupy 2.99GB
This for me is within acceptable limits
- Is this acceptably fast for a one-hour mono project ?
I've not tested this extensively, but closing a saved project seems to take a lot longer than closing an unsaved project.
I'm finding that just after a couple of days testing the UP is much easier to manage:
- Open: only one thing to look for, you don't get confused trying to "Open" the data folder
- Delete: also only one thing to look for - and on W10 at least the folders and files are always separated so tour aup could be a long way away from its data folder (which could lead to fumble-fingers trouble)
It is possible that some users may still have projects that are relying on aliased files - and note that ODL has been removed from 3.0.0
- P1 Bug #2188 ENH: No warning is given on project opening that the project is not self-contained and relies on aliased file(s
- P2 Bug #2187 -
Silent crash withno error message when using a missing aliased audio file
In 3.0.0 Save Compressed Copy of Project and Save Compressed Copy of Project
QA discussed the Backup Project issue and rapidly reached agreement.
1) QA likes the short form of the command File > Save Project > Backup Project
2) And QA agrees that there should be no overwrite of backup projects (or any other projects with the Backup command).
Accordingly the current error message used for the deprecated Save Lossless... and Save Compressed... can be used as-is:
- Windows - works properly - can be opened or imported
- Mac - behavior unknown
- Linux - Steve reported by emails that this works properly
- the new backup Macro command "Save Copy" offers a file with extension .aup and not .aup3
- the existing Macro command "Save Project2" offers a file with extension .aup and not .aup3
The new backup Macro command "Save Copy" appears to effectively be a duplicate of "Save Project2"
- Leland 07Jul20: it’s really not a duplicate (I had the feeling at first too). The difference is that once “Save Project2” writes out the new file, that file becomes the active one. With “Save Backup” the original file remains the active one.
Tested with Automatic save and Automatic Export
Paul indicates that this may have changed with SQLite 3.0.0 - so needs re-checking.
Leland 07Jul20: On Windows we get an exception loop. On Linux we get an unhandled exception. On OSX it's a bit weird. We don't get a crash, but some of the menus no longer work...like I can't Quit even though the menu item appears to be available.
- Very long projects
- Peter 14Jul20: Overnight I tested a Timed Recording of 5 hours and dis the production work to whittle it down to the required 2 hours and exported - all on Audacity 3.0.0 0fbabb0. Audio was fine - I had a label track issue that I can't now reproduce.
- Simultaneous playback and recording
- James requested: Can you do some testing of play-through record please Peter? The point there is that we are both reading and writing the database, so there might possibly (low probability) be new issues around lock files. It's unlikely, but let's find out. So for worst results, play back a mix of 4 stereo channels, and record stereo and at the highest sampling rate your card offers at the same time. If we're unlucky this might get SQLite in a twist. It might try to do things in big batches and lock us out for too long.
- This worked fine on W10 with my Edirol UA-1EX
- Projects with many, many, tracks
- If I use Save Project
- the project is saved with the correct name
- but the project name does not propagate to the top banner of the Audacity window, ir remains as "Audacity"
- If I use Save Project As - then the project name does NOT propagate to renaming the banner.
On Mac when I first use Save Project As I get a blank filename offered and Documents as the location (which is good)
When I next use Save Project As a) The location offered is Session Data (this is bad) b) The project name field has: New Project 2020-07-10 11-53-11N-2.aupunsaved.aup3 - which looks like a temp filename c) Pressing Save button saves it with that rubbishy file name
Windows is not similarly affected
Paul raised this issue by email.
- We do not expect it to be cross platform at the moment. Our integers are the wrong way round.
- As RM I expect us to be revisiting the binary format and using a fixed endianness.
- It will not hurt performance.
- I also expect to use a more compact autosave format than now, but not zipped, better for recording, and to be doing that during 3.0.0.
Steve wrote by email: I'm frequently seeing the error message when opening a backup:
- "This project was not saved properly the last time Audacity ran.
- It has been recovered to the last snapshot."
Steps to reproduce:
- Launch Audacity
- Generate "Chirp"
- "Save Project" - name it "a"
- "Backup Project" - name it "b"
- "Undo" (undo Amplify)
- "Undo" (Undo Chirp)
- Generate "Tone"
- "Save Project" (updates "a")
- Exit Audacity
- Relaunch Audacity
- "Open" -> select project "b".
- Observe: "This project was not saved properly the last time Audacity ran. It has been recovered to the last snapshot."
Steve 13Jul20: fixed in commit 6f233cbff
- Peter 13Jul20: Confirmed on W10 with Audacity 3.0.0 6f233cb
The "Total space used" in the History window may indicate much less than the size on disk.
Steps to reproduce:
- Generate 1 hour Rhythm Track
- Save Project
- Generate 1 second "pluck"
- Observe: The project size is over 600 MB with 1 second of audio and hardly any Undo history (only the "Pluck").
- Observe: "View menu > History" shows: "Total space used: 172.3 KB"
- For the History window to indicate both "total space used" and "size on disk" for the project.
- For the History window to provide an option to "compact project" (vacuum the project) to reclaim disk space.
Peter 16Jul20: Steve wrote by email: This is looking better, but I'm not sure that compacting is working correctly.
I've been playing with a project, adding long tracks and deleting them to build up a large database, then deleting all tracks and generating a 1 second "ping".
- On saving and closing, the AUP3 file was 1.3GB.
- On "compacting" with "DB Browser for SQLite", the file size went down to 524.3 kB (524,288 bytes).
The checkbox "Compact at close" is selected.
Corrupted unopenable project
- Import some audio.
- Save and name the project - note file size
- Close the track.
- Generate something
- Close the project
- “Save Changes?” - No
- Observe: project is compacted - note file size has changed
- attempt to open the project
- Observe: "Message: failed to retrieve samples”
Reported by Bill on Mac, confirmed by Peter on Windows
Bill 17Jul2020: With build _1f87d4f, at step 7 the file size does not change significantly; at step 9 the project opens properly showing the audio imported in step 1.
Unremovable database bloat.
- Import some audio.
- Save and name the project - note file size
- Add new mono track
- Generate something (substantial - like 30 minutes) into it
- Close the project
- Observe: note file size has increased
- “Save Changes?” - No
- Observe: project is not compacted
- Observe: file size indicates that the samples for the generated track are stored in the file
- Open the project
- Observe: the generated track is not there, as expected
There seems to be no way to get rid of the bloat.
Reported by Bill on Mac and confirmed by Peter on W10
Bill 17Jul2020: with build 1f87d4f there is no bloat at step 9; seems fixed
- Launch Audacity
- File > Save Project > Save Project (or Save Project As)
- Observe: error message disk full or unwritable
- Record a little, or import audio
- Delete the new track (to empty project)
- File > Save Project > Save Project
- Observe: warning - your project is empty
- Click "Yes"
- Observe: empty project is now saved (and tests Ok on reopening)
Note that at Step 4 if you just add a new empty track, this still fails at Step 9 with the error message disk full or unwritable
Tests were on W10 with Audacity 3.0.0 6ffced4
This is a regression on earlier 3.0.0 alpha builds - but there is a possibility that this may be a Microsoft issue - as they served me with yet another security upgrade this morning.
Bill 17Jul2020: Confirmed on Mac with build c174b25
Bill 17Jul2020: With build 1f87d4f, no error after step 2; at step 7 get warning "Your project is now empty..."; click Yes, project is saved