audacity-devel Mailing List for Audacity (Page 9)
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
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: Steve F. <ste...@gm...> - 2021-04-28 21:30:55
|
Yes I'm using "Portable Settings" for all but one version (3.0.2). Steve On Wed, 28 Apr 2021 at 22:15, Leland <ll...@ho...> wrote: > I’ve tried several times now and and not able to get this to happen. But, > do you happen to be running with portable settings? I haven’t tried that > yet, but I can “imagine” that multiple copies of Audacity could run then > since the “data directory” is used to generate the IPC key. > > > > *From:* Steve Fiddle <ste...@gm...> > *Sent:* Tuesday, April 27, 2021 10:19 AM > *To:* Audacity-Devel list <aud...@li...> > *Subject:* Re: [Audacity-devel] Multiple versions of Audacity 3.x running > simultaneously ??? > > > > > > > > On Tue, 27 Apr 2021 at 04:39, Leland <ll...@ho...> wrote: > > Steve, what happens if you try to run the same version multiple times? > I’m on Ubuntu 20.10 and when I try to execute the same executable it brings > the already running Audacity to the front. > > > > If I try to execute the same executable, it brings the already running > Audacity to the front. > > I can however have two identical builds of Audacity 3.0.2 and run both at > the same time. > > > > Steve > > > > > > *From:* Steve Fiddle <ste...@gm...> > *Sent:* Monday, April 26, 2021 2:21 PM > *To:* Audacity-Devel list <aud...@li...> > *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running > simultaneously ??? > > > > Do we still check that only one instance of Audacity is running? > > If so, that's not working. > > > > I'll send a screenshot separately in case the mailing system blocks it. > > > > 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: Leland <ll...@ho...> - 2021-04-28 21:14:08
|
I’ve tried several times now and and not able to get this to happen. But, do you happen to be running with portable settings? I haven’t tried that yet, but I can “imagine” that multiple copies of Audacity could run then since the “data directory” is used to generate the IPC key. From: Steve Fiddle <ste...@gm...> Sent: Tuesday, April 27, 2021 10:19 AM To: Audacity-Devel list <aud...@li...> Subject: Re: [Audacity-devel] Multiple versions of Audacity 3.x running simultaneously ??? On Tue, 27 Apr 2021 at 04:39, Leland <ll...@ho... <mailto:ll...@ho...> > wrote: Steve, what happens if you try to run the same version multiple times? I’m on Ubuntu 20.10 and when I try to execute the same executable it brings the already running Audacity to the front. If I try to execute the same executable, it brings the already running Audacity to the front. I can however have two identical builds of Audacity 3.0.2 and run both at the same time. Steve From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...> > Sent: Monday, April 26, 2021 2:21 PM To: Audacity-Devel list <aud...@li... <mailto:aud...@li...> > Subject: [Audacity-devel] Multiple versions of Audacity 3.x running simultaneously ??? Do we still check that only one instance of Audacity is running? If so, that's not working. I'll send a screenshot separately in case the mailing system blocks it. Steve _______________________________________________ audacity-devel mailing list aud...@li... <mailto:aud...@li...> https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Leland <ll...@ho...> - 2021-04-28 21:01:20
|
Ooo, that’s not good. Let me try it, but I can’t for the life of me think why it could happen. From: Steve Fiddle <ste...@gm...> Sent: Tuesday, April 27, 2021 10:19 AM To: Audacity-Devel list <aud...@li...> Subject: Re: [Audacity-devel] Multiple versions of Audacity 3.x running simultaneously ??? On Tue, 27 Apr 2021 at 04:39, Leland <ll...@ho... <mailto:ll...@ho...> > wrote: Steve, what happens if you try to run the same version multiple times? I’m on Ubuntu 20.10 and when I try to execute the same executable it brings the already running Audacity to the front. If I try to execute the same executable, it brings the already running Audacity to the front. I can however have two identical builds of Audacity 3.0.2 and run both at the same time. Steve From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...> > Sent: Monday, April 26, 2021 2:21 PM To: Audacity-Devel list <aud...@li... <mailto:aud...@li...> > Subject: [Audacity-devel] Multiple versions of Audacity 3.x running simultaneously ??? Do we still check that only one instance of Audacity is running? If so, that's not working. I'll send a screenshot separately in case the mailing system blocks it. Steve _______________________________________________ audacity-devel mailing list aud...@li... <mailto:aud...@li...> https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: freddyjohn <fre...@pr...> - 2021-04-28 20:25:49
|
If anyone was interested there was a paper written on audacity’s data structure. “A Fast Data Structure for Disk-Based Audio Editing” Best version I could find is in Computer Music Journal, 26:2, pp. 62–76, Summer 2002 Sent from ProtonMail for iOS On Thu, Apr 22, 2021 at 1:34 PM, freddyjohn via audacity-devel <aud...@li...> wrote: > Hello its me again I have three questions for my open source DAW for android. > If this is not the place to ask these questions I apologize and would love direction on a community that may be able to answer them. In my experience, Stack Overflow and blogs like it is not that place. I of course have tried and implemented my own solutions but I want to hear from you guys. > > 1.) what are the data structures used to efficiently handle edits to audio? > is it a b-tree, do you use a piece table, what is the structure inside those XML files? > > what I've tried: > I have found a solution using piece table. I keep track of all the edits in one file and when the user is finished > I serialize the java object and append it to the end of the file along with integer that describes the byte length of the java object so that it can be de-serialized during another session acting as a project file. > I have spent some time looking through audacity source code and reading audacity blogs but I am still not sure exactly what data structure is used. > This was an excellent read -> http://www.aosabook.org/en/audacity.html > > 2.)how do we handle modulations now that the file is in blocks? > did you have to worry about the continuity of the LFO for a phaser about these blocks for example? > > what I've tried: > I can see an easy solution to this by calculating the leftover phase and offsetting the next modulation wave by this leftover phase. > but for an echo it seems you would need a completely different solution. > > 3.)Another thing I am struggling with is displaying audio efficiently. > > what I've tried: > on Android we have limited heap memory so I cannot just go and ask for huge Bitmap allocation I need to keep space open for bringing byte[] into program memory to perform modulations so I just ask for a Bitmap that is the h,w of the screen then I scale the audio into this space like this > > let, > screen width of fixed sized = w_N > amount of samples = s_N > > then the equation to scale s within w can be found via > s_N > ∑ i * (w_N/s_N) > i=0 > > and in order to translate the selection on the screen back into byte land we can use this equation > w_i * (s_N/w_N) = s_i > > for example, a screen of 500px, an audio file of 1000 bytes and a selection within 500px of 500 > 500*1000/500=1000. > > I also ensure to never select an odd byte depending on the selected encoding as this creates an extremely unfavorable offset that causes the audio byte stream to not decode correctly. > > Of course this is O(n) and not very efficient at all. The time it takes to display the file will grow with the length of the file which is very unfavorable to the user. I understand Audacity uses summary information of the audio for parts of its display but I am having a difficult time understanding how we can translate a selection within this summary information to actual file byte locations. > > It seems that these problems are linked and after spending some time trying to tackle them myself I would really love to hear from the Audacity Team about how they found solutions to these problems. > > Sent with [ProtonMail](https://protonmail.com) Secure Email. |
From: Bill W. <bi...@go...> - 2021-04-27 21:14:37
|
> On 2021/04/27, at 1:12 PM, Steve Fiddle <ste...@gm...> wrote: > > > > On Tue, 27 Apr 2021 at 16:52, Bill Wharrie <bi...@go... <mailto:bi...@go...>> wrote: > > >> On 2021/04/27, at 11:27 AM, Steve Fiddle <ste...@gm... <mailto:ste...@gm...>> wrote: >> >> >> >> On Tue, 27 Apr 2021 at 09:25, Peter Sampson <pet...@gm... <mailto:pet...@gm...>> wrote: >> >> >> On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho... <mailto:ll...@ho...>> wrote: >> Steve, what happens if you try to run the same version multiple times? I’m on Ubuntu 20.10 and when I try to execute the same executable it brings the already running Audacity to the front. >> >> >> On W1p I cannot run 3.0.3 and 2.4.2 at the same time >> >> 1) Launch 3.0.3 >> 2) Restore Down to make the window small >> 3) Attempt to launch 2.4.2 >> 4) Observe: Audacity icon in applications bar flashes orange >> 5) Observe the 3.0.3 window is maximized to full screen >> 6) Observe: no 2.4.2 is launched >> 7) Observe: no error message >> >> The same happens if I start with 2.4.2 and then try to launch 3.0.3 >> >> Step 5 is annoying - if I want my window resized I want to do it myself, not >> have it forced upon me. >> >> It may be a bit annoying, but so is hitting your kneecap with a hammer - the trick to avoid the annoyance is to not do it ;-) > > That does not change the fact that it shouldn’t happen. > >> >> On the other hand, the good thing about bringing the window to the front maximised, is that you can't miss seeing that Audacity is running, even if there is an "always on top" error dialog from another app which could conceivably hide a non-maximised Audacity window. > > You’re turning a bug into a feature? > > or perhaps you're turning a feature into a bug? I'm not sure what was intended other than not allowing multiple instances of Audacity. > If I recall correctly, raising the Audacity window to the front is intentional, but I don't know about maximising the window. That’s not what I recall. When attempting to launch a second Audacity, it just failed. It did not bring the currently-running Audacity to the front and it did not zoom the window. So, on my Mac … Start 3.0.2. Fine Switch to Finder Start 3.0.0 3.0.0 icon appears briefly in the dock 3.0.2 icon bounces a few times in the dock then stops Audacity 3.0.2 window zooms to “fill the screen” but not “full screen” (same as option-click on the green zoom button) Audacity 3.0.2 does not come to the front. Switching to Audacity 3.0.2, an option-click on the green zoom button restores the previous window position and size. I complained about this maybe a year ago and others could not reproduce it. Now Peter is seeing it consistently on his Mac, as am I (both Catalina and Big Sur). I this really important? Perhaps not. P3? But it is annoying and it is definitely unintended and unwanted behaviour and makes us look bad. — Bill > > Steve > > > — Bill > >> >> Steve >> >> >> >> Step 7, the lack of error message is unhelpful, the user is not informed of >> the isue >> >> On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after >> launching 3.0.3 - and vice versa. >> >> Do we need to log this issue in Bugzilla ? >> >> Peter. >> >> >> >> >> >> From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...>> >> Sent: Monday, April 26, 2021 2:21 PM >> To: Audacity-Devel list <aud...@li... <mailto:aud...@li...>> >> Subject: [Audacity-devel] Multiple versions of Audacity 3.x running simultaneously ??? >> >> >> >> Do we still check that only one instance of Audacity is running? >> >> If so, that's not working. >> >> >> >> I'll send a screenshot separately in case the mailing system blocks it. >> >> >> >> Steve >> >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... <mailto:aud...@li...> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel> >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... <mailto:aud...@li...> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel> >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... <mailto:aud...@li...> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel> > _______________________________________________ > audacity-devel mailing list > aud...@li... <mailto:aud...@li...> > https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel> > _______________________________________________ > audacity-devel mailing list > aud...@li... <mailto:aud...@li...> > https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel> |
From: Steve F. <ste...@gm...> - 2021-04-27 17:13:21
|
On Tue, 27 Apr 2021 at 16:52, Bill Wharrie <bi...@go...> wrote: > > > On 2021/04/27, at 11:27 AM, Steve Fiddle <ste...@gm...> wrote: > > > > On Tue, 27 Apr 2021 at 09:25, Peter Sampson < > pet...@gm...> wrote: > >> >> >> On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho...> wrote: >> >>> Steve, what happens if you try to run the same version multiple times? >>> I’m on Ubuntu 20.10 and when I try to execute the same executable it brings >>> the already running Audacity to the front. >>> >> >> On W1p I cannot run 3.0.3 and 2.4.2 at the same time >> >> 1) Launch 3.0.3 >> 2) Restore Down to make the window small >> 3) Attempt to launch 2.4.2 >> 4) Observe: Audacity icon in applications bar flashes orange >> 5) Observe the 3.0.3 window is maximized to full screen >> 6) Observe: no 2.4.2 is launched >> 7) Observe: no error message >> >> The same happens if I start with 2.4.2 and then try to launch 3.0.3 >> >> Step 5 is annoying - if I want my window resized I want to do it myself, >> not >> have it forced upon me. >> > > It may be a bit annoying, but so is hitting your kneecap with a hammer - > the trick to avoid the annoyance is to not do it ;-) > > > That does not change the fact that it shouldn’t happen. > > > On the other hand, the good thing about bringing the window to the front > maximised, is that you can't miss seeing that Audacity is running, even if > there is an "always on top" error dialog from another app which could > conceivably hide a non-maximised Audacity window. > > > You’re turning a bug into a feature? > or perhaps you're turning a feature into a bug? I'm not sure what was intended other than not allowing multiple instances of Audacity. If I recall correctly, raising the Audacity window to the front is intentional, but I don't know about maximising the window. Steve > > — Bill > > > Steve > > > >> >> Step 7, the lack of error message is unhelpful, the user is not informed >> of >> the isue >> >> On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after >> launching 3.0.3 - and vice versa. >> >> Do we need to log this issue in Bugzilla ? >> >> Peter. >> >> >> >> >>> >>> *From:* Steve Fiddle <ste...@gm...> >>> *Sent:* Monday, April 26, 2021 2:21 PM >>> *To:* Audacity-Devel list <aud...@li...> >>> *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running >>> simultaneously ??? >>> >>> >>> >>> Do we still check that only one instance of Audacity is running? >>> >>> If so, that's not working. >>> >>> >>> >>> I'll send a screenshot separately in case the mailing system blocks it. >>> >>> >>> >>> 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 >> > _______________________________________________ > 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: Bill W. <bi...@go...> - 2021-04-27 15:50:44
|
> On 2021/04/27, at 11:27 AM, Steve Fiddle <ste...@gm...> wrote: > > > > On Tue, 27 Apr 2021 at 09:25, Peter Sampson <pet...@gm... <mailto:pet...@gm...>> wrote: > > > On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho... <mailto:ll...@ho...>> wrote: > Steve, what happens if you try to run the same version multiple times? I’m on Ubuntu 20.10 and when I try to execute the same executable it brings the already running Audacity to the front. > > > On W1p I cannot run 3.0.3 and 2.4.2 at the same time > > 1) Launch 3.0.3 > 2) Restore Down to make the window small > 3) Attempt to launch 2.4.2 > 4) Observe: Audacity icon in applications bar flashes orange > 5) Observe the 3.0.3 window is maximized to full screen > 6) Observe: no 2.4.2 is launched > 7) Observe: no error message > > The same happens if I start with 2.4.2 and then try to launch 3.0.3 > > Step 5 is annoying - if I want my window resized I want to do it myself, not > have it forced upon me. > > It may be a bit annoying, but so is hitting your kneecap with a hammer - the trick to avoid the annoyance is to not do it ;-) That does not change the fact that it shouldn’t happen. > > On the other hand, the good thing about bringing the window to the front maximised, is that you can't miss seeing that Audacity is running, even if there is an "always on top" error dialog from another app which could conceivably hide a non-maximised Audacity window. You’re turning a bug into a feature? — Bill > > Steve > > > > Step 7, the lack of error message is unhelpful, the user is not informed of > the isue > > On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after > launching 3.0.3 - and vice versa. > > Do we need to log this issue in Bugzilla ? > > Peter. > > > > > > From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...>> > Sent: Monday, April 26, 2021 2:21 PM > To: Audacity-Devel list <aud...@li... <mailto:aud...@li...>> > Subject: [Audacity-devel] Multiple versions of Audacity 3.x running simultaneously ??? > > > > Do we still check that only one instance of Audacity is running? > > If so, that's not working. > > > > I'll send a screenshot separately in case the mailing system blocks it. > > > > Steve > > _______________________________________________ > audacity-devel mailing list > aud...@li... <mailto:aud...@li...> > https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel> > _______________________________________________ > audacity-devel mailing list > aud...@li... <mailto:aud...@li...> > https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel> > _______________________________________________ > audacity-devel mailing list > aud...@li... <mailto:aud...@li...> > https://lists.sourceforge.net/lists/listinfo/audacity-devel <https://lists.sourceforge.net/lists/listinfo/audacity-devel> |
From: Steve F. <ste...@gm...> - 2021-04-27 15:28:01
|
On Tue, 27 Apr 2021 at 09:25, Peter Sampson <pet...@gm...> wrote: > > > On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho...> wrote: > >> Steve, what happens if you try to run the same version multiple times? >> I’m on Ubuntu 20.10 and when I try to execute the same executable it brings >> the already running Audacity to the front. >> > > On W1p I cannot run 3.0.3 and 2.4.2 at the same time > > 1) Launch 3.0.3 > 2) Restore Down to make the window small > 3) Attempt to launch 2.4.2 > 4) Observe: Audacity icon in applications bar flashes orange > 5) Observe the 3.0.3 window is maximized to full screen > 6) Observe: no 2.4.2 is launched > 7) Observe: no error message > > The same happens if I start with 2.4.2 and then try to launch 3.0.3 > > Step 5 is annoying - if I want my window resized I want to do it myself, > not > have it forced upon me. > It may be a bit annoying, but so is hitting your kneecap with a hammer - the trick to avoid the annoyance is to not do it ;-) On the other hand, the good thing about bringing the window to the front maximised, is that you can't miss seeing that Audacity is running, even if there is an "always on top" error dialog from another app which could conceivably hide a non-maximised Audacity window. Steve > > Step 7, the lack of error message is unhelpful, the user is not informed of > the isue > > On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after > launching 3.0.3 - and vice versa. > > Do we need to log this issue in Bugzilla ? > > Peter. > > > > >> >> *From:* Steve Fiddle <ste...@gm...> >> *Sent:* Monday, April 26, 2021 2:21 PM >> *To:* Audacity-Devel list <aud...@li...> >> *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running >> simultaneously ??? >> >> >> >> Do we still check that only one instance of Audacity is running? >> >> If so, that's not working. >> >> >> >> I'll send a screenshot separately in case the mailing system blocks it. >> >> >> >> 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-04-27 15:20:12
|
On Tue, 27 Apr 2021 at 04:39, Leland <ll...@ho...> wrote: > Steve, what happens if you try to run the same version multiple times? > I’m on Ubuntu 20.10 and when I try to execute the same executable it brings > the already running Audacity to the front. > If I try to execute the same executable, it brings the already running Audacity to the front. I can however have two identical builds of Audacity 3.0.2 and run both at the same time. Steve > > > *From:* Steve Fiddle <ste...@gm...> > *Sent:* Monday, April 26, 2021 2:21 PM > *To:* Audacity-Devel list <aud...@li...> > *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running > simultaneously ??? > > > > Do we still check that only one instance of Audacity is running? > > If so, that's not working. > > > > I'll send a screenshot separately in case the mailing system blocks it. > > > > Steve > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: James C. <jam...@gm...> - 2021-04-27 10:01:49
|
2.x mixing with 3.x is 99% not an issue. 3.x treats 2.x projects as read only. It can't/won't damage a 2.x project. 2.x can't even read 3.x projects. It can't/won't damage a 3.x project. So, after you realise you probably shouldn't be running two versions and close both you find neither project is damaged. The '1%' issue is if you open a large 2.x project in 3.x (and so start making a converted .aup3 copy) and at the same time open AND edit the 2.x project in 2.x. Then the rug is being pulled from under the 3.x conversion because the pile-of-files it is converting is being changed as it converts. So the conversion could fail, possibly even silently with part edits appearing in the 'conversion'. But in the 1% case you'd still have your original edited 2.x project. You'd just have a broken/useless 3.x conversion. I don't think the 1% case matters. We're talking about a minority of people who keep both 2.x and 3.x Audacity around and who decide to run both and to edit during conversion, and even then the result is not disastrous. --James. On Tue, 27 Apr 2021 at 10:05, Peter Sampson <pet...@gm...> wrote: > > > On Tue, Apr 27, 2021 at 9:44 AM Leland Lucius <ll...@ho...> wrote: > >> The Windows uses a different method so that's expected. The Mac behavior >> is also expected and was discussed before. Not sure if it was mailing list >> or bugzilla. >> >> Linux is supposed to work like Mac. >> > > 1) So is what we have desired behavior ? > > 2) How many of our IRL users are going to encounter this? > > 3) Windows seems straightforward and safe - in uninformative > > 4) How safe is it on Mac to be running two different versions > simultaneously? > Particularity 3,x and 2.x ? > > Peter. > > > > > >> On Tue, Apr 27, 2021, 3:25 AM Peter Sampson < >> pet...@gm...> wrote: >> >>> >>> >>> On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho...> wrote: >>> >>>> Steve, what happens if you try to run the same version multiple times? >>>> I’m on Ubuntu 20.10 and when I try to execute the same executable it brings >>>> the already running Audacity to the front. >>>> >>> >>> On W1p I cannot run 3.0.3 and 2.4.2 at the same time >>> >>> 1) Launch 3.0.3 >>> 2) Restore Down to make the window small >>> 3) Attempt to launch 2.4.2 >>> 4) Observe: Audacity icon in applications bar flashes orange >>> 5) Observe the 3.0.3 window is maximized to full screen >>> 6) Observe: no 2.4.2 is launched >>> 7) Observe: no error message >>> >>> The same happens if I start with 2.4.2 and then try to launch 3.0.3 >>> >>> Step 5 is annoying - if I want my window resized I want to do it myself, >>> not >>> have it forced upon me. >>> >>> Step 7, the lack of error message is unhelpful, the user is not informed >>> of >>> the isue >>> >>> On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after >>> launching 3.0.3 - and vice versa. >>> >>> Do we need to log this issue in Bugzilla ? >>> >>> Peter. >>> >>> >>> >>> >>>> >>>> *From:* Steve Fiddle <ste...@gm...> >>>> *Sent:* Monday, April 26, 2021 2:21 PM >>>> *To:* Audacity-Devel list <aud...@li...> >>>> *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running >>>> simultaneously ??? >>>> >>>> >>>> >>>> Do we still check that only one instance of Audacity is running? >>>> >>>> If so, that's not working. >>>> >>>> >>>> >>>> I'll send a screenshot separately in case the mailing system blocks it. >>>> >>>> >>>> >>>> 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 >>> >> _______________________________________________ >> 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-04-27 09:04:13
|
On Tue, Apr 27, 2021 at 9:44 AM Leland Lucius <ll...@ho...> wrote: > The Windows uses a different method so that's expected. The Mac behavior > is also expected and was discussed before. Not sure if it was mailing list > or bugzilla. > > Linux is supposed to work like Mac. > 1) So is what we have desired behavior ? 2) How many of our IRL users are going to encounter this? 3) Windows seems straightforward and safe - in uninformative 4) How safe is it on Mac to be running two different versions simultaneously? Particularity 3,x and 2.x ? Peter. > On Tue, Apr 27, 2021, 3:25 AM Peter Sampson < > pet...@gm...> wrote: > >> >> >> On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho...> wrote: >> >>> Steve, what happens if you try to run the same version multiple times? >>> I’m on Ubuntu 20.10 and when I try to execute the same executable it brings >>> the already running Audacity to the front. >>> >> >> On W1p I cannot run 3.0.3 and 2.4.2 at the same time >> >> 1) Launch 3.0.3 >> 2) Restore Down to make the window small >> 3) Attempt to launch 2.4.2 >> 4) Observe: Audacity icon in applications bar flashes orange >> 5) Observe the 3.0.3 window is maximized to full screen >> 6) Observe: no 2.4.2 is launched >> 7) Observe: no error message >> >> The same happens if I start with 2.4.2 and then try to launch 3.0.3 >> >> Step 5 is annoying - if I want my window resized I want to do it myself, >> not >> have it forced upon me. >> >> Step 7, the lack of error message is unhelpful, the user is not informed >> of >> the isue >> >> On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after >> launching 3.0.3 - and vice versa. >> >> Do we need to log this issue in Bugzilla ? >> >> Peter. >> >> >> >> >>> >>> *From:* Steve Fiddle <ste...@gm...> >>> *Sent:* Monday, April 26, 2021 2:21 PM >>> *To:* Audacity-Devel list <aud...@li...> >>> *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running >>> simultaneously ??? >>> >>> >>> >>> Do we still check that only one instance of Audacity is running? >>> >>> If so, that's not working. >>> >>> >>> >>> I'll send a screenshot separately in case the mailing system blocks it. >>> >>> >>> >>> 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 >> > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: Leland L. <ll...@ho...> - 2021-04-27 08:43:30
|
The Windows uses a different method so that's expected. The Mac behavior is also expected and was discussed before. Not sure if it was mailing list or bugzilla. Linux is supposed to work like Mac. On Tue, Apr 27, 2021, 3:25 AM Peter Sampson <pet...@gm...> wrote: > > > On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho...> wrote: > >> Steve, what happens if you try to run the same version multiple times? >> I’m on Ubuntu 20.10 and when I try to execute the same executable it brings >> the already running Audacity to the front. >> > > On W1p I cannot run 3.0.3 and 2.4.2 at the same time > > 1) Launch 3.0.3 > 2) Restore Down to make the window small > 3) Attempt to launch 2.4.2 > 4) Observe: Audacity icon in applications bar flashes orange > 5) Observe the 3.0.3 window is maximized to full screen > 6) Observe: no 2.4.2 is launched > 7) Observe: no error message > > The same happens if I start with 2.4.2 and then try to launch 3.0.3 > > Step 5 is annoying - if I want my window resized I want to do it myself, > not > have it forced upon me. > > Step 7, the lack of error message is unhelpful, the user is not informed of > the isue > > On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after > launching 3.0.3 - and vice versa. > > Do we need to log this issue in Bugzilla ? > > Peter. > > > > >> >> *From:* Steve Fiddle <ste...@gm...> >> *Sent:* Monday, April 26, 2021 2:21 PM >> *To:* Audacity-Devel list <aud...@li...> >> *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running >> simultaneously ??? >> >> >> >> Do we still check that only one instance of Audacity is running? >> >> If so, that's not working. >> >> >> >> I'll send a screenshot separately in case the mailing system blocks it. >> >> >> >> 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-04-27 08:36:33
|
On Tue, Apr 27, 2021 at 9:30 AM Peter Sampson < pet...@gm...> wrote: > > > On Tue, Apr 27, 2021 at 9:24 AM Peter Sampson < > pet...@gm...> wrote: > >> >> >> On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho...> wrote: >> >>> Steve, what happens if you try to run the same version multiple times? >>> I’m on Ubuntu 20.10 and when I try to execute the same executable it brings >>> the already running Audacity to the front. >>> >> >> On W1p I cannot run 3.0.3 and 2.4.2 at the same time >> >> 1) Launch 3.0.3 >> 2) Restore Down to make the window small >> 3) Attempt to launch 2.4.2 >> 4) Observe: Audacity icon in applications bar flashes orange >> 5) Observe the 3.0.3 window is maximized to full screen >> 6) Observe: no 2.4.2 is launched >> 7) Observe: no error message >> >> The same happens if I start with 2.4.2 and then try to launch 3.0.3 >> > > On W10 the same thing happens if I try to launch 3.0.2 after I already > have 3.0.3 > running and Restored Down to smaller window size. > > On mac OS 11.2.3 Big Sur- if I try to launch 3.0.2 after I already have > 3.0.3 > running and reduced to smaller window size - it's like Windows, no 3.0.2 is > launched but the 3.0.3 window is maximized within the window (not full > screen) > > In both cases there is no helpful instructive error message. > > Peter. > > > >> Step 5 is annoying - if I want my window resized I want to do it myself, >> not >> have it forced upon me. >> >> Step 7, the lack of error message is unhelpful, the user is not informed >> of >> the isue >> >> On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after >> launching 3.0.3 - and vice versa. >> >> Do we need to log this issue in Bugzilla ? >> > This does not appear to be a (recent )regression I get the same behaviors ads described above if I try to co-launch 3.4.2 and 2.3.3. Peter. >> Peter. >> >> >> >> >>> >>> *From:* Steve Fiddle <ste...@gm...> >>> *Sent:* Monday, April 26, 2021 2:21 PM >>> *To:* Audacity-Devel list <aud...@li...> >>> *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running >>> simultaneously ??? >>> >>> >>> >>> Do we still check that only one instance of Audacity is running? >>> >>> If so, that's not working. >>> >>> >>> >>> I'll send a screenshot separately in case the mailing system blocks it. >>> >>> >>> >>> Steve >>> _______________________________________________ >>> audacity-devel mailing list >>> aud...@li... >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel >>> >> |
From: Peter S. <pet...@gm...> - 2021-04-27 08:30:58
|
On Tue, Apr 27, 2021 at 9:24 AM Peter Sampson < pet...@gm...> wrote: > > > On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho...> wrote: > >> Steve, what happens if you try to run the same version multiple times? >> I’m on Ubuntu 20.10 and when I try to execute the same executable it brings >> the already running Audacity to the front. >> > > On W1p I cannot run 3.0.3 and 2.4.2 at the same time > > 1) Launch 3.0.3 > 2) Restore Down to make the window small > 3) Attempt to launch 2.4.2 > 4) Observe: Audacity icon in applications bar flashes orange > 5) Observe the 3.0.3 window is maximized to full screen > 6) Observe: no 2.4.2 is launched > 7) Observe: no error message > > The same happens if I start with 2.4.2 and then try to launch 3.0.3 > On W10 the same thing happens if I try to launch 3.0.2 after I already have 3.0.3 running and Restored Down to smaller window size. On mac OS 11.2.3 Big Sur- if I try to launch 3.0.2 after I already have 3.0.3 running and reduced to smaller window size - it's like Windows, no 3.0.2 is launched but the 3.0.3 window is maximized within the window (not full screen) In both cases there is no helpful instructive error message. Peter. > Step 5 is annoying - if I want my window resized I want to do it myself, > not > have it forced upon me. > > Step 7, the lack of error message is unhelpful, the user is not informed of > the isue > > On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after > launching 3.0.3 - and vice versa. > > Do we need to log this issue in Bugzilla ? > > Peter. > > > > >> >> *From:* Steve Fiddle <ste...@gm...> >> *Sent:* Monday, April 26, 2021 2:21 PM >> *To:* Audacity-Devel list <aud...@li...> >> *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running >> simultaneously ??? >> >> >> >> Do we still check that only one instance of Audacity is running? >> >> If so, that's not working. >> >> >> >> I'll send a screenshot separately in case the mailing system blocks it. >> >> >> >> Steve >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > |
From: Peter S. <pet...@gm...> - 2021-04-27 08:24:42
|
On Tue, Apr 27, 2021 at 4:39 AM Leland <ll...@ho...> wrote: > Steve, what happens if you try to run the same version multiple times? > I’m on Ubuntu 20.10 and when I try to execute the same executable it brings > the already running Audacity to the front. > On W1p I cannot run 3.0.3 and 2.4.2 at the same time 1) Launch 3.0.3 2) Restore Down to make the window small 3) Attempt to launch 2.4.2 4) Observe: Audacity icon in applications bar flashes orange 5) Observe the 3.0.3 window is maximized to full screen 6) Observe: no 2.4.2 is launched 7) Observe: no error message The same happens if I start with 2.4.2 and then try to launch 3.0.3 Step 5 is annoying - if I want my window resized I want to do it myself, not have it forced upon me. Step 7, the lack of error message is unhelpful, the user is not informed of the isue On Mac (mac OS 11.2.3 Big Sur) I can successfully launch 2.4.2 after launching 3.0.3 - and vice versa. Do we need to log this issue in Bugzilla ? Peter. > > *From:* Steve Fiddle <ste...@gm...> > *Sent:* Monday, April 26, 2021 2:21 PM > *To:* Audacity-Devel list <aud...@li...> > *Subject:* [Audacity-devel] Multiple versions of Audacity 3.x running > simultaneously ??? > > > > Do we still check that only one instance of Audacity is running? > > If so, that's not working. > > > > I'll send a screenshot separately in case the mailing system blocks it. > > > > Steve > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: Leland <ll...@ho...> - 2021-04-27 03:38:33
|
Steve, what happens if you try to run the same version multiple times? I’m on Ubuntu 20.10 and when I try to execute the same executable it brings the already running Audacity to the front. From: Steve Fiddle <ste...@gm...> Sent: Monday, April 26, 2021 2:21 PM To: Audacity-Devel list <aud...@li...> Subject: [Audacity-devel] Multiple versions of Audacity 3.x running simultaneously ??? Do we still check that only one instance of Audacity is running? If so, that's not working. I'll send a screenshot separately in case the mailing system blocks it. Steve |
From: Leland L. <ll...@ho...> - 2021-04-26 20:07:11
|
Yepper, we knew about the 2.4 vs 3.0 difference, but the other bit is new and apparently Linux only. Thanks for checking. I'll boot up.the old Linux VM I'm a little while. On Mon, Apr 26, 2021, 2:45 PM Bill Wharrie <bi...@go...> wrote: > On Mac 11.2.3 I can’t have 3.0.0 and 3.0.2 running simultaneously, but I > can have 3.0.0 and 2.4.2. > > — Bill > > > On 2021/04/26, at 3:21 PM, Steve Fiddle <ste...@gm...> > wrote: > > > > Do we still check that only one instance of Audacity is running? > > If so, that's not working. > > > > I'll send a screenshot separately in case the mailing system blocks it. > > > > 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: Bill W. <bi...@go...> - 2021-04-26 19:45:17
|
On Mac 11.2.3 I can’t have 3.0.0 and 3.0.2 running simultaneously, but I can have 3.0.0 and 2.4.2. — Bill > On 2021/04/26, at 3:21 PM, Steve Fiddle <ste...@gm...> wrote: > > Do we still check that only one instance of Audacity is running? > If so, that's not working. > > I'll send a screenshot separately in case the mailing system blocks it. > > Steve > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Leland L. <ll...@ho...> - 2021-04-26 19:41:05
|
I'll look into it when I get home. On Mon, Apr 26, 2021, 2:23 PM Steve Fiddle <ste...@gm...> wrote: > Here's the screenshot (attached) > > Steve > > [image: Screenshot_2021-04-26_20-17-55.png] > > On Mon, 26 Apr 2021 at 20:21, Steve Fiddle <ste...@gm...> > wrote: > >> Do we still check that only one instance of Audacity is running? >> If so, that's not working. >> >> I'll send a screenshot separately in case the mailing system blocks it. >> >> Steve >> > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: Steve F. <ste...@gm...> - 2021-04-26 19:22:41
|
Here's the screenshot (attached) Steve [image: Screenshot_2021-04-26_20-17-55.png] On Mon, 26 Apr 2021 at 20:21, Steve Fiddle <ste...@gm...> wrote: > Do we still check that only one instance of Audacity is running? > If so, that's not working. > > I'll send a screenshot separately in case the mailing system blocks it. > > Steve > |
From: Steve F. <ste...@gm...> - 2021-04-26 19:22:00
|
Do we still check that only one instance of Audacity is running? If so, that's not working. I'll send a screenshot separately in case the mailing system blocks it. Steve |
From: Max M. <mm...@po...> - 2021-04-26 14:59:51
|
Hi all, since Audacity 3.0.2 is released now, I rebased my Compressor effect onto the latest master. Max On Sunday, 28 March 2021 at 13:46, Max Maisel wrote: > Hi James, > > it's no problem for me to wait for the 3.0.1 release. > > The latency is mainly caused by various kinds of lookahead. One > lookahead is selected directly by the user, another lookahead is > implicit in case of the exponential fit envelope detector because the > algorithm needs to process the signal backwards in the attack stage. > > Latencies in the range of minutes are extreme cases if users select > high lookahead times or, in case of exponential fit, high attack > times. > But I don't want to limit the ranges of the lookahead and attack time > sliders for offline processing just because of latency in realtime > mode. > > When using the analog simulation envelope detector together with low > lookahead (a few milliseconds) like a real analog compressor, there > is > almost no noticably latency. > > Max > > On Saturday, 27 March 2021 at 14:41, James Crook wrote: > > Hi Max. > > > > The previous update I had on this was about the long latency. > > Disabling realtime preview is sort of OK, but something seems > > wrong. > > A one minute latency is colossal. That points to something > > underlying wrong. > > > > Also 3.0.1 has now become very very much a maintenance release for > > addressing the 3.0.0 unitary project issues. Paul would love to > > get > > some structural > > changes in that improve independence between pieces of code, and I > > am > > saying no. > > We'd also like to get portaudio and FFmpeg library updates in, and > > I > > am saying no. > > > > It is pretty clear that the release after 3.0.1 is going to be > > quite > > soon, so as RM > > I'm sorry to have to say that your compressor will have to sit out > > for 3.0.1. > > > > 3.0.1 is due to actually release on 17th April, so it's a further > > delay of about 3 > > weeks for you in seeing progress on your compressor getting in to > > Audacity. > > > > Is there a good reason for the very long latency? > > > > --James. > > > > > > > > > > On Sat, 27 Mar 2021 at 07:56, Max Maisel <mm...@po...> wrote: > > > Hi all, > > > > > > I've polished my Dynamic Compressor effect and think it is ready > > > now > > > for inclusion. > > > > > > Since my last mail (see > > > https://sourceforge.net/p/audacity/mailman/message/37109016/ for > > > the > > > initial message), I mainly reworked the user interface accoring > > > to > > > your > > > feedback and fixed several bugs. > > > > > > The effect is basically realtime capable but for now realtime > > > preview > > > is disabled after some discussion with Steve because there are > > > bad user experience due to high processing latency in the effect > > > at > > > some settings. > > > > > > Main probleme here is, that the RealtimeEffectManager gives the > > > effect > > > a small block, e.g. 256 samples, and expects the same amount of > > > samples > > > in return. So if an effect like my compressor has a high > > > processing > > > latency, there can be an initial silence for over one minute > > > which > > > the > > > users will think is a bug. Any changes made to the effect > > > settings > > > will > > > only take effect after this long time as well. > > > > > > A possible solution would be latency compensation in the > > > RealtimeEffectManager so that the effect can request the required > > > amount of samples in advance at the beginning or when the user > > > changes > > > settings. The silence at the beginning can then be discarded so > > > that > > > users do not notice it. But this is out of scope of the > > > compressor > > > effect changes. > > > > > > The lastest revision including CI builds can be found in my pull > > > request at https://github.com/audacity/audacity/pull/676. > > > > > > The latest documentation for the effect is can be found at > > > https://alphamanual.audacityteam.org/man/Dynamic_Compressor. > > > > > > I'm looking forward to further feedback and integration. > > > > > > Max > > > > > > > > > > > > > > > _______________________________________________ > > > 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-04-26 14:35:51
|
Found it. It's a bug, and a regression against Audacity 3.0.0. Unfortunately Audacity 3.0.2 was released with the bug. I'll be committing the fix shortly. Steve On Mon, 26 Apr 2021 at 00:35, Steve Fiddle <ste...@gm...> wrote: > I have tried with both jackd and jackd2, but jack support fails with both. > Currently I have jackd installed and have libjack-dev. > > Running cmake includes the following (below): > > Steve > > -- Found ALSA: /usr/lib/x86_64-linux-gnu/libasound.so (found version > "1.2.2") > CMake Warning at cmake-proxies/portaudio-v19/CMakeLists.txt:91 > (find_package): > By not providing "Findjack.cmake" in CMAKE_MODULE_PATH this project has > asked CMake to find a package configuration file provided by "jack", but > CMake did not find one. > > Could not find a package configuration file provided by "jack" with any > of > the following names: > > jackConfig.cmake > jack-config.cmake > > Add the installation prefix of "jack" to CMAKE_PREFIX_PATH or set > "jack_DIR" to a directory containing one of the above files. If "jack" > provides a separate development package or SDK, be sure it has been > installed. > |
From: Steve F. <ste...@gm...> - 2021-04-25 23:35:52
|
I have tried with both jackd and jackd2, but jack support fails with both. Currently I have jackd installed and have libjack-dev. Running cmake includes the following (below): Steve -- Found ALSA: /usr/lib/x86_64-linux-gnu/libasound.so (found version "1.2.2") CMake Warning at cmake-proxies/portaudio-v19/CMakeLists.txt:91 (find_package): By not providing "Findjack.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "jack", but CMake did not find one. Could not find a package configuration file provided by "jack" with any of the following names: jackConfig.cmake jack-config.cmake Add the installation prefix of "jack" to CMAKE_PREFIX_PATH or set "jack_DIR" to a directory containing one of the above files. If "jack" provides a separate development package or SDK, be sure it has been installed. |
From: freddyjohn <fre...@pr...> - 2021-04-22 17:34:51
|
Hello its me again I have three questions for my open source DAW for android. If this is not the place to ask these questions I apologize and would love direction on a community that may be able to answer them. In my experience, Stack Overflow and blogs like it is not that place. I of course have tried and implemented my own solutions but I want to hear from you guys. 1.) what are the data structures used to efficiently handle edits to audio? is it a b-tree, do you use a piece table, what is the structure inside those XML files? what I've tried: I have found a solution using piece table. I keep track of all the edits in one file and when the user is finished I serialize the java object and append it to the end of the file along with integer that describes the byte length of the java object so that it can be de-serialized during another session acting as a project file. I have spent some time looking through audacity source code and reading audacity blogs but I am still not sure exactly what data structure is used. This was an excellent read -> http://www.aosabook.org/en/audacity.html 2.)how do we handle modulations now that the file is in blocks? did you have to worry about the continuity of the LFO for a phaser about these blocks for example? what I've tried: I can see an easy solution to this by calculating the leftover phase and offsetting the next modulation wave by this leftover phase. but for an echo it seems you would need a completely different solution. 3.)Another thing I am struggling with is displaying audio efficiently. what I've tried: on Android we have limited heap memory so I cannot just go and ask for huge Bitmap allocation I need to keep space open for bringing byte[] into program memory to perform modulations so I just ask for a Bitmap that is the h,w of the screen then I scale the audio into this space like this let, screen width of fixed sized = w_N amount of samples = s_N then the equation to scale s within w can be found via s_N ∑ i * (w_N/s_N) i=0 and in order to translate the selection on the screen back into byte land we can use this equation w_i * (s_N/w_N) = s_i for example, a screen of 500px, an audio file of 1000 bytes and a selection within 500px of 500 500*1000/500=1000. I also ensure to never select an odd byte depending on the selected encoding as this creates an extremely unfavorable offset that causes the audio byte stream to not decode correctly. Of course this is O(n) and not very efficient at all. The time it takes to display the file will grow with the length of the file which is very unfavorable to the user. I understand Audacity uses summary information of the audio for parts of its display but I am having a difficult time understanding how we can translate a selection within this summary information to actual file byte locations. It seems that these problems are linked and after spending some time trying to tackle them myself I would really love to hear from the Audacity Team about how they found solutions to these problems. Sent with [ProtonMail](https://protonmail.com) Secure Email. |