audacity-devel Mailing List for Audacity (Page 15)
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: David B. <drb...@gm...> - 2021-04-03 18:08:01
|
On Sat, 3 Apr 2021 at 18:48, James Crook <jam...@gm...> wrote: > Probably 11 AM GMT Monday 5th April. > Manual will be whatever it is at that point too. > > If you've anything planned to go in, please say. > Leland is due to fix an accessibility problem - https://bugzilla.audacityteam.org/show_bug.cgi?id=2211#c5 I won't be able to check the fix before Monday, but will be able to do so before 11am. David. > > On Sat, 3 Apr 2021 at 16:27, David Bailes <drb...@gm...> wrote: > >> On Sat, 3 Apr 2021 at 14:12, James Crook <jam...@gm...> wrote: >> >>> Current plan is for code freeze for Monday 5th April, even bug fixes >>> (except for P1 bugs, none currently) from there on should be as pull >>> requests. That is the same as closing date for translations. >>> >> >> When on Monday? >> thanks, >> David. >> >> >>> >>> I would particularly like to get the fix for >>> https://bugzilla.audacityteam.org/show_bug.cgi?id=2722 >>> into that. >>> >>> Steve, can you give us an update on that, and change the current debug >>> status of the plug-in please? >>> >>> >>> --James. >>> _______________________________________________ >>> 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: James C. <jam...@gm...> - 2021-04-03 17:47:25
|
Probably 11 AM GMT Monday 5th April. Manual will be whatever it is at that point too. If you've anything planned to go in, please say. On Sat, 3 Apr 2021 at 16:27, David Bailes <drb...@gm...> wrote: > On Sat, 3 Apr 2021 at 14:12, James Crook <jam...@gm...> wrote: > >> Current plan is for code freeze for Monday 5th April, even bug fixes >> (except for P1 bugs, none currently) from there on should be as pull >> requests. That is the same as closing date for translations. >> > > When on Monday? > thanks, > David. > > >> >> I would particularly like to get the fix for >> https://bugzilla.audacityteam.org/show_bug.cgi?id=2722 >> into that. >> >> Steve, can you give us an update on that, and change the current debug >> status of the plug-in please? >> >> >> --James. >> _______________________________________________ >> 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-03 15:57:30
|
On Sat, 3 Apr 2021 at 15:51, Roberto Bittar <rbi...@gm...> wrote: > This is my last message here. > I get all your messages. > I don't know how I got on this list and I don't know how to get out. > Please remove my name from the list. > Grateful > Congratulations > > Subscribing and unsubscribing is done through this page: https://lists.sourceforge.net/lists/listinfo/audacity-devel It's a DIY service. Steve |
|
From: David B. <drb...@gm...> - 2021-04-03 15:26:33
|
On Sat, 3 Apr 2021 at 14:12, James Crook <jam...@gm...> wrote: > Current plan is for code freeze for Monday 5th April, even bug fixes > (except for P1 bugs, none currently) from there on should be as pull > requests. That is the same as closing date for translations. > When on Monday? thanks, David. > > I would particularly like to get the fix for > https://bugzilla.audacityteam.org/show_bug.cgi?id=2722 > into that. > > Steve, can you give us an update on that, and change the current debug > status of the plug-in please? > > > --James. > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Paul L. <pau...@gm...> - 2021-04-03 14:51:00
|
We didn’t get to review and merge of those fixes for dithering I prepared. Next release then. PRL On Saturday, April 3, 2021, James Crook <jam...@gm...> wrote: > Current plan is for code freeze for Monday 5th April, even bug fixes > (except for P1 bugs, none currently) from there on should be as pull > requests. That is the same as closing date for translations. > > I would particularly like to get the fix for > https://bugzilla.audacityteam.org/show_bug.cgi?id=2722 > into that. > > Steve, can you give us an update on that, and change the current debug > status of the plug-in please? > > > --James. > |
|
From: Roberto B. <rbi...@gm...> - 2021-04-03 14:50:00
|
This is my last message here. I get all your messages. I don't know how I got on this list and I don't know how to get out. Please remove my name from the list. Grateful Congratulations Em sáb., 3 de abr. de 2021 às 09:00, John Colket <jc...@gm...> escreveu: > ==== Translation ==== > In the video, I also showed that the selection area does not follow the > increase or reduction of the selected area. > > If you need more information just let me know. > ================= > Roberto, thank you for your problem report. I have been able to reproduce > the clicking with the information you provided. I am not aware of others > having similar issues, so I have created a bug report in Audacity for you. > You may follow it here: > https://bugzilla.audacityteam.org/show_bug.cgi?id=2731 > > Please do not reply here to this email, and in the future, as James has > requested, please ask your questions on the Audacity forum. Thank you. > > - John > > ==== Translation ==== > > Roberto, obrigado por seu relatório de problema. Consegui reproduzir o > clique com as informações que você forneceu. Não estou ciente de outros com > problemas semelhantes, então criei um relatório de bug no Audacity para > você. Você pode acompanhá-lo aqui: > https://bugzilla.audacityteam.org/show_bug.cgi?id=2731 > Não responda aqui a este e-mail e, no futuro, conforme James solicitou, > faça suas perguntas no fórum do Audacity. Obrigada. > - João > > ==== Translation of James' note ==== > > Por favor, use o inglês, Roberto, e pergunte no fórum do Audacity, não > aqui. > https://forum.audacityteam.org/ > > Esta lista de e-mail é para pessoas que estão desenvolvendo o Audacity. > > > On Sat, Apr 3, 2021 at 6:40 AM James Crook <jam...@gm...> > wrote: > >> Please use English, Roberto, and please ask on the Audacity forum, not >> here. >> https://forum.audacityteam.org/ >> >> This email list is for people developing Audacity. >> >> --James. >> >> On Sat, 3 Apr 2021 at 00:51, Roberto Bittar <rbi...@gm...> wrote: >> >>> Audio para Audacity.wav >>> <https://drive.google.com/file/d/1gptzmAZUS0c1uReoLVCY-wHAUeqgt5R2/view?usp=drive_web> >>> Video Audacity.mp4 >>> <https://drive.google.com/file/d/1HOOpIOjjNTygyk6vIEv0qIjgr02cgNm2/view?usp=drive_web> >>> >>> No video, também mostrei que a área de seleção não acompanha o aumento >>> ou redução da area selecionada. >>> >>> Se precisarem de mais informação é só avisar. >>> >>> Em sex., 2 de abr. de 2021 às 19:19, John Colket <jc...@gm...> >>> escreveu: >>> >>>> Roberto, >>>> >>>> OK, I generated a 60 second DTMF tone, created a label at the 30 second >>>> mark, then ran Sliding Stetch with all boxes set to 0 except Final Tempo >>>> Change set to 7. The results were as expected. No difficulties. No >>>> clicks, no issues with label position. I repeated this test on 2.4.2, >>>> 3.0.0 and on the most recent 3.0.1 alpha. Can you provide more details? >>>> >>>> - John >>>> >>>> ==== Translation ===== >>>> >>>> OK, eu gerei um tom DTMF de 60 segundos, criei uma etiqueta na marca de >>>> 30 segundos e, em seguida, executei o Sliding Stetch com todas as caixas >>>> definidas como 0, exceto Final Tempo Change definido como 7. Os resultados >>>> foram os esperados. Sem dificuldades. Sem cliques, sem problemas com a >>>> posição do rótulo. Repeti este teste no 2.4.2, 3.0.0 e no 3.0.1 alpha mais >>>> recente. Você pode fornecer mais detalhes? >>>> >>>> On Fri, Apr 2, 2021 at 12:58 PM James Crook <jam...@gm...> >>>> wrote: >>>> >>>>> Google translate gives us this: >>>>> >>>>> Hey guys. >>>>> Nice work from you. >>>>> I'm from Brazil - Minas Gerais - Belo Horizonte. >>>>> I found an error in the Extend Slider Effect +7. >>>>> CLICKS appear. Before this error did not exist or I did not go through >>>>> this. >>>>> Another problem with this same effect is that the MARKING does not >>>>> follow the change in the DRAWING. >>>>> That is, if I marked and increased the stretch, the markup should >>>>> accompany the new design. >>>>> Abs >>>>> >>>>> >>>>> >>>>> On Fri, 2 Apr 2021 at 17:37, Roberto Bittar <rbi...@gm...> >>>>> wrote: >>>>> >>>>>> Olá Pessoal. >>>>>> Belo trabalho de vocês. >>>>>> Sou do Brasil - Minas Gerais - Belo Horizonte. >>>>>> Encontrei um erro no Efeito Estender Deslizante +7. >>>>>> Aparecem CLICKS. Antes não existia este erro ou eu não passei por >>>>>> isto. >>>>>> Outro problema neste mesmo efeito é que a MARCAÇÃO não acompanha a >>>>>> alteração do DESENHO. >>>>>> Ou seja, se eu marquei e aumentei o trecho, a marcação deveria >>>>>> acompanhar o novo desenho. >>>>>> Abs. >>>>>> >>>>>> Em qua., 31 de mar. de 2021 às 09:50, James Crook < >>>>>> jam...@gm...> escreveu: >>>>>> >>>>>>> I've just updated the Audacity .pot and .po files and we are now in >>>>>>> String Freeze for 3.0.1. >>>>>>> >>>>>>> There is an exemption from String Freeze for adding/updating >>>>>>> necessary error/warning messages. Also the more cryptic error messages >>>>>>> that come originally from SQLIte are better not translated. >>>>>>> >>>>>>> Code, by contrast, is not frozen yet, and even P4 fixes are still >>>>>>> fine. >>>>>>> >>>>>>> Target date for having 3.0.1 builds with the updated translations >>>>>>> and an actual code freeze is 5th April, and target date for release is 17th >>>>>>> April. >>>>>>> >>>>>>> Our biggest worry is currently Bug 2700. We don't really have a >>>>>>> handle on it. >>>>>>> https://bugzilla.audacityteam.org/show_bug.cgi?id=2700 >>>>>>> >>>>>>> However we do have other fixes that matter, and we want to get those >>>>>>> fixes out to users. >>>>>>> >>>>>>> --James. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>> >>> _______________________________________________ >>> 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: James C. <jam...@gm...> - 2021-04-03 14:09:01
|
Thanks! That's perfect! --James. On Sat, 3 Apr 2021 at 14:46, Steve Fiddle <ste...@gm...> wrote: > > > On Sat, 3 Apr 2021 at 14:12, James Crook <jam...@gm...> wrote: > >> Current plan is for code freeze for Monday 5th April, even bug fixes >> (except for P1 bugs, none currently) from there on should be as pull >> requests. That is the same as closing date for translations. >> >> I would particularly like to get the fix for >> https://bugzilla.audacityteam.org/show_bug.cgi?id=2722 >> into that. >> >> Steve, can you give us an update on that, and change the current debug >> status of the plug-in please? >> > > I posted a fixed version of the noise gate plug-in to bugzilla yesterday. > > The problem is caused by changes in the Nyquist library. > The fix / workaround is not ideal, but the modified Noise Gate is good for > 6 hour selections at 44100Hz, and throws a meaningful error if the > selection is too long (The error throws at a safe limit of 1 billion > samples). > > Following a discussion with Roger, it looks like a better fix is possible, > using a little known and rarely used primitive that has been available in > Nyquist all along. I shall be working on this today. > > Steve > > >> >> >> --James. >> _______________________________________________ >> 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-03 13:45:04
|
On Sat, 3 Apr 2021 at 14:12, James Crook <jam...@gm...> wrote: > Current plan is for code freeze for Monday 5th April, even bug fixes > (except for P1 bugs, none currently) from there on should be as pull > requests. That is the same as closing date for translations. > > I would particularly like to get the fix for > https://bugzilla.audacityteam.org/show_bug.cgi?id=2722 > into that. > > Steve, can you give us an update on that, and change the current debug > status of the plug-in please? > I posted a fixed version of the noise gate plug-in to bugzilla yesterday. The problem is caused by changes in the Nyquist library. The fix / workaround is not ideal, but the modified Noise Gate is good for 6 hour selections at 44100Hz, and throws a meaningful error if the selection is too long (The error throws at a safe limit of 1 billion samples). Following a discussion with Roger, it looks like a better fix is possible, using a little known and rarely used primitive that has been available in Nyquist all along. I shall be working on this today. Steve > > > --James. > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: James C. <jam...@gm...> - 2021-04-03 13:11:36
|
Current plan is for code freeze for Monday 5th April, even bug fixes (except for P1 bugs, none currently) from there on should be as pull requests. That is the same as closing date for translations. I would particularly like to get the fix for https://bugzilla.audacityteam.org/show_bug.cgi?id=2722 into that. Steve, can you give us an update on that, and change the current debug status of the plug-in please? --James. |
|
From: John C. <jc...@gm...> - 2021-04-03 11:58:54
|
==== Translation ==== In the video, I also showed that the selection area does not follow the increase or reduction of the selected area. If you need more information just let me know. ================= Roberto, thank you for your problem report. I have been able to reproduce the clicking with the information you provided. I am not aware of others having similar issues, so I have created a bug report in Audacity for you. You may follow it here: https://bugzilla.audacityteam.org/show_bug.cgi?id=2731 Please do not reply here to this email, and in the future, as James has requested, please ask your questions on the Audacity forum. Thank you. - John ==== Translation ==== Roberto, obrigado por seu relatório de problema. Consegui reproduzir o clique com as informações que você forneceu. Não estou ciente de outros com problemas semelhantes, então criei um relatório de bug no Audacity para você. Você pode acompanhá-lo aqui: https://bugzilla.audacityteam.org/show_bug.cgi?id=2731 Não responda aqui a este e-mail e, no futuro, conforme James solicitou, faça suas perguntas no fórum do Audacity. Obrigada. - João ==== Translation of James' note ==== Por favor, use o inglês, Roberto, e pergunte no fórum do Audacity, não aqui. https://forum.audacityteam.org/ Esta lista de e-mail é para pessoas que estão desenvolvendo o Audacity. On Sat, Apr 3, 2021 at 6:40 AM James Crook <jam...@gm...> wrote: > Please use English, Roberto, and please ask on the Audacity forum, not > here. > https://forum.audacityteam.org/ > > This email list is for people developing Audacity. > > --James. > > On Sat, 3 Apr 2021 at 00:51, Roberto Bittar <rbi...@gm...> wrote: > >> Audio para Audacity.wav >> <https://drive.google.com/file/d/1gptzmAZUS0c1uReoLVCY-wHAUeqgt5R2/view?usp=drive_web> >> Video Audacity.mp4 >> <https://drive.google.com/file/d/1HOOpIOjjNTygyk6vIEv0qIjgr02cgNm2/view?usp=drive_web> >> >> No video, também mostrei que a área de seleção não acompanha o aumento ou >> redução da area selecionada. >> >> Se precisarem de mais informação é só avisar. >> >> Em sex., 2 de abr. de 2021 às 19:19, John Colket <jc...@gm...> >> escreveu: >> >>> Roberto, >>> >>> OK, I generated a 60 second DTMF tone, created a label at the 30 second >>> mark, then ran Sliding Stetch with all boxes set to 0 except Final Tempo >>> Change set to 7. The results were as expected. No difficulties. No >>> clicks, no issues with label position. I repeated this test on 2.4.2, >>> 3.0.0 and on the most recent 3.0.1 alpha. Can you provide more details? >>> >>> - John >>> >>> ==== Translation ===== >>> >>> OK, eu gerei um tom DTMF de 60 segundos, criei uma etiqueta na marca de >>> 30 segundos e, em seguida, executei o Sliding Stetch com todas as caixas >>> definidas como 0, exceto Final Tempo Change definido como 7. Os resultados >>> foram os esperados. Sem dificuldades. Sem cliques, sem problemas com a >>> posição do rótulo. Repeti este teste no 2.4.2, 3.0.0 e no 3.0.1 alpha mais >>> recente. Você pode fornecer mais detalhes? >>> >>> On Fri, Apr 2, 2021 at 12:58 PM James Crook <jam...@gm...> >>> wrote: >>> >>>> Google translate gives us this: >>>> >>>> Hey guys. >>>> Nice work from you. >>>> I'm from Brazil - Minas Gerais - Belo Horizonte. >>>> I found an error in the Extend Slider Effect +7. >>>> CLICKS appear. Before this error did not exist or I did not go through >>>> this. >>>> Another problem with this same effect is that the MARKING does not >>>> follow the change in the DRAWING. >>>> That is, if I marked and increased the stretch, the markup should >>>> accompany the new design. >>>> Abs >>>> >>>> >>>> >>>> On Fri, 2 Apr 2021 at 17:37, Roberto Bittar <rbi...@gm...> >>>> wrote: >>>> >>>>> Olá Pessoal. >>>>> Belo trabalho de vocês. >>>>> Sou do Brasil - Minas Gerais - Belo Horizonte. >>>>> Encontrei um erro no Efeito Estender Deslizante +7. >>>>> Aparecem CLICKS. Antes não existia este erro ou eu não passei por isto. >>>>> Outro problema neste mesmo efeito é que a MARCAÇÃO não acompanha a >>>>> alteração do DESENHO. >>>>> Ou seja, se eu marquei e aumentei o trecho, a marcação deveria >>>>> acompanhar o novo desenho. >>>>> Abs. >>>>> >>>>> Em qua., 31 de mar. de 2021 às 09:50, James Crook < >>>>> jam...@gm...> escreveu: >>>>> >>>>>> I've just updated the Audacity .pot and .po files and we are now in >>>>>> String Freeze for 3.0.1. >>>>>> >>>>>> There is an exemption from String Freeze for adding/updating >>>>>> necessary error/warning messages. Also the more cryptic error messages >>>>>> that come originally from SQLIte are better not translated. >>>>>> >>>>>> Code, by contrast, is not frozen yet, and even P4 fixes are still >>>>>> fine. >>>>>> >>>>>> Target date for having 3.0.1 builds with the updated translations and >>>>>> an actual code freeze is 5th April, and target date for release is 17th >>>>>> April. >>>>>> >>>>>> Our biggest worry is currently Bug 2700. We don't really have a >>>>>> handle on it. >>>>>> https://bugzilla.audacityteam.org/show_bug.cgi?id=2700 >>>>>> >>>>>> However we do have other fixes that matter, and we want to get those >>>>>> fixes out to users. >>>>>> >>>>>> --James. >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>> >> _______________________________________________ >> 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: James C. <jam...@gm...> - 2021-04-03 10:39:11
|
Please use English, Roberto, and please ask on the Audacity forum, not here. https://forum.audacityteam.org/ This email list is for people developing Audacity. --James. On Sat, 3 Apr 2021 at 00:51, Roberto Bittar <rbi...@gm...> wrote: > Audio para Audacity.wav > <https://drive.google.com/file/d/1gptzmAZUS0c1uReoLVCY-wHAUeqgt5R2/view?usp=drive_web> > Video Audacity.mp4 > <https://drive.google.com/file/d/1HOOpIOjjNTygyk6vIEv0qIjgr02cgNm2/view?usp=drive_web> > > No video, também mostrei que a área de seleção não acompanha o aumento ou > redução da area selecionada. > > Se precisarem de mais informação é só avisar. > > Em sex., 2 de abr. de 2021 às 19:19, John Colket <jc...@gm...> > escreveu: > >> Roberto, >> >> OK, I generated a 60 second DTMF tone, created a label at the 30 second >> mark, then ran Sliding Stetch with all boxes set to 0 except Final Tempo >> Change set to 7. The results were as expected. No difficulties. No >> clicks, no issues with label position. I repeated this test on 2.4.2, >> 3.0.0 and on the most recent 3.0.1 alpha. Can you provide more details? >> >> - John >> >> ==== Translation ===== >> >> OK, eu gerei um tom DTMF de 60 segundos, criei uma etiqueta na marca de >> 30 segundos e, em seguida, executei o Sliding Stetch com todas as caixas >> definidas como 0, exceto Final Tempo Change definido como 7. Os resultados >> foram os esperados. Sem dificuldades. Sem cliques, sem problemas com a >> posição do rótulo. Repeti este teste no 2.4.2, 3.0.0 e no 3.0.1 alpha mais >> recente. Você pode fornecer mais detalhes? >> >> On Fri, Apr 2, 2021 at 12:58 PM James Crook <jam...@gm...> >> wrote: >> >>> Google translate gives us this: >>> >>> Hey guys. >>> Nice work from you. >>> I'm from Brazil - Minas Gerais - Belo Horizonte. >>> I found an error in the Extend Slider Effect +7. >>> CLICKS appear. Before this error did not exist or I did not go through >>> this. >>> Another problem with this same effect is that the MARKING does not >>> follow the change in the DRAWING. >>> That is, if I marked and increased the stretch, the markup should >>> accompany the new design. >>> Abs >>> >>> >>> >>> On Fri, 2 Apr 2021 at 17:37, Roberto Bittar <rbi...@gm...> >>> wrote: >>> >>>> Olá Pessoal. >>>> Belo trabalho de vocês. >>>> Sou do Brasil - Minas Gerais - Belo Horizonte. >>>> Encontrei um erro no Efeito Estender Deslizante +7. >>>> Aparecem CLICKS. Antes não existia este erro ou eu não passei por isto. >>>> Outro problema neste mesmo efeito é que a MARCAÇÃO não acompanha a >>>> alteração do DESENHO. >>>> Ou seja, se eu marquei e aumentei o trecho, a marcação deveria >>>> acompanhar o novo desenho. >>>> Abs. >>>> >>>> Em qua., 31 de mar. de 2021 às 09:50, James Crook < >>>> jam...@gm...> escreveu: >>>> >>>>> I've just updated the Audacity .pot and .po files and we are now in >>>>> String Freeze for 3.0.1. >>>>> >>>>> There is an exemption from String Freeze for adding/updating necessary >>>>> error/warning messages. Also the more cryptic error messages that come >>>>> originally from SQLIte are better not translated. >>>>> >>>>> Code, by contrast, is not frozen yet, and even P4 fixes are still fine. >>>>> >>>>> Target date for having 3.0.1 builds with the updated translations and >>>>> an actual code freeze is 5th April, and target date for release is 17th >>>>> April. >>>>> >>>>> Our biggest worry is currently Bug 2700. We don't really have a >>>>> handle on it. >>>>> https://bugzilla.audacityteam.org/show_bug.cgi?id=2700 >>>>> >>>>> However we do have other fixes that matter, and we want to get those >>>>> fixes out to users. >>>>> >>>>> --James. >>>>> >>>>> _______________________________________________ >>>>> 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 >> > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Roberto B. <rbi...@gm...> - 2021-04-02 23:50:17
|
Audio para Audacity.wav <https://drive.google.com/file/d/1gptzmAZUS0c1uReoLVCY-wHAUeqgt5R2/view?usp=drive_web> Video Audacity.mp4 <https://drive.google.com/file/d/1HOOpIOjjNTygyk6vIEv0qIjgr02cgNm2/view?usp=drive_web> No video, também mostrei que a área de seleção não acompanha o aumento ou redução da area selecionada. Se precisarem de mais informação é só avisar. Em sex., 2 de abr. de 2021 às 19:19, John Colket <jc...@gm...> escreveu: > Roberto, > > OK, I generated a 60 second DTMF tone, created a label at the 30 second > mark, then ran Sliding Stetch with all boxes set to 0 except Final Tempo > Change set to 7. The results were as expected. No difficulties. No > clicks, no issues with label position. I repeated this test on 2.4.2, > 3.0.0 and on the most recent 3.0.1 alpha. Can you provide more details? > > - John > > ==== Translation ===== > > OK, eu gerei um tom DTMF de 60 segundos, criei uma etiqueta na marca de 30 > segundos e, em seguida, executei o Sliding Stetch com todas as caixas > definidas como 0, exceto Final Tempo Change definido como 7. Os resultados > foram os esperados. Sem dificuldades. Sem cliques, sem problemas com a > posição do rótulo. Repeti este teste no 2.4.2, 3.0.0 e no 3.0.1 alpha mais > recente. Você pode fornecer mais detalhes? > > On Fri, Apr 2, 2021 at 12:58 PM James Crook <jam...@gm...> > wrote: > >> Google translate gives us this: >> >> Hey guys. >> Nice work from you. >> I'm from Brazil - Minas Gerais - Belo Horizonte. >> I found an error in the Extend Slider Effect +7. >> CLICKS appear. Before this error did not exist or I did not go through >> this. >> Another problem with this same effect is that the MARKING does not follow >> the change in the DRAWING. >> That is, if I marked and increased the stretch, the markup should >> accompany the new design. >> Abs >> >> >> >> On Fri, 2 Apr 2021 at 17:37, Roberto Bittar <rbi...@gm...> wrote: >> >>> Olá Pessoal. >>> Belo trabalho de vocês. >>> Sou do Brasil - Minas Gerais - Belo Horizonte. >>> Encontrei um erro no Efeito Estender Deslizante +7. >>> Aparecem CLICKS. Antes não existia este erro ou eu não passei por isto. >>> Outro problema neste mesmo efeito é que a MARCAÇÃO não acompanha a >>> alteração do DESENHO. >>> Ou seja, se eu marquei e aumentei o trecho, a marcação deveria >>> acompanhar o novo desenho. >>> Abs. >>> >>> Em qua., 31 de mar. de 2021 às 09:50, James Crook < >>> jam...@gm...> escreveu: >>> >>>> I've just updated the Audacity .pot and .po files and we are now in >>>> String Freeze for 3.0.1. >>>> >>>> There is an exemption from String Freeze for adding/updating necessary >>>> error/warning messages. Also the more cryptic error messages that come >>>> originally from SQLIte are better not translated. >>>> >>>> Code, by contrast, is not frozen yet, and even P4 fixes are still fine. >>>> >>>> Target date for having 3.0.1 builds with the updated translations and >>>> an actual code freeze is 5th April, and target date for release is 17th >>>> April. >>>> >>>> Our biggest worry is currently Bug 2700. We don't really have a handle >>>> on it. >>>> https://bugzilla.audacityteam.org/show_bug.cgi?id=2700 >>>> >>>> However we do have other fixes that matter, and we want to get those >>>> fixes out to users. >>>> >>>> --James. >>>> >>>> _______________________________________________ >>>> 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: John C. <jc...@gm...> - 2021-04-02 22:18:29
|
Roberto, OK, I generated a 60 second DTMF tone, created a label at the 30 second mark, then ran Sliding Stetch with all boxes set to 0 except Final Tempo Change set to 7. The results were as expected. No difficulties. No clicks, no issues with label position. I repeated this test on 2.4.2, 3.0.0 and on the most recent 3.0.1 alpha. Can you provide more details? - John ==== Translation ===== OK, eu gerei um tom DTMF de 60 segundos, criei uma etiqueta na marca de 30 segundos e, em seguida, executei o Sliding Stetch com todas as caixas definidas como 0, exceto Final Tempo Change definido como 7. Os resultados foram os esperados. Sem dificuldades. Sem cliques, sem problemas com a posição do rótulo. Repeti este teste no 2.4.2, 3.0.0 e no 3.0.1 alpha mais recente. Você pode fornecer mais detalhes? On Fri, Apr 2, 2021 at 12:58 PM James Crook <jam...@gm...> wrote: > Google translate gives us this: > > Hey guys. > Nice work from you. > I'm from Brazil - Minas Gerais - Belo Horizonte. > I found an error in the Extend Slider Effect +7. > CLICKS appear. Before this error did not exist or I did not go through > this. > Another problem with this same effect is that the MARKING does not follow > the change in the DRAWING. > That is, if I marked and increased the stretch, the markup should > accompany the new design. > Abs > > > > On Fri, 2 Apr 2021 at 17:37, Roberto Bittar <rbi...@gm...> wrote: > >> Olá Pessoal. >> Belo trabalho de vocês. >> Sou do Brasil - Minas Gerais - Belo Horizonte. >> Encontrei um erro no Efeito Estender Deslizante +7. >> Aparecem CLICKS. Antes não existia este erro ou eu não passei por isto. >> Outro problema neste mesmo efeito é que a MARCAÇÃO não acompanha a >> alteração do DESENHO. >> Ou seja, se eu marquei e aumentei o trecho, a marcação deveria acompanhar >> o novo desenho. >> Abs. >> >> Em qua., 31 de mar. de 2021 às 09:50, James Crook < >> jam...@gm...> escreveu: >> >>> I've just updated the Audacity .pot and .po files and we are now in >>> String Freeze for 3.0.1. >>> >>> There is an exemption from String Freeze for adding/updating necessary >>> error/warning messages. Also the more cryptic error messages that come >>> originally from SQLIte are better not translated. >>> >>> Code, by contrast, is not frozen yet, and even P4 fixes are still fine. >>> >>> Target date for having 3.0.1 builds with the updated translations and an >>> actual code freeze is 5th April, and target date for release is 17th April. >>> >>> Our biggest worry is currently Bug 2700. We don't really have a handle >>> on it. >>> https://bugzilla.audacityteam.org/show_bug.cgi?id=2700 >>> >>> However we do have other fixes that matter, and we want to get those >>> fixes out to users. >>> >>> --James. >>> >>> _______________________________________________ >>> 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: James C. <jam...@gm...> - 2021-04-02 16:57:57
|
Google translate gives us this: Hey guys. Nice work from you. I'm from Brazil - Minas Gerais - Belo Horizonte. I found an error in the Extend Slider Effect +7. CLICKS appear. Before this error did not exist or I did not go through this. Another problem with this same effect is that the MARKING does not follow the change in the DRAWING. That is, if I marked and increased the stretch, the markup should accompany the new design. Abs On Fri, 2 Apr 2021 at 17:37, Roberto Bittar <rbi...@gm...> wrote: > Olá Pessoal. > Belo trabalho de vocês. > Sou do Brasil - Minas Gerais - Belo Horizonte. > Encontrei um erro no Efeito Estender Deslizante +7. > Aparecem CLICKS. Antes não existia este erro ou eu não passei por isto. > Outro problema neste mesmo efeito é que a MARCAÇÃO não acompanha a > alteração do DESENHO. > Ou seja, se eu marquei e aumentei o trecho, a marcação deveria acompanhar > o novo desenho. > Abs. > > Em qua., 31 de mar. de 2021 às 09:50, James Crook <jam...@gm...> > escreveu: > >> I've just updated the Audacity .pot and .po files and we are now in >> String Freeze for 3.0.1. >> >> There is an exemption from String Freeze for adding/updating necessary >> error/warning messages. Also the more cryptic error messages that come >> originally from SQLIte are better not translated. >> >> Code, by contrast, is not frozen yet, and even P4 fixes are still fine. >> >> Target date for having 3.0.1 builds with the updated translations and an >> actual code freeze is 5th April, and target date for release is 17th April. >> >> Our biggest worry is currently Bug 2700. We don't really have a handle >> on it. >> https://bugzilla.audacityteam.org/show_bug.cgi?id=2700 >> >> However we do have other fixes that matter, and we want to get those >> fixes out to users. >> >> --James. >> >> _______________________________________________ >> 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: Roberto B. <rbi...@gm...> - 2021-04-02 16:32:05
|
Olá Pessoal. Belo trabalho de vocês. Sou do Brasil - Minas Gerais - Belo Horizonte. Encontrei um erro no Efeito Estender Deslizante +7. Aparecem CLICKS. Antes não existia este erro ou eu não passei por isto. Outro problema neste mesmo efeito é que a MARCAÇÃO não acompanha a alteração do DESENHO. Ou seja, se eu marquei e aumentei o trecho, a marcação deveria acompanhar o novo desenho. Abs. Em qua., 31 de mar. de 2021 às 09:50, James Crook <jam...@gm...> escreveu: > I've just updated the Audacity .pot and .po files and we are now in String > Freeze for 3.0.1. > > There is an exemption from String Freeze for adding/updating necessary > error/warning messages. Also the more cryptic error messages that come > originally from SQLIte are better not translated. > > Code, by contrast, is not frozen yet, and even P4 fixes are still fine. > > Target date for having 3.0.1 builds with the updated translations and an > actual code freeze is 5th April, and target date for release is 17th April. > > Our biggest worry is currently Bug 2700. We don't really have a handle on > it. > https://bugzilla.audacityteam.org/show_bug.cgi?id=2700 > > However we do have other fixes that matter, and we want to get those fixes > out to users. > > --James. > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: James C. <jam...@gm...> - 2021-03-31 12:49:22
|
I've just updated the Audacity .pot and .po files and we are now in String Freeze for 3.0.1. There is an exemption from String Freeze for adding/updating necessary error/warning messages. Also the more cryptic error messages that come originally from SQLIte are better not translated. Code, by contrast, is not frozen yet, and even P4 fixes are still fine. Target date for having 3.0.1 builds with the updated translations and an actual code freeze is 5th April, and target date for release is 17th April. Our biggest worry is currently Bug 2700. We don't really have a handle on it. https://bugzilla.audacityteam.org/show_bug.cgi?id=2700 However we do have other fixes that matter, and we want to get those fixes out to users. --James. |
|
From: Robert H. <aar...@gm...> - 2021-03-30 07:07:20
|
On 28/03/2021, Peter Sampson <pet...@gm...> wrote: > On Sun, Mar 28, 2021 at 12:46 PM Max Maisel <mm...@po...> wrote: > >> Hi James, >> >> it's no problem for me to wait for the 3.0.1 release. >> > > Max, > > I'm hoping that between us we can get the real time preview working before > this > gets released - it will make it much more useful (and more fun). > I would go further and say that it is essential to have real time preview. Static preview without parameter manipulation is pointless, especially for a compressor. Not to mention that the conventional preview doesn't include other tracks and lacks therefore context. I think you have to make compromises on the Attack/Release calculations. Would it be helpful to work with approximations and the already stored peak/RMS values? The rendering (= applying the effect) could still be executed accurately though. Robert > Peter > > > >> 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 >> >> >> >> >> _______________________________________________ >> audacity-devel mailing list >> aud...@li... >> https://lists.sourceforge.net/lists/listinfo/audacity-devel >> > |
|
From: James C. <jam...@gm...> - 2021-03-29 12:19:40
|
Dave, each version of wxWidgets fixes some problems and introduces some new ones. We have only tested with wx3.1.3. We have not tested with wx3.1.4. It is probably pretty safe to use wx3.1.4. But we haven't tested with it, so the test for using our wx3.1.3 will remain in there. Please also have a look at our recent check ins. https://github.com/audacity/audacity/commits/master You may want to cherry pick some of those. --James. On Mon, 29 Mar 2021 at 13:08, Dave Plater <dpl...@gm...> wrote: > On 3/29/21, Dave Plater <dpl...@gm...> wrote: > > Thanks very much, > > Dave > > > > On Sat, 27 Mar 2021, 17:07 James Crook, <jam...@gm...> wrote: > > > >> Dave, > >> > >> You can see that there are four actual patches here: > >> https://github.com/audacity/wxWidgets/commits/audacity-fixes-3.1.3 > >> > >> June 15th 2020 and earlier is all exactly as in wxWidgets. > >> > >> --James > >> > > It seems this was a bit of a false alarm, all of the above patches > except I never used the msw/setup0.h one, are included in > wxWidgets-3.1.4 which is current in openSUSE. This is most probably > why I didn't get any gui problems. I'll use the patch to remove the > audacity wxWidgets check and you should perhaps put in a wx 3.1.4 > requirement instead. > Thanks > Dave > > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Dave P. <dpl...@gm...> - 2021-03-29 12:07:07
|
On 3/29/21, Dave Plater <dpl...@gm...> wrote: > Thanks very much, > Dave > > On Sat, 27 Mar 2021, 17:07 James Crook, <jam...@gm...> wrote: > >> Dave, >> >> You can see that there are four actual patches here: >> https://github.com/audacity/wxWidgets/commits/audacity-fixes-3.1.3 >> >> June 15th 2020 and earlier is all exactly as in wxWidgets. >> >> --James >> It seems this was a bit of a false alarm, all of the above patches except I never used the msw/setup0.h one, are included in wxWidgets-3.1.4 which is current in openSUSE. This is most probably why I didn't get any gui problems. I'll use the patch to remove the audacity wxWidgets check and you should perhaps put in a wx 3.1.4 requirement instead. Thanks Dave |
|
From: Dave P. <dpl...@gm...> - 2021-03-29 08:26:25
|
Thanks very much, Dave On Sat, 27 Mar 2021, 17:07 James Crook, <jam...@gm...> wrote: > Dave, > > You can see that there are four actual patches here: > https://github.com/audacity/wxWidgets/commits/audacity-fixes-3.1.3 > > June 15th 2020 and earlier is all exactly as in wxWidgets. > > --James > > On Sat, 27 Mar 2021 at 14:52, Dave Plater <dpl...@gm...> wrote: > >> On 3/27/21, Dave Plater <dpl...@gm...> wrote: >> > On 3/26/21, Leland <ll...@ho...> wrote: >> >> We started requiring our version of wxWidgets because It includes >> >> important >> >> fixes that prevented crashes. This is very much like what nearly every >> >> Linux distro does. How many openSUSE packages have openSUSE specific >> >> patches? >> >> I think that the key word here is patches. I can happily patch the >> wxWidgets package built from the standard sources with umpteen patches >> but I can't create a new conflicting package. >> I dislike snaps flatpacks because they are big and cumbersome. A big >> point that Linux has over windows is the size of the installation. >> I notice that the audacity/wxWidgets package states that all bugs are >> directed to wxWidgets trax. Somehow I don't think that they will >> accept bugs against your fork. >> >> Regards >> Dave >> >> >> _______________________________________________ >> 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-03-28 11:50:57
|
On Sun, Mar 28, 2021 at 12:46 PM Max Maisel <mm...@po...> wrote: > Hi James, > > it's no problem for me to wait for the 3.0.1 release. > Max, I'm hoping that between us we can get the real time preview working before this gets released - it will make it much more useful (and more fun). Peter > 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 > > > > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Max M. <mm...@po...> - 2021-03-28 11:46:28
|
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: Jack L. <xxj...@gm...> - 2021-03-28 04:27:08
|
Actually the computer I used did not have DBPAGE turned on ( I have too many computers....). Let me make a note about that in the port since that is not the default for the system sqlite3. On Sat, Mar 27, 2021 at 9:19 PM Jack L. <xxj...@gm...> wrote: > > It looks like it's using the system version which does have dbpage > table support compiled in. > > -- ========== Configuring sqlite ========== > -- Checking for module 'sqlite3 >= 3.32.0' > -- Found sqlite3 , version 3.34.1 > -- Using 'sqlite' system library > > usr/ports/databases/sqlite3 # make showconfig > ===> The following configuration options are available for sqlite3-3.34.1,1: > ARMOR=off: Detect misuse of the API > DBPAGE=on: Enable DBPAGE Virtual Table > DBSTAT=on: Enable DBSTAT Virtual Table > DIRECT_READ=on: File is read directly from disk > DQS=on: Double-quoted String Literals > EXTENSION=on: Allow loadable extensions > FTS3_TOKEN=on: Enable two-args version fts3_tokenizer > FTS4=on: Enable FTS3/4 (Full Text Search) module > FTS5=on: Enable version 5 full-text search engine > LIKENOTBLOB=off: LIKE does not match blobs > MEMMAN=off: Allow it to release unused memory > METADATA=on: Enable column metadata > NORMALIZE=off: Enable normalized sql function > NULL_TRIM=off: Omits NULL columns at the ends of rows > RBU=off: Enable the resumable bulk update > SECURE_DELETE=on: Overwrite deleted information with zeros > SORT_REF=off: To use references in the sorter > STMT=off: Prepared statement scan status > STSHELL=on: Statically link libsqlite3 into shell > TCL=off: Enable tcl extension and sqlite_analyzer > THREADS=on: Threading support > TRUSTED_SCHEMA=off: SQL functions & virtual tables are considered unsafe > UNKNOWN_SQL=off: Suppress unknown function errors > UNLOCK_NOTIFY=on: Enable notification on unlocking > URI=on: Enable use the URI filename > URI_AUTHORITY=off: Allow convert URL into a UNC > ====> Optional extensions > JSON1=off: Enable the JSON1 extension > SESSION=off: Enable the session extension > ====> Optional functions > OFFSET=off: Enable sqlite_offset() returning record's file offset > SER1=off: Enable the sqlite3_[de]serialize() interface > SOUNDEX=off: Enable the soundex() SQL function > ====> Unicode support > ICU=off: Unicode support via ICU > UNICODE61=on: Unicode Version 6.1 tokenizer > ====> Index type for range queries > RTREE=on: Enable R*Tree module > RTREE_INT=off: Store 32-bit sig int (no float) coordinates > GEOPOLY=off: Uses the GeoJSON notation (RFC-7946) > ====> Where to store temporary file: you have to select exactly one of them > TS0=off: Always use temporary file > TS1=off: File by default, change allowed PRAGMA > TS2=off: Memory by default, change allowed PRAGMA > TS3=on: Always use memory > ====> Which query planner to use, stability or ...: you can only > select none or one of them > STAT3=off: Collect histogram data from leftmost column > STAT4=off: Collect histogram data from all columns > ====> Command line editing library: you can only select none or one of them > READLINE=off: Command line editing via libreadline > LIBEDIT=off: Command line editing via libedit > > On Sat, Mar 27, 2021 at 9:11 PM Leland <ll...@ho...> wrote: > > > > Are you using FreeBSD's sqlite3 package or the one we supply? We require the sqlite "dbpage table" support be compiled in. This is controlled with the SQLITE_ENABLE_DBPAGE_VTAB sqlite3 compile define. > > > > > -----Original Message----- > > > From: Jack L. <xxj...@gm...> > > > Sent: Saturday, March 27, 2021 10:28 PM > > > To: Audacity-Devel list <aud...@li...> > > > Subject: [Audacity-devel] Internal Error DBConnection > > > > > > I was using the latest audacity 3.0.0 with all the patches on FreeBSD and just > > > came across an "Internal Error". I ctrl+o and opened file1, > > > ctrl+o another file 2, closed file 1, following message appears: > > > > > > 20:21:04: Debug: Cached a statement for 3 > > > 20:21:36: Debug: Cached a statement for 1 > > > 20:21:54: Debug: Cached a statement for 6 > > > 20:21:54: Debug: prepare error no such table: sqlite_dbpage > > > > > > and then internal error in screenshot. After closing all the dialogs, it was > > > working normally again. > > > > > > > > _______________________________________________ > > audacity-devel mailing list > > aud...@li... > > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
|
From: Jack L. <xxj...@gm...> - 2021-03-28 04:20:15
|
It looks like it's using the system version which does have dbpage
table support compiled in.
-- ========== Configuring sqlite ==========
-- Checking for module 'sqlite3 >= 3.32.0'
-- Found sqlite3 , version 3.34.1
-- Using 'sqlite' system library
usr/ports/databases/sqlite3 # make showconfig
===> The following configuration options are available for sqlite3-3.34.1,1:
ARMOR=off: Detect misuse of the API
DBPAGE=on: Enable DBPAGE Virtual Table
DBSTAT=on: Enable DBSTAT Virtual Table
DIRECT_READ=on: File is read directly from disk
DQS=on: Double-quoted String Literals
EXTENSION=on: Allow loadable extensions
FTS3_TOKEN=on: Enable two-args version fts3_tokenizer
FTS4=on: Enable FTS3/4 (Full Text Search) module
FTS5=on: Enable version 5 full-text search engine
LIKENOTBLOB=off: LIKE does not match blobs
MEMMAN=off: Allow it to release unused memory
METADATA=on: Enable column metadata
NORMALIZE=off: Enable normalized sql function
NULL_TRIM=off: Omits NULL columns at the ends of rows
RBU=off: Enable the resumable bulk update
SECURE_DELETE=on: Overwrite deleted information with zeros
SORT_REF=off: To use references in the sorter
STMT=off: Prepared statement scan status
STSHELL=on: Statically link libsqlite3 into shell
TCL=off: Enable tcl extension and sqlite_analyzer
THREADS=on: Threading support
TRUSTED_SCHEMA=off: SQL functions & virtual tables are considered unsafe
UNKNOWN_SQL=off: Suppress unknown function errors
UNLOCK_NOTIFY=on: Enable notification on unlocking
URI=on: Enable use the URI filename
URI_AUTHORITY=off: Allow convert URL into a UNC
====> Optional extensions
JSON1=off: Enable the JSON1 extension
SESSION=off: Enable the session extension
====> Optional functions
OFFSET=off: Enable sqlite_offset() returning record's file offset
SER1=off: Enable the sqlite3_[de]serialize() interface
SOUNDEX=off: Enable the soundex() SQL function
====> Unicode support
ICU=off: Unicode support via ICU
UNICODE61=on: Unicode Version 6.1 tokenizer
====> Index type for range queries
RTREE=on: Enable R*Tree module
RTREE_INT=off: Store 32-bit sig int (no float) coordinates
GEOPOLY=off: Uses the GeoJSON notation (RFC-7946)
====> Where to store temporary file: you have to select exactly one of them
TS0=off: Always use temporary file
TS1=off: File by default, change allowed PRAGMA
TS2=off: Memory by default, change allowed PRAGMA
TS3=on: Always use memory
====> Which query planner to use, stability or ...: you can only
select none or one of them
STAT3=off: Collect histogram data from leftmost column
STAT4=off: Collect histogram data from all columns
====> Command line editing library: you can only select none or one of them
READLINE=off: Command line editing via libreadline
LIBEDIT=off: Command line editing via libedit
On Sat, Mar 27, 2021 at 9:11 PM Leland <ll...@ho...> wrote:
>
> Are you using FreeBSD's sqlite3 package or the one we supply? We require the sqlite "dbpage table" support be compiled in. This is controlled with the SQLITE_ENABLE_DBPAGE_VTAB sqlite3 compile define.
>
> > -----Original Message-----
> > From: Jack L. <xxj...@gm...>
> > Sent: Saturday, March 27, 2021 10:28 PM
> > To: Audacity-Devel list <aud...@li...>
> > Subject: [Audacity-devel] Internal Error DBConnection
> >
> > I was using the latest audacity 3.0.0 with all the patches on FreeBSD and just
> > came across an "Internal Error". I ctrl+o and opened file1,
> > ctrl+o another file 2, closed file 1, following message appears:
> >
> > 20:21:04: Debug: Cached a statement for 3
> > 20:21:36: Debug: Cached a statement for 1
> > 20:21:54: Debug: Cached a statement for 6
> > 20:21:54: Debug: prepare error no such table: sqlite_dbpage
> >
> > and then internal error in screenshot. After closing all the dialogs, it was
> > working normally again.
>
>
>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
|
|
From: Leland <ll...@ho...> - 2021-03-28 04:11:10
|
Are you using FreeBSD's sqlite3 package or the one we supply? We require the sqlite "dbpage table" support be compiled in. This is controlled with the SQLITE_ENABLE_DBPAGE_VTAB sqlite3 compile define. > -----Original Message----- > From: Jack L. <xxj...@gm...> > Sent: Saturday, March 27, 2021 10:28 PM > To: Audacity-Devel list <aud...@li...> > Subject: [Audacity-devel] Internal Error DBConnection > > I was using the latest audacity 3.0.0 with all the patches on FreeBSD and just > came across an "Internal Error". I ctrl+o and opened file1, > ctrl+o another file 2, closed file 1, following message appears: > > 20:21:04: Debug: Cached a statement for 3 > 20:21:36: Debug: Cached a statement for 1 > 20:21:54: Debug: Cached a statement for 6 > 20:21:54: Debug: prepare error no such table: sqlite_dbpage > > and then internal error in screenshot. After closing all the dialogs, it was > working normally again. |
1022 messages has been excluded from this view by a project administrator.
