Unitary Project - issue tracking
This page is to track the early issues with Unitary Project.
|
Contents
UP-1 initial launch
UP-2 Save Project grayed-out
UP-3 Drag&Drop
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
UP-11 MIDI
UP-12 recent files list
UP-13 Move and Rename a closed project (
) UP-13a Move after Closing
UP-14 Recovery
UP-15 cannot update a project
UP-16 Nyquist EGATs crash
UP-17 Projects can be larger on UP-3.0.0
UP-18 Closing Audacity is slower with UP-3.0.0
UP-19 Easier opening and deleting
UP-20 Aliased Projects - Bugs 2188 & 2187
UP-21 Backup command
UP-22 Import .aup projects
UP-23 Macro commands: Save Copy and Save Project2
UP-24 Timer Record
UP-25 Test disk-space exhaustion
UP-26 Stress Tests
UP-27 Deleting, Moving renaming active project files
UP-28 Use of OS to create a copy project
UP-29 Save Project does not propagate project name to Audacity window
UP-30 On Mac second use of Save Project as has bad name/location- UP-31
- UP-32
- UP-33
- UP-34
- UP-35
- UP-36
- UP-37
- UP-38
- UP-39
- UP-40
- UP-41
- UP-42
UP-01 - initial launch 
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.
UP-02 - Save Project grayed-out 
initial launch Save Project grayed-out on Win, Mac & Linux
This was a regression on 2.4.2 and earlier.
UP-03 - Drag&Drop 
I can't drag&drop a .aup3 file onto an open Audacity project window. From discussions with Leland I was expecting to be able to.
On Windows I can drag&drop an .aup3 file onto the Audacity app icon on my desktop and it launches - but I still can't drag&drop it onto an open Audacity project
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 fails
On Mac I can't drag&drop onto either the Audacity icon in the apps bar or an open Audacity project
Drag&Drop of an .aup3 file onto an Audacity app in Finder or the Audacity icon in the apps bar
Drag&Drop of an .aup3 file onto an open Audacity Window fails
On Linux, drag & drop projects are not recognized.
UP-04 - more on Save Project 
Once the initial Save As has been made - the for subsequent saves the Save Project is no longer grayed out and I can use it to save.
UP-05 - Amplify crashes 
Amplify works on W10 - and still does with Audacity 3.0.0 e7fd679
UP-06 - Save location and name 
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 ...
Windows - Location offered is Documents\Audacity and the offered name is left blank
Mac - Location offered is Documents - offered name is left blank.
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.
Linux - Location offered is Documents - offered name is left blank.
UP-07 - new project save name and location 
Saving a new project - odd name (based on temp file) and location (Session Data) offered
UP-08 - last-used location not remembered
?
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.
Windows: it's always Documents after relaunching Audacity. While Audacity remains open the last-used location is remembered, but is lost when Audacity is closed.
Mac it's always Documents after relaunching Audacity. While Audacity remains open the last-used location is remembered, but is lost when Audacity is closed.
Linux - it's always Documents after relaunching Audacity. While Audacity remains open the last-used location is remembered, but is lost when Audacity is closed.
UP-09 - error opening empty project 
Mac
On Mac now works with Audacity 3.0.0 51b3b0f
Linux
Linux can open an empty project.
Windows
works properly on W10 with Audacity 3.0.0 e7fd679
UP-10 - timing tests 
further X-platform testing later
Some preliminary timing tests on W10 with Phas-1 build
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
UP-3.0.0
- 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
2.4.2
- 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
UP-11 - MIDI 
On both W10 and macOS Catalina I can
- import MIDI files
- play MIDI tracks
UP-12 - recent files list 
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.
UP-13 - Move and Rename a closed project
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.
UP-13a - Move after Closing 
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).
UP-14 - Recovery 
Testing with a simulated crash.
Windows
Recovery fails - I get a new empty unnamed project opened with no offer of recovery
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.
Mac
Recovery fails - I get a new empty unnamed project opened with no offer of recovery
If I try to re-open the project I get:
>Error Opening Project
>Unable to parse project information.
Linux
> Unable to parse project information.
UP-15 - cannot update a project 
Windows
works properly with Audacity 3.0.0 e7fd679
Mac
works properly with Audacity 3.0.0 e08fb5e
Linux
works properly with Audacity 3.0.0 e08fb5e
UP-16 - Nyquist EGATs crash 
With Phase-2 Audacity 3.0.0 e7fd679 these all now work. I'm guessing that the fix for Amplify crashing also cured all these.
Phase-1 On Windows and Mac most shipped Nyquist effects, generators, analyzers and tools crash Audacity.
The only three that work are
- Tremolo
- Vocoder
- Rhythm track
All above the line effects, generators and analyzers work
Linux - All effects and generators tried so far (including the above three) work correctly.
UP-17 - Projects can be larger on UP-3.0.0 
Projects in UP-3.0.0 can 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)
Leland 06Jul20: The project file should now be about normal after the project is closed. I'll probably want to add a progress dialog.
- Peter 06Jul20: Testing on W10 with Audacity 3.0.0 6c2cd20 confirms that Audacity now releases the not-needed bloat-space on Exit. But this has reverted to being slow again see UP-18
Peter 04Jul20: Saving a project withe 3.0.0 temporarily requires double the disk space as a temporary .bak of the project is created during the save only released when the Save completes. For large projects this could be a problem.
- Leland 06Jul20: Unfortunately, I don't see a way around this. There will always be at least two copies during the save. This is the same for 2.4.2 as well, it's just not as easy to see.
Windows
testing on Audacity 3.0.0 6c2cd20 - the bloat-space is released on exit from Audacity (it is slow though seeUP-18)
Mac
testing on Audacity 3.0.0 6c2cd20 - the bloat-space is released on exit from Audacity (it is much quicker than Windows)
Linux
with Audacity 3.0.0 6c2cd20 - the bloat-space is released on exit from Audacity
Re-test later
we will need to retest later as the UP development project progresses
UP-18 - Closing Audacity is slower with UP-3.0.0 
Closing Audacity is slower with UP-3.0.0
progress bar when closing is slow
further X-platform testing later
A lot of journaling appears to be taking place as the project closes. And this is without "vacuuming" to release unused space see UP17.
This is very noticeable on larger projects (a one-hour mono chirp with a few effects is sufficient).
Peter 03Jul20: Leland made a fix and with Audacity 3.0.0 48287e9 closing Audacity is much quicker, almost instaneous for an already saved project.
Windows
Testing on W10 with Audacity 3.0.0 6c2cd20 - this has reverted to being slow again.
Tests similarly on Mac with Audacity 3.0.0 6c2cd20 with the space being properly on Exit(I can't make the second Save as that is the bug that removes the .aup3 file)
Mac
But Exit or Quit on Mac is much faster than on W10 taking a mere 3-4 seconds cf. 20-plus seconds on W10 with the same project steps.
- Is this acceptably fast for a one-hour mono project ?
Linux
Better than before. It's still slower than 2.4.2, which was virtually instant, but nowhere near as slow as it was initially.
I've not tested this extensively, but closing a saved project seems to take a lot longer than closing an unsaved project.
UP-19 - Easier opening and deleting 
It's much easier to find projects for opening and for deleting them
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)
UP-20 - Aliased Projects 
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
P1 Bug #2187 - Silent crash (with no error message) when using a missing aliased audio file
James wrote by email: The current bug about it still applies. There are good chances we will fix the problem for 3.0.0.
- would involve a silent copy-in. We would not need to alert the user.
- would tell the user about the error.
They would not need to go back to 2.4.2 to correct the problem. There is though the possibility that the bug stays open (unless QA raise it to P1).
Peter replied: I am thus unsure what to do about these two bugs.
As we are going to have a major d/b transition it would be good if we could fix these for 3.0.0
But I'm suspecting that by now there may be very few aliased project - so maybe it's not worth a lot of effort. I'm very undecided right now - but I'm going to log them in this UP-issues page just to keep some focus on them.
UP-21 - Backup command 
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:
UP-22 Import .aup projects 
We need an import utility for .aup projects from Audacity 2.4.2 and earlier.
UP-23 - Macro commands 
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.
UP-24 - Timer Record 
Tested with Automatic save and Automatic Export
UP-25 - Test disk-space exhaustion 
check that disk-space exhaustion error traps still work properly.
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.
UP-26 Stress Tests 
Very long projects
Multi-track projects with lots of tracks
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
UP-27 Deleting, Moving renaming active project files 
Windows
Audacity prevents Deleting, Moving or renaming active project files: .aup -wal and -shm while a project remains open
Mac
Linux
You can delete the -wal and -shm on Linux.
UP-28 Use of OS to create a copy project 
Windows: use Windows Explorer to copy a project. Open it with Audacity
Mac: use Windows Explorer to copy a project. Open it with Audacity
UP-29 Save Project does not propagate project name to Audacity window 
Save Project does not propagate project name to Audacity window
This is a regression on 2.4.2
Windows: Testing on W10 with Audacity 3.0.0 b12fafb
- If I use Save Project
- the project is saved with the correct name
- but the project name does nor propagate to the tip banner of the Audacity window, ir remains as "Audacity"
- If I use Save Project As - then the project name does propagate to renaming the banner.
Mac: Testing on macOS with Audacity 3.0.0 b12fafb
- If I use Save Project
- the project is saved with the correct name
- but the project name does nor propagate to the tip 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.
UP-30 On Mac second use of Save Project as has bad name/location 
On Mac second use of Save Project as has bad name/location
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

