Thread: [Audacity-quality] Generators corrupt project?
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Bill W. <bi...@go...> - 2010-02-10 05:14:07
|
Steps to reproduce: 1) New project, generate tone 10 seconds 2) Click at 5 arbitrary points and Edit > Split at each one - you now have six clips 3) Save the project <- this appears to be important! 4) Starting with the first clip, double-click in each clip in turn and Generate > DTMF Tones accepting the defaults. At some point whitespace will be created following the affected clip. A "faint split line" may appear. Spurious clips may be created. The length of the track may be increased. Any of these generators - Chirp, DTMF, Noise, Silence, Tone - will cause the error. 5) Save the project and open the .aup file in a text editor. There may be overlapping and/or duplicated waveclips. This may not always generate the error. Start with a clean project and try again. I can get it to happen every time. I'm not absolutely certain that saving the project (step 3) is necessary, or if waiting for the auto-save interval is good enough. All I can say at this point is that I set one of these up and it would not fail, and after I saved the project it did fail. In another case setting it up, then coming back to the email for a while, then going back to it, it would fail even though it had not been saved. If you cannot reproduce this, I have a project that is "ready to fail". Contact me off list for a zip file (720K) or a 7zip file (312K). I'm on a Mac G5 (PPC) system 10.5.8, Audacity 1.3.12-alpha-Feb 8 2010. Could this be related to: P2 R (Windows) Projects crash when applying repeated effects on zoomed in regions towards the end of audio tracks (wiki) which is now at: http://bugzilla.audacityteam.org/show_bug.cgi?id=9 That bug report references this thread: http://n2.nabble.com/Various-P2s-and-P3s-a-repeatable-case-td4040974.html which talks about "faint clip lines" and "P2 Boundary drawing problem with Generate and SoundTouch " From what I've been able to determine it looks like a "faint clip line" is a sign of overlapping clips and a corrupt .aup file? -- Bill |
From: David B. <drb...@go...> - 2010-02-10 17:45:12
|
On Wed, Feb 10, 2010 at 5:13 AM, Bill Wharrie <bi...@go...> wrote: > Steps to reproduce: > > 1) New project, generate tone 10 seconds > 2) Click at 5 arbitrary points and Edit > Split at each one - you now > have six clips > 3) Save the project <- this appears to be important! > 4) Starting with the first clip, double-click in each clip in turn and > Generate > DTMF Tones accepting the defaults. If you generate a tone of say 20 samples rather than 10 seconds, then I think it's easier to see when things go wrong (and they do). I didn't bother to save the project, and there were still problems, David. (Audacity 1.3.11 windows 7) |
From: Al D. <bus...@gm...> - 2010-02-10 19:00:59
|
On Wednesday 10 February 2010 10:44:36 David Bailes wrote: > On Wed, Feb 10, 2010 at 5:13 AM, Bill Wharrie <bi...@go...> wrote: > > Steps to reproduce: > > > > 1) New project, generate tone 10 seconds > > 2) Click at 5 arbitrary points and Edit > Split at each one - you > > now have six clips > > 3) Save the project <- this appears to be important! > > 4) Starting with the first clip, double-click in each clip in > > turn and Generate > DTMF Tones accepting the defaults. > > If you generate a tone of say 20 samples rather than 10 seconds, > then I think it's easier to see when things go wrong (and they > do). I didn't bother to save the project, and there were still > problems, > Thanks for the report. I definitely saw something go wrong when zoomed in, and it was caused by inconsistent comparison of selection boundaries to clip endpoints. Fix checked in for that. I'll also check Bill's project and see if there's anything else going wrong. - Al > David. > (Audacity 1.3.11 windows 7) > > ------------------------------------------------------------------- > ----------- SOLARIS 10 is the OS for Data Centers - provides > features such as DTrace, Predictive Self Healing and Award Winning > ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
From: David B. <drb...@go...> - 2010-02-10 17:46:38
|
On Wed, Feb 10, 2010 at 5:13 AM, Bill Wharrie <bi...@go...> wrote: > Steps to reproduce: > > 1) New project, generate tone 10 seconds > 2) Click at 5 arbitrary points and Edit > Split at each one - you now > have six clips > 3) Save the project <- this appears to be important! > 4) Starting with the first clip, double-click in each clip in turn and > Generate > DTMF Tones accepting the defaults. If you generate a tone of say 20 samples rather than 10 seconds, then I think it's easier to see when things go wrong (and they do). I didn't bother to save the project, and there were still problems, David. (Audacity 1.3.11 windows 7) |
From: Al D. <bus...@gm...> - 2010-02-10 19:01:37
|
On Tuesday 09 February 2010 22:13:56 Bill Wharrie wrote: > Steps to reproduce: > > 1) New project, generate tone 10 seconds > 2) Click at 5 arbitrary points and Edit > Split at each one - you > now have six clips > 3) Save the project <- this appears to be important! > 4) Starting with the first clip, double-click in each clip in turn > and Generate > DTMF Tones accepting the defaults. > > At some point whitespace will be created following the affected > clip. A "faint split line" may appear. Spurious clips may be > created. The length of the track may be increased. > > Any of these generators - Chirp, DTMF, Noise, Silence, Tone - will > cause the error. > > 5) Save the project and open the .aup file in a text editor. There > may be overlapping and/or duplicated waveclips. > > This may not always generate the error. Start with a clean project > and try again. I can get it to happen every time. I'm not > absolutely certain that saving the project (step 3) is necessary, > or if waiting for the auto-save interval is good enough. All I can > say at this point is that I set one of these up and it would not > fail, and after I saved the project it did fail. In another case > setting it up, then coming back to the email for a while, then > going back to it, it would fail even though it had not been saved. > > If you cannot reproduce this, I have a project that is "ready to > fail". Contact me off list for a zip file (720K) or a 7zip file > (312K). > Could you send me that project? I got something to reproduce but I want to see if you have something different. Thanks. - Al > I'm on a Mac G5 (PPC) system 10.5.8, Audacity 1.3.12-alpha-Feb 8 > 2010. > > Could this be related to: > > P2 R (Windows) Projects crash when applying repeated effects on > zoomed in regions towards the end of audio tracks (wiki) > > which is now at: > > http://bugzilla.audacityteam.org/show_bug.cgi?id=9 > > That bug report references this thread: > > http://n2.nabble.com/Various-P2s-and-P3s-a-repeatable-case-td404097 > 4.html > > which talks about "faint clip lines" and "P2 Boundary drawing > problem with Generate and SoundTouch " > > From what I've been able to determine it looks like a "faint clip > line" is a sign of overlapping clips and a corrupt .aup file? > > -- Bill > > ------------------------------------------------------------------- > ----------- SOLARIS 10 is the OS for Data Centers - provides > features such as DTrace, Predictive Self Healing and Award Winning > ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
From: Bill W. <bi...@go...> - 2010-02-11 03:03:36
|
It's not just the generators. Once you've found a clip that produces the failure when applying one of the generators, I have found that the following effects will produce similar failures: Change Pitch, Change Speed, Change Tempo, Equalization, Noise Removal, Sliding Time Scale/ Pitch Shift, Clip Fix, Cross Fade In, Cross Fade Out, High Pass Filter, Low Pass Filter, Tremolo. The following do not cause a failure: Amplify, Bass Boost, Click Removal, Compressor, Echo, Fade In, Fade Out, Invert, Leveller, Normalize, Reverse, Wah-wah. The following were not tested: Auto-Duck, Repair, Repeat, Vocoder, Vocal Remover. The Nyquist Prompt with just "s" in the command window produces the failure. -- Bill |
From: Al D. <bus...@gm...> - 2010-02-11 05:57:32
|
On Wednesday 10 February 2010 20:03:27 Bill Wharrie wrote: > It's not just the generators. Once you've found a clip that > produces the failure when applying one of the generators, I have > found that the following effects will produce similar failures: > Change Pitch, Change Speed, Change Tempo, Equalization, Noise > Removal, Sliding Time Scale/ Pitch Shift, Clip Fix, Cross Fade In, > Cross Fade Out, High Pass Filter, Low Pass Filter, Tremolo. > > The following do not cause a failure: Amplify, Bass Boost, Click > Removal, Compressor, Echo, Fade In, Fade Out, Invert, Leveller, > Normalize, Reverse, Wah-wah. > > The following were not tested: Auto-Duck, Repair, Repeat, Vocoder, > Vocal Remover. > > The Nyquist Prompt with just "s" in the command window produces the > failure. > The function I fixed is used by many effects and, IIRC, Edit->Paste, as well as generators. So I'd expect that similar failures would occur while using many effects. Hopefully that's fixed now... I haven't had a chance to extensively test with your project -- it sounded like some of the problems may have been unrelated, and that there's more that needs fixing. Also, David mentioned some other little flaws that I'm interested in. - Al > -- Bill > > ------------------------------------------------------------------- > ----------- SOLARIS 10 is the OS for Data Centers - provides > features such as DTrace, Predictive Self Healing and Award Winning > ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
From: Bill W. <bi...@go...> - 2010-02-21 23:08:19
|
On 11-Feb-10, at 12:57 AM, Al Dimond wrote: > > I haven't had a chance to extensively test with your project -- it > sounded like some of the problems may have been unrelated, and that > there's more that needs fixing. Also, David mentioned some other > little > flaws that I'm interested in. > As of the Feb 21 build, problems remain. DTMF generator will sometimes add an extra clip of a few samples at the end of the selection. It is still possible to create a situation where spurious clips are created using any built-in generator. -- Bill |
From: James C. <cr...@in...> - 2010-02-22 19:38:23
|
Is this a regression on 1.3.11? I ask, because if so in my book that would make it a P1. --James. On 21/02/2010 23:08, Bill Wharrie wrote: > On 11-Feb-10, at 12:57 AM, Al Dimond wrote: > >> I haven't had a chance to extensively test with your project -- it >> sounded like some of the problems may have been unrelated, and that >> there's more that needs fixing. Also, David mentioned some other >> little >> flaws that I'm interested in. >> >> > As of the Feb 21 build, problems remain. DTMF generator will sometimes > add an extra clip of a few samples at the end of the selection. It is > still possible to create a situation where spurious clips are created > using any built-in generator. > > -- Bill > |
From: Bill W. <bi...@go...> - 2010-02-22 21:43:34
|
On 22-Feb-10, at 2:38 PM, James Crook wrote: > Is this a regression on 1.3.11? I ask, because if so in my book that > would make it a P1. > AFAICT the problem been around in one form or another since 1.3.8. After Al's most recent fix, the problem of "faint split lines" (which indicate overlapping clips and a corrupt AUP file) appears to be gone - at least I can no longer reproduce it. -- Bill |
From: Gale A. <ga...@au...> - 2010-02-23 03:49:58
|
| From Bill Wharrie <bi...@go...> | Mon, 22 Feb 2010 16:43:27 -0500 | Subject: [Audacity-quality] Generators corrupt project? > > On 22-Feb-10, at 2:38 PM, James Crook wrote: > > > Is this a regression on 1.3.11? I ask, because if so in my book that > > would make it a P1. > > > > AFAICT the problem been around in one form or another since 1.3.8. > > After Al's most recent fix, the problem of "faint split lines" (which > indicate overlapping clips and a corrupt AUP file) appears to be gone > - at least I can no longer reproduce it. > > -- Bill Bill, thanks for following this up. I'd lost sight of testing Al's fix until a couple of days ago, did a cursory test a couple of times on a tone of 20 samples' length, found no problem at all, but lacked the time to try with longer tones. I'd urge again that if a repeatable problem appears that is clearly a bug, put it straight on Bugzilla as Px. If you have a small project demonstrating the issue, you can add it as an attachment to Bugzilla, whereas attachments to -quality over 1 MB are impossible. We're far more likely to keep a bug visible and ensure fixes to it are properly tested if it is on Bugzilla from the outset. Only consider posting to -quality where it isn't clear the issue is a bug, if you want to gauge support for adding an enhancement issue to Bugzilla, or if you want to suggest a new Proposal page on the Wiki for fleshing out ideas. If I left something out that belongs here, let me know. Back to the bug, after further testing 10 seconds' tones on XP in SVN, I can 80% replicate spurious clips. Similar but worse problems including unwanted white space insertion are in 1.3.11 Release. I can't obviously crash SVN by clicking around close to or applying effects over spurious clips. Therefore I've created a new repeatable P2 bug for it: http://bugzilla.audacityteam.org/show_bug.cgi?id=123 Please make all further observations on Bugzilla. Thanks Gale > On 11-Feb-10, at 12:57 AM, Al Dimond wrote: > > > > I haven't had a chance to extensively test with your project -- it > > sounded like some of the problems may have been unrelated, and that > > there's more that needs fixing. Also, David mentioned some other > > little > > flaws that I'm interested in. > > > > As of the Feb 21 build, problems remain. DTMF generator will sometimes > add an extra clip of a few samples at the end of the selection. It is > still possible to create a situation where spurious clips are created > using any built-in generator. > > > -- Bill > |