Thanks for helping keep SourceForge clean.
Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
Audacity
A free multi-track audio editor and recorder
audacity-quality — Quality Assurance: priorities for overall usability, interface choices, & bugs
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
(60) |
Oct
|
Nov
|
Dec
|
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-09-22 12:11:31
|
On Fri, Sep 22, 2017 at 12:48 PM, Peter Sampson < petersampsonaudacity@...> wrote: > > > On Fri, Sep 22, 2017 at 11:25 AM, James Crook <crookj@...> wrote: > >> Paul, as you are RM if you want to change it unilaterally from my >> perspective you can just go ahead. >> >> There are so many million tweaks possible to theming that I do not wish >> to do them onesey twosey myself. >> The 'correct' workflow is to either collect them on the page: >> http://wiki.audacityteam.org/wiki/Bugs_In_DA_Integration >> under 'Theme Tweaks Requested by Team'. >> or on the page http://wiki.audacityteam.org/wiki/Theme_Tweaks. >> >> Then at some point they can be actioned as a batch. >> > > > Yebbut, it's probably worth a quick fix for the colour of the in-track > track name, > but we (Paul that is) will need to choose carefully. > And remember we need to consider what it looks like on audio tracks when in Spectrogram views - so care is needed. > This recent complaint is only one of many that we've had over the years. > > The way it is now does not appear to be theme dependent (though perhaps > later it should be). > One thing I note (that I had never noticed before) is that it appears to be only audio tracks that have an in-track trackname displayed. There is no such trackname display for: Label tracks, Note tracks or Time tracks, Is this intentionional? Personally I see no reason why these tracks should notalso have in-track displayed names (but maybe not for 2.2.0). Peter > > Peter > >> >> >> >> >> >> >> >> >> On 9/22/2017 8:43 AM, Peter Sampson wrote: >> >> On Fri, Sep 22, 2017 at 2:59 AM, Paul Licameli <paul.licameli@...> <paul.licameli@...> >> wrote: >> >> >> An opinion about the Selection colors in the default, Light theme, which >> is debatable; >> >> >> indeed - debatable, and no more than that (especially at this stage) >> >> >> >> a complaint about too-low contrast for the yellow Track Name overlay (last >> checkbox in Tracks preferences), which I have to agree with. >> >> Not a show-stopper but maybe there can be a quick fix for the track >> overlay color? >> >> >> This has been discussed many times in the past, including more complex >> solutions >> that would allow for the user to choose the required colour - and even mor >> complex >> to allow them to choose the trackname colour on a per-track basis. >> >> As far as I remember, no agreement could ever be reached - so nothing >> happened. >> >> I've always found the yellow a liitke hard to read agains the gray >> background in 2.1.3 >> and earlier. >> >> In 2.2.0 alpha/beta I still find the same in Light (defailt) and Classic - >> but in Dark and >> High Contrast the yeloow is an excellent choice being perfectly clear. >> >> So if any (simple) changes are made to the colour, then we would need to >> ensure that >> it works well in allfour available themes. >> >> Peter/ >> >> >> >> http://forum.audacityteam.org/viewtopic.php?f=50&t=97173 >> >> PRL >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing listAudacity-quality@...nethttps://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >> >> >> _______________________________________________ >> Audacity-quality mailing listAudacity-quality@...nethttps://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-09-22 11:48:47
|
On Fri, Sep 22, 2017 at 11:25 AM, James Crook <crookj@...> wrote: > Paul, as you are RM if you want to change it unilaterally from my > perspective you can just go ahead. > > There are so many million tweaks possible to theming that I do not wish to > do them onesey twosey myself. > The 'correct' workflow is to either collect them on the page: > http://wiki.audacityteam.org/wiki/Bugs_In_DA_Integration > under 'Theme Tweaks Requested by Team'. > or on the page http://wiki.audacityteam.org/wiki/Theme_Tweaks. > > Then at some point they can be actioned as a batch. > Yebbut, it's probably worth a quick fix for the colour of the in-track track name, but we (Paul that is) will need to choose carefully. This recent complaint is only one of many that we've had over the years. The way it is now does not appear to be theme dependent (though perhaps later it should be). Peter > > > > > > > > > On 9/22/2017 8:43 AM, Peter Sampson wrote: > > On Fri, Sep 22, 2017 at 2:59 AM, Paul Licameli <paul.licameli@...> <paul.licameli@...> > wrote: > > > An opinion about the Selection colors in the default, Light theme, which > is debatable; > > > indeed - debatable, and no more than that (especially at this stage) > > > > a complaint about too-low contrast for the yellow Track Name overlay (last > checkbox in Tracks preferences), which I have to agree with. > > Not a show-stopper but maybe there can be a quick fix for the track > overlay color? > > > This has been discussed many times in the past, including more complex > solutions > that would allow for the user to choose the required colour - and even mor > complex > to allow them to choose the trackname colour on a per-track basis. > > As far as I remember, no agreement could ever be reached - so nothing > happened. > > I've always found the yellow a liitke hard to read agains the gray > background in 2.1.3 > and earlier. > > In 2.2.0 alpha/beta I still find the same in Light (defailt) and Classic - > but in Dark and > High Contrast the yeloow is an excellent choice being perfectly clear. > > So if any (simple) changes are made to the colour, then we would need to > ensure that > it works well in allfour available themes. > > Peter/ > > > > http://forum.audacityteam.org/viewtopic.php?f=50&t=97173 > > PRL > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing listAudacity-quality@...nethttps://lists.sourceforge.net/lists/listinfo/audacity-quality > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Audacity-quality mailing listAudacity-quality@...nethttps://lists.sourceforge.net/lists/listinfo/audacity-quality > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: James Crook <crookj@in...> - 2017-09-22 10:25:46
|
Paul, as you are RM if you want to change it unilaterally from my perspective you can just go ahead. There are so many million tweaks possible to theming that I do not wish to do them onesey twosey myself. The 'correct' workflow is to either collect them on the page: http://wiki.audacityteam.org/wiki/Bugs_In_DA_Integration under 'Theme Tweaks Requested by Team'. or on the page http://wiki.audacityteam.org/wiki/Theme_Tweaks. Then at some point they can be actioned as a batch. On 9/22/2017 8:43 AM, Peter Sampson wrote: > On Fri, Sep 22, 2017 at 2:59 AM, Paul Licameli <paul.licameli@...> > wrote: > >> An opinion about the Selection colors in the default, Light theme, which >> is debatable; >> > indeed - debatable, and no more than that (especially at this stage) > > >> a complaint about too-low contrast for the yellow Track Name overlay (last >> checkbox in Tracks preferences), which I have to agree with. >> >> Not a show-stopper but maybe there can be a quick fix for the track >> overlay color? >> > This has been discussed many times in the past, including more complex > solutions > that would allow for the user to choose the required colour - and even mor > complex > to allow them to choose the trackname colour on a per-track basis. > > As far as I remember, no agreement could ever be reached - so nothing > happened. > > I've always found the yellow a liitke hard to read agains the gray > background in 2.1.3 > and earlier. > > In 2.2.0 alpha/beta I still find the same in Light (defailt) and Classic - > but in Dark and > High Contrast the yeloow is an excellent choice being perfectly clear. > > So if any (simple) changes are made to the colour, then we would need to > ensure that > it works well in allfour available themes. > > Peter/ > > >> http://forum.audacityteam.org/viewtopic.php?f=50&t=97173 >> >> PRL >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-09-22 07:43:50
|
On Fri, Sep 22, 2017 at 2:59 AM, Paul Licameli <paul.licameli@...> wrote: > An opinion about the Selection colors in the default, Light theme, which > is debatable; > indeed - debatable, and no more than that (especially at this stage) > a complaint about too-low contrast for the yellow Track Name overlay (last > checkbox in Tracks preferences), which I have to agree with. > > Not a show-stopper but maybe there can be a quick fix for the track > overlay color? > This has been discussed many times in the past, including more complex solutions that would allow for the user to choose the required colour - and even mor complex to allow them to choose the trackname colour on a per-track basis. As far as I remember, no agreement could ever be reached - so nothing happened. I've always found the yellow a liitke hard to read agains the gray background in 2.1.3 and earlier. In 2.2.0 alpha/beta I still find the same in Light (defailt) and Classic - but in Dark and High Contrast the yeloow is an excellent choice being perfectly clear. So if any (simple) changes are made to the colour, then we would need to ensure that it works well in allfour available themes. Peter/ > > http://forum.audacityteam.org/viewtopic.php?f=50&t=97173 > > PRL > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-22 01:59:21
|
An opinion about the Selection colors in the default, Light theme, which is debatable; a complaint about too-low contrast for the yellow Track Name overlay (last checkbox in Tracks preferences), which I have to agree with. Not a show-stopper but maybe there can be a quick fix for the track overlay color? http://forum.audacityteam.org/viewtopic.php?f=50&t=97173 PRL |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-20 19:11:56
|
On Wed, Sep 20, 2017 at 3:06 PM, Robert Hänggi <aarjay.robert@...> wrote: > Thanks Paul > > My question was if users have to write this line themselves for older > plug-ins. > > I think a nice solution would be to add the preview choice to options > under manage--it is currently unused for Nyquist effects. > That's unfortunately only a possibility for post-2.2.0 > > Robert > Steve should be the one to consider this suggestion. He is on vacation right now. PRL > > On 20/09/2017, Paul Licameli <paul.licameli@...> wrote: > > The problem bisects to the following commit. I don't understand the > intent > > completely. But I think preview must now be explicitly enabled in the > > Nyquist source. This can be done with the special comment > > > > ;preview xxx > > > > where xxx is one of: enabled, true, linear, selection > > > > The latter two choices imply other behavior. linear is of course wrong > for > > a compressor. selection means always preview the effect on the complete > > selection. > > > > PRL > > > > > > Author: Steve Daulton <stevedaulton@...> 2017-05-21 18:11:21 > > Committer: Steve Daulton <stevedaulton@...> 2017-05-21 18:11:21 > > Parent: 99e5516ee21f6d69086dc41a6b0ea65f7bf37b72 (Save built-in browser > > size) > > Branches: master and many more (60) > > Follows: Audacity-2.1.3, DarkAudacity-2.1.3x > > Precedes: Audacity-2.2.0-beta-20170901, midi-out-2-bug-1690, > > midi-out-2-full-autoconf, midi-out-2-reworded-ready > > > > Add help button support for other Nyquist effects > > > > > > On Wed, Sep 20, 2017 at 4:23 AM, Robert Hänggi <aarjay.robert@...> > > wrote: > > > >> Hi > >> I have a couple of Nyquist plug-ins that do no longer show a preview > >> button. > >> For instance Chris' Compressor. > >> Do you really want that, should user edit the files in order to get a > >> preview back? > >> > >> Thanks > >> Robert > >> > >> ------------------------------------------------------------ > >> ------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> _______________________________________________ > >> Audacity-quality mailing list > >> Audacity-quality@... > >> https://lists.sourceforge.net/lists/listinfo/audacity-quality > >> > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Robert Hänggi <aarjay.robert@gm...> - 2017-09-20 19:06:56
|
Thanks Paul My question was if users have to write this line themselves for older plug-ins. I think a nice solution would be to add the preview choice to options under manage--it is currently unused for Nyquist effects. That's unfortunately only a possibility for post-2.2.0 Robert On 20/09/2017, Paul Licameli <paul.licameli@...> wrote: > The problem bisects to the following commit. I don't understand the intent > completely. But I think preview must now be explicitly enabled in the > Nyquist source. This can be done with the special comment > > ;preview xxx > > where xxx is one of: enabled, true, linear, selection > > The latter two choices imply other behavior. linear is of course wrong for > a compressor. selection means always preview the effect on the complete > selection. > > PRL > > > Author: Steve Daulton <stevedaulton@...> 2017-05-21 18:11:21 > Committer: Steve Daulton <stevedaulton@...> 2017-05-21 18:11:21 > Parent: 99e5516ee21f6d69086dc41a6b0ea65f7bf37b72 (Save built-in browser > size) > Branches: master and many more (60) > Follows: Audacity-2.1.3, DarkAudacity-2.1.3x > Precedes: Audacity-2.2.0-beta-20170901, midi-out-2-bug-1690, > midi-out-2-full-autoconf, midi-out-2-reworded-ready > > Add help button support for other Nyquist effects > > > On Wed, Sep 20, 2017 at 4:23 AM, Robert Hänggi <aarjay.robert@...> > wrote: > >> Hi >> I have a couple of Nyquist plug-ins that do no longer show a preview >> button. >> For instance Chris' Compressor. >> Do you really want that, should user edit the files in order to get a >> preview back? >> >> Thanks >> Robert >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-20 17:53:31
|
The problem bisects to the following commit. I don't understand the intent
completely. But I think preview must now be explicitly enabled in the
Nyquist source. This can be done with the special comment
;preview xxx
where xxx is one of: enabled, true, linear, selection
The latter two choices imply other behavior. linear is of course wrong for
a compressor. selection means always preview the effect on the complete
selection.
PRL
Author: Steve Daulton <stevedaulton@...> 2017-05-21 18:11:21
Committer: Steve Daulton <stevedaulton@...> 2017-05-21 18:11:21
Parent: 99e5516ee21f6d69086dc41a6b0ea65f7bf37b72 (Save built-in browser
size)
Branches: master and many more (60)
Follows: Audacity-2.1.3, DarkAudacity-2.1.3x
Precedes: Audacity-2.2.0-beta-20170901, midi-out-2-bug-1690,
midi-out-2-full-autoconf, midi-out-2-reworded-ready
Add help button support for other Nyquist effects
On Wed, Sep 20, 2017 at 4:23 AM, Robert Hänggi <aarjay.robert@...>
wrote:
> Hi
> I have a couple of Nyquist plug-ins that do no longer show a preview
> button.
> For instance Chris' Compressor.
> Do you really want that, should user edit the files in order to get a
> preview back?
>
> Thanks
> Robert
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@...
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
|
|
From: Robert Hänggi <aarjay.robert@gm...> - 2017-09-20 08:23:19
|
Hi I have a couple of Nyquist plug-ins that do no longer show a preview button. For instance Chris' Compressor. Do you really want that, should user edit the files in order to get a preview back? Thanks Robert |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-18 18:30:20
|
On Mon, Sep 18, 2017 at 1:23 PM, David Bailes <drbailes@...> wrote: > On 18 September 2017 at 16:06, Paul Licameli <paul.licameli@...> > wrote: > >> >> >> On Mon, Sep 18, 2017 at 6:51 AM, David Bailes <drbailes@...> wrote: >> >>> On 18 September 2017 at 11:50, Paul Licameli <paul.licameli@...> >>> wrote: >>> >>>> Did you use the installer or the .zip? I would think the error should >>>> be alike either way. >>> >>> >>> .zip >>> >> >> Could you try the installer too, please? >> > > Same problem. > > >> >> FossHub tells me over 8500 have downloaded the installer and 1500 the >> .zip. So installer is more popular. >> >> I have not heard complaints of the .dlls working -- surely we would know >> by now if it was happening with earlier builds of Win10. >> > > It's working fine on my Windows 10 1703. > I doubt that many of those who have downloaded the beta are running it on > a preview of the fall update. > I do find the failure very surprising. > > David. > I copied those libraries from somewhere on my Windows 8 (!) system and nobody complained, yet. You have told me the remedy: bundle it with what was packaged in version 2.1.3. PRL > >> PRL >> >> >> >>> >>> David. >>> >>> >>>> >>>> PRL >>>> >>>> >>>> On Monday, September 18, 2017, David Bailes <drbailes@...> wrote: >>>> >>>>> testing audacity 2.2.0 beta portable version on Windowa 10 1709 build >>>>> 16288.1 32bit (Insider preview of fall creators update, slow ring). >>>>> >>>>> On opening Audacity, I get dialogs complaining about msvcr120.dll and >>>>> msvcp120.dll, for example: >>>>> >>>>> --------------------------- >>>>> audacity.exe - Bad Image >>>>> --------------------------- >>>>> C:\Users\drbai\Downloads\audacity-win-2.2.0-beta-20170901\Audacity-test\MSVCR120.dll >>>>> is either not designed to run on Windows or it contains an error. Try >>>>> installing the program again using the original installation media or >>>>> contact your system administrator or the software vendor for support. Error >>>>> status 0xc000035a. >>>>> --------------------------- >>>>> OK >>>>> --------------------------- >>>>> >>>>> Audacity 2.1.3 runs ok. The sizes of these dlls in the beta and in >>>>> 2.1.3 are different, and I can get the beta to run either by removing the >>>>> dlls or by replacing them with the 2.1.3 versions. >>>>> >>>>> David. >>>>> >>>>> >>>> ------------------------------------------------------------ >>>> ------------------ >>>> Check out the vibrant tech community on one of the world's most >>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>>> _______________________________________________ >>>> Audacity-quality mailing list >>>> Audacity-quality@... >>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>>> >>>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >>> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: David Bailes <drbailes@gm...> - 2017-09-18 17:23:09
|
On 18 September 2017 at 16:06, Paul Licameli <paul.licameli@...> wrote: > > > On Mon, Sep 18, 2017 at 6:51 AM, David Bailes <drbailes@...> wrote: > >> On 18 September 2017 at 11:50, Paul Licameli <paul.licameli@...> >> wrote: >> >>> Did you use the installer or the .zip? I would think the error should >>> be alike either way. >> >> >> .zip >> > > Could you try the installer too, please? > Same problem. > > FossHub tells me over 8500 have downloaded the installer and 1500 the > .zip. So installer is more popular. > > I have not heard complaints of the .dlls working -- surely we would know > by now if it was happening with earlier builds of Win10. > It's working fine on my Windows 10 1703. I doubt that many of those who have downloaded the beta are running it on a preview of the fall update. I do find the failure very surprising. David. > > PRL > > > >> >> David. >> >> >>> >>> PRL >>> >>> >>> On Monday, September 18, 2017, David Bailes <drbailes@...> wrote: >>> >>>> testing audacity 2.2.0 beta portable version on Windowa 10 1709 build >>>> 16288.1 32bit (Insider preview of fall creators update, slow ring). >>>> >>>> On opening Audacity, I get dialogs complaining about msvcr120.dll and >>>> msvcp120.dll, for example: >>>> >>>> --------------------------- >>>> audacity.exe - Bad Image >>>> --------------------------- >>>> C:\Users\drbai\Downloads\audacity-win-2.2.0-beta-20170901\Audacity-test\MSVCR120.dll >>>> is either not designed to run on Windows or it contains an error. Try >>>> installing the program again using the original installation media or >>>> contact your system administrator or the software vendor for support. Error >>>> status 0xc000035a. >>>> --------------------------- >>>> OK >>>> --------------------------- >>>> >>>> Audacity 2.1.3 runs ok. The sizes of these dlls in the beta and in >>>> 2.1.3 are different, and I can get the beta to run either by removing the >>>> dlls or by replacing them with the 2.1.3 versions. >>>> >>>> David. >>>> >>>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >>> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-18 15:07:08
|
On Mon, Sep 18, 2017 at 6:51 AM, David Bailes <drbailes@...> wrote: > On 18 September 2017 at 11:50, Paul Licameli <paul.licameli@...> > wrote: > >> Did you use the installer or the .zip? I would think the error should be >> alike either way. > > > .zip > Could you try the installer too, please? FossHub tells me over 8500 have downloaded the installer and 1500 the .zip. So installer is more popular. I have not heard complaints of the .dlls working -- surely we would know by now if it was happening with earlier builds of Win10. PRL > > David. > > >> >> PRL >> >> >> On Monday, September 18, 2017, David Bailes <drbailes@...> wrote: >> >>> testing audacity 2.2.0 beta portable version on Windowa 10 1709 build >>> 16288.1 32bit (Insider preview of fall creators update, slow ring). >>> >>> On opening Audacity, I get dialogs complaining about msvcr120.dll and >>> msvcp120.dll, for example: >>> >>> --------------------------- >>> audacity.exe - Bad Image >>> --------------------------- >>> C:\Users\drbai\Downloads\audacity-win-2.2.0-beta-20170901\Audacity-test\MSVCR120.dll >>> is either not designed to run on Windows or it contains an error. Try >>> installing the program again using the original installation media or >>> contact your system administrator or the software vendor for support. Error >>> status 0xc000035a. >>> --------------------------- >>> OK >>> --------------------------- >>> >>> Audacity 2.1.3 runs ok. The sizes of these dlls in the beta and in 2.1.3 >>> are different, and I can get the beta to run either by removing the dlls or >>> by replacing them with the 2.1.3 versions. >>> >>> David. >>> >>> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: David Bailes <drbailes@gm...> - 2017-09-18 10:51:59
|
On 18 September 2017 at 11:50, Paul Licameli <paul.licameli@...> wrote: > Did you use the installer or the .zip? I would think the error should be > alike either way. .zip David. > > PRL > > > On Monday, September 18, 2017, David Bailes <drbailes@...> wrote: > >> testing audacity 2.2.0 beta portable version on Windowa 10 1709 build >> 16288.1 32bit (Insider preview of fall creators update, slow ring). >> >> On opening Audacity, I get dialogs complaining about msvcr120.dll and >> msvcp120.dll, for example: >> >> --------------------------- >> audacity.exe - Bad Image >> --------------------------- >> C:\Users\drbai\Downloads\audacity-win-2.2.0-beta-20170901\Audacity-test\MSVCR120.dll >> is either not designed to run on Windows or it contains an error. Try >> installing the program again using the original installation media or >> contact your system administrator or the software vendor for support. Error >> status 0xc000035a. >> --------------------------- >> OK >> --------------------------- >> >> Audacity 2.1.3 runs ok. The sizes of these dlls in the beta and in 2.1.3 >> are different, and I can get the beta to run either by removing the dlls or >> by replacing them with the 2.1.3 versions. >> >> David. >> >> > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-18 10:50:32
|
Did you use the installer or the .zip? I would think the error should be alike either way. PRL On Monday, September 18, 2017, David Bailes <drbailes@...> wrote: > testing audacity 2.2.0 beta portable version on Windowa 10 1709 build > 16288.1 32bit (Insider preview of fall creators update, slow ring). > > On opening Audacity, I get dialogs complaining about msvcr120.dll and > msvcp120.dll, for example: > > --------------------------- > audacity.exe - Bad Image > --------------------------- > C:\Users\drbai\Downloads\audacity-win-2.2.0-beta-20170901\Audacity-test\MSVCR120.dll > is either not designed to run on Windows or it contains an error. Try > installing the program again using the original installation media or > contact your system administrator or the software vendor for support. Error > status 0xc000035a. > --------------------------- > OK > --------------------------- > > Audacity 2.1.3 runs ok. The sizes of these dlls in the beta and in 2.1.3 > are different, and I can get the beta to run either by removing the dlls or > by replacing them with the 2.1.3 versions. > > David. > > |
|
From: David Bailes <drbailes@gm...> - 2017-09-18 09:45:35
|
testing audacity 2.2.0 beta portable version on Windowa 10 1709 build 16288.1 32bit (Insider preview of fall creators update, slow ring). On opening Audacity, I get dialogs complaining about msvcr120.dll and msvcp120.dll, for example: --------------------------- audacity.exe - Bad Image --------------------------- C:\Users\drbai\Downloads\audacity-win-2.2.0-beta-20170901\Audacity-test\MSVCR120.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc000035a. --------------------------- OK --------------------------- Audacity 2.1.3 runs ok. The sizes of these dlls in the beta and in 2.1.3 are different, and I can get the beta to run either by removing the dlls or by replacing them with the 2.1.3 versions. David. |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-17 22:17:39
|
On Sun, Sep 17, 2017 at 5:05 PM, Bill Wharrie <billwh@...> wrote: > Mac 10.11.4 and Audacity-alpha Sept 17 commit a5aaaf > > I was investigating bug 1554 when I came across this: > > 1) Delete audacity.cfg > 2) Launch Audacity and immediately quit using Cmd+Q* > 3) Launch Audacity > 4) View > Toolbars > Spectral Selection Toolbar** > 5) View > Toolbars > Reset Toolbars > 6) Quit Audacity using Cmd+Q* > The debug dialog appears but it is unresponsive because Audacity has hung. > Force quit is required. > > Repetition of steps 3 to 6 consistently results in a hang/crash. > > *I don’t know if doing Audacity > Quit instead of Cmd+Q really makes a > difference, but it seemed to. > > **If in step 4 you choose Scrub Toolbar, the crash doesn’t happen. > > — Bill > > I cannot reproduce this in either a release or a debug build. I reverted the fix for bug 1554, before commit a5aaaf. I explained why in comments for ecd149edad. We can release without fixing it. PRL > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Bill Wharrie <billwh@go...> - 2017-09-17 21:05:59
|
Mac 10.11.4 and Audacity-alpha Sept 17 commit a5aaaf I was investigating bug 1554 when I came across this: 1) Delete audacity.cfg 2) Launch Audacity and immediately quit using Cmd+Q* 3) Launch Audacity 4) View > Toolbars > Spectral Selection Toolbar** 5) View > Toolbars > Reset Toolbars 6) Quit Audacity using Cmd+Q* The debug dialog appears but it is unresponsive because Audacity has hung. Force quit is required. Repetition of steps 3 to 6 consistently results in a hang/crash. *I don’t know if doing Audacity > Quit instead of Cmd+Q really makes a difference, but it seemed to. **If in step 4 you choose Scrub Toolbar, the crash doesn’t happen. — Bill |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-12 19:36:26
|
Taking interest in translation lately, I have tried setting Audacity's language to Arabic or Hebrew or Farsi, the three right-to-left languages that we support. And some REALLY WEIRD things happen on Windows! I think this should be a regular part of testing of future features of Audacity. Do you think there is not a lot of Audacity usage in countries with RTL languages? Well, see how awful and confusing the Windows version gets -- and maybe that explains why! On Mac, things otherwise seem sane. (On Mac, there is also the language setting in System Preferences. This affects things like menu layout, putting accelerators left of names when you choose an RTL language, independently of Audacity's preferences.) On Windows, if you open a new main window after changing language in Audacity's Preferences, or if you restart Audacity, then almost everything gets drawn mirrored! Even the digits in the time ruler! Beginning with the splash screen bitmap, flipping the logo and showing backwards Latin letters. yticaduA I blame wxWidgets. Some examination of its source code for mention of LayoutDirection indicates that there is some native notion of layout direction of windows and drawing contexts, on Windows and GTK, but not on Mac. Audacity is trying to use this native layout direction when it is there. But it must be doing some erroneous things with it. I think we can compensate with calls to wxWindow::SetLayoutDirection whenever we build any window that paints bitmaps, overriding what wxWidgets is doing by default. But these changes will have to go in many places, and again, as new features are developed, then they should be tested in RTL locales too, to make sure they don't draw strangely. PRL |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-10 17:13:00
|
Beware English grammar bias when you write code with translatable strings! I have not read it all yet, but I recommed that all developers become familiar with the guidelines in the following section of the gettext reference: https://www.gnu.org/software/gettext/manual/gettext.html#Preparing-Strings Phrases should not be assembled from individually translated words and numerals and punctuation, as is done in too many places now. Translated strings should put words in context. Don't assemble a noun and an adjective, separately translated -- think of the agreement that some languages require, or that the adjective may come after. Basque puts the numeral 1 after the noun, but other numerals before, so number plus noun, at least, should be in a single format string, as _("%d hours") -- do NOT format _("%d %s") where %s is the result of another one-word translation. Some languages require more than two alternative forms of a phrase to make correct plurals. Some languages have complicated rules (Russian: If the number modulo ten is two, three, or four, then use genitive singular case. UNLESS it is 12, 13, or 14 modulo 100 -- in which case use genitive plural. Otherwise...). I have learned that the GNU gettext utilities, that the wxWidgets translation is based on, can produce translation files that accommodate these complications. We have only to use the wxPLURAL macro in all the appropriate places. http://docs.wxwidgets.org/3.1/group__group__funcmacro__string.html#gadc7c2f1bab3914af93feb47945003409 Perhaps we will not always present full sentences for translation, as the reference recommends, but surely we should present as much context as we can. As your RM I do not intend to fix these bad grammar problems now -- I have been aware of them, but I came too late to an understanding of how gettext helps us address them. As a contributor in the next version, I do mean to attempt a sweep of these things. A question then is how to maintain good practice in new code. Who will police it? Where in the wiki should we add the recommendations? PRL |
|
From: Cliff Scott <flyer185@gm...> - 2017-09-09 00:38:42
|
Interesting. FFox is my default browser and the manual and the helps each open a new window even though FFox is set to force everything to a new tab. Somehow Audacity is sending the command in a way that forces a new window. Open the manual and I get 1 new window, click a help button another window opens. What happens if FFox is not open, but Edge is and you click for the local manual or helps? Does it open new windows for Edge the same as I see here on FFox? The one advantage of this way of doing it is that if, FFox in my case, is open in another desktop then the new window appears in what ever desktop Audacity is running in so the user doesn't need to switch desktops to read it. I guess I see this may be useful after all now that I see this aspect. Cliff > On Sep 8, 2017, at 5:11 PM, Peter Sampson <petersampsonaudacity@...> wrote: > > If I have the local Manual installed then the Help >Manual, and > the various new help buttons, open in a new tab in my > already open Firefox. > > With no local Manual -or with Prefs set get the online Manual, then > the first use opens in a new Microsoft Edge, subsequent uses open > new tabs in that Edge. > > Note the Firefox is my browser of choice for use - but Edge is my > default browser. > > Peter. > > > On Fri, Sep 8, 2017 at 9:35 PM, Cliff Scott <flyer185@... <mailto:flyer185@...>> wrote: > Playing with the beta the help>manual opens in a new firefox window even though firefox is already running. The last alpha I built didn't do that, but as expected opened in a new tab in the existing window. To my way of thinking this will not be a welcome change. Is there a definite reason for it being this way now? > > Cliff > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot>; > _______________________________________________ > 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>; > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-09-08 22:12:21
|
If I have the local Manual installed then the Help >Manual, and the various new help buttons, open in a new tab in my already open Firefox. With no local Manual -or with Prefs set get the online Manual, then the first use opens in a new Microsoft Edge, subsequent uses open new tabs in that Edge. Note the Firefox is my browser of choice for use - but Edge is my default browser. Peter. On Fri, Sep 8, 2017 at 9:35 PM, Cliff Scott <flyer185@...> wrote: > Playing with the beta the help>manual opens in a new firefox window even > though firefox is already running. The last alpha I built didn't do that, > but as expected opened in a new tab in the existing window. To my way of > thinking this will not be a welcome change. Is there a definite reason for > it being this way now? > > Cliff > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Cliff Scott <flyer185@gm...> - 2017-09-08 20:35:30
|
Playing with the beta the help>manual opens in a new firefox window even though firefox is already running. The last alpha I built didn't do that, but as expected opened in a new tab in the existing window. To my way of thinking this will not be a welcome change. Is there a definite reason for it being this way now? Cliff |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-06 17:59:37
|
On Wed, Sep 6, 2017 at 1:48 PM, Peter Sampson < petersampsonaudacity@...> wrote: > Our Consistency page in the Manual says: > https://alphamanual.audacityteam.org/man/Consistency#Capitalization_of_ > page_title_and_section_headings > > Capitalization of page title and section headings > > Use sentence capitalization, not title capitalization and not CamelCase > <https://en.wikipedia.org/wiki/CamelCase>;. This means only the first word > is capitalized except for proper nouns and "Audacity-specific entities" > such as "Device Toolbar" or "Scrubbing" or "Timeline". Generic entities > common to all software such as "context menu" or "dialog" are not > capitalized. > > > And see this secton too: > > https://alphamanual.audacityteam.org/man/Consistency#Layout > > > <https://alphamanual.audacityteam.org/man/Consistency#Layout>; > > So I think it's "by" and not "By" > A sub-menu title is not quite the same as a section sub-heading. If you look just at submenus of Tracks, I suppose it is consistent that little prepositions be lowercase. But perhaps the items shoudld be "Sort by Start Time" and "Sort by Name" for consistency with the repetition of the verb in the Align sub-menu. Edit, Labels, "Add Label At Selection" is an inconsistency elsewhere. I have said I want to "thaw" the string set to allow some additions, but I am hesitant about changes. So I will let this be but someone should reexamine all the menu names for consistency during the next release. PRL > > Peter. > > > > On Wed, Sep 6, 2017 at 6:40 PM, Paul Licameli <paul.licameli@...> > wrote: > >> Our Danish translator raises this. >> >> I keep forgetting what exactly are capitalization conventions. >> >> So: by -> By ? >> >> PRL >> >> >> ---------- Forwarded message ---------- >> From: scootergrisen <scootergrisen@...> >> Date: Tue, Sep 5, 2017 at 12:46 PM >> Subject: [Audacity-translation] Menu items "by &Start time" og "by &Name" >> should start with big letter >> To: audacity-translation@... >> >> >> I suppose these strings should be begin with big letter: >> >> #: src/Menus.cpp:1049 >> msgid "by &Start time" >> >> #: src/Menus.cpp:1052 >> msgid "by &Name" >> >> Can be seen in menu Track > Sort by. >> >> Just like in menu View > Jump to. >> There the strings begin with be letters. >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-translation mailing list >> Audacity-translation@... >> https://lists.sourceforge.net/lists/listinfo/audacity-translation >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-09-06 17:49:14
|
Our Consistency page in the Manual says: https://alphamanual.audacityteam.org/man/Consistency#Capitalization_of_page_title_and_section_headings Capitalization of page title and section headings Use sentence capitalization, not title capitalization and not CamelCase <https://en.wikipedia.org/wiki/CamelCase>;. This means only the first word is capitalized except for proper nouns and "Audacity-specific entities" such as "Device Toolbar" or "Scrubbing" or "Timeline". Generic entities common to all software such as "context menu" or "dialog" are not capitalized. And see this secton too: https://alphamanual.audacityteam.org/man/Consistency#Layout <https://alphamanual.audacityteam.org/man/Consistency#Layout>; So I think it's "by" and not "By" Peter. On Wed, Sep 6, 2017 at 6:40 PM, Paul Licameli <paul.licameli@...> wrote: > Our Danish translator raises this. > > I keep forgetting what exactly are capitalization conventions. > > So: by -> By ? > > PRL > > > ---------- Forwarded message ---------- > From: scootergrisen <scootergrisen@...> > Date: Tue, Sep 5, 2017 at 12:46 PM > Subject: [Audacity-translation] Menu items "by &Start time" og "by &Name" > should start with big letter > To: audacity-translation@... > > > I suppose these strings should be begin with big letter: > > #: src/Menus.cpp:1049 > msgid "by &Start time" > > #: src/Menus.cpp:1052 > msgid "by &Name" > > Can be seen in menu Track > Sort by. > > Just like in menu View > Jump to. > There the strings begin with be letters. > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-translation mailing list > Audacity-translation@... > https://lists.sourceforge.net/lists/listinfo/audacity-translation > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-09-06 17:40:22
|
Our Danish translator raises this. I keep forgetting what exactly are capitalization conventions. So: by -> By ? PRL ---------- Forwarded message ---------- From: scootergrisen <scootergrisen@...> Date: Tue, Sep 5, 2017 at 12:46 PM Subject: [Audacity-translation] Menu items "by &Start time" og "by &Name" should start with big letter To: audacity-translation@... I suppose these strings should be begin with big letter: #: src/Menus.cpp:1049 msgid "by &Start time" #: src/Menus.cpp:1052 msgid "by &Name" Can be seen in menu Track > Sort by. Just like in menu View > Jump to. There the strings begin with be letters. ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Audacity-translation mailing list Audacity-translation@... https://lists.sourceforge.net/lists/listinfo/audacity-translation |
897 messages has been excluded from this view by a project administrator.