Unitary Project - issue tracking

This page is to track the early issues with Unitary Project. Later we may start using Bugzilla.

UP-01 - initial launch

initial launch message

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

Launched OK but when I went to Save the empty project (a practice we recommend) the Save Project was grayed-out and unavailable.

This is a regression on 2.4.2 and earlier.

UP-03 - Drag&Drop

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

On Mac I can't drag&drop onto either the Audacity icon in the apps bar or an open Audacity project

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 Mac

Amplify works on Linux

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 ...

had I done that with 2.4.2 it would have offered Niamh's.aup so I was expecting Niamh's.aup3

Windows - but the offered name is left blank, which I prefer. Initial location offered is ...\Documents\Audacity, plus the previously used location is remembered and re-used on next use, as previously in earlier Audacities.

Mac - Location offered id 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 id Documents - offered name is left blank.

UP-07 - new project save name and location

Saving a new project - odd name and location offered

This time made a short recording an went to save the project

a) I get offered a different inappropriate name - see image

with 2.4.2 this File Name field would be blank for the user to type

b) note that when I click the down arrow I get offered a duplicate of UP1.aup3

Windows

Mac

Linux

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: Initial location offered is ...\Documents\Audacity, plus the previously used location is remembered and re-used on next use, as previously in earlier Audacity.

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.

I'm not sure which is the "better" behavior - Win or Mac ?

• Steve 02Jul20: Users should be able to set a default save location one way or another. If not by "last used", then perhaps as a Preference setting (many users have requested a Preference setting rather than "last used", though there are pros and cons to both schemes).

UP-09 - error opening empty project

Mac

On Mac trying to open a saved with File > Open of an empty project results in a crash - with Audacity 3.0.0 e7fd679

On Mac opening an empty project causes an immediate crash - and the spinning beachball-of-death !

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

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

1. Import 3-hour WAV 1:31
2. Amplify 3-hour audio 2:07
3. Export 3-hour WAV 2:16
4. Export as 3-hour MP3 4:36
5. Import 3-hour MP3 2:07

2.4.2

1. Import 3-hour WAV 0:50
2. Amplify 3-hour audio 0.50
3. Export 3-hour WAV 1:30
4. Export as 3-hour MP3 4:35
5. Import 3-hour MP3 1:12

UP-11 - MIDI

MIDI

On both W10 and macOS Catalina I can

• import MIDI files
• play MIDI tracks

UP-12 - recent files list

recent files list

On Mac the Recent Files list is a bit iffy (Steve said the same about Linux)

Also seems iffy on Windows

UP-13 - Move and Rename

Move and Rename

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-14 - Recovery

Recovery

Testing with a simulated crash.

Windows

Windows: I get a warning message

It tells me that the project is recovered (and auditioning it that seems to be true). But the "... last snapshot" is a bit worrying.

Mac

Phase-1: recovery failed on Mac I get

>Error Opening Project
>Error: XML declaration not well-formed at line 1

With Phase-2 Audacity 3.0.0 e7fd679 I now get a Crash on Mac. I get offered recovery but when I OK that I get the crash

Linux

Recovery fails:

 > Unable to parse project information.

UP-15 - cannot update a project

Linux

cannot update a project on Linux

On Linux: Attempting to resave a project (to update the saved project) opens a file browser.

Continuing with the save from step to overwrite / update the project gives an assert.

Clicking "Continue" gives the error:
"Could not save project. Perhaps /home/steve/Desktop/test3-reset.aup3
is not writable or the disk is full.

so at present it is not possible to update a project.

Steve: Attempting to update a saved project leaves the project in a state that cannot be reopened. I can provide more details about this if required.

Windows

works properly with Audacity 3.0.0 e7fd679

Mac

On Mac I get an error message when I try to save an updated project - Audacity 3.0.0 e7fd679
Error Saving Projecty
Could not save project perhaps ... is not writable or the disk is full

If I save to a different name the save goes ahead. But I can't reopen it. With Phase-2 Audacity 3.0.0 e7fd679 I can now open the updated project with the different name.

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)

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.

UP-18 Closing Audacity is slower with UP-3.0.0

Closing Audacity is slower with UP-3.0.0

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).

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

• Bug #2188 ENH: No warning is given on project opening that the project is not self-contained and relies on aliased file(s
• 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.

1. would involve a silent copy-in. We would not need to alert the user.
2. 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

new Backup Project 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:

As this was discussed openly on the devel mailing list and no-one else chipped-in, I think we are now good to go with this - so please (QA says) go ahead and implement this.