Thanks for helping keep SourceForge clean.
Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
Audacity
A free multi-track audio editor and recorder
audacity-quality — Quality Assurance: priorities for overall usability, interface choices, & bugs
You can subscribe to this list here.
| 2010 |
Jan
(78) |
Feb
(38) |
Mar
(23) |
Apr
(19) |
May
|
Jun
(5) |
Jul
(52) |
Aug
(68) |
Sep
(165) |
Oct
(152) |
Nov
(208) |
Dec
(23) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(9) |
Feb
(68) |
Mar
(38) |
Apr
(161) |
May
(73) |
Jun
(60) |
Jul
(27) |
Aug
(6) |
Sep
(2) |
Oct
(8) |
Nov
(35) |
Dec
(163) |
| 2012 |
Jan
(28) |
Feb
(214) |
Mar
(212) |
Apr
(48) |
May
(37) |
Jun
(111) |
Jul
(126) |
Aug
(144) |
Sep
(43) |
Oct
(19) |
Nov
(58) |
Dec
(79) |
| 2013 |
Jan
(121) |
Feb
(70) |
Mar
(60) |
Apr
(38) |
May
(123) |
Jun
(134) |
Jul
(32) |
Aug
(75) |
Sep
(112) |
Oct
(239) |
Nov
(123) |
Dec
(126) |
| 2014 |
Jan
(25) |
Feb
(35) |
Mar
(29) |
Apr
(71) |
May
(68) |
Jun
(38) |
Jul
(37) |
Aug
(92) |
Sep
(43) |
Oct
(252) |
Nov
(216) |
Dec
(504) |
| 2015 |
Jan
(348) |
Feb
(220) |
Mar
(131) |
Apr
(185) |
May
(389) |
Jun
(361) |
Jul
(185) |
Aug
(258) |
Sep
(132) |
Oct
(36) |
Nov
(136) |
Dec
(55) |
| 2016 |
Jan
(64) |
Feb
(66) |
Mar
(31) |
Apr
(286) |
May
(381) |
Jun
(422) |
Jul
(258) |
Aug
(254) |
Sep
(134) |
Oct
(296) |
Nov
(347) |
Dec
(276) |
| 2017 |
Jan
(388) |
Feb
(293) |
Mar
(366) |
Apr
(378) |
May
(395) |
Jun
(483) |
Jul
(507) |
Aug
(298) |
Sep
(89) |
Oct
(187) |
Nov
|
Dec
|
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-19 09:45:26
|
On Wed, Oct 18, 2017 at 6:48 PM, Paul Licameli <paul.licameli@...> wrote: > > > On Wed, Oct 18, 2017 at 1:37 PM, Peter Sampson < > petersampsonaudacity@...> wrote: > >> >> >> On Wed, Oct 18, 2017 at 6:35 PM, Paul Licameli <paul.licameli@...> >> wrote: >> >>> >>> >>> On Wed, Oct 18, 2017 at 5:55 AM, Peter Sampson < >>> petersampsonaudacity@...> wrote: >>> >>>> >>>> >>>> On Tue, Oct 17, 2017 at 9:32 PM, Paul Licameli <paul.licameli@... >>>> > wrote: >>>> >>>>> >>>>> >>>>> On Tue, Oct 17, 2017 at 10:55 AM, Peter Sampson < >>>>> petersampsonaudacity@...> wrote: >>>>> >>>>>> Testing RC1-2 for cleanup on disk overruns >>>>>> >>>>>> On W10: >>>>>> >>>>>> 6) Audacity cleans up correctly after a failed Export, deleting the >>>>>> WAV file after you acknowledge the error message >>>>>> >>>>>> 7) Audacity cleans up correctly after a failed Save Project, deleting >>>>>> the project folder. >>>>>> >>>>>> >>>>>> On macOS 10.13 High Sierra: >>>>>> >>>>>> 8) Audacity cleans up correctly after a failed Export, deleting the >>>>>> WAV file after you acknowledge the error message >>>>>> >>>>>> 9) BUT Audacity FAILS cleans up correctly after a failed Save >>>>>> Project, leaving the project folder with a couple of sub-folders but empty >>>>>> with no .au files >>>>>> >>>>> >>>>> It worked for me on El Capitan. >>>>> >>>>> Are you sure those folders are empty? No hidden files? >>>>> >>>> >>>> >>>> Tested again today on High Sierra 10.13 >>>> >>>> Still did *not* clean up. :-(( >>>> >>>> But this time the sub-folders had many .au files >>>> >>> >>> I tried writing the "obvious" and not difficult clean up for this >>> unusual contingency, but it isn't working, for unknown reasons. >>> >>> I will not try any further fix for RC. >>> >> >> Fair 'nuff >> >> but do we need to log it as P3 so that it gets a release note? >> > > Okay > PRL > Logged as P3 Bug #1758 On macOS High Sierra - after a failed project save (insufficient space) the data folder is not deleted https://bugzilla.audacityteam.org/show_bug.cgi?id=1758 Right now we know that this bug affects High Sierra macOS 10.13, but does not appear to affect El Capitan. Further testing on different macOS/OSX versions would be useful. @Paul: I have not assigned this bug to you - but I'm assuming you're likely to pick this up but I know that you do not plan to tackle this until after 2.2.0 is released. Peter. > > >> >> >> >>> >>> PRL >>> >>> >>> >>>> >>>> >>>> >>>> It also left behind a WEDS21xzsqj (the project was called WEDS2) >>>> >>>> Opening this with the offered Terminal.app I see: >>>> >>>> Last login: Wed Oct18 09:56:45 on ttys000 >>>> Peters-Macbook-Pro:~ petersampson$ /Volumes/UDISKPRO/WEDS21xsqj ; exit; >>>> logout >>>> Saving session... >>>> ...copying shared history >>>> ...saving history...truncating history files... >>>> ...completed. >>>> >>>> [Process completed] >>>> >>>> >>>> >>>> Normal projects do not leave such files behind. >>>> >>>> >>>> Peter. >>>> >>>> >>>> >>>> >>>> >>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> 10) I also found two extraneous files on my USB clip after these >>>>>> tests - not entirely sure if it was Mac or Windows, but I suspect Mac >>>>>> as I didn't get any extra ones when I did the last two testings for >>>>>> 6) and 7) above: >>>>>> >>>>>> BIGLnore >>>>>> BIGGERLRDDx >>>>>> >>>>>> (I had been working with failed projects and exports called BIG and >>>>>> BIGGER on Mac - on W10 my tests used BIGGEST) >>>>>> >>>>>> >>>>> What exactly are the paths to those files? What was the path to the >>>>> .aup file and the _data file? >>>>> >>>>> >>>>>> >>>>>> 9) and 10) are certainly not release blockers - buy maybe should be >>>>>> logged as P3 with Release Notes so that the user can be aware. >>>>>> >>>>>> Peter, >>>>>> >>>>> >>>>> They are not, and I think neither is 5. >>>>> >>>>> Though I do think "C:\" would be a better naming of the volume than >>>>> just "C". >>>>> >>>>> A and B below are considerations for another release of course. >>>>> >>>>> PRL >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> ---------------------------------------------oooooooOOOooooo >>>>>> oo---------------------------------------------------- >>>>>> >>>>>> >>>>>> *General Comments* >>>>>> >>>>>> These are comments for another day - but capturing these thoughts >>>>>> while I think them as I test. >>>>>> >>>>>> A) with the record disk overrun we could be helpful by displaying >>>>>> messages, probably overlaying the recording waveform, as the user gets to >>>>>> critical >>>>>> levels of disk space. I'm thinking a green/amber/red set of warnings >>>>>> at various stages. >>>>>> >>>>>> I know I was carefully looking at the Status Bar as I conducted the >>>>>> tests - but I'm suspecting many users overlook that. We all certainly did >>>>>> as evidenced >>>>>> that none of us noticed the P1 bug #1756, me included, till I >>>>>> conducted these tests - and it's been broken for a while now. >>>>>> >>>>>> >>>>>> B) Withe the disk overrun situations for Exports and Saves we could >>>>>> be much more helpful if we calculated the available and required space in >>>>>> advance >>>>>> of actually starting the Export or Save and then abandoning it >>>>>> partway through. >>>>>> >>>>>> My tests were with very small available space, but if as a user I was >>>>>> 10-15 minutes or so for the Save of a large project or an Export from such >>>>>> a project >>>>>> I'd bee pretty annoyed to have wasted those 10-15 minutes (or even >>>>>> more) ending in a falure condition. >>>>>> >>>>>> IIRC I think we have a proposal in the Wiki for this (I don't think >>>>>> we have one, yet, for A) above) >>>>>> >>>>>> Peter. >>>>>> >>>>>> >>>>>> On Tue, Oct 17, 2017 at 3:04 PM, Peter Sampson < >>>>>> petersampsonaudacity@...> wrote: >>>>>> >>>>>>> I've just been testing the second build of RC1 on W10 and macOS >>>>>>> 10.13 High Sierra. >>>>>>> >>>>>>> First the good news: >>>>>>> >>>>>>> 1) On both platforms while recording the Status Bar message for >>>>>>> remaining disk space has been restored and works >>>>>>> >>>>>>> 2) Even better, it is persistent now and doesn't disappear and >>>>>>> reappear as it used to. >>>>>>> >>>>>>> 3) Also even better it now overrides other potential Status bar >>>>>>> messages, for example if you hover the cursor over the action buttons in >>>>>>> the TCP >>>>>>> >>>>>>> >>>>>>> Now the not so good news: >>>>>>> >>>>>>> 4) With disk/volume overrun while recording on Mac we get the nice >>>>>>> helpful updated message: >>>>>>> >>>>>>> "Audacity failed to write to a file. >>>>>>> Perhaps <volume and a bit of pathing> is not >>>>>>> writable or the disk is full." >>>>>>> >>>>>>> 5) But with W10 we still get the old unenhanced, unhelpful, message: >>>>>>> >>>>>>> "Audacity failed to write to a file in <volume>" :-(( >>>>>>> >>>>>>> >>>>>>> next I'll be testing the overrun cleanup fixes that Paul made >>>>>>> recently. >>>>>>> >>>>>>> Peter >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-18 19:30:30
|
On Wed, Oct 18, 2017 at 9:18 AM, Peter Sampson < petersampsonaudacity@...> wrote: > A minor issue but Connie would like "greying" to be spelt "graying" for > the US English that she prefers: > > "Non-Greying out of effects when no selection (and explanatory dialog with help button)" > > Thanks for fixing that Paul (I've noted the commit). Peter > > Peter. > > > On Wed, Oct 18, 2017 at 2:53 AM, Bill Wharrie <billwh@...> wrote: > >> >> On 2017/10/17, at 9:01 PM, Paul Licameli <paul.licameli@...> wrote: >> >> Thank you, Bill. >> >> I am not sure I know what this refers to: "Overhaul of clip handling >> code using newer (safer) idioms" >> >> Maybe you mean the rewrite iterations over tracks that I have mentioned? >> But that is a project I haven't submitted yet! >> >> You mention me (only) by name here -- that makes me feel a bit immodest. >> I'll remove that if you don't mind. >> >> >> That was copied from http://wiki.audacityteam. >> org/wiki/Release_Notes_2.2.0 >> which was written by James. So I’ll update that page. >> >> — Bill >> >> >> PRL >> >> >> On Tue, Oct 17, 2017 at 7:56 PM, Bill Wharrie <billwh@...> wrote: >> >>> Here’s an updated README with the feedback@ address removed in favour >>> of sending people to http://audacityteam.org/contact/#feedback >>> >>> as well as removing the time track stuff. >>> >>> — Bill >>> >>> >>> >>> >>> On 2017/10/17, at 6:43 PM, Bill Wharrie <billwh@...> wrote: >>> >>> >>> On 2017/10/17, at 6:33 PM, Paul Licameli <paul.licameli@...> >>> wrote: >>> >>> Where do I find the up-to-date version of README.txt? >>> >>> >>> Here’s the one I did up a month or so ago. I’ve removed the time track >>> stuff. Peter has seen this before and may have made some changes. >>> >>> — Bill >>> >>> >>> <README 220.txt> >>> >>> PRL >>> >>> >>> >>> On Tue, Oct 17, 2017 at 6:30 PM, Bill Wharrie <billwh@...> wrote: >>> >>>> And we probably want to remove the reference to “Time Track >>>> cut/copy/paste” from the README. >>>> — Bill >>>> >>>> > On 2017/10/17, at 6:27 PM, Bill Wharrie <billwh@...> wrote: >>>> > >>>> > The title says it all. >>>> > >>>> > (Not that it matters much with the README buried in the bundle) >>>> > >>>> > — Bill >>>> > ------------------------------------------------------------ >>>> ------------------ >>>> > Check out the vibrant tech community on one of the world's most >>>> > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sd >>>> m.link/slashdot >>>> > _______________________________________________ >>>> > Audacity-quality mailing list >>>> > Audacity-quality@... >>>> > https://lists.sourceforge.net/lists/listinfo/audacity-quality >>>> >>>> >>>> ------------------------------------------------------------ >>>> ------------------ >>>> Check out the vibrant tech community on one of the world's most >>>> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sd >>>> m.link/slashdot >>>> _______________________________________________ >>>> Audacity-quality mailing list >>>> Audacity-quality@... >>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sd >>> m.link/slashdot_______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sd >>> m.link/slashdot_______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org>;! >>> http://sdm.link/slashdot >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >>> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org>;! >> http://sdm.link/slashdot_______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-10-18 17:09:33
|
I figured out the formatting error and fixed it. Did you also notice the
bad link text with "ext" in it? All the result of some misplaced
characters.
(How did I find this? Because another comment of Peter's made me grep for
all "{{" in the local help, which is not identical to the online Wiki
source, but has passed through some processing. There were only a few
occurrences, mostly correct formatting directives for warnings, but this
one jumped out as wrong.)
PRL
On Wed, Oct 18, 2017 at 12:59 PM, Paul Licameli <paul.licameli@...>
wrote:
> Look here and see {{{ext}}} visible to the reader after the description of
> Chirp:
>
> http://alphamanual.audacityteam.org/man/Keyboard_Shortcut_Reference
>
> http://alphamanual.audacityteam.org/m/index.php?title=Keyboard_Shortcut_
> Reference&oldid=55876
>
> I will delete it, but was this markup intended to display something else
> that is missing?
>
> PRL
>
>
|
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-18 17:07:33
|
On Wed, Oct 18, 2017 at 5:59 PM, Paul Licameli <paul.licameli@...>
wrote:
> Look here and see {{{ext}}} visible to the reader after the description of
> Chirp:
>
> http://alphamanual.audacityteam.org/man/Keyboard_Shortcut_Reference
>
> http://alphamanual.audacityteam.org/m/index.php?title=Keyboard_Shortcut_
> Reference&oldid=55876
>
> I will delete it, but was this markup intended to display something else
> that is missing?
>
Good catch. :-))
I think here James was intending to link to:
http://alphamanual.audacityteam.org/man/Tone
Peter
> PRL
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Audacity-quality mailing list
> Audacity-quality@...
> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>
>
|
|
From: Paul Licameli <paul.licameli@gm...> - 2017-10-18 16:59:46
|
Look here and see {{{ext}}} visible to the reader after the description of
Chirp:
http://alphamanual.audacityteam.org/man/Keyboard_Shortcut_Reference
http://alphamanual.audacityteam.org/m/index.php?title=Keyboard_Shortcut_Reference&oldid=55876
I will delete it, but was this markup intended to display something else
that is missing?
PRL
|
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-18 16:39:27
|
On Wed, Oct 18, 2017 at 5:33 PM, Paul Licameli <paul.licameli@...> wrote: > > > On Wed, Oct 18, 2017 at 12:19 PM, Peter Sampson < > petersampsonaudacity@...> wrote: > >> >> >> On Wed, Oct 18, 2017 at 5:13 PM, Paul Licameli <paul.licameli@...> >> wrote: >> >>> >>> >>> On Wed, Oct 18, 2017 at 6:18 AM, Peter Sampson < >>> petersampsonaudacity@...> wrote: >>> >>>> >>>> >>>> On Tue, Oct 17, 2017 at 10:00 PM, Paul Licameli < >>>> paul.licameli@...> wrote: >>>> >>>>> >>>>> >>>>> On Tue, Oct 17, 2017 at 12:09 PM, Peter Sampson < >>>>> petersampsonaudacity@...> wrote: >>>>> >>>>>> So we got my "mystery shopper" to install 2.2.0 RC1-2 on a clean >>>>>> machine. >>>>>> (Brand new - she so liked my recent purchase that she shelled out and >>>>>> bought the same) >>>>>> >>>>>> 1) Installation from the Fosshub link with the exe went fine >>>>>> >>>>>> 2) Audacity launched and ran OK >>>>>> >>>>>> >>>>>> 3) with the LAME and FFmpeg installations there are some issues >>>>>> >>>>>> 3.1) In Edit > Preferences > Interface both the Download buttons >>>>>> do not honor the >>>>>> (default) Preference setting for local Manual - but rather target the >>>>>> online Manual. >>>>>> This would cause a failure for a user with a local Manual but no >>>>>> internet link (but >>>>>> of course they could not proceed to the downloads in this case) >>>>>> >>>>> >>>>> Which help pages did you try to find? >>>>> >>>> >>>> >>>> These are not help buttons that go to help pages >>>> >>>> Rather it is the "Download" buttons in the >>>> a) Prefs>Libraries >>>> b) "Locate LAME" dialog >>>> c) "Locate FFmpeg" dialog >>>> >>>> >>>> Note that b and c have two access routes >>>> 1) via Prefs>Libraries >>>> 2) by trying to export to MP3 (LAME) or AAC (FFmpeg) >>>> >>>> >>>> It is the Download button in the "Locate LAME" dialog that is broken - >>>> its counterpart in the Prefs>Libraies works fine, >>>> >>>> So all you should need to do is to change the target in the Download >>>> button in the "Locate LAME" dialog to match >>>> that which we have for the LAME Download button in Prefs>Libraries. >>>> >>>> >>>> The problem that I realized today (actually my mystery shopper >>>> realized) is the the workaround I put in the bug report yesterday >>>> only works if you access via preferences - NOT if you access via a >>>> failed Export/Import >>>> >>>> >>>> >>>> >>>> The FFmpeg buttons work correctly in both Prefs>Libraries and in the >>>> "Locate FFmpeg" dialog >>>> >>>> >>>> >>>> >>>> >>>>> >>>>> I have tried it myself, and I observe that online help does not work >>>>> with generators but local does. I think Steve had to do something earlier >>>>> to fix local help for generators. This included commit >>>>> ccc802aa8bab391706e83a7e06f66b30619e5f24 but I think it also included >>>>> some online changes. I see local has separate .html pages for each >>>>> generator, but the online has sections within a page, so there is not a >>>>> correspondence of addresses as expected between the two. >>>>> >>>>> I tried the Amplify effect and it works ok either local or online. >>>>> >>>>> Maybe there are other examples. >>>>> >>>>> I remind you that you will not have local help if you got Audacity >>>>> with the .zip not the installer. Then when you choose local you get the >>>>> message that local help is not installed. >>>>> >>>> >>>> >>>> Indeed and that is what we decided we want to remain happening (has >>>> always been so) >>>> >>> >>> Who decided? When? >>> >> >> >> We all discussed this recently in a recent email thread and the consensus >> was that the zip versions should not contain the local Manual >> Only the Windows EXE and the Mac DMG will contain the local Manual as >> part of the download. >> >> AFAIK this is the way it has always been. >> >> But I'd be open to persuasion to include the local Manual in the zip >> download too ... >> > > Sorry, I got confused and responded in the wrong place. I agree about > .zip versions for Windows. > > The thing that I say still needs fixing, is the few places where we still > use a # anchor to a local help page, which causes us to ignore local help > and go online. These are the Download buttons in Libraries preferences, as > discussed recently. > > What was done for Generators -- putting help for each on its own page -- > needs to be done too for this information about LAME and FFmpeg, and I have > done some of the work. > Ah yes I saw that. We may want to put a placeholder ednote in the original locations with the anchors to remind us of the duplications. Peter. > PRL > > > >> >> >> Peter. >> >> >> >>> Why not try to fix it now? I have been trying to fix it, and it >>> requires some editing in alphamanual.audacityteam.org. >>> >>> The FAQ page now makes the two relevant section headers clickable links, >>> which each lead to a short page that dupicates the section text. The >>> duplication online is strange, but it causes the procedure that downloads >>> and packages local help to do the right thing. >>> >>> (Technical question for James: >>> At least, that is because I assumed that links to the new pages are >>> needed so that the script finds them. But now that I have observed the >>> delay in availability of changes to the script, I wonder if I was wrong. >>> Does the script discover files by crawling links? Or does it enumerate all >>> available pages in the page, so that the new pages would be found even if >>> they were orphans?) >>> >>> PRL >>> >>> >>> >>>> >>>> >>>> >>>>> >>>>> (By the way. Is mystery shopper native in other languages? In the >>>>> coming release I want to give some attention to quality of translations.) >>>>> >>>> >>>> >>>> >>>> She certainly is, she's a German speaking Swiss whether she'd be up for >>>> recruitment, I really don't know ... >>>> >>>> She's more likely to be interested in testing - but I suppose she could >>>> test auf Deutsch >>>> >>>> Peter >>>> >>>> >>>> >>>> >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> 3.2) Press the Locate button in the FFmpeg section and then the >>>>>> Download in the resulting dialog. >>>>>> >>>>>> This too targets the online Manual rather than the local Manual >>>>>> (overriding the pref settinf gor local) >>>>>> >>>>>> >>>>>> 3.3) Press the Locate button in the LAME section and then the >>>>>> Download in the resulting dialog. >>>>>> >>>>>> This results in a failure to find the web-page (also going online >>>>>> ignoring the local Manual setting- but >>>>>> more importantly with a presumably incorrect web address). >>>>>> >>>>>> On my PC: http://www.webaddresshelp.bt.c >>>>>> om/main?ParticipantID=mg76cjr54t8kx45jjw4j4k9j5hsr5m26&Faile >>>>>> dURI=http%3A%2F%2Ffaq_installation_and_plug_ins.html%2F&Fail >>>>>> ureMode=1&Implementation=&AddInType=4&Version=pywr1.0&Client >>>>>> Location=uk >>>>>> >>>>>> and the following error message: >>>>>> >"Sorry, the website faq_installation_and_plug_ins.html cannot be >>>>>> found" >>>>>> >>>>>> This is certainly at least a P3 Bug (P2 borderline) >>>>>> There is the workaround to use the Download button the prefs pane. >>>>>> >>>>>> 3.1 and 3.2 are probably P3 bugs - but I'm open to persuasion re >>>>>> ignoring them >>>>>> as the user need internet access to effect the Downloads. >>>>>> >>>>>> >>>>>> 4) using her local Manual obtained from Help > Manual >>>>>> and going to the Windows installation page, following the >>>>>> instructions and the links, she successfully >>>>>> installed both LAME and FFmpeg and both were operational. >>>>>> >>>>> >>>>> Is this another example of non-correspondence, as with the generators? >>>>> PRL >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>> 5) Closing Audacity, trashing the config files and re-launching >>>>>> Audacity. >>>>>> In Preferences > Libraries the LAME and FFmpeg libraries were >>>>>> automatically found. >>>>>> >>>>>> This is in contrast to what happens on my very similar machine where >>>>>> they have to be manually >>>>>> located again. The only difference being that I did no install - >>>>>> rather I copied the LAME for Audacity >>>>>> and the FFmpeg for Audacity folders from the C:\Proram Files (x86) >>>>>> folder from my old PC to my >>>>>> new PC. >>>>>> >>>>>> Perhaps I should try trashing and those and re-installing properly? >>>>>> >>>>>> Peter >>>>>> >>>>>> >>>>> >>>> >>> >> > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-18 16:19:55
|
On Wed, Oct 18, 2017 at 5:13 PM, Paul Licameli <paul.licameli@...> wrote: > > > On Wed, Oct 18, 2017 at 6:18 AM, Peter Sampson < > petersampsonaudacity@...> wrote: > >> >> >> On Tue, Oct 17, 2017 at 10:00 PM, Paul Licameli <paul.licameli@...> >> wrote: >> >>> >>> >>> On Tue, Oct 17, 2017 at 12:09 PM, Peter Sampson < >>> petersampsonaudacity@...> wrote: >>> >>>> So we got my "mystery shopper" to install 2.2.0 RC1-2 on a clean >>>> machine. >>>> (Brand new - she so liked my recent purchase that she shelled out and >>>> bought the same) >>>> >>>> 1) Installation from the Fosshub link with the exe went fine >>>> >>>> 2) Audacity launched and ran OK >>>> >>>> >>>> 3) with the LAME and FFmpeg installations there are some issues >>>> >>>> 3.1) In Edit > Preferences > Interface both the Download buttons do >>>> not honor the >>>> (default) Preference setting for local Manual - but rather target the >>>> online Manual. >>>> This would cause a failure for a user with a local Manual but no >>>> internet link (but >>>> of course they could not proceed to the downloads in this case) >>>> >>> >>> Which help pages did you try to find? >>> >> >> >> These are not help buttons that go to help pages >> >> Rather it is the "Download" buttons in the >> a) Prefs>Libraries >> b) "Locate LAME" dialog >> c) "Locate FFmpeg" dialog >> >> >> Note that b and c have two access routes >> 1) via Prefs>Libraries >> 2) by trying to export to MP3 (LAME) or AAC (FFmpeg) >> >> >> It is the Download button in the "Locate LAME" dialog that is broken - >> its counterpart in the Prefs>Libraies works fine, >> >> So all you should need to do is to change the target in the Download >> button in the "Locate LAME" dialog to match >> that which we have for the LAME Download button in Prefs>Libraries. >> >> >> The problem that I realized today (actually my mystery shopper realized) >> is the the workaround I put in the bug report yesterday >> only works if you access via preferences - NOT if you access via a failed >> Export/Import >> >> >> >> >> The FFmpeg buttons work correctly in both Prefs>Libraries and in the >> "Locate FFmpeg" dialog >> >> >> >> >> >>> >>> I have tried it myself, and I observe that online help does not work >>> with generators but local does. I think Steve had to do something earlier >>> to fix local help for generators. This included commit >>> ccc802aa8bab391706e83a7e06f66b30619e5f24 but I think it also included >>> some online changes. I see local has separate .html pages for each >>> generator, but the online has sections within a page, so there is not a >>> correspondence of addresses as expected between the two. >>> >>> I tried the Amplify effect and it works ok either local or online. >>> >>> Maybe there are other examples. >>> >>> I remind you that you will not have local help if you got Audacity with >>> the .zip not the installer. Then when you choose local you get the message >>> that local help is not installed. >>> >> >> >> Indeed and that is what we decided we want to remain happening (has >> always been so) >> > > Who decided? When? > We all discussed this recently in a recent email thread and the consensus was that the zip versions should not contain the local Manual Only the Windows EXE and the Mac DMG will contain the local Manual as part of the download. AFAIK this is the way it has always been. But I'd be open to persuasion to include the local Manual in the zip download too ... Peter. > Why not try to fix it now? I have been trying to fix it, and it requires > some editing in alphamanual.audacityteam.org. > > The FAQ page now makes the two relevant section headers clickable links, > which each lead to a short page that dupicates the section text. The > duplication online is strange, but it causes the procedure that downloads > and packages local help to do the right thing. > > (Technical question for James: > At least, that is because I assumed that links to the new pages are needed > so that the script finds them. But now that I have observed the delay in > availability of changes to the script, I wonder if I was wrong. Does the > script discover files by crawling links? Or does it enumerate all > available pages in the page, so that the new pages would be found even if > they were orphans?) > > PRL > > > >> >> >> >>> >>> (By the way. Is mystery shopper native in other languages? In the >>> coming release I want to give some attention to quality of translations.) >>> >> >> >> >> She certainly is, she's a German speaking Swiss whether she'd be up for >> recruitment, I really don't know ... >> >> She's more likely to be interested in testing - but I suppose she could >> test auf Deutsch >> >> Peter >> >> >> >> >>> >>> >>> >>>> >>>> >>>> 3.2) Press the Locate button in the FFmpeg section and then the >>>> Download in the resulting dialog. >>>> >>>> This too targets the online Manual rather than the local Manual >>>> (overriding the pref settinf gor local) >>>> >>>> >>>> 3.3) Press the Locate button in the LAME section and then the Download >>>> in the resulting dialog. >>>> >>>> This results in a failure to find the web-page (also going online >>>> ignoring the local Manual setting- but >>>> more importantly with a presumably incorrect web address). >>>> >>>> On my PC: http://www.webaddresshelp.bt.com/main?ParticipantID=mg76cjr5 >>>> 4t8kx45jjw4j4k9j5hsr5m26&FailedURI=http%3A%2F%2Ffaq_installa >>>> tion_and_plug_ins.html%2F&FailureMode=1&Implementation=&AddI >>>> nType=4&Version=pywr1.0&ClientLocation=uk >>>> >>>> and the following error message: >>>> >"Sorry, the website faq_installation_and_plug_ins.html cannot be >>>> found" >>>> >>>> This is certainly at least a P3 Bug (P2 borderline) >>>> There is the workaround to use the Download button the prefs pane. >>>> >>>> 3.1 and 3.2 are probably P3 bugs - but I'm open to persuasion re >>>> ignoring them >>>> as the user need internet access to effect the Downloads. >>>> >>>> >>>> 4) using her local Manual obtained from Help > Manual >>>> and going to the Windows installation page, following the instructions >>>> and the links, she successfully >>>> installed both LAME and FFmpeg and both were operational. >>>> >>> >>> Is this another example of non-correspondence, as with the generators? >>> PRL >>> >>> >>> >>>> >>>> >>>> 5) Closing Audacity, trashing the config files and re-launching >>>> Audacity. >>>> In Preferences > Libraries the LAME and FFmpeg libraries were >>>> automatically found. >>>> >>>> This is in contrast to what happens on my very similar machine where >>>> they have to be manually >>>> located again. The only difference being that I did no install - >>>> rather I copied the LAME for Audacity >>>> and the FFmpeg for Audacity folders from the C:\Proram Files (x86) >>>> folder from my old PC to my >>>> new PC. >>>> >>>> Perhaps I should try trashing and those and re-installing properly? >>>> >>>> Peter >>>> >>>> >>> >> > |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-10-18 16:02:39
|
I have come across this code for certain built-in help texts:
if(Key==wxT("wma-proprietary"))
{
return WrapText(
wxString(wxT("<p>"))+
_("Audacity can import unprotected files in many other formats
(such as M4A and WMA, \
compressed WAV files from portable recorders and audio from video files) if
you download and install \
the optional [[
http://manual.audacityteam.org/man/faq_opening_and_saving_files.html#foreign|
\
FFmpeg library]] to your computer.").mention() + wxT("</p><p>") +
_("You can also read our help on importing \
[[
http://manual.audacityteam.org/man/faq_opening_and_saving_files.html#midi|MIDI
files]] \
and tracks from [[
http://manual.audacityteam.org/man/faq_opening_and_saving_files.html#fromcd|
\
audio CDs]].").mention() + wxT("</p>")
);
You can reach this only after an error importing a file (in
AudacityProject::Import), and then you press the ? button. I got there by
making a text file with just an X in it, and renaming that as damaged.flac,
and trying to import it.
More legibly there are three urls:
http://manual.audacityteam.org/man/faq_opening_and_saving_files.html#foreign
http://manual.audacityteam.org/man/faq_opening_and_saving_files.html#midi
http://manual.audacityteam.org/man/faq_opening_and_saving_files.html#fromcd
I find that I need to change the format of those links to make them work in
the alphamanual instead (use some capital letters and remove .html), but
even after that fix, only two out of three exit.
That is because the section about #midi now in manual mentions that midi
cannot be played, which is incorrect for alphamanual, but the section was
simply deleted, not updated.
Should the code change just to omit the link, or, shoulld alphamanual be
edited to put some mention of midi back on that FAQ page?
PRL
|
|
From: Cliff Scott <flyer185@gm...> - 2017-10-18 14:53:45
|
> On Oct 18, 2017, at 9:27 AM, Peter Sampson <petersampsonaudacity@...> wrote: > > I have been testing the following P2 bugs with RC1-1 and RC1-2 on my Macbook Pro High Sierra macOS 10.13 > > http://bugzilla.audacityteam.org/show_bug.cgi?id=1702 <http://bugzilla.audacityteam.org/show_bug.cgi?id=1702>; > Mac: Summary: LAME, FFmpeg and other dll loading woes. > > <x-msg://37/goog_1560932547>http://bugzilla.audacityteam.org/show_bug.cgi?id=1567 <http://bugzilla.audacityteam.org/show_bug.cgi?id=1567>; > Mac Sierra: LAME, FFmpeg and some plugins disappear. (intermittent) > > http://bugzilla.audacityteam.org/show_bug.cgi?id=290 <http://bugzilla.audacityteam.org/show_bug.cgi?id=290>; > Mac: LAME: Audacity looks for LAME in a restricted folder that Mac no longer supports > > > I tested on: > a) my privileged administrator account (trashing the config files) > b) my standard non-privileged test user account (trashing the config files) > c) my totally unprivileged Guest account (config files auto-deleted on last log-off from this account) > > In all 3 use cases I do not encounter the problems listed in these bugs: > 1) LAME library is found properly - and works > 2) FFmpeg library is found properly - and works > 3) No effects are missing > > > I know from off list email that Cliff does not experience these issues on his Mac. > I'm assuming, as he has not mentioned this, that Bill does not see this either. Can you confirm Bill? > > > I shall wait until we get the RC out in the wild for a few days - and if there are no reports relating to these bugs > I shall be closing them as RESOLVED. > > Peter +1 Cliff |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-18 14:27:42
|
I have been testing the following P2 bugs with RC1-1 and RC1-2 on my Macbook Pro High Sierra macOS 10.13 http://bugzilla.audacityteam.org/show_bug.cgi?id=1702 Mac: Summary: LAME, FFmpeg and other dll loading woes. <goog_1560932547> http://bugzilla.audacityteam.org/show_bug.cgi?id=1567 Mac Sierra: LAME, FFmpeg and some plugins disappear. (intermittent) http://bugzilla.audacityteam.org/show_bug.cgi?id=290 Mac: LAME: Audacity looks for LAME in a restricted folder that Mac no longer supports I tested on: a) my privileged administrator account (trashing the config files) b) my standard non-privileged test user account (trashing the config files) c) my totally unprivileged Guest account (config files auto-deleted on last log-off from this account) In all 3 use cases I do not encounter the problems listed in these bugs: 1) LAME library is found properly - and works 2) FFmpeg library is found properly - and works 3) No effects are missing I know from off list email that Cliff does not experience these issues on his Mac. I'm assuming, as he has not mentioned this, that Bill does not see this either. Can you confirm Bill? I shall wait until we get the RC out in the wild for a few days - and if there are no reports relating to these bugs I shall be closing them as RESOLVED. Peter |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-18 10:18:40
|
On Tue, Oct 17, 2017 at 10:00 PM, Paul Licameli <paul.licameli@...> wrote: > > > On Tue, Oct 17, 2017 at 12:09 PM, Peter Sampson < > petersampsonaudacity@...> wrote: > >> So we got my "mystery shopper" to install 2.2.0 RC1-2 on a clean machine. >> (Brand new - she so liked my recent purchase that she shelled out and >> bought the same) >> >> 1) Installation from the Fosshub link with the exe went fine >> >> 2) Audacity launched and ran OK >> >> >> 3) with the LAME and FFmpeg installations there are some issues >> >> 3.1) In Edit > Preferences > Interface both the Download buttons do >> not honor the >> (default) Preference setting for local Manual - but rather target the >> online Manual. >> This would cause a failure for a user with a local Manual but no internet >> link (but >> of course they could not proceed to the downloads in this case) >> > > Which help pages did you try to find? > These are not help buttons that go to help pages Rather it is the "Download" buttons in the a) Prefs>Libraries b) "Locate LAME" dialog c) "Locate FFmpeg" dialog Note that b and c have two access routes 1) via Prefs>Libraries 2) by trying to export to MP3 (LAME) or AAC (FFmpeg) It is the Download button in the "Locate LAME" dialog that is broken - its counterpart in the Prefs>Libraies works fine, So all you should need to do is to change the target in the Download button in the "Locate LAME" dialog to match that which we have for the LAME Download button in Prefs>Libraries. The problem that I realized today (actually my mystery shopper realized) is the the workaround I put in the bug report yesterday only works if you access via preferences - NOT if you access via a failed Export/Import The FFmpeg buttons work correctly in both Prefs>Libraries and in the "Locate FFmpeg" dialog > > I have tried it myself, and I observe that online help does not work with > generators but local does. I think Steve had to do something earlier to > fix local help for generators. This included commit > ccc802aa8bab391706e83a7e06f66b30619e5f24 but I think it also included > some online changes. I see local has separate .html pages for each > generator, but the online has sections within a page, so there is not a > correspondence of addresses as expected between the two. > > I tried the Amplify effect and it works ok either local or online. > > Maybe there are other examples. > > I remind you that you will not have local help if you got Audacity with > the .zip not the installer. Then when you choose local you get the message > that local help is not installed. > Indeed and that is what we decided we want to remain happening (has always been so) > > (By the way. Is mystery shopper native in other languages? In the coming > release I want to give some attention to quality of translations.) > She certainly is, she's a German speaking Swiss whether she'd be up for recruitment, I really don't know ... She's more likely to be interested in testing - but I suppose she could test auf Deutsch Peter > > > >> >> >> 3.2) Press the Locate button in the FFmpeg section and then the Download >> in the resulting dialog. >> >> This too targets the online Manual rather than the local Manual >> (overriding the pref settinf gor local) >> >> >> 3.3) Press the Locate button in the LAME section and then the Download in >> the resulting dialog. >> >> This results in a failure to find the web-page (also going online >> ignoring the local Manual setting- but >> more importantly with a presumably incorrect web address). >> >> On my PC: http://www.webaddresshelp.bt.com/main?ParticipantID=mg76cjr5 >> 4t8kx45jjw4j4k9j5hsr5m26&FailedURI=http%3A%2F%2Ffaq_ins >> tallation_and_plug_ins.html%2F&FailureMode=1&Implementatio >> n=&AddInType=4&Version=pywr1.0&ClientLocation=uk >> >> and the following error message: >> >"Sorry, the website faq_installation_and_plug_ins.html cannot be found" >> >> This is certainly at least a P3 Bug (P2 borderline) >> There is the workaround to use the Download button the prefs pane. >> >> 3.1 and 3.2 are probably P3 bugs - but I'm open to persuasion re ignoring >> them >> as the user need internet access to effect the Downloads. >> >> >> 4) using her local Manual obtained from Help > Manual >> and going to the Windows installation page, following the instructions >> and the links, she successfully >> installed both LAME and FFmpeg and both were operational. >> > > Is this another example of non-correspondence, as with the generators? > PRL > > > >> >> >> 5) Closing Audacity, trashing the config files and re-launching Audacity. >> In Preferences > Libraries the LAME and FFmpeg libraries were >> automatically found. >> >> This is in contrast to what happens on my very similar machine where they >> have to be manually >> located again. The only difference being that I did no install - rather >> I copied the LAME for Audacity >> and the FFmpeg for Audacity folders from the C:\Proram Files (x86) folder >> from my old PC to my >> new PC. >> >> Perhaps I should try trashing and those and re-installing properly? >> >> Peter >> >> > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-18 08:47:54
|
On Tue, Oct 17, 2017 at 9:27 PM, Paul Licameli <paul.licameli@...> wrote: > > > On Tue, Oct 17, 2017 at 10:04 AM, Peter Sampson < > petersampsonaudacity@...> wrote: > >> I've just been testing the second build of RC1 on W10 and macOS 10.13 >> High Sierra. >> >> First the good news: >> >> 1) On both platforms while recording the Status Bar message for >> remaining disk space has been restored and works >> >> 2) Even better, it is persistent now and doesn't disappear and reappear >> as it used to. >> >> 3) Also even better it now overrides other potential Status bar >> messages, for example if you hover the cursor over the action buttons in >> the TCP >> >> >> Now the not so good news: >> >> 4) With disk/volume overrun while recording on Mac we get the nice >> helpful updated message: >> >> "Audacity failed to write to a file. >> Perhaps <volume and a bit of pathing> is not >> writable or the disk is full." >> >> 5) But with W10 we still get the old unenhanced, unhelpful, message: >> >> "Audacity failed to write to a file in <volume>" :-(( >> >> >> next I'll be testing the overrun cleanup fixes that Paul made recently. >> >> Peter >> > > Try it again with no audacity.cfg. > > It works for me when all defaults. > Ah, so now it works for me with the fuller more helpful message. But the odd thing about this is that this is how my prefs should have been set when I was testing this yesterday :-// When I test I always trash the config files to get defaults (unless I'm testing non-defaults deliberately) Plus I never reset the language (unless and until I'm testing suchlike for bug-testing purposes). But it works now with default settings - so hey ho ... > > It does not work if "English" is chosen. Rather it must be "System". > Confirmed Peter. > > PRL > > > > |
|
From: Peter Sampson <petersampsonaudacity@gm...> - 2017-10-18 08:19:27
|
A minor issue but Connie would like "greying" to be spelt "graying" for the US English that she prefers: "Non-Greying out of effects when no selection (and explanatory dialog with help button)" Peter. On Wed, Oct 18, 2017 at 2:53 AM, Bill Wharrie <billwh@...> wrote: > > On 2017/10/17, at 9:01 PM, Paul Licameli <paul.licameli@...> wrote: > > Thank you, Bill. > > I am not sure I know what this refers to: "Overhaul of clip handling code > using newer (safer) idioms" > > Maybe you mean the rewrite iterations over tracks that I have mentioned? > But that is a project I haven't submitted yet! > > You mention me (only) by name here -- that makes me feel a bit immodest. > I'll remove that if you don't mind. > > > That was copied from http://wiki.audacityteam.org/wiki/Release_Notes_2.2.0 > which was written by James. So I’ll update that page. > > — Bill > > > PRL > > > On Tue, Oct 17, 2017 at 7:56 PM, Bill Wharrie <billwh@...> wrote: > >> Here’s an updated README with the feedback@ address removed in favour of >> sending people to http://audacityteam.org/contact/#feedback >> >> as well as removing the time track stuff. >> >> — Bill >> >> >> >> >> On 2017/10/17, at 6:43 PM, Bill Wharrie <billwh@...> wrote: >> >> >> On 2017/10/17, at 6:33 PM, Paul Licameli <paul.licameli@...> wrote: >> >> Where do I find the up-to-date version of README.txt? >> >> >> Here’s the one I did up a month or so ago. I’ve removed the time track >> stuff. Peter has seen this before and may have made some changes. >> >> — Bill >> >> >> <README 220.txt> >> >> PRL >> >> >> >> On Tue, Oct 17, 2017 at 6:30 PM, Bill Wharrie <billwh@...> wrote: >> >>> And we probably want to remove the reference to “Time Track >>> cut/copy/paste” from the README. >>> — Bill >>> >>> > On 2017/10/17, at 6:27 PM, Bill Wharrie <billwh@...> wrote: >>> > >>> > The title says it all. >>> > >>> > (Not that it matters much with the README buried in the bundle) >>> > >>> > — Bill >>> > ------------------------------------------------------------ >>> ------------------ >>> > Check out the vibrant tech community on one of the world's most >>> > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sd >>> m.link/slashdot >>> > _______________________________________________ >>> > Audacity-quality mailing list >>> > Audacity-quality@... >>> > https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sd >>> m.link/slashdot >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality >>> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sd >> m.link/slashdot_______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sd >> m.link/slashdot_______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org>;! >> http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://slashdot.org>;! > http://sdm.link/slashdot_______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: David Bailes <drbailes@gm...> - 2017-10-18 07:50:21
|
On 17 October 2017 at 14:47, David Bailes <drbailes@...> wrote: > This was tested using yesterdays rc1. > Just using a single audio track. > 1) If a time range is selected, but the track isn't selected: > a) Pressing Delete results in a "Disallowed" dialog, saying there was > a problem with the last action, if you think it's a bug....... > b) Pressing Ctrl+K, or choosing Delete from the Edit menu, deselects > the time range, and places the cursor at the start of the former time range. > > 2) If a time range isn't selected, and the track is either selected or not: > a) Pressing Delete results in a "No audio selected" dialog. Fine. > b) Pressing Ctrl+K or choosing Delete from the Edit menu, does > nothing, even though the menu item is enabled. > > Only 2b is user friendly. > should, or course, have been: Only 2a is user friendly. David. > > David. > > > |
|
From: David Bailes <drbailes@gm...> - 2017-10-18 07:33:31
|
On 17 October 2017 at 11:21, Paul Licameli <paul.licameli@...> wrote: > The point of the crash means you were stopping, not starting. > > mOwningProject is used when you stop, but it is set when you start, from > ::GetActiveProject() which returns a global variable, and I think that was > unexpectedly null. > > I suspect you had more than one project open, and you closed one of them > before starting playback in the other, but also with changes of active > application that may be hard to reproduce. I suspect some keystroke event > to start play was processed before the window activation event. (Which > operating system? > Window 10. > Perhaps the bug is possible only on some systems.) > > I have disliked the use of the global ::GetActiveProject for a while, and > this increases my dislike. > > I wrote a simple null check at 969427980492f5079e197bfc3de3551806ee4940. > I will not try to reproduce the problem for myself, suspecting this to be > difficult. > > I don't think this is a new bug in the version, just a difficult one to > trigger that nobody noticed for a long time. > Probably the case, David. > > PRL > > > On Tue, Oct 17, 2017 at 5:10 AM, David Bailes <drbailes@...> wrote: > >> Using latest commit: b49e467412337be1d2aa0a3b45ba830b04a625b7 >> >> I was running Audacity with the debugger, pressed space to stop (possibly >> could have been start), and got a crash. Call stack below. >> >> In AudioIO::StopStream Line 2760 >> MixerBoard* pMixerBoard = mOwningProject->GetMixerBoard(); >> mOwningProject was NULL. >> >> I haven't been able to quickly repeat the problem. There was just a >> single track, and I was changing focus between Audacity and Visual Studio >> frequently at the time. Maybe someone familiar this code may have an idea >> why mOwningProject might be NULL. >> >> David. >> >> Audacity.exe!AudacityProject::GetMixerBoard() Line 496 C++ >> > Audacity.exe!AudioIO::StopStream() Line 2760 C++ >> Audacity.exe!ControlToolBar::StopPlaying(bool stopStream) Line 850 C++ >> Audacity.exe!AudacityProject::OnPlayStop() Line 2651 C++ >> Audacity.exe!VoidFunctor<AudacityProject>::operator()(int __formal, >> const wxEvent * __formal) Line 43 C++ >> Audacity.exe!CommandManager::HandleCommandEntry(const CommandListEntry >> * entry, CommandFlag flags, CommandFlag mask, const wxEvent * evt) Line 1473 >> C++ >> Audacity.exe!CommandManager::FilterKeyEvent(AudacityProject * project, >> const wxKeyEvent & evt, bool permit) Line 1430 C++ >> Audacity.exe!CommandManagerEventMonitor::FilterEvent::__l18::<lambda>() >> Line 235 C++ >> Audacity.exe!GuardedCall<int,wxEventFilter::<unnamed-enum-Event_Skip> >> <lambda>(void),SimpleGuard<enum wxEventFilter::<unnamed-enum-Event_Skip> >> >,DefaultDelayedHandlerAction>(const CommandManagerEventMonitor::Fi >> lterEvent::__l18::wxEventFilter::<unnamed-enum-Event_Skip> >> <lambda>(void) & body, const SimpleGuard<enum wxEventFilter::<unnamed-enum-Event_Skip> >> > & handler, const DefaultDelayedHandlerAction & delayedHandler) Line 188 >> C++ >> Audacity.exe!CommandManagerEventMonitor::FilterEvent(wxEvent & event) >> Line 200 C++ >> wxbase30ud_vc_custom.dll!wxEvtHandler::ProcessEvent(wxEvent & event) >> Line 1475 C++ >> wxmsw30ud_core_vc_custom.dll!wxKeyboardHook(int nCode, unsigned short >> wParam, unsigned long lParam) Line 6737 C++ >> [External Code] >> [Frames below may be incorrect and/or missing, no symbols loaded for >> user32.dll] >> wxbase30ud_vc_custom.dll!wxEventLoopManual::ProcessEvents() Line 172 >> C++ >> wxbase30ud_vc_custom.dll!wxEventLoopManual::DoRun() Line 206 C++ >> wxbase30ud_vc_custom.dll!wxEventLoopBase::Run() Line 78 C++ >> wxbase30ud_vc_custom.dll!wxAppConsoleBase::MainLoop() Line 334 C++ >> wxbase30ud_vc_custom.dll!wxAppConsoleBase::OnRun() Line 259 C++ >> wxmsw30ud_core_vc_custom.dll!wxAppBase::OnRun() Line 304 C++ >> wxbase30ud_vc_custom.dll!wxEntryReal(int & argc, wchar_t * * argv) >> Line 495 C++ >> wxbase30ud_vc_custom.dll!wxEntry(int & argc, wchar_t * * argv) Line 188 >> C++ >> wxmsw30ud_core_vc_custom.dll!wxEntry(HINSTANCE__ * hInstance, >> HINSTANCE__ * __formal, char * __formal, int nCmdShow) Line 430 C++ >> Audacity.exe!WinMain(HINSTANCE__ * hInstance, HINSTANCE__ * >> hPrevInstance, char * __formal, int nCmdShow) Line 685 C++ >> [External Code] >> >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: Bill Wharrie <billwh@go...> - 2017-10-18 01:53:42
|
> On 2017/10/17, at 9:01 PM, Paul Licameli <paul.licameli@...> wrote: > > Thank you, Bill. > > I am not sure I know what this refers to: "Overhaul of clip handling code using newer (safer) idioms" > > Maybe you mean the rewrite iterations over tracks that I have mentioned? But that is a project I haven't submitted yet! > > You mention me (only) by name here -- that makes me feel a bit immodest. I'll remove that if you don't mind. That was copied from http://wiki.audacityteam.org/wiki/Release_Notes_2.2.0 which was written by James. So I’ll update that page. — Bill > > PRL > > > On Tue, Oct 17, 2017 at 7:56 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: > Here’s an updated README with the feedback@ address removed in favour of sending people to http://audacityteam.org/contact/#feedback <http://audacityteam.org/contact/#feedback>; > > as well as removing the time track stuff. > > — Bill > > > > >> On 2017/10/17, at 6:43 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: >> >>> >>> On 2017/10/17, at 6:33 PM, Paul Licameli <paul.licameli@... <mailto:paul.licameli@...>> wrote: >>> >>> Where do I find the up-to-date version of README.txt? >> >> Here’s the one I did up a month or so ago. I’ve removed the time track stuff. Peter has seen this before and may have made some changes. >> >> — Bill >> >>> >> <README 220.txt> >>> PRL >>> >> >>> >>> On Tue, Oct 17, 2017 at 6:30 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: >>> And we probably want to remove the reference to “Time Track cut/copy/paste” from the README. >>> — Bill >>> >>> > On 2017/10/17, at 6:27 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: >>> > >>> > The title says it all. >>> > >>> > (Not that it matters much with the README buried in the bundle) >>> > >>> > — Bill >>> > ------------------------------------------------------------------------------ >>> > Check out the vibrant tech community on one of the world's most >>> > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot <http://sdm.link/slashdot>; >>> > _______________________________________________ >>> > Audacity-quality mailing list >>> > Audacity-quality@... <mailto:Audacity-quality@...> >>> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >>> >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot <http://sdm.link/slashdot>; >>> _______________________________________________ >>> Audacity-quality mailing list >>> Audacity-quality@... <mailto:Audacity-quality@...> >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________>; >>> Audacity-quality mailing list >>> Audacity-quality@... <mailto:Audacity-quality@...> >>> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________>; >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-10-18 01:01:12
|
Thank you, Bill. I am not sure I know what this refers to: "Overhaul of clip handling code using newer (safer) idioms" Maybe you mean the rewrite iterations over tracks that I have mentioned? But that is a project I haven't submitted yet! You mention me (only) by name here -- that makes me feel a bit immodest. I'll remove that if you don't mind. PRL On Tue, Oct 17, 2017 at 7:56 PM, Bill Wharrie <billwh@...> wrote: > Here’s an updated README with the feedback@ address removed in favour of > sending people to http://audacityteam.org/contact/#feedback > > as well as removing the time track stuff. > > — Bill > > > > > On 2017/10/17, at 6:43 PM, Bill Wharrie <billwh@...> wrote: > > > On 2017/10/17, at 6:33 PM, Paul Licameli <paul.licameli@...> wrote: > > Where do I find the up-to-date version of README.txt? > > > Here’s the one I did up a month or so ago. I’ve removed the time track > stuff. Peter has seen this before and may have made some changes. > > — Bill > > > <README 220.txt> > > PRL > > > > On Tue, Oct 17, 2017 at 6:30 PM, Bill Wharrie <billwh@...> wrote: > >> And we probably want to remove the reference to “Time Track >> cut/copy/paste” from the README. >> — Bill >> >> > On 2017/10/17, at 6:27 PM, Bill Wharrie <billwh@...> wrote: >> > >> > The title says it all. >> > >> > (Not that it matters much with the README buried in the bundle) >> > >> > — Bill >> > ------------------------------------------------------------ >> ------------------ >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http:// >> sdm.link/slashdot >> > _______________________________________________ >> > Audacity-quality mailing list >> > Audacity-quality@... >> > https://lists.sourceforge.net/lists/listinfo/audacity-quality >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http:// >> sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http:// > sdm.link/slashdot_______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http:// > sdm.link/slashdot_______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: Bill Wharrie <billwh@go...> - 2017-10-17 23:56:28
|
Here’s an updated README with the feedback@ address removed in favour of sending people to http://audacityteam.org/contact/#feedback as well as removing the time track stuff. — Bill > On 2017/10/17, at 6:43 PM, Bill Wharrie <billwh@...> wrote: > >> >> On 2017/10/17, at 6:33 PM, Paul Licameli <paul.licameli@... <mailto:paul.licameli@...>> wrote: >> >> Where do I find the up-to-date version of README.txt? > > Here’s the one I did up a month or so ago. I’ve removed the time track stuff. Peter has seen this before and may have made some changes. > > — Bill > >> > <README 220.txt> >> PRL >> > >> >> On Tue, Oct 17, 2017 at 6:30 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: >> And we probably want to remove the reference to “Time Track cut/copy/paste” from the README. >> — Bill >> >> > On 2017/10/17, at 6:27 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: >> > >> > The title says it all. >> > >> > (Not that it matters much with the README buried in the bundle) >> > >> > — Bill >> > ------------------------------------------------------------------------------ >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot <http://sdm.link/slashdot>; >> > _______________________________________________ >> > Audacity-quality mailing list >> > Audacity-quality@... <mailto:Audacity-quality@...> >> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot <http://sdm.link/slashdot>; >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________>; >> Audacity-quality mailing list >> Audacity-quality@... <mailto:Audacity-quality@...> >> https://lists.sourceforge.net/lists/listinfo/audacity-quality > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________>; > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; |
|
From: Bill Wharrie <billwh@go...> - 2017-10-17 22:43:09
|
> On 2017/10/17, at 6:33 PM, Paul Licameli <paul.licameli@...> wrote: > > Where do I find the up-to-date version of README.txt? Here’s the one I did up a month or so ago. I’ve removed the time track stuff. Peter has seen this before and may have made some changes. — Bill > > > PRL > > > On Tue, Oct 17, 2017 at 6:30 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: > And we probably want to remove the reference to “Time Track cut/copy/paste” from the README. > — Bill > > > On 2017/10/17, at 6:27 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: > > > > The title says it all. > > > > (Not that it matters much with the README buried in the bundle) > > > > — Bill > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot>; > > _______________________________________________ > > Audacity-quality mailing list > > Audacity-quality@... <mailto:Audacity-quality@...> > > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-10-17 22:34:08
|
Where do I find the up-to-date version of README.txt? PRL On Tue, Oct 17, 2017 at 6:30 PM, Bill Wharrie <billwh@...> wrote: > And we probably want to remove the reference to “Time Track > cut/copy/paste” from the README. > — Bill > > > On 2017/10/17, at 6:27 PM, Bill Wharrie <billwh@...> wrote: > > > > The title says it all. > > > > (Not that it matters much with the README buried in the bundle) > > > > — Bill > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Audacity-quality mailing list > > Audacity-quality@... > > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
|
From: Paul Licameli <paul.licameli@gm...> - 2017-10-17 22:31:02
|
On Tue, Oct 17, 2017 at 6:14 PM, Bill Wharrie <billwh@...> wrote: > > On 2017/10/17, at 6:07 PM, Peter Sampson <petersampsonaudacity@...> > wrote: > > > > On Tue, Oct 17, 2017 at 11:02 PM, Bill Wharrie <billwh@...> wrote: > >> This is listed in the Release Notes as an Improvement in 2.2.0. >> >> IMO the implementation leaves something to be desired. I’m not suggesting >> we do another RC cycle for this, but perhaps we could remove it from the >> release notes and fix it up for the next release? I can’t imagine this is a >> high priority for many users. This feature is not documented in the manual: >> > > > We should remove it then from the New Features page if we will be making > another download of the Manual before release. > > > I had forgotten it was in the manual as well. > > Paul: are you OK with downloading the manual again for the release? > > — Bill > Sigh. Yet another false start for RC1. Sure, I will package the local manuals again, it's just routine. As for the new feature announcement -- I added this capability, but I don't mind not putting it in New Features. As I have said, it was only incidental to other more important work. Please file some bug reports if not already done, to improve its behavior. PRL > > That's where I encountered it - and it confused me no end ... > > Peter > > > > >> >> https://alphamanual.audacityteam.org/man/Time_Tracks >> >> Steps to reproduce: >> 1 new project >> 2 generate or import audio >> 3 Tracks > Add New > Time Track >> 4 make some radical adjustments at the start of the Time Track (just so >> they’re easy to see) >> 5 drag a selection in the Time Track only (at or near the start so it >> includes the adjustments made in 4 - again, just so it’s easy to see what >> happens) >> 6 Copy — error message ("select the audio for Copy to use") >> 7 drag a similar selection in the Audio Track and extend it into the Time >> Track and Copy — apparent success >> 8 click outside the tracks or otherwise make sure no tracks are selected >> and set editing cursor to time zero (Skip to Start) >> 9 Paste >> a) A new audio track is created and the copied audio is pasted into it >> b) An envelope (corresponding to the selection range copied in step 6) is >> pasted into the start of the Time Track, pushing the existing Time Track >> envelope to the right. >> >> So you can’t really cut/copy/paste in a time track the way you can in a >> Label Track. >> >> — Bill >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>;! http:// >> sdm.link/slashdot >> _______________________________________________ >> Audacity-quality mailing list >> Audacity-quality@... >> https://lists.sourceforge.net/lists/listinfo/audacity-quality >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http:// > sdm.link/slashdot_______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > > |
|
From: Bill Wharrie <billwh@go...> - 2017-10-17 22:30:19
|
And we probably want to remove the reference to “Time Track cut/copy/paste” from the README. — Bill > On 2017/10/17, at 6:27 PM, Bill Wharrie <billwh@...> wrote: > > The title says it all. > > (Not that it matters much with the README buried in the bundle) > > — Bill > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |
|
From: Bill Wharrie <billwh@go...> - 2017-10-17 22:27:42
|
The title says it all. (Not that it matters much with the README buried in the bundle) — Bill |
|
From: Bill Wharrie <billwh@go...> - 2017-10-17 22:14:20
|
> On 2017/10/17, at 6:07 PM, Peter Sampson <petersampsonaudacity@...> wrote: > > > > On Tue, Oct 17, 2017 at 11:02 PM, Bill Wharrie <billwh@... <mailto:billwh@...>> wrote: > This is listed in the Release Notes as an Improvement in 2.2.0. > > IMO the implementation leaves something to be desired. I’m not suggesting we do another RC cycle for this, but perhaps we could remove it from the release notes and fix it up for the next release? I can’t imagine this is a high priority for many users. This feature is not documented in the manual: > > > We should remove it then from the New Features page if we will be making another download of the Manual before release. I had forgotten it was in the manual as well. Paul: are you OK with downloading the manual again for the release? — Bill > > That's where I encountered it - and it confused me no end ... > > Peter > > > > > https://alphamanual.audacityteam.org/man/Time_Tracks <https://alphamanual.audacityteam.org/man/Time_Tracks>; > > Steps to reproduce: > 1 new project > 2 generate or import audio > 3 Tracks > Add New > Time Track > 4 make some radical adjustments at the start of the Time Track (just so they’re easy to see) > 5 drag a selection in the Time Track only (at or near the start so it includes the adjustments made in 4 - again, just so it’s easy to see what happens) > 6 Copy — error message ("select the audio for Copy to use") > 7 drag a similar selection in the Audio Track and extend it into the Time Track and Copy — apparent success > 8 click outside the tracks or otherwise make sure no tracks are selected and set editing cursor to time zero (Skip to Start) > 9 Paste > a) A new audio track is created and the copied audio is pasted into it > b) An envelope (corresponding to the selection range copied in step 6) is pasted into the start of the Time Track, pushing the existing Time Track envelope to the right. > > So you can’t really cut/copy/paste in a time track the way you can in a Label Track. > > — Bill > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot <http://sdm.link/slashdot>; > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org <http://slashdot.org/>;! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________>; > Audacity-quality mailing list > Audacity-quality@... <mailto:Audacity-quality@...> > https://lists.sourceforge.net/lists/listinfo/audacity-quality <https://lists.sourceforge.net/lists/listinfo/audacity-quality>; |
|
From: Steve the Fiddle <stevethefiddle@gm...> - 2017-10-17 22:13:24
|
On 17 October 2017 at 23:02, Bill Wharrie <billwh@...> wrote: > This is listed in the Release Notes as an Improvement in 2.2.0. > > IMO the implementation leaves something to be desired. I’m not suggesting > we do another RC cycle for this, but perhaps we could remove it from the > release notes and fix it up for the next release? +1 for not listing it as an improvement in the release notes. As it stands it is not something we want to brag about. Steve > I can’t imagine this is a high priority for many users. This feature is > not documented in the manual: > > https://alphamanual.audacityteam.org/man/Time_Tracks > > Steps to reproduce: > 1 new project > 2 generate or import audio > 3 Tracks > Add New > Time Track > 4 make some radical adjustments at the start of the Time Track (just so > they’re easy to see) > 5 drag a selection in the Time Track only (at or near the start so it > includes the adjustments made in 4 - again, just so it’s easy to see what > happens) > 6 Copy — error message ("select the audio for Copy to use") > 7 drag a similar selection in the Audio Track and extend it into the Time > Track and Copy — apparent success > 8 click outside the tracks or otherwise make sure no tracks are selected > and set editing cursor to time zero (Skip to Start) > 9 Paste > a) A new audio track is created and the copied audio is pasted into it > b) An envelope (corresponding to the selection range copied in step 6) is > pasted into the start of the Time Track, pushing the existing Time Track > envelope to the right. > > So you can’t really cut/copy/paste in a time track the way you can in a > Label Track. > > — Bill > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Audacity-quality mailing list > Audacity-quality@... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
897 messages has been excluded from this view by a project administrator.