audacity-devel Mailing List for Audacity (Page 3)
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
Menu
▾
▴
audacity-devel — Discussion among Audacity developers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(50) |
Nov
(77) |
Dec
(169) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(139) |
Feb
(147) |
Mar
(111) |
Apr
(348) |
May
(262) |
Jun
(294) |
Jul
(315) |
Aug
(186) |
Sep
(132) |
Oct
(135) |
Nov
(358) |
Dec
(241) |
| 2003 |
Jan
(557) |
Feb
(489) |
Mar
(361) |
Apr
(378) |
May
(493) |
Jun
(348) |
Jul
(289) |
Aug
(259) |
Sep
(322) |
Oct
(463) |
Nov
(305) |
Dec
(201) |
| 2004 |
Jan
(198) |
Feb
(186) |
Mar
(192) |
Apr
(216) |
May
(175) |
Jun
(200) |
Jul
(277) |
Aug
(127) |
Sep
(64) |
Oct
(208) |
Nov
(170) |
Dec
(154) |
| 2005 |
Jan
(239) |
Feb
(171) |
Mar
(123) |
Apr
(55) |
May
(74) |
Jun
(100) |
Jul
(129) |
Aug
(221) |
Sep
(209) |
Oct
(270) |
Nov
(590) |
Dec
(313) |
| 2006 |
Jan
(377) |
Feb
(189) |
Mar
(234) |
Apr
(180) |
May
(230) |
Jun
(404) |
Jul
(574) |
Aug
(300) |
Sep
(424) |
Oct
(444) |
Nov
(363) |
Dec
(153) |
| 2007 |
Jan
(223) |
Feb
(106) |
Mar
(311) |
Apr
(233) |
May
(336) |
Jun
(278) |
Jul
(467) |
Aug
(416) |
Sep
(550) |
Oct
(503) |
Nov
(483) |
Dec
(271) |
| 2008 |
Jan
(344) |
Feb
(127) |
Mar
(416) |
Apr
(381) |
May
(679) |
Jun
(749) |
Jul
(549) |
Aug
(281) |
Sep
(137) |
Oct
(324) |
Nov
(200) |
Dec
(330) |
| 2009 |
Jan
(634) |
Feb
(438) |
Mar
(560) |
Apr
(387) |
May
(313) |
Jun
(443) |
Jul
(947) |
Aug
(505) |
Sep
(477) |
Oct
(679) |
Nov
(714) |
Dec
(407) |
| 2010 |
Jan
(348) |
Feb
(283) |
Mar
(232) |
Apr
(173) |
May
(79) |
Jun
(109) |
Jul
(128) |
Aug
(62) |
Sep
(118) |
Oct
(153) |
Nov
(57) |
Dec
(76) |
| 2011 |
Jan
(105) |
Feb
(150) |
Mar
(314) |
Apr
(266) |
May
(55) |
Jun
(47) |
Jul
(113) |
Aug
(70) |
Sep
(77) |
Oct
(93) |
Nov
(106) |
Dec
(190) |
| 2012 |
Jan
(68) |
Feb
(188) |
Mar
(313) |
Apr
(80) |
May
(122) |
Jun
(222) |
Jul
(94) |
Aug
(239) |
Sep
(64) |
Oct
(164) |
Nov
(168) |
Dec
(277) |
| 2013 |
Jan
(336) |
Feb
(156) |
Mar
(80) |
Apr
(135) |
May
(150) |
Jun
(139) |
Jul
(160) |
Aug
(266) |
Sep
(386) |
Oct
(465) |
Nov
(366) |
Dec
(156) |
| 2014 |
Jan
(190) |
Feb
(88) |
Mar
(60) |
Apr
(38) |
May
(146) |
Jun
(104) |
Jul
(189) |
Aug
(424) |
Sep
(235) |
Oct
(990) |
Nov
(598) |
Dec
(393) |
| 2015 |
Jan
(256) |
Feb
(40) |
Mar
(195) |
Apr
(497) |
May
(227) |
Jun
(138) |
Jul
(257) |
Aug
(351) |
Sep
(151) |
Oct
(119) |
Nov
(78) |
Dec
(16) |
| 2016 |
Jan
(225) |
Feb
(289) |
Mar
(267) |
Apr
(318) |
May
(198) |
Jun
(177) |
Jul
(155) |
Aug
(268) |
Sep
(175) |
Oct
(56) |
Nov
(147) |
Dec
(67) |
| 2017 |
Jan
(110) |
Feb
(148) |
Mar
(191) |
Apr
(210) |
May
(164) |
Jun
(261) |
Jul
(332) |
Aug
(349) |
Sep
(54) |
Oct
(171) |
Nov
(199) |
Dec
(153) |
| 2018 |
Jan
(351) |
Feb
(182) |
Mar
(345) |
Apr
(113) |
May
(76) |
Jun
(176) |
Jul
(60) |
Aug
(171) |
Sep
(183) |
Oct
(310) |
Nov
(150) |
Dec
(23) |
| 2019 |
Jan
(91) |
Feb
(73) |
Mar
(172) |
Apr
(119) |
May
(112) |
Jun
(145) |
Jul
(66) |
Aug
(60) |
Sep
(89) |
Oct
(104) |
Nov
(89) |
Dec
(157) |
| 2020 |
Jan
(126) |
Feb
(322) |
Mar
(108) |
Apr
(98) |
May
(227) |
Jun
(194) |
Jul
(374) |
Aug
(85) |
Sep
(122) |
Oct
(44) |
Nov
(18) |
Dec
(72) |
| 2021 |
Jan
(120) |
Feb
(101) |
Mar
(169) |
Apr
(167) |
May
(115) |
Jun
(32) |
Jul
(17) |
Aug
(12) |
Sep
|
Oct
(2) |
Nov
(3) |
Dec
|
| 2022 |
Jan
(5) |
Feb
|
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2023 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Peter S. <pet...@gm...> - 2021-07-01 07:45:48
|
On Wed, Jun 30, 2021 at 11:40 PM Peter Sampson < pet...@gm...> wrote: > > > On Wed, Jun 30, 2021 at 11:38 PM Peter Sampson < > pet...@gm...> wrote: > >> >> >> On Wed, Jun 30, 2021 at 8:15 PM Martin Keary via audacity-devel < >> aud...@li...> 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 >>> >> >> >> 1) Most importantly when Audacity launches from the install and then from >> the App (64-bit app on W10) >> I get this error: >> [image: image.png] >> I did send the error reports to base with the "Send" button >> > > If I then clear my audacity settings folder and re-launch I no longer get > this error message. > I did wonder if it might be because I had been testing alpha 3.0.4 - so I 1) cleared audacity settings folder 2) ran 3.0.3 32-bit 3) ran 3.0.3 RC2 64-bit 4) Observe *no* error message on launch 5) ran 3.0.4 latest alpha 64-bit 6) ran 3.0.3 RC2 64-bit 7) Observe *no* error message on launch So I have no idea what caused that error message (perhaps the ET phone home error log may provide clues) but I can't seem to provoke this again this morning. Peter. > Peter. > > > >> >> 2) The installation EXE still fails to create a shortcut for me even >> though I ask for one. >> >> >> 3) the 64-bit 32-but Windows apps are still not clearly labelled on the >> download page, as I reported with RC1 >> [image: image.png] >> >> Peter. >> >> >> >> >>> Thanks! >>> Martin >>> _______________________________________________ >>> audacity-devel mailing list >>> aud...@li... >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>> >> |
|
From: Peter S. <pet...@gm...> - 2021-06-30 22:41:16
|
On Wed, Jun 30, 2021 at 11:38 PM Peter Sampson < pet...@gm...> wrote: > > > On Wed, Jun 30, 2021 at 8:15 PM Martin Keary via audacity-devel < > aud...@li...> 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 >> > > > 1) Most importantly when Audacity launches from the install and then from > the App (64-bit app on W10) > I get this error: > [image: image.png] > I did send the error reports to base with the "Send" button > If I then clear my audacity settings folder and re-launch I no longer get this error message. Peter. > > 2) The installation EXE still fails to create a shortcut for me even > though I ask for one. > > > 3) the 64-bit 32-but Windows apps are still not clearly labelled on the > download page, as I reported with RC1 > [image: image.png] > > Peter. > > > > >> Thanks! >> Martin >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > |
|
From: Peter S. <pet...@gm...> - 2021-06-30 22:39:12
|
On Wed, Jun 30, 2021 at 8:15 PM Martin Keary via audacity-devel < aud...@li...> 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 > 1) Most importantly when Audacity launches from the install and then from the App (64-bit app on W10) I get this error: [image: image.png] I did send the error reports to base with the "Send" button 2) The installation EXE still fails to create a shortcut for me even though I ask for one. 3) the 64-bit 32-but Windows apps are still not clearly labelled on the download page, as I reported with RC1 [image: image.png] Peter. > Thanks! > Martin > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Martin K. <m....@mu...> - 2021-06-30 19:14:49
|
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: Peter S. <pet...@gm...> - 2021-06-30 14:53:37
|
On Wed, Jun 30, 2021 at 3:40 PM Steve Fiddle <ste...@gm...> wrote: > > > On Wed, 30 Jun 2021 at 14:55, Peter Sampson < > pet...@gm...> wrote: > >> >> >> On Wed, Jun 30, 2021 at 12:06 PM Steve Fiddle <ste...@gm...> >> wrote: >> >>> Where should bugs in RCs be reported? >>> >>> Reporting here for now: >>> >>> Testing on Xubuntu 20.04 with audacity-linux-3.0.3-RC2-x86_64.AppImage >>> When >>> UpdateScheduledTime= >>> is set to an invalid value (such as nothing, as shown above), the >>> Audacity splash screen opens, then nothing - the main Audacity window does >>> not open, though Audacity is running. There's no error message, and no >>> message in the terminal. >>> The Audacity process has to be killed. >>> >> >> Is this really a bug? >> > > I think it is, because care has been taken with other settings to ensure > that Audacity still launches if settings are invalid. > > >> >> The civilian user is not supposed to go around editing audacity.cfg. >> > > True, but what if the audacity.cfg file gets corrupted somehow, or if a > user does mess with it, or if a bug elsewhere writes an invalid value, .... > Better if Audacity is more robust and can survive an invalid setting by > (automatically) dropping back to the default, (as it does with other > settings). > > >> If you do feel it is a bug I would log it as an RC bug on GitHub and fag >> it as "Re;ease 3.0.3" in the Projects >> and as "Audacity 3.0.3 in the Milestone field. >> > > You mean add it as an "Issue"? ( > https://github.com/audacity/audacity/issues) > Yepper, that's my understanding of the MUSE protocol as it stands right now. Peter. > Steve > > > >> >> Peter. >> >> >> >>> I've tested a few other setting in audacity.cfg, and they appear to >>> correctly revert to default settings when invalid. >>> >>> Steve >>> _______________________________________________ >>> audacity-devel mailing list >>> aud...@li... >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>> >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > |
|
From: Steve F. <ste...@gm...> - 2021-06-30 14:41:11
|
On Wed, 30 Jun 2021 at 14:55, Peter Sampson <pet...@gm...> wrote: > > > On Wed, Jun 30, 2021 at 12:06 PM Steve Fiddle <ste...@gm...> > wrote: > >> Where should bugs in RCs be reported? >> >> Reporting here for now: >> >> Testing on Xubuntu 20.04 with audacity-linux-3.0.3-RC2-x86_64.AppImage >> When >> UpdateScheduledTime= >> is set to an invalid value (such as nothing, as shown above), the >> Audacity splash screen opens, then nothing - the main Audacity window does >> not open, though Audacity is running. There's no error message, and no >> message in the terminal. >> The Audacity process has to be killed. >> > > Is this really a bug? > I think it is, because care has been taken with other settings to ensure that Audacity still launches if settings are invalid. > > The civilian user is not supposed to go around editing audacity.cfg. > True, but what if the audacity.cfg file gets corrupted somehow, or if a user does mess with it, or if a bug elsewhere writes an invalid value, .... Better if Audacity is more robust and can survive an invalid setting by (automatically) dropping back to the default, (as it does with other settings). > If you do feel it is a bug I would log it as an RC bug on GitHub and fag > it as "Re;ease 3.0.3" in the Projects > and as "Audacity 3.0.3 in the Milestone field. > You mean add it as an "Issue"? (https://github.com/audacity/audacity/issues) Steve > > Peter. > > > >> I've tested a few other setting in audacity.cfg, and they appear to >> correctly revert to default settings when invalid. >> >> Steve >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Peter S. <pet...@gm...> - 2021-06-30 13:53:43
|
On Wed, Jun 30, 2021 at 12:06 PM Steve Fiddle <ste...@gm...> wrote: > Where should bugs in RCs be reported? > > Reporting here for now: > > Testing on Xubuntu 20.04 with audacity-linux-3.0.3-RC2-x86_64.AppImage > When > UpdateScheduledTime= > is set to an invalid value (such as nothing, as shown above), the Audacity > splash screen opens, then nothing - the main Audacity window does not open, > though Audacity is running. There's no error message, and no message in the > terminal. > The Audacity process has to be killed. > Is this really a bug? The civilian user is not supposed to go around editing audacity.cfg. If you do feel it is a bug I would log it as an RC bug on GitHub and fag it as "Re;ease 3.0.3" in the Projects and as "Audacity 3.0.3 in the Milestone field. Peter. > I've tested a few other setting in audacity.cfg, and they appear to > correctly revert to default settings when invalid. > > Steve > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Steve F. <ste...@gm...> - 2021-06-30 11:06:12
|
Where should bugs in RCs be reported? Reporting here for now: Testing on Xubuntu 20.04 with audacity-linux-3.0.3-RC2-x86_64.AppImage When UpdateScheduledTime= is set to an invalid value (such as nothing, as shown above), the Audacity splash screen opens, then nothing - the main Audacity window does not open, though Audacity is running. There's no error message, and no message in the terminal. The Audacity process has to be killed. I've tested a few other setting in audacity.cfg, and they appear to correctly revert to default settings when invalid. Steve |
|
From: Steve F. <ste...@gm...> - 2021-06-29 09:14:24
|
On Tue, 29 Jun 2021 at 09:52, Peter Sampson <pet...@gm...> wrote: > > > On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < > aud...@li...> 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 >> Aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Peter S. <pet...@gm...> - 2021-06-29 08:52:23
|
On Mon, Jun 28, 2021 at 5:53 PM Martin Keary via Audacity-quality < aud...@li...> 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 > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Martin K. <m....@mu...> - 2021-06-28 16:56:28
|
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: Peter S. <pet...@gm...> - 2021-06-24 15:16:32
|
On Wed, Jun 23, 2021 at 9:00 PM Calum McConnell < cal...@gm...> wrote: > Thank you! The new version looks great! :) > Thanks Calum - glad you like the changes. 😃 And thanks for the nudge 😎 Peter. > On Tue, 2021-06-22 at 10:41 +0100, Steve Fiddle wrote: > > I agree with most of this, so I have substantially updated the page in the > alpha manual (for Audacity 3.0.3). > > The revised version is available here: > > https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Linux > > Steve > > On Fri, 18 Jun 2021 at 18:47, Calum McConnell < > cal...@gm...> wrote: > > Dear Audacity developers, > The VST plugin installation instructions for Linux (as they currently > exist at > > https://manual.audacityteam.org/man/installing_effect_generator_and_analyzer_plug_ins_on_linux.html > ) > aren't a good idea. On many linux systems (at the very least, Debian, > Ubuntu, and all other users of dpkg), the contents of the folders > /usr/lib and /usr/bin should not be modified by a human. This is because > the package manager is designed to have sole control over those folders. > Now, there are enough safety checks that this probably won't lead to > issues, but there are many management headaches that can result. > > The preferred location for VST plugins should be in the user's home > directory: the ~/.vst directory is mentioned on the instructions, but is > not given as the advised location. This same dichotomy (where a home > directory is available, but not the one given as a recommendation) is true > for several other plugins. > > Second, /usr/local/lib/ should be the installation directory for system- > wide plugins, not /usr/lib, even if it is a packaged version of Audacity > that is installed. This is once again because of the filesystem > standards: any files that aren't managed by the package manager should be > kept distinct from those that are controlled via package manager. Now, > this might not be a simple documentation fix: if packaged versions of > Audacity don't check /usr/local/lib for plugins, then editing the wiki is > obviously insufficient. However, it should be improved in the code to > allow that. > > Lastly, VST plugins DO NOT belong in /usr/bin. /usr/bin is specifically > for executable files, and vst plugins are formatted as libraries. Given > that alternatives exist, please don't recommend placing VST plugins in > /usr/bin > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Calum M. <cal...@gm...> - 2021-06-23 19:59:18
|
Thank you! The new version looks great! :) On Tue, 2021-06-22 at 10:41 +0100, Steve Fiddle wrote: > I agree with most of this, so I have substantially updated the page in > the alpha manual (for Audacity 3.0.3). > > The revised version is available here: > https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Linux > > Steve > > On Fri, 18 Jun 2021 at 18:47, Calum McConnell > <cal...@gm...> wrote: > > Dear Audacity developers, > > The VST plugin installation instructions for Linux (as they currently > > exist at > > > https://manual.audacityteam.org/man/installing_effect_generator_and_analyzer_plug_ins_on_linux.html > > ) > > aren't a good idea. On many linux systems (at the very least, Debian, > > Ubuntu, and all other users of dpkg), the contents of the folders > > /usr/lib and /usr/bin should not be modified by a human. This is > > because > > the package manager is designed to have sole control over those > > folders. > > Now, there are enough safety checks that this probably won't lead to > > issues, but there are many management headaches that can result. > > > > The preferred location for VST plugins should be in the user's home > > directory: the ~/.vst directory is mentioned on the instructions, but > > is > > not given as the advised location. This same dichotomy (where a home > > directory is available, but not the one given as a recommendation) is > > true > > for several other plugins. > > > > Second, /usr/local/lib/ should be the installation directory for > > system- > > wide plugins, not /usr/lib, even if it is a packaged version of > > Audacity > > that is installed. This is once again because of the filesystem > > standards: any files that aren't managed by the package manager should > > be > > kept distinct from those that are controlled via package manager. > > Now, > > this might not be a simple documentation fix: if packaged versions of > > Audacity don't check /usr/local/lib for plugins, then editing the wiki > > is > > obviously insufficient. However, it should be improved in the code to > > allow that. > > > > Lastly, VST plugins DO NOT belong in /usr/bin. /usr/bin is > > specifically > > for executable files, and vst plugins are formatted as libraries. > > Given > > that alternatives exist, please don't recommend placing VST plugins in > > /usr/bin > > _______________________________________________ > > audacity-devel mailing list > > aud...@li... > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
|
From: Peter S. <pet...@gm...> - 2021-06-23 11:30:00
|
On Tue, Jun 22, 2021 at 10:42 AM Steve Fiddle <ste...@gm...> wrote: > I agree with most of this, so I have substantially updated the page in the > alpha manual (for Audacity 3.0.3). > > The revised version is available here: > > https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Linux > @Calum McConnell: as the instigator of this thread can you please review Steve's changes in the Manual. Peter. > Steve > > On Fri, 18 Jun 2021 at 18:47, Calum McConnell < > cal...@gm...> wrote: > >> Dear Audacity developers, >> The VST plugin installation instructions for Linux (as they currently >> exist at >> >> https://manual.audacityteam.org/man/installing_effect_generator_and_analyzer_plug_ins_on_linux.html >> ) >> aren't a good idea. On many linux systems (at the very least, Debian, >> Ubuntu, and all other users of dpkg), the contents of the folders >> /usr/lib and /usr/bin should not be modified by a human. This is because >> the package manager is designed to have sole control over those folders. >> Now, there are enough safety checks that this probably won't lead to >> issues, but there are many management headaches that can result. >> >> The preferred location for VST plugins should be in the user's home >> directory: the ~/.vst directory is mentioned on the instructions, but is >> not given as the advised location. This same dichotomy (where a home >> directory is available, but not the one given as a recommendation) is true >> for several other plugins. >> >> Second, /usr/local/lib/ should be the installation directory for system- >> wide plugins, not /usr/lib, even if it is a packaged version of Audacity >> that is installed. This is once again because of the filesystem >> standards: any files that aren't managed by the package manager should be >> kept distinct from those that are controlled via package manager. Now, >> this might not be a simple documentation fix: if packaged versions of >> Audacity don't check /usr/local/lib for plugins, then editing the wiki is >> obviously insufficient. However, it should be improved in the code to >> allow that. >> >> Lastly, VST plugins DO NOT belong in /usr/bin. /usr/bin is specifically >> for executable files, and vst plugins are formatted as libraries. Given >> that alternatives exist, please don't recommend placing VST plugins in >> /usr/bin >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Sonvert B. <son...@gm...> - 2021-06-22 12:32:54
|
Hi -- Sonvert Bhardwaj |
|
From: Steve F. <ste...@gm...> - 2021-06-22 09:42:12
|
I agree with most of this, so I have substantially updated the page in the alpha manual (for Audacity 3.0.3). The revised version is available here: https://alphamanual.audacityteam.org/man/Installing_Effect,_Generator_and_Analyzer_plug-ins_on_Linux Steve On Fri, 18 Jun 2021 at 18:47, Calum McConnell <cal...@gm...> wrote: > Dear Audacity developers, > The VST plugin installation instructions for Linux (as they currently > exist at > > https://manual.audacityteam.org/man/installing_effect_generator_and_analyzer_plug_ins_on_linux.html > ) > aren't a good idea. On many linux systems (at the very least, Debian, > Ubuntu, and all other users of dpkg), the contents of the folders > /usr/lib and /usr/bin should not be modified by a human. This is because > the package manager is designed to have sole control over those folders. > Now, there are enough safety checks that this probably won't lead to > issues, but there are many management headaches that can result. > > The preferred location for VST plugins should be in the user's home > directory: the ~/.vst directory is mentioned on the instructions, but is > not given as the advised location. This same dichotomy (where a home > directory is available, but not the one given as a recommendation) is true > for several other plugins. > > Second, /usr/local/lib/ should be the installation directory for system- > wide plugins, not /usr/lib, even if it is a packaged version of Audacity > that is installed. This is once again because of the filesystem > standards: any files that aren't managed by the package manager should be > kept distinct from those that are controlled via package manager. Now, > this might not be a simple documentation fix: if packaged versions of > Audacity don't check /usr/local/lib for plugins, then editing the wiki is > obviously insufficient. However, it should be improved in the code to > allow that. > > Lastly, VST plugins DO NOT belong in /usr/bin. /usr/bin is specifically > for executable files, and vst plugins are formatted as libraries. Given > that alternatives exist, please don't recommend placing VST plugins in > /usr/bin > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Calum M. <cal...@gm...> - 2021-06-18 17:46:03
|
Dear Audacity developers, The VST plugin installation instructions for Linux (as they currently exist at https://manual.audacityteam.org/man/installing_effect_generator_and_analyzer_plug_ins_on_linux.html) aren't a good idea. On many linux systems (at the very least, Debian, Ubuntu, and all other users of dpkg), the contents of the folders /usr/lib and /usr/bin should not be modified by a human. This is because the package manager is designed to have sole control over those folders. Now, there are enough safety checks that this probably won't lead to issues, but there are many management headaches that can result. The preferred location for VST plugins should be in the user's home directory: the ~/.vst directory is mentioned on the instructions, but is not given as the advised location. This same dichotomy (where a home directory is available, but not the one given as a recommendation) is true for several other plugins. Second, /usr/local/lib/ should be the installation directory for system- wide plugins, not /usr/lib, even if it is a packaged version of Audacity that is installed. This is once again because of the filesystem standards: any files that aren't managed by the package manager should be kept distinct from those that are controlled via package manager. Now, this might not be a simple documentation fix: if packaged versions of Audacity don't check /usr/local/lib for plugins, then editing the wiki is obviously insufficient. However, it should be improved in the code to allow that. Lastly, VST plugins DO NOT belong in /usr/bin. /usr/bin is specifically for executable files, and vst plugins are formatted as libraries. Given that alternatives exist, please don't recommend placing VST plugins in /usr/bin |
|
From: Steve F. <ste...@gm...> - 2021-06-18 07:17:08
|
The following error message has been reported with Audacity 3.0.3 alpha. https://forum.audacityteam.org/viewtopic.php?p=428146#p428146 As we have no documentation about this, I've no idea what it means: { "timestamp": 1623860909, "event_id": "3148047ca5660a47b6e4e075b82ba3bd", "platform": "native", "release": "audacity@3.0.3", "contexts": { "os": { "type": "os", "name": "Windows", "version": "10.0.19043" } }, "exception": { "values": [ { "type": "File_Error", "value": "Audacity failed to read from a file in <path>:.", "mechanism": { "type": "runtime_error", "handled": false, "data": { "sqlite3.rc": "101", "sqlite3.context": "SqliteSampleBlock::Load::step" } } } ] } } |
|
From: Joost A. <Joo...@gm...> - 2021-06-15 07:29:31
|
Hi, last weekend I've installed matchering from https://github.com/sergree/matchering You can take a reference audio recording and take RMS, frequency response, peak amplitude and stereo width over to your recording from the reference audio take. There's also a CLI available to control this Python app https://github.com/sergree/matchering-cli License is GPLv3 Wouldn't it be a good idea to integrate it into Audacity via a plugin where you could define the parameters (reference audio file, quality (16, 24 32 bit) and other properties to create a new audio track based upon the track loaded within Audacity ? Just an idea... Kind regards, Joost |
|
From: John C. <jc...@gm...> - 2021-06-07 14:20:40
|
There is a "Compiling Audacity - windows" forum on discord see here: https://discord.gg/8P9RHQRa - John On Sun, Jun 6, 2021 at 11:02 PM Ajay Panthagani <aja...@gm...> wrote: > Hi, I am trying to build audacity on windows using cmake. When I run > configure it throws the following error. Please help me out. > > *fatal error C1083: Cannot open include file: 'pthread.h' : No such file > or directory* > > *OS : Windows 64bit* > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Ajay P. <aja...@gm...> - 2021-06-07 03:00:53
|
Hi, I am trying to build audacity on windows using cmake. When I run configure it throws the following error. Please help me out. *fatal error C1083: Cannot open include file: 'pthread.h' : No such file or directory* *OS : Windows 64bit* |
|
From: Ajay P. <aja...@gm...> - 2021-06-07 01:29:51
|
Hi, My name is Ajay. I would like to contribute to Audacity. Could someone please point me in the right direction? Where can I start! Thank you. |
|
From: Steve F. <ste...@gm...> - 2021-06-03 14:54:03
|
Although it's only a "P3" bug, for support issues we could really do with bug 2719 being fixed as soon as possible. Screenshots are an invaluable tool for discussing certain types of end user problems and it is extremely helpful to have a cross-platform way to get screenshots that are a reasonable size and an appropriate format for the forum. https://bugzilla.audacityteam.org/show_bug.cgi?id=2719 Steve |
|
From: Dmitry R. <di...@gm...> - 2021-06-03 09:59:32
|
Thanks freddyjohn! If you have time, please send demos that you have, it is interesting to take a look at them! Thanks in advance! P.s. hope the dog will be ok > On 2.06.2021, at 23:27, freddyjohn via audacity-devel <aud...@li...> wrote: > > Right now I am working on finishing selectable, editable, and mixable waveform feature. There are just a few bugs left. If you are interested I can send some demos when I get back from the vet > > > Sent from ProtonMail for iOS > > > On Wed, Jun 2, 2021 at 4:22 PM, freddyjohn <fre...@pr... <mailto:fre...@pr...>> wrote: >> >> I am putting substantial effort into an audacity like application for Android. I have implemented a low pass filter to smooth audio tracks but there is nothing sophisticated like signal separation yet. >> I expect to have the first version finished within a month. >> My dog is sick and getting old right now so I have been putting a lot of energy into dealing with this. >> >> Sent from ProtonMail for iOS >> >> >> On Wed, Jun 2, 2021 at 10:55 AM, Dmitry R. <di...@gm... <mailto:di...@gm...>> wrote: >>> >>> Hi team! >>> >>> Just wondering is there any port or possible variants to port Audacity Noise reduction to mobile platform (e.g. Android)? >>> >>> Any help with it would be much appreciated! >>> >>> Thanks, >>> Dmitry >>> >>> _______________________________________________ >>> audacity-devel mailing list >>> aud...@li... >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> >> > > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
|
From: Peter S. <pet...@gm...> - 2021-06-02 20:35:39
|
On Wed, Jun 2, 2021 at 10:23 PM freddyjohn via audacity-devel < aud...@li...> wrote: > I am putting substantial effort into an audacity like application for > Android. I have implemented a low pass filter to smooth audio tracks but > there is nothing sophisticated like signal separation yet. > I expect to have the first version finished within a month. > > My dog is sick and getting old right now so I have been putting a lot of > energy into dealing with this. > Fingers crossed for your dog pulling through 🤞 Peter. > Sent from ProtonMail for iOS > > > On Wed, Jun 2, 2021 at 10:55 AM, Dmitry R. <di...@gm...> wrote: > > Hi team! > > Just wondering is there any port or possible variants to port Audacity > Noise reduction to mobile platform (e.g. Android)? > > Any help with it would be much appreciated! > > Thanks, > Dmitry > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
1022 messages has been excluded from this view by a project administrator.
