You can subscribe to this list here.
| 2010 |
Jan
(78) |
Feb
(38) |
Mar
(23) |
Apr
(19) |
May
|
Jun
(5) |
Jul
(52) |
Aug
(68) |
Sep
(165) |
Oct
(152) |
Nov
(208) |
Dec
(23) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(9) |
Feb
(68) |
Mar
(38) |
Apr
(161) |
May
(73) |
Jun
(60) |
Jul
(27) |
Aug
(6) |
Sep
(2) |
Oct
(8) |
Nov
(35) |
Dec
(163) |
| 2012 |
Jan
(28) |
Feb
(214) |
Mar
(212) |
Apr
(48) |
May
(37) |
Jun
(111) |
Jul
(126) |
Aug
(144) |
Sep
(43) |
Oct
(19) |
Nov
(58) |
Dec
(79) |
| 2013 |
Jan
(121) |
Feb
(70) |
Mar
(60) |
Apr
(38) |
May
(123) |
Jun
(134) |
Jul
(32) |
Aug
(75) |
Sep
(112) |
Oct
(239) |
Nov
(123) |
Dec
(126) |
| 2014 |
Jan
(25) |
Feb
(35) |
Mar
(29) |
Apr
(71) |
May
(68) |
Jun
(38) |
Jul
(37) |
Aug
(92) |
Sep
(43) |
Oct
(252) |
Nov
(216) |
Dec
(504) |
| 2015 |
Jan
(348) |
Feb
(220) |
Mar
(131) |
Apr
(185) |
May
(389) |
Jun
(361) |
Jul
(185) |
Aug
(258) |
Sep
(132) |
Oct
(36) |
Nov
(136) |
Dec
(55) |
| 2016 |
Jan
(64) |
Feb
(66) |
Mar
(31) |
Apr
(286) |
May
(381) |
Jun
(422) |
Jul
(258) |
Aug
(254) |
Sep
(134) |
Oct
(296) |
Nov
(347) |
Dec
(276) |
| 2017 |
Jan
(388) |
Feb
(293) |
Mar
(366) |
Apr
(378) |
May
(395) |
Jun
(483) |
Jul
(507) |
Aug
(298) |
Sep
(89) |
Oct
(263) |
Nov
(332) |
Dec
(230) |
| 2018 |
Jan
(439) |
Feb
(120) |
Mar
(263) |
Apr
(123) |
May
(168) |
Jun
(204) |
Jul
(40) |
Aug
(155) |
Sep
(108) |
Oct
(104) |
Nov
(119) |
Dec
(16) |
| 2019 |
Jan
(89) |
Feb
(87) |
Mar
(87) |
Apr
(223) |
May
(73) |
Jun
(149) |
Jul
(155) |
Aug
(160) |
Sep
(41) |
Oct
(103) |
Nov
(93) |
Dec
(145) |
| 2020 |
Jan
(274) |
Feb
(256) |
Mar
(213) |
Apr
(164) |
May
(202) |
Jun
(135) |
Jul
(152) |
Aug
(311) |
Sep
(200) |
Oct
(86) |
Nov
(128) |
Dec
(65) |
| 2021 |
Jan
(189) |
Feb
(159) |
Mar
(85) |
Apr
(87) |
May
(28) |
Jun
(48) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dmitry Vedenko <vedenko@gm...> - 2021-07-01 09:32:44
|
Hi Peter, 1) Message from ET was very unexpected: Error opening a new empty project. Looks like there were some issues with TEMP 2) I will look into the issue with the shortcut 3) seems to be a CDN issue. I considered all your feedback on RC1. https://crsib-screenshots.s3.amazonaws.com/20210701_12.26.57_3cqte.png On Thu, Jul 1, 2021 at 11:15 AM Peter Sampson < petersampsonaudacity@...> wrote: > > > On Wed, Jun 30, 2021 at 8:36 PM Martin Keary via Audacity-quality < > audacity-quality@...> wrote: > >> Hi all, >> >> After fixing a few bugs, our second Release Candidate is now available >> for testing. >> >> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC2 >> > > Downloads and runs fine on macOS 11.4 Big Sur - only basic functionality > tested so far > > Peter. > > > >> Thanks! >> Martin >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2021-07-01 08:15:18
|
On Wed, Jun 30, 2021 at 8:36 PM Martin Keary via Audacity-quality < audacity-quality@...> wrote: > Hi all, > > After fixing a few bugs, our second Release Candidate is now available for > testing. > > https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC2 > Downloads and runs fine on macOS 11.4 Big Sur - only basic functionality tested so far Peter. > Thanks! > Martin > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Martin Keary <m.keary@mu...> - 2021-06-30 19:36:05
|
Hi all, After fixing a few bugs, our second Release Candidate is now available for testing. https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC2 Thanks! Martin |
|
From: Paul Licameli <paul.licameli@gm...> - 2021-06-29 15:08:44
|
Thanks again. Do you have a Discord handle that isn’t obvious? That is the new venue for open design discussions with the community. You should join if you haven’t. PRL On Tuesday, June 29, 2021, Bill Wharrie <billwh@...> wrote: > > > On 2021/06/29, at 2:56 AM, Peter Sampson <petersampsonaudacity@...> > wrote: > > > > On Tue, Jun 29, 2021 at 4:14 AM Paul Licameli <paul.licameli@...> > wrote: > >> Thanks for that work, Bill! >> >> There was a last minute decision about "Grayscale" -- keeping that as the >> black-on-white, which is how spectrograms are often printed in papers, and >> consistently with what it meant in previous versions of Audacity. "Inverse >> Grayscale" now denotes the white-on-black. >> >> This might mean one picture needs a fix. >> > > Or re-labelling. > > > Relabelled the inverse greyscale image, added greyscale image. Wait a > while for the correct image to show up on the page (the first one I > uploaded was cropped wrong). > > — Bill > > > Peter. > > > >> PRL >> >> >> On Mon, Jun 28, 2021 at 3:20 PM Bill Wharrie <billwh@...> wrote: >> >>> >>> >>> On 2021/06/28, at 1:09 PM, Peter Sampson <petersampsonaudacity@...> >>> wrote: >>> >>> >>> >>> On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < >>> audacity-quality@...> wrote: >>> >>>> Hi all, >>>> >>>> Our release candidate (3.0.3) is now ready for testing. >>>> >>>> *Download* >>>> https://www.fosshub.com/Audacity-devel.html >>>> or >>>> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 >>>> >>> >>> I have had to make some changes today to the Manual as a result of the >>> decision to >>> release Audacity 3.0.3 as a 64-bit app on Windows, including in >>> particular: >>> https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_ >>> and_Analyzer_plug-ins_on_Windows >>> Some other pages were affected too. >>> >>> And many thanks to David Bailes for catching that. >>> >>> Also Bill Wharrie has updated the Spectrogram View page >>> https://alphamanual.audacityteam.org/man/Spectrogram_View >>> Thanks for that Bill. >>> >>> >>> I finished uploading the images with the new default colour scheme about >>> 2 hours ago. Still waiting for the changes to propagate through the cache >>> (or whatever) to make sure it looks right. >>> >>> — Bill >>> >>> >>> Since these changes were made after RC1 had been build these changes >>> will not >>> be in the Manual in the app for RC1. >>> >>> This implies that an RC2 will be required to get an up to date, >>> accurate, Manual in the 3.0.3 app. >>> >>> Peter. >>> >>> >>> >>> >>> >>>> --- >>>> >>>> *New Features* >>>> Here is a link >>>> <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; >>>> to our New Features wiki. >>>> >>>> --- >>>> >>>> *Issues installing on Windows* >>>> You may be shown a warning when installing on Windows, which will >>>> inform you that the file is from an unknown developer and will require an >>>> extra step to confirm the installation. This is a known problem, which will >>>> be resolved in a few days. >>>> >>>> --- >>>> >>>> *Bugs / Issues* >>>> We are moving to a new system for collecting and prioritising bugs on GitHub >>>> issues <https://github.com/audacity/audacity/issues>;. We'd really >>>> appreciate it if you could log any issues you find there. >>>> >>>> However, if you'd prefer to log issues on the traditional bugzilla >>>> page, we will also keep track of these too. >>>> >>>> Thanks very much! >>>> Martin >>>> _______________________________________________ >>>> Audacity-quality mailing list >>>> Audacity-quality@... >>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>>> >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >>> >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > |
|
From: Bill Wharrie <billwh@go...> - 2021-06-29 15:02:52
|
> On 2021/06/29, at 2:56 AM, Peter Sampson <petersampsonaudacity@...> wrote: > > > > On Tue, Jun 29, 2021 at 4:14 AM Paul Licameli <paul.licameli@... <mailto:paul.licameli@...>> wrote: > Thanks for that work, Bill! > > There was a last minute decision about "Grayscale" -- keeping that as the black-on-white, which is how spectrograms are often printed in papers, and consistently with what it meant in previous versions of Audacity. "Inverse Grayscale" now denotes the white-on-black. > > This might mean one picture needs a fix. > > Or re-labelling. Relabelled the inverse greyscale image, added greyscale image. Wait a while for the correct image to show up on the page (the first one I uploaded was cropped wrong). — Bill > > Peter. > > > > PRL > > > On Mon, Jun 28, 2021 at 3:20 PM Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: > > >> On 2021/06/28, at 1:09 PM, Peter Sampson <petersampsonaudacity@... <mailto:petersampsonaudacity@...>> wrote: >> >> >> >> On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality <audacity-quality@... <mailto:audacity-quality@...>> wrote: >> Hi all, >> >> Our release candidate (3.0.3) is now ready for testing. >> >> Download >> https://www.fosshub.com/Audacity-devel.html <https://www.fosshub.com/Audacity-devel.html>; >> or >> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 <https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1>; >> >> I have had to make some changes today to the Manual as a result of the decision to >> release Audacity 3.0.3 as a 64-bit app on Windows, including in particular: >> https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows <https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows>; >> Some other pages were affected too. >> >> And many thanks to David Bailes for catching that. >> >> Also Bill Wharrie has updated the Spectrogram View page >> https://alphamanual.audacityteam.org/man/Spectrogram_View <https://alphamanual.audacityteam.org/man/Spectrogram_View>; >> Thanks for that Bill. > > I finished uploading the images with the new default colour scheme about 2 hours ago. Still waiting for the changes to propagate through the cache (or whatever) to make sure it looks right. > > — Bill > >> >> Since these changes were made after RC1 had been build these changes will not >> be in the Manual in the app for RC1. >> >> This implies that an RC2 will be required to get an up to date, accurate, Manual in the 3.0.3 app. >> >> Peter. >> >> >> >> >> >> --- >> >> New Features >> Here is a link <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; to our New Features wiki. >> >> --- >> >> Issues installing on Windows >> You may be shown a warning when installing on Windows, which will inform you that the file is from an unknown developer and will require an extra step to confirm the installation. This is a known problem, which will be resolved in a few days. >> >> --- >> >> Bugs / Issues >> We are moving to a new system for collecting and prioritising bugs on GitHub issues <https://github.com/audacity/audacity/issues>;. We'd really appreciate it if you could log any issues you find there. >> >> However, if you'd prefer to log issues on the traditional bugzilla page, we will also keep track of these too. >> >> Thanks very much! >> Martin >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; |
|
From: Steve Fiddle <stevethefiddle@gm...> - 2021-06-29 10:02:56
|
On Tue, 29 Jun 2021 at 10:47, David Bailes <drbailes@...> wrote: > On Tue, 29 Jun 2021 at 09:52, Peter Sampson < > petersampsonaudacity@...> wrote: > >> >> >> On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < >> audacity-quality@...> wrote: >> >>> Hi all, >>> >>> Our release candidate (3.0.3) is now ready for testing. >>> >>> *Download* >>> https://www.fosshub.com/Audacity-devel.html >>> >> >> I have just downloaded and installed the 64-bit 3.0.3 RC1 from Fosshub. >> >> 1) It failed to create a shortcut on my desktop even though I requested >> that >> in the EXE installation process. >> >> 2) the nomenclature is unclear with the Win downloads: >> [image: image.png] >> I'm assuming that the X64 means 64-bit and the x86 implies 32-bit - but >> for many users that will >> not be clear. >> >> 3) There is no ZIP install for Windows >> >> 4) There is no separate downloadable Manual >> >> 5) An RC2 will be required for a fresh pull of the Manual as Bill has >> made further changes >> to the Spectrogram View page which really should be in the Manual which >> is downloaded >> as part of the app. >> >> On the up-side: >> >> 6) The RC1 downloads fine - goes to Program files and not Program files >> (x86) >> >> 7) Launches and runs fine (only basic functionality testing so far). >> >> A question: >> >> 8) I would like to test the new Update Checking, but am not prepared to >> wait 12 hours. >> In particular I want to test that it does not foul an active or pending >> Timer Record. >> >> I note in the 3.0.3 audacity.cfg the new entry: >> >[Update] >> >ScheduledTime=1625011200000 >> >> I have no idea how that figure relates to the 12-hour update check >> interval - and thus >> how I can reduce it for testing to every 1-2 minutes. >> > > With the current code, I don't think you can. Updates aren't necessarily > checked at the ScheduledTime, > You can see that Audacity is attempting to check for updates if you remove the line ScheduledTime=.... from audacity.cfg, disconnect from the Internet, and then launch Audacity. You may also be able to configure your firewall to log outgoing traffic. I don't know if it's possible to see exactly what is being sent during an update check, or where it is being sent to, other than by analyzing outgoing packets. I assume that the data sent is the Json string that appears in the error message when the update check fails, but perhaps Paul can clarify that point. As far as I'm aware, there is no way to know if any of the data is stored or used for any purpose other than checking for updates, which is why, in my opinion, a clear and accurate privacy policy needs to be readily available for users that are bothered about such things. Steve > David. > > >> >> Please advise. >> >> >> Peter. >> >> >> >> >>> or >>> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 >>> >>> --- >>> >>> *New Features* >>> Here is a link >>> <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; >>> to our New Features wiki. >>> >>> --- >>> >>> *Issues installing on Windows* >>> You may be shown a warning when installing on Windows, which will inform >>> you that the file is from an unknown developer and will require an extra >>> step to confirm the installation. This is a known problem, which will be >>> resolved in a few days. >>> >>> --- >>> >>> *Bugs / Issues* >>> We are moving to a new system for collecting and prioritising bugs on GitHub >>> issues <https://github.com/audacity/audacity/issues>;. We'd really >>> appreciate it if you could log any issues you find there. >>> >>> However, if you'd prefer to log issues on the traditional bugzilla page, >>> we will also keep track of these too. >>> >>> Thanks very much! >>> Martin >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: David Bailes <drbailes@gm...> - 2021-06-29 09:47:35
|
On Tue, 29 Jun 2021 at 09:52, Peter Sampson <petersampsonaudacity@...> wrote: > > > On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < > audacity-quality@...> wrote: > >> Hi all, >> >> Our release candidate (3.0.3) is now ready for testing. >> >> *Download* >> https://www.fosshub.com/Audacity-devel.html >> > > I have just downloaded and installed the 64-bit 3.0.3 RC1 from Fosshub. > > 1) It failed to create a shortcut on my desktop even though I requested > that > in the EXE installation process. > > 2) the nomenclature is unclear with the Win downloads: > [image: image.png] > I'm assuming that the X64 means 64-bit and the x86 implies 32-bit - but > for many users that will > not be clear. > > 3) There is no ZIP install for Windows > > 4) There is no separate downloadable Manual > > 5) An RC2 will be required for a fresh pull of the Manual as Bill has made > further changes > to the Spectrogram View page which really should be in the Manual which is > downloaded > as part of the app. > > On the up-side: > > 6) The RC1 downloads fine - goes to Program files and not Program files > (x86) > > 7) Launches and runs fine (only basic functionality testing so far). > > A question: > > 8) I would like to test the new Update Checking, but am not prepared to > wait 12 hours. > In particular I want to test that it does not foul an active or pending > Timer Record. > > I note in the 3.0.3 audacity.cfg the new entry: > >[Update] > >ScheduledTime=1625011200000 > > I have no idea how that figure relates to the 12-hour update check > interval - and thus > how I can reduce it for testing to every 1-2 minutes. > With the current code, I don't think you can. Updates aren't necessarily checked at the ScheduledTime, David. > > Please advise. > > > Peter. > > > > >> or >> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 >> >> --- >> >> *New Features* >> Here is a link >> <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; >> to our New Features wiki. >> >> --- >> >> *Issues installing on Windows* >> You may be shown a warning when installing on Windows, which will inform >> you that the file is from an unknown developer and will require an extra >> step to confirm the installation. This is a known problem, which will be >> resolved in a few days. >> >> --- >> >> *Bugs / Issues* >> We are moving to a new system for collecting and prioritising bugs on GitHub >> issues <https://github.com/audacity/audacity/issues>;. We'd really >> appreciate it if you could log any issues you find there. >> >> However, if you'd prefer to log issues on the traditional bugzilla page, >> we will also keep track of these too. >> >> Thanks very much! >> Martin >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Steve Fiddle <stevethefiddle@gm...> - 2021-06-29 09:14:24
|
On Tue, 29 Jun 2021 at 09:52, Peter Sampson <petersampsonaudacity@...> wrote: > > > On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < > audacity-quality@...> wrote: > >> Hi all, >> >> Our release candidate (3.0.3) is now ready for testing. >> >> *Download* >> https://www.fosshub.com/Audacity-devel.html >> > > I have just downloaded and installed the 64-bit 3.0.3 RC1 from Fosshub. > > 1) It failed to create a shortcut on my desktop even though I requested > that > in the EXE installation process. > > 2) the nomenclature is unclear with the Win downloads: > [image: image.png] > I'm assuming that the X64 means 64-bit and the x86 implies 32-bit - but > for many users that will > not be clear. > > 3) There is no ZIP install for Windows > > 4) There is no separate downloadable Manual > > 5) An RC2 will be required for a fresh pull of the Manual as Bill has made > further changes > to the Spectrogram View page which really should be in the Manual which is > downloaded > as part of the app. > > On the up-side: > > 6) The RC1 downloads fine - goes to Program files and not Program files > (x86) > > 7) Launches and runs fine (only basic functionality testing so far). > > A question: > > 8) I would like to test the new Update Checking, but am not prepared to > wait 12 hours. > In particular I want to test that it does not foul an active or pending > Timer Record. > > I note in the 3.0.3 audacity.cfg the new entry: > >[Update] > >ScheduledTime=1625011200000 > > I have no idea how that figure relates to the 12-hour update check > interval - and thus > how I can reduce it for testing to every 1-2 minutes. > I have this: [Update] DefaultUpdatesChecking=0 UpdateScheduledTime=1624924800000 "DefaultUpdatesChecking=0" disables checking. "DefaultUpdatesChecking=1" enables checking. If this line is not present Audacity defaults to update checking enabled. "UpdateScheduledTime=1624924800000" is the "Unix Epoch time" (Number of seconds since Jan 01 1970 UTC) when the next check is due. A handy on-line converter: https://www.unixtimestamp.com/ If this line is not present, Audacity defaults to check on launch. This section: https://alphamanual.audacityteam.org/man/New_features_in_this_release#updates and this page: https://alphamanual.audacityteam.org/man/Application_Preferences should link to the Privacy Policy, but I've not found a privacy policy statement for the app. Steve > > Please advise. > > > Peter. > > > > >> or >> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 >> >> --- >> >> *New Features* >> Here is a link >> <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; >> to our New Features wiki. >> >> --- >> >> *Issues installing on Windows* >> You may be shown a warning when installing on Windows, which will inform >> you that the file is from an unknown developer and will require an extra >> step to confirm the installation. This is a known problem, which will be >> resolved in a few days. >> >> --- >> >> *Bugs / Issues* >> We are moving to a new system for collecting and prioritising bugs on GitHub >> issues <https://github.com/audacity/audacity/issues>;. We'd really >> appreciate it if you could log any issues you find there. >> >> However, if you'd prefer to log issues on the traditional bugzilla page, >> we will also keep track of these too. >> >> Thanks very much! >> Martin >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2021-06-29 08:52:22
|
On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < audacity-quality@...> wrote: > Hi all, > > Our release candidate (3.0.3) is now ready for testing. > > *Download* > https://www.fosshub.com/Audacity-devel.html > I have just downloaded and installed the 64-bit 3.0.3 RC1 from Fosshub. 1) It failed to create a shortcut on my desktop even though I requested that in the EXE installation process. 2) the nomenclature is unclear with the Win downloads: [image: image.png] I'm assuming that the X64 means 64-bit and the x86 implies 32-bit - but for many users that will not be clear. 3) There is no ZIP install for Windows 4) There is no separate downloadable Manual 5) An RC2 will be required for a fresh pull of the Manual as Bill has made further changes to the Spectrogram View page which really should be in the Manual which is downloaded as part of the app. On the up-side: 6) The RC1 downloads fine - goes to Program files and not Program files (x86) 7) Launches and runs fine (only basic functionality testing so far). A question: 8) I would like to test the new Update Checking, but am not prepared to wait 12 hours. In particular I want to test that it does not foul an active or pending Timer Record. I note in the 3.0.3 audacity.cfg the new entry: >[Update] >ScheduledTime=1625011200000 I have no idea how that figure relates to the 12-hour update check interval - and thus how I can reduce it for testing to every 1-2 minutes. Please advise. Peter. > or > https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 > > --- > > *New Features* > Here is a link > <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; > to our New Features wiki. > > --- > > *Issues installing on Windows* > You may be shown a warning when installing on Windows, which will inform > you that the file is from an unknown developer and will require an extra > step to confirm the installation. This is a known problem, which will be > resolved in a few days. > > --- > > *Bugs / Issues* > We are moving to a new system for collecting and prioritising bugs on GitHub > issues <https://github.com/audacity/audacity/issues>;. We'd really > appreciate it if you could log any issues you find there. > > However, if you'd prefer to log issues on the traditional bugzilla page, > we will also keep track of these too. > > Thanks very much! > Martin > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2021-06-29 06:56:43
|
On Tue, Jun 29, 2021 at 4:14 AM Paul Licameli <paul.licameli@...> wrote: > Thanks for that work, Bill! > > There was a last minute decision about "Grayscale" -- keeping that as the > black-on-white, which is how spectrograms are often printed in papers, and > consistently with what it meant in previous versions of Audacity. "Inverse > Grayscale" now denotes the white-on-black. > > This might mean one picture needs a fix. > Or re-labelling. Peter. > PRL > > > On Mon, Jun 28, 2021 at 3:20 PM Bill Wharrie <billwh@...> wrote: > >> >> >> On 2021/06/28, at 1:09 PM, Peter Sampson <petersampsonaudacity@...> >> wrote: >> >> >> >> On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < >> audacity-quality@...> wrote: >> >>> Hi all, >>> >>> Our release candidate (3.0.3) is now ready for testing. >>> >>> *Download* >>> https://www.fosshub.com/Audacity-devel.html >>> or >>> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 >>> >> >> I have had to make some changes today to the Manual as a result of the >> decision to >> release Audacity 3.0.3 as a 64-bit app on Windows, including in >> particular: >> >> https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows >> Some other pages were affected too. >> >> And many thanks to David Bailes for catching that. >> >> Also Bill Wharrie has updated the Spectrogram View page >> https://alphamanual.audacityteam.org/man/Spectrogram_View >> Thanks for that Bill. >> >> >> I finished uploading the images with the new default colour scheme about >> 2 hours ago. Still waiting for the changes to propagate through the cache >> (or whatever) to make sure it looks right. >> >> — Bill >> >> >> Since these changes were made after RC1 had been build these changes will >> not >> be in the Manual in the app for RC1. >> >> This implies that an RC2 will be required to get an up to date, accurate, >> Manual in the 3.0.3 app. >> >> Peter. >> >> >> >> >> >>> --- >>> >>> *New Features* >>> Here is a link >>> <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; to >>> our New Features wiki. >>> >>> --- >>> >>> *Issues installing on Windows* >>> You may be shown a warning when installing on Windows, which will inform >>> you that the file is from an unknown developer and will require an extra >>> step to confirm the installation. This is a known problem, which will be >>> resolved in a few days. >>> >>> --- >>> >>> *Bugs / Issues* >>> We are moving to a new system for collecting and prioritising bugs on GitHub >>> issues <https://github.com/audacity/audacity/issues>;. We'd really >>> appreciate it if you could log any issues you find there. >>> >>> However, if you'd prefer to log issues on the traditional bugzilla page, >>> we will also keep track of these too. >>> >>> Thanks very much! >>> Martin >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Paul Licameli <paul.licameli@gm...> - 2021-06-29 03:14:21
|
Thanks for that work, Bill! There was a last minute decision about "Grayscale" -- keeping that as the black-on-white, which is how spectrograms are often printed in papers, and consistently with what it meant in previous versions of Audacity. "Inverse Grayscale" now denotes the white-on-black. This might mean one picture needs a fix. PRL On Mon, Jun 28, 2021 at 3:20 PM Bill Wharrie <billwh@...> wrote: > > > On 2021/06/28, at 1:09 PM, Peter Sampson <petersampsonaudacity@...> > wrote: > > > > On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < > audacity-quality@...> wrote: > >> Hi all, >> >> Our release candidate (3.0.3) is now ready for testing. >> >> *Download* >> https://www.fosshub.com/Audacity-devel.html >> or >> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 >> > > I have had to make some changes today to the Manual as a result of the > decision to > release Audacity 3.0.3 as a 64-bit app on Windows, including in particular: > > https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows > Some other pages were affected too. > > And many thanks to David Bailes for catching that. > > Also Bill Wharrie has updated the Spectrogram View page > https://alphamanual.audacityteam.org/man/Spectrogram_View > Thanks for that Bill. > > > I finished uploading the images with the new default colour scheme about 2 > hours ago. Still waiting for the changes to propagate through the cache (or > whatever) to make sure it looks right. > > — Bill > > > Since these changes were made after RC1 had been build these changes will > not > be in the Manual in the app for RC1. > > This implies that an RC2 will be required to get an up to date, accurate, > Manual in the 3.0.3 app. > > Peter. > > > > > >> --- >> >> *New Features* >> Here is a link >> <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; to >> our New Features wiki. >> >> --- >> >> *Issues installing on Windows* >> You may be shown a warning when installing on Windows, which will inform >> you that the file is from an unknown developer and will require an extra >> step to confirm the installation. This is a known problem, which will be >> resolved in a few days. >> >> --- >> >> *Bugs / Issues* >> We are moving to a new system for collecting and prioritising bugs on GitHub >> issues <https://github.com/audacity/audacity/issues>;. We'd really >> appreciate it if you could log any issues you find there. >> >> However, if you'd prefer to log issues on the traditional bugzilla page, >> we will also keep track of these too. >> >> Thanks very much! >> Martin >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Bill Wharrie <billwh@go...> - 2021-06-28 19:55:39
|
> On 2021/06/28, at 2:55 PM, Bill Wharrie <billwh@...> wrote: > > > >> On 2021/06/28, at 1:09 PM, Peter Sampson <petersampsonaudacity@... <mailto:petersampsonaudacity@...>> wrote: >> >> >> >> On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality <audacity-quality@... <mailto:audacity-quality@...>> wrote: >> Hi all, >> >> Our release candidate (3.0.3) is now ready for testing. >> >> Download >> https://www.fosshub.com/Audacity-devel.html <https://www.fosshub.com/Audacity-devel.html>; >> or >> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 <https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1>; >> >> I have had to make some changes today to the Manual as a result of the decision to >> release Audacity 3.0.3 as a 64-bit app on Windows, including in particular: >> https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows <https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows>; >> Some other pages were affected too. >> >> And many thanks to David Bailes for catching that. >> >> Also Bill Wharrie has updated the Spectrogram View page >> https://alphamanual.audacityteam.org/man/Spectrogram_View <https://alphamanual.audacityteam.org/man/Spectrogram_View>; >> Thanks for that Bill. > > I finished uploading the images with the new default colour scheme about 2 hours ago. Still waiting for the changes to propagate through the cache (or whatever) to make sure it looks right. Finally saw the changes and caught one bad image. That has been corrected so now waiting again … — Bill > > — Bill > >> >> Since these changes were made after RC1 had been build these changes will not >> be in the Manual in the app for RC1. >> >> This implies that an RC2 will be required to get an up to date, accurate, Manual in the 3.0.3 app. >> >> Peter. >> >> >> >> >> >> --- >> >> New Features >> Here is a link <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; to our New Features wiki. >> >> --- >> >> Issues installing on Windows >> You may be shown a warning when installing on Windows, which will inform you that the file is from an unknown developer and will require an extra step to confirm the installation. This is a known problem, which will be resolved in a few days. >> >> --- >> >> Bugs / Issues >> We are moving to a new system for collecting and prioritising bugs on GitHub issues <https://github.com/audacity/audacity/issues>;. We'd really appreciate it if you could log any issues you find there. >> >> However, if you'd prefer to log issues on the traditional bugzilla page, we will also keep track of these too. >> >> Thanks very much! >> Martin >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; |
|
From: Steve Fiddle <stevethefiddle@gm...> - 2021-06-28 19:33:13
|
Testing on Ubuntu 20.04, RC1 AppImage fails to load FFmpeg: 20:14:41: Audacity 3.0.3 20:14:41: Trying to load FFmpeg libraries... 20:14:41: Trying to load FFmpeg libraries from system paths. File name is 'libavformat.so.55'. 20:14:41: Checking for monolithic avformat from 'libavformat.so.55'. 20:14:41: Error: Failed to load shared library 'libavformat.so.55' (error 0: Success) 20:14:41: Loading avutil from ''. 20:14:41: Error: Failed to load shared library '.so' (error 0: Success) 20:14:41: Loading avcodec from ''. 20:14:41: Error: Failed to load shared library '.so' (error 0: Success) 20:14:41: Loading avformat from 'libavformat.so.55'. 20:14:41: Error: Failed to load shared library 'libavformat.so.55' (error 0: Success) 20:14:41: Error: Failed to load FFmpeg libraries. 20:14:41: Error: Failed to find compatible FFmpeg libraries. 20:15:16: Attempting to load LAME from system search paths 20:15:16: Loading LAME from libmp3lame.so.0 20:15:16: Actual LAME path /lib/x86_64-linux-gnu/libmp3lame.so.0.0.0 20:15:16: LAME library successfully loaded 20:28:13: Looking for FFmpeg libraries... 20:28:13: mLibAVFormatPath is empty, starting with path '', name 'libavformat.so.55'. 20:28:18: User canceled the dialog. Failed to find FFmpeg libraries. 20:28:18: Trying to load FFmpeg libraries... 20:28:18: Trying to load FFmpeg libraries from system paths. File name is 'libavformat.so.55'. 20:28:18: Checking for monolithic avformat from 'libavformat.so.55'. 20:28:18: Error: Failed to load shared library 'libavformat.so.55' (error 0: Success) 20:28:18: Loading avutil from ''. 20:28:18: Error: Failed to load shared library '.so' (error 0: Success) 20:28:18: Loading avcodec from ''. 20:28:18: Error: Failed to load shared library '.so' (error 0: Success) 20:28:18: Loading avformat from 'libavformat.so.55'. 20:28:18: Error: Failed to load shared library 'libavformat.so.55' (error 0: Success) 20:28:18: Error: Failed to load FFmpeg libraries. 20:28:19: Error: Failed to find compatible FFmpeg libraries. Steve On Mon, 28 Jun 2021 at 20:20, Bill Wharrie <billwh@...> wrote: > > > On 2021/06/28, at 1:09 PM, Peter Sampson <petersampsonaudacity@...> > wrote: > > > > On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < > audacity-quality@...> wrote: > >> Hi all, >> >> Our release candidate (3.0.3) is now ready for testing. >> >> *Download* >> https://www.fosshub.com/Audacity-devel.html >> or >> https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 >> > > I have had to make some changes today to the Manual as a result of the > decision to > release Audacity 3.0.3 as a 64-bit app on Windows, including in particular: > > https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows > Some other pages were affected too. > > And many thanks to David Bailes for catching that. > > Also Bill Wharrie has updated the Spectrogram View page > https://alphamanual.audacityteam.org/man/Spectrogram_View > Thanks for that Bill. > > > I finished uploading the images with the new default colour scheme about 2 > hours ago. Still waiting for the changes to propagate through the cache (or > whatever) to make sure it looks right. > > — Bill > > > Since these changes were made after RC1 had been build these changes will > not > be in the Manual in the app for RC1. > > This implies that an RC2 will be required to get an up to date, accurate, > Manual in the 3.0.3 app. > > Peter. > > > > > >> --- >> >> *New Features* >> Here is a link >> <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; to >> our New Features wiki. >> >> --- >> >> *Issues installing on Windows* >> You may be shown a warning when installing on Windows, which will inform >> you that the file is from an unknown developer and will require an extra >> step to confirm the installation. This is a known problem, which will be >> resolved in a few days. >> >> --- >> >> *Bugs / Issues* >> We are moving to a new system for collecting and prioritising bugs on GitHub >> issues <https://github.com/audacity/audacity/issues>;. We'd really >> appreciate it if you could log any issues you find there. >> >> However, if you'd prefer to log issues on the traditional bugzilla page, >> we will also keep track of these too. >> >> Thanks very much! >> Martin >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Bill Wharrie <billwh@go...> - 2021-06-28 19:20:43
|
> On 2021/06/28, at 1:09 PM, Peter Sampson <petersampsonaudacity@...> wrote: > > > > On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality <audacity-quality@... <mailto:audacity-quality@...>> wrote: > Hi all, > > Our release candidate (3.0.3) is now ready for testing. > > Download > https://www.fosshub.com/Audacity-devel.html <https://www.fosshub.com/Audacity-devel.html>; > or > https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 <https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1>; > > I have had to make some changes today to the Manual as a result of the decision to > release Audacity 3.0.3 as a 64-bit app on Windows, including in particular: > https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows <https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows>; > Some other pages were affected too. > > And many thanks to David Bailes for catching that. > > Also Bill Wharrie has updated the Spectrogram View page > https://alphamanual.audacityteam.org/man/Spectrogram_View <https://alphamanual.audacityteam.org/man/Spectrogram_View>; > Thanks for that Bill. I finished uploading the images with the new default colour scheme about 2 hours ago. Still waiting for the changes to propagate through the cache (or whatever) to make sure it looks right. — Bill > > Since these changes were made after RC1 had been build these changes will not > be in the Manual in the app for RC1. > > This implies that an RC2 will be required to get an up to date, accurate, Manual in the 3.0.3 app. > > Peter. > > > > > > --- > > New Features > Here is a link <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; to our New Features wiki. > > --- > > Issues installing on Windows > You may be shown a warning when installing on Windows, which will inform you that the file is from an unknown developer and will require an extra step to confirm the installation. This is a known problem, which will be resolved in a few days. > > --- > > Bugs / Issues > We are moving to a new system for collecting and prioritising bugs on GitHub issues <https://github.com/audacity/audacity/issues>;. We'd really appreciate it if you could log any issues you find there. > > However, if you'd prefer to log issues on the traditional bugzilla page, we will also keep track of these too. > > Thanks very much! > Martin > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2021-06-28 17:09:53
|
On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < audacity-quality@...> wrote: > Hi all, > > Our release candidate (3.0.3) is now ready for testing. > > *Download* > https://www.fosshub.com/Audacity-devel.html > or > https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 > I have had to make some changes today to the Manual as a result of the decision to release Audacity 3.0.3 as a 64-bit app on Windows, including in particular: https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Windows Some other pages were affected too. And many thanks to David Bailes for catching that. Also Bill Wharrie has updated the Spectrogram View page https://alphamanual.audacityteam.org/man/Spectrogram_View Thanks for that Bill. Since these changes were made after RC1 had been build these changes will not be in the Manual in the app for RC1. This implies that an RC2 will be required to get an up to date, accurate, Manual in the 3.0.3 app. Peter. > --- > > *New Features* > Here is a link > <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; > to our New Features wiki. > > --- > > *Issues installing on Windows* > You may be shown a warning when installing on Windows, which will inform > you that the file is from an unknown developer and will require an extra > step to confirm the installation. This is a known problem, which will be > resolved in a few days. > > --- > > *Bugs / Issues* > We are moving to a new system for collecting and prioritising bugs on GitHub > issues <https://github.com/audacity/audacity/issues>;. We'd really > appreciate it if you could log any issues you find there. > > However, if you'd prefer to log issues on the traditional bugzilla page, > we will also keep track of these too. > > Thanks very much! > Martin > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Martin Keary <m.keary@mu...> - 2021-06-28 16:52:46
|
Hi all, Our release candidate (3.0.3) is now ready for testing. *Download* https://www.fosshub.com/Audacity-devel.html or https://github.com/audacity/audacity/releases/tag/Audacity-3.0.3-RC1 --- *New Features* Here is a link <https://alphamanual.audacityteam.org/man/New_features_in_this_release>; to our New Features wiki. --- *Issues installing on Windows* You may be shown a warning when installing on Windows, which will inform you that the file is from an unknown developer and will require an extra step to confirm the installation. This is a known problem, which will be resolved in a few days. --- *Bugs / Issues* We are moving to a new system for collecting and prioritising bugs on GitHub issues <https://github.com/audacity/audacity/issues>;. We'd really appreciate it if you could log any issues you find there. However, if you'd prefer to log issues on the traditional bugzilla page, we will also keep track of these too. Thanks very much! Martin |
|
From: Cliff <flyer185@gm...> - 2021-06-23 14:27:30
|
David, That link produces a small dmg that Mojave says it can’t verify. Trying the link I have to download a build dmg from github I get a huge zip file that ends up as 158mb for the installed Audacity and it won’t run because of some library issue. Can someone upload a valid dmg to Dropbox or something similar. Getting from github somehow isn’t giving me usable files. Cliff > On Jun 23, 2021, at 05:46, David Bailes <drbailes@...> wrote: > > On Wed, 23 Jun 2021 at 02:48, Cliff <flyer185@... <mailto:flyer185@...>> wrote: > David, > > I checked and I am building a release version. If the message should only come up when running a debug build why did it come up for me. Can I assume this is an error? > > Given that Steve can't reproduce the error on macOS, it would be worth you checking a recent build on Github, to check that there isn't an issue with your build. For example: > https://github.com/audacity/audacity/actions/runs/950782778 <https://github.com/audacity/audacity/actions/runs/950782778>; > > David. > > > Cliff > >> On Jun 22, 2021, at 04:57, David Bailes <drbailes@... <mailto:drbailes@...>> wrote: >> >> On Tue, 22 Jun 2021 at 10:33, Steve Fiddle <stevethefiddle@... <mailto:stevethefiddle@...>> wrote: >> Testing on both macOS and Linux: >> I don't see a crash or warning on either machine, but also I don't hear a beep on completion of longer activities. >> I don't normally have that option enabled and I don't know if it has ever worked. >> >> wxFAIL_MSG() is only called in debug versions. >> >> David. >> >> >> Steve >> >> On Tue, 22 Jun 2021 at 10:13, Steve Fiddle <stevethefiddle@... <mailto:stevethefiddle@...>> wrote: >> >> >> On Tue, 22 Jun 2021 at 09:49, David Bailes <drbailes@... <mailto:drbailes@...>> wrote: >> Hi Cliff, >> I think that there is a problem here, but not sure why it's not been showing up before. >> This is the code for osx that's being called: >> >> bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data)) >> { >> wxFAIL_MSG( "not implemented" ); >> >> return false; >> } >> >> which is called from: >> void ProgressDialog::Beep() const >> { >> int after; >> bool should; >> wxString name; >> >> gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false); >> gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60); >> gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString); >> >> if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after * 1000) >> { >> wxBusyCursor busy; >> wxSound s; >> >> if (name.empty()) >> { >> s.Create(sizeof(beep), beep); >> } >> else >> { >> s.Create(name); >> } >> >> if (s.IsOk()) >> { >> s.Play(wxSOUND_SYNC); >> } >> } >> } >> >> which is called from the ProgressDialog's destructor. >> >> So if you've got "beep on completion on longer activities" enabled in preferences, and "whatever" has taken longer than 60s, you'll get the call to wxFAIL_MSG(). >> (I can't see where BeepAfterDuration and BeepFileName can be set in preferences.) >> >> "Preferences > Interface" >> https://manual.audacityteam.org/man/interface_preferences.html <https://manual.audacityteam.org/man/interface_preferences.html>; >> >> I was not able to reproduce the problem, but I'd missed the "Beep on completion" element - I'll retest. >> >> Steve >> >> >> >> David. >> >> On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@... <mailto:flyer185@...>> wrote: >> Running MacOS Mojave. I have never seen this before. Ideas? It happens at the end of running the DeClicker plugin. Running on build #760576 does not bring up the error. I don’t have any builds between the one that works and the one that does not. The assert does always give the same trace. I don’t use any other plugins so can’t say if it’s common to all plugins or just DeClicker. Built in Effects work normally. >> >> <PastedGraphic-2.png> >> >> Cliff >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; |
|
From: David Bailes <drbailes@gm...> - 2021-06-23 10:46:48
|
On Wed, 23 Jun 2021 at 02:48, Cliff <flyer185@...> wrote: > David, > > I checked and I am building a release version. If the message should only > come up when running a debug build why did it come up for me. Can I assume > this is an error? > Given that Steve can't reproduce the error on macOS, it would be worth you checking a recent build on Github, to check that there isn't an issue with your build. For example: https://github.com/audacity/audacity/actions/runs/950782778 David. > > Cliff > > On Jun 22, 2021, at 04:57, David Bailes <drbailes@...> wrote: > > On Tue, 22 Jun 2021 at 10:33, Steve Fiddle <stevethefiddle@...> > wrote: > >> Testing on both macOS and Linux: >> I don't see a crash or warning on either machine, but also I don't hear a >> beep on completion of longer activities. >> I don't normally have that option enabled and I don't know if it has ever >> worked. >> > > wxFAIL_MSG() is only called in debug versions. > > David. > > >> >> Steve >> >> On Tue, 22 Jun 2021 at 10:13, Steve Fiddle <stevethefiddle@...> >> wrote: >> >>> >>> >>> On Tue, 22 Jun 2021 at 09:49, David Bailes <drbailes@...> wrote: >>> >>>> Hi Cliff, >>>> I think that there is a problem here, but not sure why it's not been >>>> showing up before. >>>> This is the code for osx that's being called: >>>> >>>> bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data)) >>>> { >>>> wxFAIL_MSG( "not implemented" ); >>>> >>>> return false; >>>> } >>>> >>>> which is called from: >>>> void ProgressDialog::Beep() const >>>> { >>>> int after; >>>> bool should; >>>> wxString name; >>>> >>>> gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false); >>>> gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60); >>>> gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString); >>>> >>>> if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after * >>>> 1000) >>>> { >>>> wxBusyCursor busy; >>>> wxSound s; >>>> >>>> if (name.empty()) >>>> { >>>> s.Create(sizeof(beep), beep); >>>> } >>>> else >>>> { >>>> s.Create(name); >>>> } >>>> >>>> if (s.IsOk()) >>>> { >>>> s.Play(wxSOUND_SYNC); >>>> } >>>> } >>>> } >>>> >>>> which is called from the ProgressDialog's destructor. >>>> >>>> So if you've got "beep on completion on longer activities" enabled in >>>> preferences, and "whatever" has taken longer than 60s, you'll get the call >>>> to wxFAIL_MSG(). >>>> (I can't see where BeepAfterDuration and BeepFileName can be set in >>>> preferences.) >>>> >>> >>> "Preferences > Interface" >>> https://manual.audacityteam.org/man/interface_preferences.html >>> >>> I was not able to reproduce the problem, but I'd missed the "Beep on >>> completion" element - I'll retest. >>> >>> Steve >>> >>> >>> >>>> >>>> David. >>>> >>>> On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@...> wrote: >>>> >>>>> Running MacOS Mojave. I have never seen this before. Ideas? It happens >>>>> at the end of running the DeClicker plugin. Running on build #760576 does >>>>> not bring up the error. I don’t have any builds between the one that works >>>>> and the one that does not. The assert does always give the same trace. I >>>>> don’t use any other plugins so can’t say if it’s common to all plugins or >>>>> just DeClicker. Built in Effects work normally. >>>>> >>>>> <PastedGraphic-2.png> >>>>> >>>>> Cliff >>>>> _______________________________________________ >>>>> Audacity-quality mailing list >>>>> Audacity-quality@... >>>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>>>> >>>> _______________________________________________ >>>> Audacity-quality mailing list >>>> Audacity-quality@... >>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>>> >>> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Cliff <flyer185@gm...> - 2021-06-23 01:47:42
|
David,
I checked and I am building a release version. If the message should only come up when running a debug build why did it come up for me. Can I assume this is an error?
Cliff
> On Jun 22, 2021, at 04:57, David Bailes <drbailes@...> wrote:
>
> On Tue, 22 Jun 2021 at 10:33, Steve Fiddle <stevethefiddle@... <mailto:stevethefiddle@...>> wrote:
> Testing on both macOS and Linux:
> I don't see a crash or warning on either machine, but also I don't hear a beep on completion of longer activities.
> I don't normally have that option enabled and I don't know if it has ever worked.
>
> wxFAIL_MSG() is only called in debug versions.
>
> David.
>
>
> Steve
>
> On Tue, 22 Jun 2021 at 10:13, Steve Fiddle <stevethefiddle@... <mailto:stevethefiddle@...>> wrote:
>
>
> On Tue, 22 Jun 2021 at 09:49, David Bailes <drbailes@... <mailto:drbailes@...>> wrote:
> Hi Cliff,
> I think that there is a problem here, but not sure why it's not been showing up before.
> This is the code for osx that's being called:
>
> bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data))
> {
> wxFAIL_MSG( "not implemented" );
>
> return false;
> }
>
> which is called from:
> void ProgressDialog::Beep() const
> {
> int after;
> bool should;
> wxString name;
>
> gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false);
> gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60);
> gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString);
>
> if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after * 1000)
> {
> wxBusyCursor busy;
> wxSound s;
>
> if (name.empty())
> {
> s.Create(sizeof(beep), beep);
> }
> else
> {
> s.Create(name);
> }
>
> if (s.IsOk())
> {
> s.Play(wxSOUND_SYNC);
> }
> }
> }
>
> which is called from the ProgressDialog's destructor.
>
> So if you've got "beep on completion on longer activities" enabled in preferences, and "whatever" has taken longer than 60s, you'll get the call to wxFAIL_MSG().
> (I can't see where BeepAfterDuration and BeepFileName can be set in preferences.)
>
> "Preferences > Interface"
> https://manual.audacityteam.org/man/interface_preferences.html <https://manual.audacityteam.org/man/interface_preferences.html>;
>
> I was not able to reproduce the problem, but I'd missed the "Beep on completion" element - I'll retest.
>
> Steve
>
>
>
> David.
>
> On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@... <mailto:flyer185@...>> wrote:
> Running MacOS Mojave. I have never seen this before. Ideas? It happens at the end of running the DeClicker plugin. Running on build #760576 does not bring up the error. I don’t have any builds between the one that works and the one that does not. The assert does always give the same trace. I don’t use any other plugins so can’t say if it’s common to all plugins or just DeClicker. Built in Effects work normally.
>
> <PastedGraphic-2.png>
>
> Cliff
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@... <mailto:Audacity-quality@...>
> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>;
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@... <mailto:Audacity-quality@...>
> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>;
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@... <mailto:Audacity-quality@...>
> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>;
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@... <mailto:Audacity-quality@...>
> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>;
|
|
From: Cliff <flyer185@gm...> - 2021-06-22 11:41:43
|
Confirmed that the Beep was the issue. I don’t know why I had set that, guess to test and now we know it does not work.
As far as I know this is not a debug version. It’s the same setup as I’ve used ever since we started using Cmake. Is there a setting I need to set to not get a debug version?
Cliff
> On Jun 22, 2021, at 04:57, David Bailes <drbailes@...> wrote:
>
> On Tue, 22 Jun 2021 at 10:33, Steve Fiddle <stevethefiddle@... <mailto:stevethefiddle@...>> wrote:
> Testing on both macOS and Linux:
> I don't see a crash or warning on either machine, but also I don't hear a beep on completion of longer activities.
> I don't normally have that option enabled and I don't know if it has ever worked.
>
> wxFAIL_MSG() is only called in debug versions.
>
> David.
>
>
> Steve
>
> On Tue, 22 Jun 2021 at 10:13, Steve Fiddle <stevethefiddle@... <mailto:stevethefiddle@...>> wrote:
>
>
> On Tue, 22 Jun 2021 at 09:49, David Bailes <drbailes@... <mailto:drbailes@...>> wrote:
> Hi Cliff,
> I think that there is a problem here, but not sure why it's not been showing up before.
> This is the code for osx that's being called:
>
> bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data))
> {
> wxFAIL_MSG( "not implemented" );
>
> return false;
> }
>
> which is called from:
> void ProgressDialog::Beep() const
> {
> int after;
> bool should;
> wxString name;
>
> gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false);
> gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60);
> gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString);
>
> if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after * 1000)
> {
> wxBusyCursor busy;
> wxSound s;
>
> if (name.empty())
> {
> s.Create(sizeof(beep), beep);
> }
> else
> {
> s.Create(name);
> }
>
> if (s.IsOk())
> {
> s.Play(wxSOUND_SYNC);
> }
> }
> }
>
> which is called from the ProgressDialog's destructor.
>
> So if you've got "beep on completion on longer activities" enabled in preferences, and "whatever" has taken longer than 60s, you'll get the call to wxFAIL_MSG().
> (I can't see where BeepAfterDuration and BeepFileName can be set in preferences.)
>
> "Preferences > Interface"
> https://manual.audacityteam.org/man/interface_preferences.html <https://manual.audacityteam.org/man/interface_preferences.html>;
>
> I was not able to reproduce the problem, but I'd missed the "Beep on completion" element - I'll retest.
>
> Steve
>
>
>
> David.
>
> On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@... <mailto:flyer185@...>> wrote:
> Running MacOS Mojave. I have never seen this before. Ideas? It happens at the end of running the DeClicker plugin. Running on build #760576 does not bring up the error. I don’t have any builds between the one that works and the one that does not. The assert does always give the same trace. I don’t use any other plugins so can’t say if it’s common to all plugins or just DeClicker. Built in Effects work normally.
>
> <PastedGraphic-2.png>
>
> Cliff
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@... <mailto:Audacity-quality@...>
> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>;
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@... <mailto:Audacity-quality@...>
> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>;
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@... <mailto:Audacity-quality@...>
> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>;
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@... <mailto:Audacity-quality@...>
> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>;
|
|
From: David Bailes <drbailes@gm...> - 2021-06-22 09:57:52
|
On Tue, 22 Jun 2021 at 10:33, Steve Fiddle <stevethefiddle@...> wrote:
> Testing on both macOS and Linux:
> I don't see a crash or warning on either machine, but also I don't hear a
> beep on completion of longer activities.
> I don't normally have that option enabled and I don't know if it has ever
> worked.
>
wxFAIL_MSG() is only called in debug versions.
David.
>
> Steve
>
> On Tue, 22 Jun 2021 at 10:13, Steve Fiddle <stevethefiddle@...>
> wrote:
>
>>
>>
>> On Tue, 22 Jun 2021 at 09:49, David Bailes <drbailes@...> wrote:
>>
>>> Hi Cliff,
>>> I think that there is a problem here, but not sure why it's not been
>>> showing up before.
>>> This is the code for osx that's being called:
>>>
>>> bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data))
>>> {
>>> wxFAIL_MSG( "not implemented" );
>>>
>>> return false;
>>> }
>>>
>>> which is called from:
>>> void ProgressDialog::Beep() const
>>> {
>>> int after;
>>> bool should;
>>> wxString name;
>>>
>>> gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false);
>>> gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60);
>>> gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString);
>>>
>>> if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after *
>>> 1000)
>>> {
>>> wxBusyCursor busy;
>>> wxSound s;
>>>
>>> if (name.empty())
>>> {
>>> s.Create(sizeof(beep), beep);
>>> }
>>> else
>>> {
>>> s.Create(name);
>>> }
>>>
>>> if (s.IsOk())
>>> {
>>> s.Play(wxSOUND_SYNC);
>>> }
>>> }
>>> }
>>>
>>> which is called from the ProgressDialog's destructor.
>>>
>>> So if you've got "beep on completion on longer activities" enabled in
>>> preferences, and "whatever" has taken longer than 60s, you'll get the call
>>> to wxFAIL_MSG().
>>> (I can't see where BeepAfterDuration and BeepFileName can be set in
>>> preferences.)
>>>
>>
>> "Preferences > Interface"
>> https://manual.audacityteam.org/man/interface_preferences.html
>>
>> I was not able to reproduce the problem, but I'd missed the "Beep on
>> completion" element - I'll retest.
>>
>> Steve
>>
>>
>>
>>>
>>> David.
>>>
>>> On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@...> wrote:
>>>
>>>> Running MacOS Mojave. I have never seen this before. Ideas? It happens
>>>> at the end of running the DeClicker plugin. Running on build #760576 does
>>>> not bring up the error. I don’t have any builds between the one that works
>>>> and the one that does not. The assert does always give the same trace. I
>>>> don’t use any other plugins so can’t say if it’s common to all plugins or
>>>> just DeClicker. Built in Effects work normally.
>>>>
>>>>
>>>> Cliff
>>>> _______________________________________________
>>>> Audacity-quality mailing list
>>>> Audacity-quality@...
>>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>>
>>> _______________________________________________
>>> Audacity-quality mailing list
>>> Audacity-quality@...
>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>
>> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@...
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
|
|
From: David Bailes <drbailes@gm...> - 2021-06-22 09:50:18
|
On Windows, I manually set BeepAfterDuration=5 in audacity.cfg (for easier
testing), and I get beeps when the preference is enabled,
David.
On Tue, 22 Jun 2021 at 10:33, Steve Fiddle <stevethefiddle@...> wrote:
> Testing on both macOS and Linux:
> I don't see a crash or warning on either machine, but also I don't hear a
> beep on completion of longer activities.
> I don't normally have that option enabled and I don't know if it has ever
> worked.
>
> Steve
>
> On Tue, 22 Jun 2021 at 10:13, Steve Fiddle <stevethefiddle@...>
> wrote:
>
>>
>>
>> On Tue, 22 Jun 2021 at 09:49, David Bailes <drbailes@...> wrote:
>>
>>> Hi Cliff,
>>> I think that there is a problem here, but not sure why it's not been
>>> showing up before.
>>> This is the code for osx that's being called:
>>>
>>> bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data))
>>> {
>>> wxFAIL_MSG( "not implemented" );
>>>
>>> return false;
>>> }
>>>
>>> which is called from:
>>> void ProgressDialog::Beep() const
>>> {
>>> int after;
>>> bool should;
>>> wxString name;
>>>
>>> gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false);
>>> gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60);
>>> gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString);
>>>
>>> if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after *
>>> 1000)
>>> {
>>> wxBusyCursor busy;
>>> wxSound s;
>>>
>>> if (name.empty())
>>> {
>>> s.Create(sizeof(beep), beep);
>>> }
>>> else
>>> {
>>> s.Create(name);
>>> }
>>>
>>> if (s.IsOk())
>>> {
>>> s.Play(wxSOUND_SYNC);
>>> }
>>> }
>>> }
>>>
>>> which is called from the ProgressDialog's destructor.
>>>
>>> So if you've got "beep on completion on longer activities" enabled in
>>> preferences, and "whatever" has taken longer than 60s, you'll get the call
>>> to wxFAIL_MSG().
>>> (I can't see where BeepAfterDuration and BeepFileName can be set in
>>> preferences.)
>>>
>>
>> "Preferences > Interface"
>> https://manual.audacityteam.org/man/interface_preferences.html
>>
>> I was not able to reproduce the problem, but I'd missed the "Beep on
>> completion" element - I'll retest.
>>
>> Steve
>>
>>
>>
>>>
>>> David.
>>>
>>> On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@...> wrote:
>>>
>>>> Running MacOS Mojave. I have never seen this before. Ideas? It happens
>>>> at the end of running the DeClicker plugin. Running on build #760576 does
>>>> not bring up the error. I don’t have any builds between the one that works
>>>> and the one that does not. The assert does always give the same trace. I
>>>> don’t use any other plugins so can’t say if it’s common to all plugins or
>>>> just DeClicker. Built in Effects work normally.
>>>>
>>>>
>>>> Cliff
>>>> _______________________________________________
>>>> Audacity-quality mailing list
>>>> Audacity-quality@...
>>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>>
>>> _______________________________________________
>>> Audacity-quality mailing list
>>> Audacity-quality@...
>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>
>> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@...
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
|
|
From: Steve Fiddle <stevethefiddle@gm...> - 2021-06-22 09:32:59
|
Testing on both macOS and Linux:
I don't see a crash or warning on either machine, but also I don't hear a
beep on completion of longer activities.
I don't normally have that option enabled and I don't know if it has ever
worked.
Steve
On Tue, 22 Jun 2021 at 10:13, Steve Fiddle <stevethefiddle@...> wrote:
>
>
> On Tue, 22 Jun 2021 at 09:49, David Bailes <drbailes@...> wrote:
>
>> Hi Cliff,
>> I think that there is a problem here, but not sure why it's not been
>> showing up before.
>> This is the code for osx that's being called:
>>
>> bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data))
>> {
>> wxFAIL_MSG( "not implemented" );
>>
>> return false;
>> }
>>
>> which is called from:
>> void ProgressDialog::Beep() const
>> {
>> int after;
>> bool should;
>> wxString name;
>>
>> gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false);
>> gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60);
>> gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString);
>>
>> if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after *
>> 1000)
>> {
>> wxBusyCursor busy;
>> wxSound s;
>>
>> if (name.empty())
>> {
>> s.Create(sizeof(beep), beep);
>> }
>> else
>> {
>> s.Create(name);
>> }
>>
>> if (s.IsOk())
>> {
>> s.Play(wxSOUND_SYNC);
>> }
>> }
>> }
>>
>> which is called from the ProgressDialog's destructor.
>>
>> So if you've got "beep on completion on longer activities" enabled in
>> preferences, and "whatever" has taken longer than 60s, you'll get the call
>> to wxFAIL_MSG().
>> (I can't see where BeepAfterDuration and BeepFileName can be set in
>> preferences.)
>>
>
> "Preferences > Interface"
> https://manual.audacityteam.org/man/interface_preferences.html
>
> I was not able to reproduce the problem, but I'd missed the "Beep on
> completion" element - I'll retest.
>
> Steve
>
>
>
>>
>> David.
>>
>> On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@...> wrote:
>>
>>> Running MacOS Mojave. I have never seen this before. Ideas? It happens
>>> at the end of running the DeClicker plugin. Running on build #760576 does
>>> not bring up the error. I don’t have any builds between the one that works
>>> and the one that does not. The assert does always give the same trace. I
>>> don’t use any other plugins so can’t say if it’s common to all plugins or
>>> just DeClicker. Built in Effects work normally.
>>>
>>>
>>> Cliff
>>> _______________________________________________
>>> Audacity-quality mailing list
>>> Audacity-quality@...
>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>>
>> _______________________________________________
>> Audacity-quality mailing list
>> Audacity-quality@...
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
>
|
|
From: Steve Fiddle <stevethefiddle@gm...> - 2021-06-22 09:14:27
|
On Tue, 22 Jun 2021 at 09:49, David Bailes <drbailes@...> wrote:
> Hi Cliff,
> I think that there is a problem here, but not sure why it's not been
> showing up before.
> This is the code for osx that's being called:
>
> bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data))
> {
> wxFAIL_MSG( "not implemented" );
>
> return false;
> }
>
> which is called from:
> void ProgressDialog::Beep() const
> {
> int after;
> bool should;
> wxString name;
>
> gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false);
> gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60);
> gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString);
>
> if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after *
> 1000)
> {
> wxBusyCursor busy;
> wxSound s;
>
> if (name.empty())
> {
> s.Create(sizeof(beep), beep);
> }
> else
> {
> s.Create(name);
> }
>
> if (s.IsOk())
> {
> s.Play(wxSOUND_SYNC);
> }
> }
> }
>
> which is called from the ProgressDialog's destructor.
>
> So if you've got "beep on completion on longer activities" enabled in
> preferences, and "whatever" has taken longer than 60s, you'll get the call
> to wxFAIL_MSG().
> (I can't see where BeepAfterDuration and BeepFileName can be set in
> preferences.)
>
"Preferences > Interface"
https://manual.audacityteam.org/man/interface_preferences.html
I was not able to reproduce the problem, but I'd missed the "Beep on
completion" element - I'll retest.
Steve
>
> David.
>
> On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@...> wrote:
>
>> Running MacOS Mojave. I have never seen this before. Ideas? It happens at
>> the end of running the DeClicker plugin. Running on build #760576 does not
>> bring up the error. I don’t have any builds between the one that works and
>> the one that does not. The assert does always give the same trace. I don’t
>> use any other plugins so can’t say if it’s common to all plugins or just
>> DeClicker. Built in Effects work normally.
>>
>>
>> Cliff
>> _______________________________________________
>> Audacity-quality mailing list
>> Audacity-quality@...
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@...
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
|
|
From: David Bailes <drbailes@gm...> - 2021-06-22 08:49:05
|
Hi Cliff,
I think that there is a problem here, but not sure why it's not been
showing up before.
This is the code for osx that's being called:
bool wxSound::Create(size_t WXUNUSED(size), const void* WXUNUSED(data))
{
wxFAIL_MSG( "not implemented" );
return false;
}
which is called from:
void ProgressDialog::Beep() const
{
int after;
bool should;
wxString name;
gPrefs->Read(wxT("/GUI/BeepOnCompletion"), &should, false);
gPrefs->Read(wxT("/GUI/BeepAfterDuration"), &after, 60);
gPrefs->Read(wxT("/GUI/BeepFileName"), &name, wxEmptyString);
if (should && wxGetUTCTimeMillis().GetValue() - mStartTime > after *
1000)
{
wxBusyCursor busy;
wxSound s;
if (name.empty())
{
s.Create(sizeof(beep), beep);
}
else
{
s.Create(name);
}
if (s.IsOk())
{
s.Play(wxSOUND_SYNC);
}
}
}
which is called from the ProgressDialog's destructor.
So if you've got "beep on completion on longer activities" enabled in
preferences, and "whatever" has taken longer than 60s, you'll get the call
to wxFAIL_MSG().
(I can't see where BeepAfterDuration and BeepFileName can be set in
preferences.)
David.
On Mon, 21 Jun 2021 at 03:31, Cliff <flyer185@...> wrote:
> Running MacOS Mojave. I have never seen this before. Ideas? It happens at
> the end of running the DeClicker plugin. Running on build #760576 does not
> bring up the error. I don’t have any builds between the one that works and
> the one that does not. The assert does always give the same trace. I don’t
> use any other plugins so can’t say if it’s common to all plugins or just
> DeClicker. Built in Effects work normally.
>
>
> Cliff
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@...
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
|
