Re: Audacity 3.0.0 RC 003 for testing.

On Thu, Feb 25, 2021 at 1:45 PM John Colket <[email protected]> wrote:

> David, Peter,
>
>    Thanks for your reports - now I can enjoy my day out of town in
> peace.  🙂
>

Logged as P1 regression Bug #2677
*Bug 2677* <https://bugzilla.audacityteam.org/show_bug.cgi?id=2677> - Win/Mac:
An AUP file can crash Audacity when opened in 3.0.0

Peter.



> - John
>
> On Thu, Feb 25, 2021 at 8:12 AM Peter Sampson <
> [email protected]> wrote:
>
>>
>>
>> On Thu, Feb 25, 2021 at 1:04 PM David Bailes <[email protected]> wrote:
>>
>>> On Thu, 25 Feb 2021 at 12:46, John Colket <[email protected]> wrote:
>>>
>>>> Steve, thanks for checking.  As you know I am on Windows, which I think
>>>> I neglected to say before but which I think you all know.  I wonder if it
>>>> is something in my configuration files....   I'll check into this later....
>>>>
>>>
>>> I can confirm the crash on Windows 10,
>>>
>>
>> a)  This AUP file crashes for me on W10 with 3.0.0 RC03
>>
>> b) 2.4.2 attempts to open it - but reports the missing data folder
>>
>> Peter.
>>
>>
>>
>>> David.
>>>
>>>
>>>> On Thu, Feb 25, 2021 at 7:39 AM Steve Fiddle <[email protected]>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Thu, 25 Feb 2021 at 12:31, John Colket <[email protected]> wrote:
>>>>>
>>>>>> So last night, I was BLOCKED from attaching a ZIP file of my .aup
>>>>>> file.
>>>>>> I just checked and my aup file with an empty project directory
>>>>>> crashes RC03 repeatedly.
>>>>>> Here is a link to the ZIP file:
>>>>>> https://www.dropbox.com/s/haw9xtbpmi5b7wz/20200305-GCBS.zip?dl=0
>>>>>>
>>>>>
>>>>> That doesn't crash for me with RC3 on Linux, though I do of course get
>>>>> a warning about missing blockfiles, and then a project with no audio.
>>>>>
>>>>> Steve
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> Later....
>>>>>>
>>>>>> - John
>>>>>>
>>>>>> On Thu, Feb 25, 2021 at 5:44 AM Peter Sampson <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Feb 25, 2021 at 10:25 AM Peter Sampson <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Feb 25, 2021 at 10:00 AM Peter Sampson <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Feb 25, 2021 at 2:13 AM John Colket <[email protected]>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> FYI. I seem to be doing something wrong.  When I drag-and-drop an
>>>>>>>>>> .aup file into Audacity 2.4.2, it complains:
>>>>>>>>>> ============================================
>>>>>>>>>> Error importing
>>>>>>>>>> "C:\Users......aup" is an Audacity Project file.
>>>>>>>>>> Use the 'File > Open' command to open Audacity Projects.
>>>>>>>>>> ============================================
>>>>>>>>>> I click OK, am PO'd, but life goes on.
>>>>>>>>>>
>>>>>>>>>> Not so with RC03 (Feb 24 2021, 52d04f)
>>>>>>>>>> So for the first .aup I tried to do this with Audacity hung.  The
>>>>>>>>>> second one worked OK. 🙂
>>>>>>>>>> They are both 1GB projects, so I do not want to send them along
>>>>>>>>>> just yet.
>>>>>>>>>> Project "Open"s in 2.4.2 OK.
>>>>>>>>>>
>>>>>>>>>> Open in 3.0.0 causes crash.  I can send
>>>>>>>>>>
>>>>>>>>>> C:\Users\requi\AppData\Local\Temp\Audacity_dbgrpt-13928-20210224T203453.zip
>>>>>>>>>> along if you are interested.
>>>>>>>>>>
>>>>>>>>>> Crash seems to occur in wxWidgets called from ImportAUP.cpp(780):
>>>>>>>>>>             AudacityMessageBox(
>>>>>>>>>>                XO("Couldn't find the project data folder:
>>>>>>>>>> \"%s\"").Format(*value),
>>>>>>>>>>                XO("Error Opening Project"),
>>>>>>>>>>                wxOK | wxCENTRE,
>>>>>>>>>>                &window);
>>>>>>>>>>
>>>>>>>>>> Value is "200305-GCBS_data" which looks right?
>>>>>>>>>> Again, project Opens OK in 2.4.2.
>>>>>>>>>>
>>>>>>>>>> I can't spend any more time on this just now.  And I will be out
>>>>>>>>>> of town tomorrow and Saturday. We can talk Friday maybe.
>>>>>>>>>>
>>>>>>>>>> Sorry to give this to you. Zipped .aup only file attached.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Management Summary
>>>>>>>>> ----------------------------
>>>>>>>>> I tested all if this pretty thoroughly on more than one occasion
>>>>>>>>> in the past and AFAICT
>>>>>>>>> it was all working properly (second half) of this email will be a
>>>>>>>>> set of use-case tests.
>>>>>>>>>
>>>>>>>>> So this crash is somewhat alarming
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ----------------------------------------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> The way that Audacity is suppose to work is
>>>>>>>>> -------------------------------------------------------
>>>>>>>>>
>>>>>>>>> 1) Drag and drop onto an open Audacity project is effectively a de
>>>>>>>>> facto File>Import, so:
>>>>>>>>>
>>>>>>>>> a) audio files van be dragged& dropped onto an Audacity Window,
>>>>>>>>> just  as they can be
>>>>>>>>> imported with the File>Import command
>>>>>>>>>
>>>>>>>>> b) AUP or AUP3 files cannot be dragged and dropped onto an open
>>>>>>>>> Audacity project window
>>>>>>>>> just as they cannot be opened with the File>Import command
>>>>>>>>> In both these cases an error message is shown telling the user to
>>>>>>>>> use File>Open instead
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2) Drag and drop onto a shortcut icon or onto an .exe/.app file is
>>>>>>>>> a de facto File>Open command
>>>>>>>>>
>>>>>>>>> a) AUP or AUP3 files can be dragged and dropped onto a shortcut
>>>>>>>>> icon or onto a .exe/,app file
>>>>>>>>> and Audacity will launch and open the project.  Just as is the
>>>>>>>>> case when using File>Open to open
>>>>>>>>> the project.
>>>>>>>>>
>>>>>>>>> b) Audio files can be dragged and dropped onto a .exe/.app file
>>>>>>>>> and they will be "opened" in Audacity
>>>>>>>>> with a launch of Audacity and an implicit Import of the audio file
>>>>>>>>> (mote carefully that we do not actually
>>>>>>>>> "open" the audio file itself).  File>Open can be used in a similar
>>>>>>>>> way with audio files.
>>>>>>>>>
>>>>>>>>> c) Audio files cannot be dragged and dropped onto an Audacity
>>>>>>>>> shortcut icon, it doesn't work.
>>>>>>>>> I don't know if this is intentional i.e. a "feature" or if it is a
>>>>>>>>> "bug"
>>>>>>>>>
>>>>>>>>> some notes here.
>>>>>>>>>
>>>>>>>>> i) In the course of UP development Leland experimented for a while
>>>>>>>>> in allowing the "Import" of Audacity
>>>>>>>>> projects, enabling both the command and the use to frag and drop
>>>>>>>>> to import or open an Audacity project.
>>>>>>>>> including importing a different project into an already existing
>>>>>>>>> project/
>>>>>>>>> Sadly this gave rise to some intractable bugs, so we withdrew this
>>>>>>>>> and reverted to our previous 2.4.2
>>>>>>>>> and earlier behaviors of not allowing Import of projects.
>>>>>>>>>
>>>>>>>>> ii) an Easter egg has been allowed to remain whereby in 3.0.0 an
>>>>>>>>> AUP project can be imported into a
>>>>>>>>> 3.0.0 project - BUT an AUP3 project cannot.
>>>>>>>>> There is a small downside to having left this in, in that users my
>>>>>>>>> be confused as to why they can import
>>>>>>>>> AUP but not AUP3.  Personally I would block import of AUP into
>>>>>>>>> 3.0.0 projects just for "consistency", but
>>>>>>>>> that's not the case.  It remains an undocumented Easter Egg.
>>>>>>>>>
>>>>>>>>> iii) 2b and 2c are technically a data impurity - in that we do not
>>>>>>>>> "Open" users' audio files.
>>>>>>>>> rather we allow use of this command to pseudo "Import" their audio
>>>>>>>>> file after Audacity
>>>>>>>>> makes the Open Project.
>>>>>>>>> This leads to user confusion, believing wrongly that they are
>>>>>>>>> operating directly on their WAV, MP3 etc
>>>>>>>>> audio file.
>>>>>>>>> In contrast data purity exists at the output end as you van only
>>>>>>>>> Save a Project and Export an audio file.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> Now for the use-case tests.
>>>>>>>>> ----------------------------------
>>>>>>>>>
>>>>>>>>> To set this up  use 2.4.2 to create a project and save it on your
>>>>>>>>> desktop as an AUP project test.aup and
>>>>>>>>> similarly use 3.30. RC03 to create a project and save this on your
>>>>>>>>> desktop as an AUP3 project test.aup3
>>>>>>>>> I made the projects by importing a 3 minute stereo song.
>>>>>>>>>
>>>>>>>>> UC1) D&D AUP onto open 2.4.2
>>>>>>>>> a) launch 2.4.2
>>>>>>>>> b) try to drag&drop test.aup onto it
>>>>>>>>> c) Observe: helpful error message
>>>>>>>>> This PO'd Joh (he says) but then it's always been this way
>>>>>>>>>
>>>>>>>>> UC2) D&D AUP3 onto open 2.4.2
>>>>>>>>> a) launch 2.4.2
>>>>>>>>> b) try to drag&drop test.aup3 onto it
>>>>>>>>> c) Observe: error message saying filetype not recognized
>>>>>>>>> That is to be expected as when we built 2.4.2 we had no
>>>>>>>>> expectation of AUP3 files and thus
>>>>>>>>> no way to trap them.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> UC3) D&D AUP3 onto open  3.0.0
>>>>>>>>> a) launch  3.0.0
>>>>>>>>> b) try to drag&drop test.aup3 onto it
>>>>>>>>> c) Observe: helpful error message telling you to use File>Open
>>>>>>>>> Instead
>>>>>>>>>
>>>>>>>>> UC4) D&D AUP onto open 3.0.0
>>>>>>>>> a) launch  3.0.0
>>>>>>>>> b) try to drag&drop test.aup onto it
>>>>>>>>> c) Observe: the project is imported
>>>>>>>>> This is the "Easter Egg" - and is somewhat inconsistent with UC3
>>>>>>>>>
>>>>>>>>
>>>>>>> BTW I think this "Easter Egg" occurs because technically Audacity
>>>>>>> 3.0.0 is not actually "Opening" an AUP project.
>>>>>>> Rater it is "Importing" it and converting it into an AUP3 project.
>>>>>>>
>>>>>>> If you look carefully at the progress message while this is taking
>>>>>>> p;ace you will observe that Audacity is telling you
>>>>>>> that it is "Importing AUP Project files..."
>>>>>>>
>>>>>>> So technically this  could be regarded as "pure" and "proper"
>>>>>>> behavior.
>>>>>>>
>>>>>>> Peter.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>
>>>>>>>>> UC5) D&D onto shortcut items on desktop
>>>>>>>>> a) D&D AUP onto 2.4.2 shortcut - it works
>>>>>>>>> b) D&D AUP3 onto 3.0.0 shortcut - it works
>>>>>>>>> c) D&D AUP onto 3.0.0 shortcut - it works
>>>>>>>>> d) D&D AUP3 onto 2.4.2 shortcut => error message
>>>>>>>>>
>>>>>>>>> UC6) D&D onto ,exe files
>>>>>>>>> a) D&D AUP onto Audacity242.exe  - it works
>>>>>>>>> b) D&D AUP3 onto  Audacity300.exe - it works
>>>>>>>>> c) D&D AUP onto  Audacity300.exe - it works
>>>>>>>>> d) D&D AUP3 onto  Audacity242.exe  => error message
>>>>>>>>>
>>>>>>>>> So this looks from these use-case tests to be working as expected.
>>>>>>>>>
>>>>>>>>> I do realize that John's project that he wrote about is *much*
>>>>>>>>> bigger than my test projects
>>>>>>>>> here - so I will try to find time later today to repeat these
>>>>>>>>> tests with a pair of 1GB projects.
>>>>>>>>>
>>>>>>>>
>>>>>>>> So I repeated these tests with a one hour stereo wav file of music
>>>>>>>> - both AUP3 and AUP c. 1.2GB
>>>>>>>>
>>>>>>>> All tests still worked fine.
>>>>>>>>
>>>>>>>> Peter.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Peter.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> - John
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Feb 24, 2021 at 10:29 AM Peter Sampson <
>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Feb 24, 2021 at 3:08 PM Leland <[email protected]>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> The packaging/install/cmake issue is still valid, but the other
>>>>>>>>>>>> issue seems to be related to Zam plugins only.  Still researching though.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I L*O*V*E the Zam VU meter  😎
>>>>>>>>>>> http://www.zamaudio.com/?p=976
>>>>>>>>>>>
>>>>>>>>>>> Any chance we could make one of these for Audacity ?
>>>>>>>>>>>
>>>>>>>>>>> Peter.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *From:* Leland <[email protected]>
>>>>>>>>>>>> *Sent:* Wednesday, February 24, 2021 8:22 AM
>>>>>>>>>>>> *To:* [email protected]
>>>>>>>>>>>> *Subject:* Re: [Audacity-devel] Audacity 3.0.0 RC 003 for
>>>>>>>>>>>> testing.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Bummer, I’ve just found a couple of LV2 problems on Linux.  One
>>>>>>>>>>>> is simply a packaging/install/cmake issue.  The other one is a hang when
>>>>>>>>>>>> using (any, I think) LV2 plugins a second time.  Doesn’t have to be the
>>>>>>>>>>>> same LV2 plugin either, just any LV2 plugin.  At least that’s what it seems
>>>>>>>>>>>> like right now.  Just identified and haven’t had a chance to dig further.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *From:* James Crook <[email protected]>
>>>>>>>>>>>> *Sent:* Wednesday, February 24, 2021 7:17 AM
>>>>>>>>>>>> *To:* audacity-devel <[email protected]>
>>>>>>>>>>>> *Subject:* [Audacity-devel] Audacity 3.0.0 RC 003 for testing.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> We've addressed bug 2673 and I've spun new release candidates,
>>>>>>>>>>>> RC03.
>>>>>>>>>>>>
>>>>>>>>>>>> https://www.fosshub.com/Audacity-devel.html
>>>>>>>>>>>>
>>>>>>>>>>>> Please give them a good workout.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --James
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> audacity-win-3.0.0rc03.exe    (application/x-msdownload) - 29376712 bytes
>>>>>>>>>>>>
>>>>>>>>>>>> SHA-256 c9b98d11b27b60acc54bd637dd057dc8a5cdbdea3e2bb9ac54c6ba026870af49
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> audacity-win-3.0.0rc03.zip    (application/x-zip-compressed) - 12507830 bytes
>>>>>>>>>>>>
>>>>>>>>>>>> SHA-256 744551b725d9d38aa8a6825231e1ef5a813c8fe034b59fe0b29328b92b40d834
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> audacity-man-3.0.0rc03.zip    (application/x-zip-compressed) - 23114150 bytes
>>>>>>>>>>>>
>>>>>>>>>>>> SHA-256 e037890b70a556eff533cee9ab0a7bcf07957efba4612801eb8906b3ab99ace0
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> audacity-macos-3.0.0rc03.dmg        (n/a) - 41327238 bytes
>>>>>>>>>>>>
>>>>>>>>>>>> SHA-256 232caec5a8805673c02fd04f812149bf7fe70385e42a4fd662125b424b8aa33c
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> audacity-minsrc-3.0.0rc03.tar.xz        (n/a) - 13299040 bytes
>>>>>>>>>>>>
>>>>>>>>>>>> SHA-256 df18b4bb8811cb042a5223513ce1c07a4162f84ad90e9e9ae2ebf4782d039a8c
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> audacity-devel mailing list
>>>>>>>>>>>> [email protected]
>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> audacity-devel mailing list
>>>>>>>>>>> [email protected]
>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>> audacity-devel mailing list
>>>>>> [email protected]
>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>>>>>
>>>>> _______________________________________________
>>>>> audacity-devel mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>>>>
>>>> _______________________________________________
>>>> audacity-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>>>
>>> _______________________________________________
>>> audacity-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>>
>> _______________________________________________
>> audacity-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
> _______________________________________________
> audacity-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

_______________________________________________
audacity-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-devel