Thread: [Audacity-quality] Mixer Board issues
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Bill W. <bi...@go...> - 2010-11-02 15:50:57
|
There appear to be several problems with the Mixer Board. The following with Audacity 1.3.13 Oct 31 2010 Mac OS X 10.5.8 PPC 1) Audacity crashes with the following steps: a) New Project b) Tracks > Add New > Audio Track c) Generate Tone d) View > Mixer Board e) Tracks > Add New > Audio Track f) Generate > Tone Audacity crashes. In general, adding a new track then generating audio into it, while the Mixer Board is open, will crash Audacity. Recording a new track with the Mixer Board open does not crash. 2) Mixer board opens with meters extending into the horizontal scrollbar area at the bottom of the window. a) New Project b) Generate > Tone c) View > Mixer Board d) Play and observe mixer board meters This happens regardless of the meter range selected in Preferences :: Interface. 3) Pan slider is sometimes not drawn in some mixer board track strips. a) New Project b) Generate > Tone c) Tracks > New Audio Track d) Generate > Tone e) View > Mixer Board Second audio track in Mixer Board does not have pan slider drawn. 4) Manipulating the pan or gain sliders on the mixer board draws vertical dark green lines in some of the tracks in the project window - continuing the steps from #3 f) Select first audio track by clicking in the TrackInfo panel g) Click Skip to Start button in project window h) Click Play button i) Switch to Mixer Board j) Manipulate any pan or gain slider while Audacity is playing - dark green vertical lines are drawn in the track where the slider is not being manipulated - the lines are cleared if you manipulate a slider in the other channel - the lines are cleared when you stop I'd like confirmation of these before I raise a bug on Bugzilla. Also, if we do raise a bug there, do we raise one or four? -- Bill |
From: Peter S. <pet...@ya...> - 2010-11-02 19:50:17
|
Hi Bill Testing on 1.3.13 May23 2010 Unicide running on Windows XP-HE-SP3 1) doesn't crash 2) can't see what you're getting at 3) both audio tracks have pan slider drwn in miser board 4) works properly Peter. Peter Sampson Tel: +44 (0)1625 524 780 Mob: +44 (0)7732 278 299 ________________________________ From: Bill Wharrie <bi...@go...> To: audacity-quality characterization <aud...@li...> Sent: Tue, November 2, 2010 3:50:48 PM Subject: [Audacity-quality] Mixer Board issues There appear to be several problems with the Mixer Board. The following with Audacity 1.3.13 Oct 31 2010 Mac OS X 10.5.8 PPC 1) Audacity crashes with the following steps: a) New Project b) Tracks > Add New > Audio Track c) Generate Tone d) View > Mixer Board e) Tracks > Add New > Audio Track f) Generate > Tone Audacity crashes. In general, adding a new track then generating audio into it, while the Mixer Board is open, will crash Audacity. Recording a new track with the Mixer Board open does not crash. 2) Mixer board opens with meters extending into the horizontal scrollbar area at the bottom of the window. a) New Project b) Generate > Tone c) View > Mixer Board d) Play and observe mixer board meters This happens regardless of the meter range selected in Preferences :: Interface. 3) Pan slider is sometimes not drawn in some mixer board track strips. a) New Project b) Generate > Tone c) Tracks > New Audio Track d) Generate > Tone e) View > Mixer Board Second audio track in Mixer Board does not have pan slider drawn. 4) Manipulating the pan or gain sliders on the mixer board draws vertical dark green lines in some of the tracks in the project window - continuing the steps from #3 f) Select first audio track by clicking in the TrackInfo panel g) Click Skip to Start button in project window h) Click Play button i) Switch to Mixer Board j) Manipulate any pan or gain slider while Audacity is playing - dark green vertical lines are drawn in the track where the slider is not being manipulated - the lines are cleared if you manipulate a slider in the other channel - the lines are cleared when you stop I'd like confirmation of these before I raise a bug on Bugzilla. Also, if we do raise a bug there, do we raise one or four? -- Bill ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Audacity-quality mailing list Aud...@li... https://lists.sourceforge.net/lists/listinfo/audacity-quality |
From: Gale A. <ga...@au...> - 2010-11-02 20:10:09
|
| From Bill Wharrie <bi...@go...> | Tue, 2 Nov 2010 11:50:48 -0400 | Subject: [Audacity-quality] Mixer Board issues > There appear to be several problems with the Mixer Board. > > The following with Audacity 1.3.13 Oct 31 2010 Mac OS X 10.5.8 PPC > > 1) Audacity crashes with the following steps: > a) New Project > b) Tracks > Add New > Audio Track > c) Generate Tone > d) View > Mixer Board > e) Tracks > Add New > Audio Track > f) Generate > Tone > Audacity crashes. > In general, adding a new track then generating audio into it, while > the Mixer Board is open, will crash Audacity. Recording a new track > with the Mixer Board open does not crash. Thanks, Bill. No crash here in Unicode Release on Win 7 or Ubuntu 10.10. > 2) Mixer board opens with meters extending into the horizontal > scrollbar area at the bottom of the window. > a) New Project > b) Generate > Tone > c) View > Mixer Board > d) Play and observe mixer board meters > This happens regardless of the meter range selected in Preferences :: > Interface. Don't see it on either OS at default -60 dB meter range (Win is 1024 x 768, Ubuntu 800x600). Can you post a screenshot? > 3) Pan slider is sometimes not drawn in some mixer board track strips. > a) New Project > b) Generate > Tone > c) Tracks > New Audio Track > d) Generate > Tone > e) View > Mixer Board > Second audio track in Mixer Board does not have pan slider drawn. On Ubuntu 10.10, in each of four attempts with that scenario, *neither* track in Mixer Board has a pan slider. If I do a), b), Edit > Duplicate then View > Mixer Board, the first track has a pan slider but not the second. Neither scenario is a problem on Win 7. > 4) Manipulating the pan or gain sliders on the mixer board draws > vertical dark green lines in some of the tracks in the project window > - continuing the steps from #3 > f) Select first audio track by clicking in the TrackInfo panel > g) Click Skip to Start button in project window > h) Click Play button > i) Switch to Mixer Board > j) Manipulate any pan or gain slider while Audacity is playing > - dark green vertical lines are drawn in the track where the slider is > not being manipulated > - the lines are cleared if you manipulate a slider in the other channel > - the lines are cleared when you stop As in 3), I can't see any pan slider on Ubuntu, but yes I can reproduce the gain slider affecting the unmanipulated track with green lines. These playback cursor lines appear in other circumstances too on Linux (can't find it in Bugzilla right now). In addition, a small black rectangle appears at random positions on the screen when manipulating (which is actually http://bugzilla.audacityteam.org/show_bug.cgi?id=186#c1 ) . No problems here on Windows 7. > I'd like confirmation of these before I raise a bug on Bugzilla. Also, > if we do raise a bug there, do we raise one or four? You'll have to raise a bug for the crash 1) I think (starting at P2 for now) if it's reproducible on your machine after reboot and initialising .cfg. 2) - can we see the shot? 3) - will have to be a P2 for Linux and OS X, in my book. 4) - I think it's possibly part of a more general issue, I'll leave it to one side for now until the other issue can be found in the list. Gale |
From: Bill W. <bi...@go...> - 2010-11-02 23:49:54
Attachments:
MixerBoardMeter.png
|
Peter and Gale: I've retested everything after resetting .cfg and rebooting. On 2-Nov-10, at 4:10 PM, Gale Andrews wrote: > > | From Bill Wharrie <bi...@go...> > | Tue, 2 Nov 2010 11:50:48 -0400 > | Subject: [Audacity-quality] Mixer Board issues >> There appear to be several problems with the Mixer Board. >> >> The following with Audacity 1.3.13 Oct 31 2010 Mac OS X 10.5.8 PPC >> >> 1) Audacity crashes with the following steps: >> a) New Project >> b) Tracks > Add New > Audio Track >> c) Generate Tone >> d) View > Mixer Board >> e) Tracks > Add New > Audio Track >> f) Generate > Tone >> Audacity crashes. >> In general, adding a new track then generating audio into it, while >> the Mixer Board is open, will crash Audacity. Recording a new track >> with the Mixer Board open does not crash. > > Thanks, Bill. No crash here in Unicode Release on Win 7 or Ubuntu > 10.10. > Well, this is frustrating. After rebooting and initializing cfg, no crash. So I started changing some prefs (16-bit, copy audio into project) and got the crash. So I initialized cfg again to try the prefs one by one, and got the crash. So I rebooted, made sure cfg was initialized, and got the crash. Rebooted, made sure cfg was initialized, got no crash. Restarted Audacity without reboot, chose not to recover project, did procedure, got the crash. The Apple crash log shows (in part) Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffff8 Crashed Thread: 0 Thread 0 Crashed: 0 net.sourceforge.audacity 0x002caba4 wxTextCtrl::wxTextCtrl(wxWindow*, int, wxString const&, wxPoint const&, wxSize const&, long, wxValidator const&, wxString const&) + 12780 1 net.sourceforge.audacity 0x002cd958 wxTextCtrl::wxTextCtrl(wxWindow*, int, wxString const&, wxPoint const&, wxSize const&, long, wxValidator const&, wxString const&) + 24480 2 net.sourceforge.audacity 0x00145f78 AudacityPrintout::~AudacityPrintout() + 45636 3 net.sourceforge.audacity 0x00105548 LangHash::operator[] (wxString const&) + 52020 4 net.sourceforge.audacity 0x00105de0 LangHash::operator[] (wxString const&) + 54220 5 net.sourceforge.audacity 0x001d735c wxAboutDialogCreditItemsListNode::~wxAboutDialogCreditItemsListNode() + 7416 6 net.sourceforge.audacity 0x0013b9a4 AudacityPrintout::~AudacityPrintout() + 3184 7 net.sourceforge.audacity 0x00546344 wxStandardPaths::~wxStandardPaths() + 2148 8 net.sourceforge.audacity 0x00546544 wxStandardPaths::~wxStandardPaths() + 2660 9 net.sourceforge.audacity 0x00546930 wxStandardPaths::~wxStandardPaths() + 3664 10 net.sourceforge.audacity 0x004476a8 non-virtual thunk to wxListBoxBase::~wxListBoxBase() + 10760 11 net.sourceforge.audacity 0x0039a15c wxListEvent::Clone() const + 15276 12 net.sourceforge.audacity 0x003d0910 wxMBConvUTF16Base::~wxMBConvUTF16Base() + 33520 So let's put this one aside for the moment, as I can't get a reproduceable crash. Perhaps too many factors at play - including choosing not to recover the crashed project. This also may be another PPC 10.5.8 thing like the VST scanning. FWIW, the crash happens before the tone waveform is drawn. There is a pause of several seconds after OKing the Tone dialog, then (sometimes) about 1 second of the beachball of death, then the crash. I cannot reproduce this at all in 1.3.12. > >> 2) Mixer board opens with meters extending into the horizontal >> scrollbar area at the bottom of the window. >> a) New Project >> b) Generate > Tone >> c) View > Mixer Board >> d) Play and observe mixer board meters >> This happens regardless of the meter range selected in Preferences :: >> Interface. > > Don't see it on either OS at default -60 dB meter range (Win is 1024 > x 768, > Ubuntu 800x600). Can you post a screenshot? |
From: Bill W. <bi...@go...> - 2010-11-02 23:58:16
|
> > 3) - will have to be a P2 for Linux and OS X, in my book. > Committed Bug 250 - Pan slider sometimes not drawn in Mixer Board http://bugzilla.audacityteam.org/show_bug.cgi?id=250 -- Bill |
From: Gale A. <ga...@au...> - 2010-11-03 18:48:40
Attachments:
MixerBoardMeter.png
|
| From Bill Wharrie <bi...@go...> | Tue, 2 Nov 2010 19:49:44 -0400 | Subject: [Audacity-quality] Mixer Board issues > I've retested everything after resetting .cfg and rebooting. > > On 2-Nov-10, at 4:10 PM, Gale Andrews wrote: > > > > > | From Bill Wharrie <bi...@go...> > > | Tue, 2 Nov 2010 11:50:48 -0400 > > | Subject: [Audacity-quality] Mixer Board issues > >> There appear to be several problems with the Mixer Board. > >> > >> The following with Audacity 1.3.13 Oct 31 2010 Mac OS X 10.5.8 PPC > >> > >> 1) Audacity crashes with the following steps: > >> a) New Project > >> b) Tracks > Add New > Audio Track > >> c) Generate Tone > >> d) View > Mixer Board > >> e) Tracks > Add New > Audio Track > >> f) Generate > Tone > >> Audacity crashes. > >> In general, adding a new track then generating audio into it, while > >> the Mixer Board is open, will crash Audacity. Recording a new track > >> with the Mixer Board open does not crash. > > > > Thanks, Bill. No crash here in Unicode Release on Win 7 or Ubuntu > > 10.10. > > > > Well, this is frustrating. After rebooting and initializing cfg, no > crash. So I started changing some prefs (16-bit, copy audio into > project) and got the crash. So I initialized cfg again to try the > prefs one by one, and got the crash. So I rebooted, made sure cfg was > initialized, and got the crash. Rebooted, made sure cfg was > initialized, got no crash. Restarted Audacity without reboot, chose > not to recover project, did procedure, got the crash. The Apple crash > log shows (in part) > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffff8 > Crashed Thread: 0 > > Thread 0 Crashed: > 0 net.sourceforge.audacity 0x002caba4 > wxTextCtrl::wxTextCtrl(wxWindow*, int, wxString const&, wxPoint > const&, wxSize const&, long, wxValidator const&, wxString const&) + > 12780 > 1 net.sourceforge.audacity 0x002cd958 > wxTextCtrl::wxTextCtrl(wxWindow*, int, wxString const&, wxPoint > const&, wxSize const&, long, wxValidator const&, wxString const&) + > 24480 > 2 net.sourceforge.audacity 0x00145f78 > AudacityPrintout::~AudacityPrintout() + 45636 > 3 net.sourceforge.audacity 0x00105548 LangHash::operator[] > (wxString const&) + 52020 > 4 net.sourceforge.audacity 0x00105de0 LangHash::operator[] > (wxString const&) + 54220 > 5 net.sourceforge.audacity 0x001d735c > wxAboutDialogCreditItemsListNode::~wxAboutDialogCreditItemsListNode() > + 7416 > 6 net.sourceforge.audacity 0x0013b9a4 > AudacityPrintout::~AudacityPrintout() + 3184 > 7 net.sourceforge.audacity 0x00546344 > wxStandardPaths::~wxStandardPaths() + 2148 > 8 net.sourceforge.audacity 0x00546544 > wxStandardPaths::~wxStandardPaths() + 2660 > 9 net.sourceforge.audacity 0x00546930 > wxStandardPaths::~wxStandardPaths() + 3664 > 10 net.sourceforge.audacity 0x004476a8 non-virtual thunk to > wxListBoxBase::~wxListBoxBase() + 10760 > 11 net.sourceforge.audacity 0x0039a15c wxListEvent::Clone() > const + 15276 > 12 net.sourceforge.audacity 0x003d0910 > wxMBConvUTF16Base::~wxMBConvUTF16Base() + 33520 > > So let's put this one aside for the moment, as I can't get a > reproduceable crash. Perhaps too many factors at play - including > choosing not to recover the crashed project. This also may be another > PPC 10.5.8 thing like the VST scanning. > > FWIW, the crash happens before the tone waveform is drawn. There is a > pause of several seconds after OKing the Tone dialog, then (sometimes) > about 1 second of the beachball of death, then the crash. > > I cannot reproduce this at all in 1.3.12. I've played around more in Ubuntu and rebooted several times (and initialised .cfg). I still can't reproduce your 1a) through to f), but both of these give a 100% repeatable segfault: 1) a) New Project b) Tracks > Add New > Audio Track c) Record (i.e. in stereo, which should open a new stereo track) 2) a) New Project b) Tracks > Add New > Audio Track c) View > Mixer Board d) Generate > Tone If in 1) I replace c) with Generate > Tone, there is never a crash. My 1) or 2) don't repro in Win 7. So it looks as if it could be an issue with Tracks > Add New > Audio Track, but I'm not sure what changed there since 1.3.12? Can you repro either of my 1) or 2)? > >> 2) Mixer board opens with meters extending into the horizontal > >> scrollbar area at the bottom of the window. > >> a) New Project > >> b) Generate > Tone > >> c) View > Mixer Board > >> d) Play and observe mixer board meters > >> This happens regardless of the meter range selected in Preferences :: > >> Interface. > > > > Don't see it on either OS at default -60 dB meter range (Win is 1024 > > x 768, > > Ubuntu 800x600). Can you post a screenshot? > > This (screenshot attached) is on a 1900x1280 screen. > > On Win or Linux, once the Mixer Board is displayed, can you resize the > window to clip the bottom of the meters? I can resize the Mixer Board window down as far as possible and the meters are still drawn only within the track. Can you get Koz or someone on the Forum to try this on Snow Leopard? > >> 3) Pan slider is sometimes not drawn in some mixer board track > >> strips. > >> a) New Project > >> b) Generate > Tone > >> c) Tracks > New Audio Track > >> d) Generate > Tone > >> e) View > Mixer Board > >> Second audio track in Mixer Board does not have pan slider drawn. > > > > On Ubuntu 10.10, in each of four attempts with that scenario, > > *neither* > > track in Mixer Board has a pan slider. > > > > If I do a), b), Edit > Duplicate then View > Mixer Board, the first > > track > > has a pan slider but not the second. > > > > Neither scenario is a problem on Win 7. > > OK, so this one is confirmed on Mac and Linux, no problem on Win7? Correct. Thanks for raising Bug 250 for this. Gale > >> 4) Manipulating the pan or gain sliders on the mixer board draws > >> vertical dark green lines in some of the tracks in the project window > >> - continuing the steps from #3 > >> f) Select first audio track by clicking in the TrackInfo panel > >> g) Click Skip to Start button in project window > >> h) Click Play button > >> i) Switch to Mixer Board > >> j) Manipulate any pan or gain slider while Audacity is playing > >> - dark green vertical lines are drawn in the track where the slider > >> is > >> not being manipulated > >> - the lines are cleared if you manipulate a slider in the other > >> channel > >> - the lines are cleared when you stop > > > > As in 3), I can't see any pan slider on Ubuntu, but yes I can > > reproduce > > the gain slider affecting the unmanipulated track with green lines. > > These playback cursor lines appear in other circumstances too on > > Linux (can't find it in Bugzilla right now). > > > > > > In addition, a small black rectangle appears at random positions on > > the screen when manipulating (which is actually > > http://bugzilla.audacityteam.org/show_bug.cgi?id=186#c1 ) . > > > > No problems here on Windows 7. > > > > > >> I'd like confirmation of these before I raise a bug on Bugzilla. > >> Also, > >> if we do raise a bug there, do we raise one or four? > > > > You'll have to raise a bug for the crash 1) I think (starting at P2 > > for now) > > if it's reproducible on your machine after reboot and > > initialising .cfg. > > See above. I want to do more testing before I do that. > > > > > 2) - can we see the shot? > > See above. Apparently Mac only. > > > > > 3) - will have to be a P2 for Linux and OS X, in my book. > > OK, will do. > > > > > 4) - I think it's possibly part of a more general issue, I'll leave > > it to one > > side for now until the other issue can be found in the list. > > OK. > |
From: Bill W. <bi...@go...> - 2010-11-03 20:20:39
|
On 3-Nov-10, at 2:48 PM, Gale Andrews wrote: > > | From Bill Wharrie <bi...@go...> > | Tue, 2 Nov 2010 19:49:44 -0400 > | Subject: [Audacity-quality] Mixer Board issues >> I've retested everything after resetting .cfg and rebooting. >> >> On 2-Nov-10, at 4:10 PM, Gale Andrews wrote: >> >>> >>> | From Bill Wharrie <bi...@go...> >>> | Tue, 2 Nov 2010 11:50:48 -0400 >>> | Subject: [Audacity-quality] Mixer Board issues >>>> There appear to be several problems with the Mixer Board. >>>> >>>> The following with Audacity 1.3.13 Oct 31 2010 Mac OS X 10.5.8 PPC >>>> >>>> 1) Audacity crashes with the following steps: >>>> a) New Project >>>> b) Tracks > Add New > Audio Track >>>> c) Generate Tone >>>> d) View > Mixer Board >>>> e) Tracks > Add New > Audio Track >>>> f) Generate > Tone >>>> Audacity crashes. >>>> In general, adding a new track then generating audio into it, while >>>> the Mixer Board is open, will crash Audacity. Recording a new track >>>> with the Mixer Board open does not crash. >>> >>> Thanks, Bill. No crash here in Unicode Release on Win 7 or Ubuntu >>> 10.10. >>> >> >> Well, this is frustrating. After rebooting and initializing cfg, no >> crash. So I started changing some prefs (16-bit, copy audio into >> project) and got the crash. So I initialized cfg again to try the >> prefs one by one, and got the crash. So I rebooted, made sure cfg was >> initialized, and got the crash. Rebooted, made sure cfg was >> initialized, got no crash. Restarted Audacity without reboot, chose >> not to recover project, did procedure, got the crash. <snip> >> >> So let's put this one aside for the moment, as I can't get a >> reproduceable crash. Perhaps too many factors at play - including >> choosing not to recover the crashed project. This also may be another >> PPC 10.5.8 thing like the VST scanning. >> >> FWIW, the crash happens before the tone waveform is drawn. There is a >> pause of several seconds after OKing the Tone dialog, then >> (sometimes) >> about 1 second of the beachball of death, then the crash. >> >> I cannot reproduce this at all in 1.3.12. > > I've played around more in Ubuntu and rebooted several times > (and initialised .cfg). I still can't reproduce your 1a) through to > f), > but both of these give a 100% repeatable segfault: > > 1) a) New Project > b) Tracks > Add New > Audio Track > c) Record (i.e. in stereo, which should open a new stereo track) I cannot get this to crash. A new stereo track is created and recorded into. > > 2) a) New Project > b) Tracks > Add New > Audio Track > c) View > Mixer Board > d) Generate > Tone This crashes every time with an initialized cfg and no crashed project to recover. That is, after a crash I start Audacity, choose not to recover the project, quit Audacity then initialize the cfg. Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000052 Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffff8 Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000041bffff8 Crashed Thread: 0 Now, just to complicate matters, if I initialize cfg, start Audacity (and choose not to recover the project from a previous crash, if that occurs), then quit Audacity, I have a cfg filled with the default values. If I then start Audacity and do your 2 a,b,c, I *usually* get the crash. One time I didn't, but now 5 times in a row I have gotten it, even after rebooting. > > If in 1) I replace c) with Generate > Tone, there is never a crash. Same here. No crash. In my case it seems to be dependent on the Mixer Board being open. > My 1) or 2) don't repro in Win 7. So it looks as if it could be an > issue > with Tracks > Add New > Audio Track, but I'm not sure what changed > there since 1.3.12? Can you repro either of my 1) or 2)? I'm not sure this is related to Add New > Audio Track. The fault occurs when the Mixer Board is open and one attempts to generate audio into the new track. I tried your 1 a) b) then Append Record (to force recording into the new track) and got no crash with an initialized cfg. -- Bill > > >>>> 2) Mixer board opens with meters extending into the horizontal >>>> scrollbar area at the bottom of the window. >>>> a) New Project >>>> b) Generate > Tone >>>> c) View > Mixer Board >>>> d) Play and observe mixer board meters >>>> This happens regardless of the meter range selected in >>>> Preferences :: >>>> Interface. >>> >>> Don't see it on either OS at default -60 dB meter range (Win is 1024 >>> x 768, >>> Ubuntu 800x600). Can you post a screenshot? >> >> This (screenshot attached) is on a 1900x1280 screen. >> >> On Win or Linux, once the Mixer Board is displayed, can you resize >> the >> window to clip the bottom of the meters? > > I can resize the Mixer Board window down as far as possible and > the meters are still drawn only within the track. Can you get Koz or > someone on the Forum to try this on Snow Leopard? > > >>>> 3) Pan slider is sometimes not drawn in some mixer board track >>>> strips. >>>> a) New Project >>>> b) Generate > Tone >>>> c) Tracks > New Audio Track >>>> d) Generate > Tone >>>> e) View > Mixer Board >>>> Second audio track in Mixer Board does not have pan slider drawn. >>> >>> On Ubuntu 10.10, in each of four attempts with that scenario, >>> *neither* >>> track in Mixer Board has a pan slider. >>> >>> If I do a), b), Edit > Duplicate then View > Mixer Board, the first >>> track >>> has a pan slider but not the second. >>> >>> Neither scenario is a problem on Win 7. >> >> OK, so this one is confirmed on Mac and Linux, no problem on Win7? > > Correct. Thanks for raising Bug 250 for this. > > > > > Gale > > > >>>> 4) Manipulating the pan or gain sliders on the mixer board draws >>>> vertical dark green lines in some of the tracks in the project >>>> window >>>> - continuing the steps from #3 >>>> f) Select first audio track by clicking in the TrackInfo panel >>>> g) Click Skip to Start button in project window >>>> h) Click Play button >>>> i) Switch to Mixer Board >>>> j) Manipulate any pan or gain slider while Audacity is playing >>>> - dark green vertical lines are drawn in the track where the slider >>>> is >>>> not being manipulated >>>> - the lines are cleared if you manipulate a slider in the other >>>> channel >>>> - the lines are cleared when you stop >>> >>> As in 3), I can't see any pan slider on Ubuntu, but yes I can >>> reproduce >>> the gain slider affecting the unmanipulated track with green lines. >>> These playback cursor lines appear in other circumstances too on >>> Linux (can't find it in Bugzilla right now). >> >> >>> >>> In addition, a small black rectangle appears at random positions on >>> the screen when manipulating (which is actually >>> http://bugzilla.audacityteam.org/show_bug.cgi?id=186#c1 ) . >>> >>> No problems here on Windows 7. >>> >>> >>>> I'd like confirmation of these before I raise a bug on Bugzilla. >>>> Also, >>>> if we do raise a bug there, do we raise one or four? >>> >>> You'll have to raise a bug for the crash 1) I think (starting at P2 >>> for now) >>> if it's reproducible on your machine after reboot and >>> initialising .cfg. >> >> See above. I want to do more testing before I do that. >> >>> >>> 2) - can we see the shot? >> >> See above. Apparently Mac only. >> >>> >>> 3) - will have to be a P2 for Linux and OS X, in my book. >> >> OK, will do. >> >>> >>> 4) - I think it's possibly part of a more general issue, I'll leave >>> it to one >>> side for now until the other issue can be found in the list. >> >> OK. >> > < > MixerBoardMeter > .png > > > ------------------------------------------------------------------------------ > Achieve Improved Network Security with IP and DNS Reputation. > Defend against bad network traffic, including botnets, malware, > phishing sites, and compromised hosts - saving your company time, > money, and embarrassment. Learn More! > http://p.sf.net/sfu/hpdev2dev-nov_______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |
From: Bill W. <bi...@go...> - 2010-11-05 16:17:01
|
On 3-Nov-10, at 4:20 PM, Bill Wharrie wrote: > > On 3-Nov-10, at 2:48 PM, Gale Andrews wrote: > >> <snip> >> >> I've played around more in Ubuntu and rebooted several times >> (and initialised .cfg). I still can't reproduce your 1a) through to >> f), >> but both of these give a 100% repeatable segfault: >> >> 1) a) New Project >> b) Tracks > Add New > Audio Track >> c) Record (i.e. in stereo, which should open a new stereo track) > > I cannot get this to crash. A new stereo track is created and recorded > into. > >> >> 2) a) New Project >> b) Tracks > Add New > Audio Track >> c) View > Mixer Board >> d) Generate > Tone > > This crashes every time with an initialized cfg and no crashed project > to recover. That is, after a crash I start Audacity, choose not to > recover the project, quit Audacity then initialize the cfg. > > Exception Type: EXC_BAD_ACCESS (SIGBUS) > Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000052 > Crashed Thread: 0 > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffff8 > Crashed Thread: 0 > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x0000000041bffff8 > Crashed Thread: 0 > > Now, just to complicate matters, if I initialize cfg, start Audacity > (and choose not to recover the project from a previous crash, if that > occurs), then quit Audacity, I have a cfg filled with the default > values. If I then start Audacity and do your 2 a,b,c, I *usually* get > the crash. One time I didn't, but now 5 times in a row I have gotten > it, even after rebooting. > >> >> If in 1) I replace c) with Generate > Tone, there is never a crash. > > Same here. No crash. In my case it seems to be dependent on the Mixer > Board being open. > >> My 1) or 2) don't repro in Win 7. So it looks as if it could be an >> issue >> with Tracks > Add New > Audio Track, but I'm not sure what changed >> there since 1.3.12? Can you repro either of my 1) or 2)? > > I'm not sure this is related to Add New > Audio Track. The fault > occurs when the Mixer Board is open and one attempts to generate audio > into the new track. I tried your 1 a) b) then Append Record (to force > recording into the new track) and got no crash with an initialized > cfg. It seems we have a reproduceable crash here. I have put off raising a bug pending further discussion. > > >> >> >>>>> 2) Mixer board opens with meters extending into the horizontal >>>>> scrollbar area at the bottom of the window. >>>>> a) New Project >>>>> b) Generate > Tone >>>>> c) View > Mixer Board >>>>> d) Play and observe mixer board meters >>>>> This happens regardless of the meter range selected in >>>>> Preferences :: >>>>> Interface. >>>> >>>> Don't see it on either OS at default -60 dB meter range (Win is >>>> 1024 >>>> x 768, >>>> Ubuntu 800x600). Can you post a screenshot? >>> >>> This (screenshot attached) is on a 1900x1280 screen. >>> >>> On Win or Linux, once the Mixer Board is displayed, can you resize >>> the >>> window to clip the bottom of the meters? >> >> I can resize the Mixer Board window down as far as possible and >> the meters are still drawn only within the track. Can you get Koz or >> someone on the Forum to try this on Snow Leopard? Per this forum thread http://forum.audacityteam.org/viewtopic.php?f=15&t=43606 confirmed on 10.5 Intel and 10.6. Raised bug, P3 for now. http://bugzilla.audacityteam.org/show_bug.cgi?id=252 >> >> >>>>> 3) Pan slider is sometimes not drawn in some mixer board track >>>>> strips. >>>>> a) New Project >>>>> b) Generate > Tone >>>>> c) Tracks > New Audio Track >>>>> d) Generate > Tone >>>>> e) View > Mixer Board >>>>> Second audio track in Mixer Board does not have pan slider drawn. >>>> >>>> On Ubuntu 10.10, in each of four attempts with that scenario, >>>> *neither* >>>> track in Mixer Board has a pan slider. >>>> >>>> If I do a), b), Edit > Duplicate then View > Mixer Board, the first >>>> track >>>> has a pan slider but not the second. >>>> >>>> Neither scenario is a problem on Win 7. >>> >>> OK, so this one is confirmed on Mac and Linux, no problem on Win7? >> >> Correct. Thanks for raising Bug 250 for this. >> >>>>> 4) Manipulating the pan or gain sliders on the mixer board draws >>>>> vertical dark green lines in some of the tracks in the project >>>>> window >>>>> - continuing the steps from #3 >>>>> f) Select first audio track by clicking in the TrackInfo panel >>>>> g) Click Skip to Start button in project window >>>>> h) Click Play button >>>>> i) Switch to Mixer Board >>>>> j) Manipulate any pan or gain slider while Audacity is playing >>>>> - dark green vertical lines are drawn in the track where the >>>>> slider >>>>> is >>>>> not being manipulated >>>>> - the lines are cleared if you manipulate a slider in the other >>>>> channel >>>>> - the lines are cleared when you stop >>>> >>>> As in 3), I can't see any pan slider on Ubuntu, but yes I can >>>> reproduce >>>> the gain slider affecting the unmanipulated track with green lines. >>>> These playback cursor lines appear in other circumstances too on >>>> Linux (can't find it in Bugzilla right now). >>> >>> >>>> >>>> In addition, a small black rectangle appears at random positions on >>>> the screen when manipulating (which is actually >>>> http://bugzilla.audacityteam.org/show_bug.cgi?id=186#c1 ) . >>>> >>>> No problems here on Windows 7. >>>> >>>> I looked through all the bugs on bugzilla and couldn't see anything that described the painting of vertical green lines in the tracks (or similar) when manipulating a slider on the Mixer Board. NEW ISSUE On Mixer Board, gain slider desynchronizes from pointer during a drag. The slider handle appears to move about half the distance that the pointer moves. -- Bill |
From: Vaughan J. <va...@au...> - 2010-11-08 23:23:05
|
On 11/5/2010 9:16 AM, Bill Wharrie wrote: > > On 3-Nov-10, at 4:20 PM, Bill Wharrie wrote: > >> >> On 3-Nov-10, at 2:48 PM, Gale Andrews wrote: >> >>> > > <snip> > > > It seems we have a reproduceable crash here. I have put off raising a > bug pending further discussion. Let me know. Per Gale, these issues don't happen on Windows, from what I've seen in this thread. > <snip> >> >> >>> >>> >>>>>> 2) Mixer board opens with meters extending into the horizontal >>>>>> scrollbar area at the bottom of the window. >>>>>> a) New Project >>>>>> b) Generate > Tone >>>>>> c) View > Mixer Board >>>>>> d) Play and observe mixer board meters >>>>>> This happens regardless of the meter range selected in >>>>>> Preferences :: >>>>>> Interface. >>>>> >>>>> Don't see it on either OS at default -60 dB meter range (Win is >>>>> 1024 >>>>> x 768, >>>>> Ubuntu 800x600). Can you post a screenshot? >>>> >>>> This (screenshot attached) is on a 1900x1280 screen. >>>> >>>> On Win or Linux, once the Mixer Board is displayed, can you resize >>>> the >>>> window to clip the bottom of the meters? >>> >>> I can resize the Mixer Board window down as far as possible and >>> the meters are still drawn only within the track. Can you get Koz or >>> someone on the Forum to try this on Snow Leopard? > > Per this forum thread http://forum.audacityteam.org/viewtopic.php?f=15&t=43606 > confirmed on 10.5 Intel and 10.6. Raised bug, P3 for now. > > http://bugzilla.audacityteam.org/show_bug.cgi?id=252 Mac does some drawing buffering differently. There are lots of special-case places for Mac drawing in the code. Probably more fruitful for a Mac developer to work on this. > <snip> > > NEW ISSUE > On Mixer Board, gain slider desynchronizes from pointer during a drag. > The slider handle appears to move about half the distance that the > pointer moves. > It's not specific to Mixer Board, it happens in the TrackPanel gain sliders, too. And on the velocity sliders for Note Tracks (if EXPERIMENTAL_MIDI_OUT is on). It's more noticeable in Mixer Board than TrackPanel because the slider is so much bigger. It's intentional. Not sure of the history, but it's moderated by a "speed" factor, and lets you get fine adjustments even moving the mouse quickly. - Vaughan |
From: Bill W. <bi...@go...> - 2010-11-08 23:27:57
|
On 8-Nov-10, at 6:23 PM, Vaughan Johnson wrote: <snip> >> >> NEW ISSUE >> On Mixer Board, gain slider desynchronizes from pointer during a >> drag. >> The slider handle appears to move about half the distance that the >> pointer moves. >> > > It's not specific to Mixer Board, it happens in the TrackPanel gain > sliders, too. And on the velocity sliders for Note Tracks (if > EXPERIMENTAL_MIDI_OUT is on). It's more noticeable in Mixer Board than > TrackPanel because the slider is so much bigger. > > It's intentional. Not sure of the history, but it's moderated by a > "speed" factor, and lets you get fine adjustments even moving the > mouse > quickly. > Vaughn: Thanks for the info. Yes, I just yesterday noticed the same thing on the TrackPanel gain sliders. It may be intentional, and it may give "finer" control, but it is disconcerting. -- Bill |
From: Bill W. <bi...@go...> - 2010-11-09 19:17:56
|
On 3-Nov-10, at 2:48 PM, Gale Andrews wrote: <snip> > I've played around more in Ubuntu and rebooted several times > (and initialised .cfg). I still can't reproduce your 1a) through to > f), > but both of these give a 100% repeatable segfault: > > 1) a) New Project > b) Tracks > Add New > Audio Track > c) Record (i.e. in stereo, which should open a new stereo track) > > 2) a) New Project > b) Tracks > Add New > Audio Track > c) View > Mixer Board > d) Generate > Tone > > If in 1) I replace c) with Generate > Tone, there is never a crash. > My 1) or 2) don't repro in Win 7. So it looks as if it could be an > issue > with Tracks > Add New > Audio Track, but I'm not sure what changed > there since 1.3.12? Can you repro either of my 1) or 2)? > More testing on Gale's two sequences. 1) I cannot get this to crash on any of the three machines I have access to. 2) This crashes on all three machines: OS X 10.5.8 PPC G5 OS X 10.4.11 PPC G4 Powerbook OS X 10.4.11 Intel Core Two Duo. When launching Audacity after the crash I get the crash recovery dialog. If I choose to recover the project the error log shows: 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e00000b1.au' 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e00002d4.au' 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e000031d.au' 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e0000334.au' 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e000077a.au' 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e0000da8.au' 14:06:18: Warning: Project check ignored orphan blockfile(s). They will be deleted when project is saved. 14:06:19: Warning: Project check found file inconsistencies inspecting the loaded project data. And the project window opens with the empty mono audio track. Gale, do we need more testers/reports before raising a bug? Should we ask on the forum? -- Bill |
From: Gale A. <ga...@au...> - 2010-11-10 02:58:35
|
| From Bill Wharrie <bi...@go...> | Tue, 9 Nov 2010 14:17:48 -0500 | Subject: [Audacity-quality] Mixer Board issues > > On 3-Nov-10, at 2:48 PM, Gale Andrews wrote: > > <snip> > > > I've played around more in Ubuntu and rebooted several times > > (and initialised .cfg). I still can't reproduce your 1a) through to > > f), > > but both of these give a 100% repeatable segfault: > > > > 1) a) New Project > > b) Tracks > Add New > Audio Track > > c) Record (i.e. in stereo, which should open a new stereo track) > > > > 2) a) New Project > > b) Tracks > Add New > Audio Track > > c) View > Mixer Board > > d) Generate > Tone > > > > If in 1) I replace c) with Generate > Tone, there is never a crash. > > My 1) or 2) don't repro in Win 7. So it looks as if it could be an > > issue > > with Tracks > Add New > Audio Track, but I'm not sure what changed > > there since 1.3.12? Can you repro either of my 1) or 2)? > > > More testing on Gale's two sequences. > > 1) I cannot get this to crash on any of the three machines I have > access to. > > 2) This crashes on all three machines: > OS X 10.5.8 PPC G5 > OS X 10.4.11 PPC G4 Powerbook > OS X 10.4.11 Intel Core Two Duo. Sorry I've been silent on this. I have though been doing some playing around myself and 3) below crashes 100% for me on Win 7 and Ubuntu in two scenarios (first) with only USE_MIDI defined (as in released builds) and (second) with USE_MIDI and EXPERIMENTAL_MIDI_OUT both defined (which allows MIDI playback and adds that "Velocity" slider to Mixer Board): 3) a) Add an audio track (either generate or import will reproduce) b) Import a MIDI c) View > Mixer Board d) Click X top left to remove the MIDI e) Edit > Undo f) Edit > Redo It isn't predictable whether the crash will occur in d), e) or f), but one of those three will always crash for me. So we have three "similar, but not the same" crashes. Can you (Bill) repro 3)? You only need to test with USE_MIDI on as in the Nightly. The only common factor for me in all three is "adding a new track" (but not necessarily with Tracks > Add New > Audio Track). You have a second common factor in Mixer Board. The "spurious green lines" is obviously less important but I haven't yet looked again on Bugzilla. > When launching Audacity after the crash [in 2)] I get the crash recovery > dialog. If I choose to recover the project the error log shows: > > 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e00000b1.au' > 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e00002d4.au' > 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e000031d.au' > 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e0000334.au' > 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e000077a.au' > 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e0000da8.au' > 14:06:18: Warning: Project check ignored orphan blockfile(s). They > will be deleted when project is saved. > 14:06:19: Warning: Project check found file inconsistencies inspecting > the loaded project data. > > And the project window opens with the empty mono audio track. Bug 20 possibly strikes again: http://bugzilla.audacityteam.org/show_bug.cgi?id=20 On Ubuntu if I run 2) and recover the project after the crash, I get an empty mono track as you do. It should I think recover the tone as it is there in the .au files in /tmp (unless you would argue the crash has not left time for the autosave file to be written properly). The autosave file only lists one .au file. That .au is in the /tmp folder, but it is still reported as an orphan in the log, along with five others not in the autosave file. On Windows, if I force quit after following 2) through, recovery is OK. I'll add this "failed recovery" scenario to Bug 20, unless Vaughan thinks it's unreasonable to recover the tone in this case. > Gale, do we need more testers/reports before raising a bug? Should we > ask on the forum? I don't think so, once you've tested 3). There should be three repeatable crashes a developer on the appropriate platform can get their teeth into. It just depends if we group them or not; partly this may depend what you find with 3). Help from the Forum testing fixes to these crashes may be good. More generally, Crash Recovery (Bug 20) really does need heavy testing on Mac with multiple scenarios because two-thirds of the problem reports about it were on that platform. Enlisting the Mac Forum to help with Bug 20 testing may be a good idea. Gale |
From: Bill W. <bi...@go...> - 2010-11-10 05:01:48
|
On 9-Nov-10, at 9:58 PM, Gale Andrews wrote: > <snip> > I have though been doing some playing > around myself and 3) below crashes 100% for me on Win 7 and Ubuntu > in two scenarios (first) with only USE_MIDI defined (as in released > builds) and (second) with USE_MIDI and EXPERIMENTAL_MIDI_OUT > both defined (which allows MIDI playback and adds that "Velocity" > slider to Mixer Board): > > 3) a) Add an audio track (either generate or import will reproduce) > b) Import a MIDI > c) View > Mixer Board > d) Click X top left to remove the MIDI > e) Edit > Undo > f) Edit > Redo > > It isn't predictable whether the crash will occur in d), e) or f), > but one > of those three will always crash for me. > > So we have three "similar, but not the same" crashes. Can you (Bill) > repro 3)? You only need to test with USE_MIDI on as in the Nightly. > I sometimes have to add g) Undo h) Redo i) Undo But it will crash for me at e, g or i. That is, it seems to always be on the Undo step. This with an initialized cfg and 1.3.13 Nov 7 Mac PPC 10.5.8. -- Bill |
From: Vaughan J. <va...@au...> - 2010-11-11 01:04:19
|
On 11/9/2010 6:58 PM, Gale Andrews wrote: > > | From Bill Wharrie <bi...@go...> > | Tue, 9 Nov 2010 14:17:48 -0500 > | Subject: [Audacity-quality] Mixer Board issues >> >> On 3-Nov-10, at 2:48 PM, Gale Andrews wrote: >> >> <snip> >> >>> I've played around more in Ubuntu and rebooted several times >>> (and initialised .cfg). I still can't reproduce your 1a) through to >>> f), >>> but both of these give a 100% repeatable segfault: >>> >>> 1) a) New Project >>> b) Tracks > Add New > Audio Track >>> c) Record (i.e. in stereo, which should open a new stereo track) >>> >>> 2) a) New Project >>> b) Tracks > Add New > Audio Track >>> c) View > Mixer Board >>> d) Generate > Tone >>> >>> If in 1) I replace c) with Generate > Tone, there is never a crash. >>> My 1) or 2) don't repro in Win 7. So it looks as if it could be an >>> issue >>> with Tracks > Add New > Audio Track, but I'm not sure what changed >>> there since 1.3.12? Can you repro either of my 1) or 2)? >> >> >> More testing on Gale's two sequences. >> >> 1) I cannot get this to crash on any of the three machines I have >> access to. >> >> 2) This crashes on all three machines: >> OS X 10.5.8 PPC G5 >> OS X 10.4.11 PPC G4 Powerbook >> OS X 10.4.11 Intel Core Two Duo. > > Sorry I've been silent on this. I have though been doing some playing > around myself and 3) below crashes 100% for me on Win 7 and Ubuntu > in two scenarios (first) with only USE_MIDI defined (as in released > builds) and (second) with USE_MIDI and EXPERIMENTAL_MIDI_OUT > both defined (which allows MIDI playback and adds that "Velocity" > slider to Mixer Board): > > 3) a) Add an audio track (either generate or import will reproduce) > b) Import a MIDI > c) View > Mixer Board > d) Click X top left to remove the MIDI > e) Edit > Undo > f) Edit > Redo > > It isn't predictable whether the crash will occur in d), e) or f), but one > of those three will always crash for me. > > So we have three "similar, but not the same" crashes. Can you (Bill) > repro 3)? You only need to test with USE_MIDI on as in the Nightly. > > The only common factor for me in all three is "adding a new track" > (but not necessarily with Tracks > Add New > Audio Track). You have > a second common factor in Mixer Board. I looked into this, and it's another bug introduced by Roger's commit 10680. When I said it was okay for him to make these changes, it was with the understanding that they would all be under EXPERIMENTAL_MIDI_OUT and not threaten our code stability with that turned off. In fixing bug 250 and looking into this, I've found he did a *lot* of it under USE_MIDI and even more with no flag at all. I'm disappointed in this and am going to back out his changes. > > The "spurious green lines" is obviously less important but I haven't yet > looked again on Bugzilla. Are these also new since his changes? > > >> When launching Audacity after the crash [in 2)] I get the crash recovery >> dialog. If I choose to recover the project the error log shows: >> >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e00000b1.au' >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e00002d4.au' >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e000031d.au' >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e0000334.au' >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e000077a.au' >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e0000da8.au' >> 14:06:18: Warning: Project check ignored orphan blockfile(s). They >> will be deleted when project is saved. >> 14:06:19: Warning: Project check found file inconsistencies inspecting >> the loaded project data. >> >> And the project window opens with the empty mono audio track. > > Bug 20 possibly strikes again: > http://bugzilla.audacityteam.org/show_bug.cgi?id=20 Much more likely a newly introduced bug. - Vaughan > > On Ubuntu if I run 2) and recover the project after the crash, I get > an empty mono track as you do. > > It should I think recover the tone as it is there in the .au files in /tmp > (unless you would argue the crash has not left time for the autosave > file to be written properly). The autosave file only lists one .au file. > That .au is in the /tmp folder, but it is still reported as an orphan in > the log, along with five others not in the autosave file. > > On Windows, if I force quit after following 2) through, recovery is OK. > > I'll add this "failed recovery" scenario to Bug 20, unless Vaughan > thinks it's unreasonable to recover the tone in this case. > > >> Gale, do we need more testers/reports before raising a bug? Should we >> ask on the forum? > > I don't think so, once you've tested 3). There should be three repeatable > crashes a developer on the appropriate platform can get their teeth into. > It just depends if we group them or not; partly this may depend what > you find with 3). > > Help from the Forum testing fixes to these crashes may be good. More > generally, Crash Recovery (Bug 20) really does need heavy testing on > Mac with multiple scenarios because two-thirds of the problem reports > about it were on that platform. Enlisting the Mac Forum to help with > Bug 20 testing may be a good idea. > > > > > > Gale |
From: Bill W. <bi...@go...> - 2010-11-11 01:52:09
Attachments:
GreenLines2.jpg
|
On 10-Nov-10, at 8:04 PM, Vaughan Johnson wrote: > > > On 11/9/2010 6:58 PM, Gale Andrews wrote: >> > <snip> >> >> The "spurious green lines" is obviously less important but I >> haven't yet >> looked again on Bugzilla. > > Are these also new since his changes? > Vaughan: The best I can do to track this is download and run a Mac nightly that was built before commit 10680. That was Sept 18, and the closest build I can get is Sept 15, so I tried that. The green lines are there: |
From: Vaughan J. <va...@au...> - 2010-11-11 02:19:12
|
(Trying again on a bounced message. These bounces are so random!) On 11/10/2010 6:07 PM, Vaughan Johnson wrote: > On 11/10/2010 5:52 PM, Bill Wharrie wrote: >> >> On 10-Nov-10, at 8:04 PM, Vaughan Johnson wrote: >> >>> >>> >>> On 11/9/2010 6:58 PM, Gale Andrews wrote: >>>> >>> <snip> >> >>>> >>>> The "spurious green lines" is obviously less important but I haven't yet >>>> looked again on Bugzilla. >>> >>> Are these also new since his changes? >>> >> >> Vaughan: >> The best I can do to track this is download and run a Mac nightly that >> was built before commit 10680. That was Sept 18, and the closest build I >> can get is Sept 15, so I tried that. The green lines are there: >> >> >> >> >> In this case I am manipulating the track 1 slider on the mixer board >> while the project plays. Not only are there green lines in the waveform, >> there are little grey lines written in the yellow border. When you stop >> everything is cleared. If you manipulate another slider in the mixer >> board the green and grey lines are cleared but continue in the other >> track as you manipulate the slider. >> >> [A little later] >> >> Guess I could have saved myself some time - the green lines and the >> drawing into the yellow border are there in 1.3.9 but not 1.3.8. Also, >> the error drawing the meters in the mixer board is in 1.3.9 but not 1.3.8. >> >> -- Bill >> >> > > Thanks, Bill. I'll look into that after Roger's changes are backed out. > It should be back to the 1.3.9 code at that time, I think, and I can > then check what changed between 1.3.8 and 1.3.9, that introduced these bugs. > > Thanks, > Vaughan > > > |
From: Vaughan J. <va...@au...> - 2010-11-11 02:20:46
|
PS: Is there a bugzilla entry for the green lines and overdrawn meters? - V On 11/10/2010 6:07 PM, Vaughan Johnson wrote: > On 11/10/2010 5:52 PM, Bill Wharrie wrote: >> >> On 10-Nov-10, at 8:04 PM, Vaughan Johnson wrote: >> >>> >>> >>> On 11/9/2010 6:58 PM, Gale Andrews wrote: >>>> >>> <snip> >> >>>> >>>> The "spurious green lines" is obviously less important but I haven't yet >>>> looked again on Bugzilla. >>> >>> Are these also new since his changes? >>> >> >> Vaughan: >> The best I can do to track this is download and run a Mac nightly that >> was built before commit 10680. That was Sept 18, and the closest build I >> can get is Sept 15, so I tried that. The green lines are there: >> >> >> >> >> In this case I am manipulating the track 1 slider on the mixer board >> while the project plays. Not only are there green lines in the waveform, >> there are little grey lines written in the yellow border. When you stop >> everything is cleared. If you manipulate another slider in the mixer >> board the green and grey lines are cleared but continue in the other >> track as you manipulate the slider. >> >> [A little later] >> >> Guess I could have saved myself some time - the green lines and the >> drawing into the yellow border are there in 1.3.9 but not 1.3.8. Also, >> the error drawing the meters in the mixer board is in 1.3.9 but not 1.3.8. >> >> -- Bill >> >> > > Thanks, Bill. I'll look into that after Roger's changes are backed out. > It should be back to the 1.3.9 code at that time, I think, and I can > then check what changed between 1.3.8 and 1.3.9, that introduced these bugs. > > Thanks, > Vaughan > > > |
From: Bill W. <bi...@go...> - 2010-11-11 02:51:46
|
On 10-Nov-10, at 9:21 PM, Vaughan Johnson wrote: > PS: Is there a bugzilla entry for the green lines and overdrawn > meters? > > - V > Overdrawn meters is bug 252. http://bugzilla.audacityteam.org/show_bug.cgi?id=252 No entry for the green lines. Gale thinks it may already be covered by a current bug report, but I can't find anything. -- Bill |
From: Vaughan J. <va...@au...> - 2010-11-12 01:23:57
|
On 11/10/2010 6:51 PM, Bill Wharrie wrote: > > On 10-Nov-10, at 9:21 PM, Vaughan Johnson wrote: > >> PS: Is there a bugzilla entry for the green lines and overdrawn >> meters? >> >> - V >> > > Overdrawn meters is bug 252. > http://bugzilla.audacityteam.org/show_bug.cgi?id=252 > > No entry for the green lines. Gale thinks it may already be covered by > a current bug report, but I can't find anything. > Gale, can you confirm it has an entry somewhere, or can we please add it to bug 252 (including adding the newer image that shows the green lines)? Thanks for adding the note about introduction into 1.3.9. Thanks, Vaughan |
From: Bill W. <bi...@go...> - 2010-11-11 14:54:29
|
On 10-Nov-10, at 8:52 PM, Bill Wharrie wrote: > > Guess I could have saved myself some time - the green lines and the > drawing into the yellow border are there in 1.3.9 but not 1.3.8. > Also, the error drawing the meters in the mixer board is in 1.3.9 > but not 1.3.8. Looks like I should have tested more carefully - sorry. This may not be a mixer board issue at all. 1) New Project 2) Generate Tone 3) New Audio Track 4) Generate Tone 5) Click in track 1 to give it focus 6) Play 7) Manipulate gain sliders in tracks 1 and 2 8) Stop 9) Click in track 2 to give it focus 10) Play and manipulate gain sliders in tracks 1 and 2 In 1.3.7.1: When you click outside of the waveform (whether on the Play button, in the Track Panel, or anywhere else in the project window) the yellow focus border goes away. You can click in a playing track and the focus border re-appears, but as soon as you click outside the wave (to manipulate the gain slider) the focus border goes away again. There is no spurious drawing in the waveform. In 1.3.8: 1) The focus border does not go away if you click in a control (such as a transport button, mixer toolbar slider, meter, or track gain control), but does go away if you click in "blank" area, or in the Selection toolbar. 2) If a track does not have focus (because you have clicked in the Selection Toolbar), when you click on any track panel gain slider, focus is returned to the last track that had focus. 3) When you click and hold (but do not move) a track gain slider, grey is drawn in the yellow focus border, but the green lines are not drawn in the other track. 4) When you move the slider, green lines are drawn in the other track, but the grey is (mostly) not drawn in the yellow focus border. 5) When you manipulate the other slider, the green lines are cleared, but the grey in the focus border stays, and the green lines appear in the other track. In 1.3.9, add step 4a) View > Mixer Board 1) The green lines are not drawn when manipulating a gain slider in a track panel, whether the mixer board is visible or not. 2) The grey is drawn in the focus border when manipulating a gain slider in a track panel. 3) If you manipulate a gain slider in the mixer board, the green lines are drawn, as well as the grey in the focus border. 4) The meters are drawn properly in the mixer board 1.3.10 seems to behave the same as 1.3.9, Except this is where the meters start being drawn incorrectly in the mixer board. In 1.3.10 the mute and solo buttons are drawn above the meters but in 1.3.9 they are drawn below the meters. Summary: 1.3.7.1: No spurious drawing, and focus border is handled differently from present. 1.3.8: Spurious drawing of grey in focus border and green lines in tracks. 1.3.9: When using track panel gain slider, spurious drawing of grey in focus border occurs but not green lines. When using mixer board gain slider, spurious drawing of grey in focus border and green lines occurs. So, unless you used the mixer board, it appeared that the drawing of the green lines was gone in 1.3.9, leaving the minor annoyance of the grey being drawn in the yellow focus border. -- Bill |
From: Vaughan J. <va...@au...> - 2010-11-12 01:28:38
|
On 11/11/2010 6:54 AM, Bill Wharrie wrote: > > On 10-Nov-10, at 8:52 PM, Bill Wharrie wrote: > >> >> Guess I could have saved myself some time - the green lines and the >> drawing into the yellow border are there in 1.3.9 but not 1.3.8. >> Also, the error drawing the meters in the mixer board is in 1.3.9 >> but not 1.3.8. > > Looks like I should have tested more carefully - sorry. This may not > be a mixer board issue at all. Thanks, Bill. Looks like it should be a separate bug from 252. If there isn't already a bug entry for this, please make one and add the image from your previous message and your discussion of it, below. - Vaughan > > 1) New Project > 2) Generate Tone > 3) New Audio Track > 4) Generate Tone > 5) Click in track 1 to give it focus > 6) Play > 7) Manipulate gain sliders in tracks 1 and 2 > 8) Stop > 9) Click in track 2 to give it focus > 10) Play and manipulate gain sliders in tracks 1 and 2 > > In 1.3.7.1: > When you click outside of the waveform (whether on the Play button, in > the Track Panel, or anywhere else in the project window) the yellow > focus border goes away. You can click in a playing track and the focus > border re-appears, but as soon as you click outside the wave (to > manipulate the gain slider) the focus border goes away again. There is > no spurious drawing in the waveform. > > In 1.3.8: > 1) The focus border does not go away if you click in a control (such > as a transport button, mixer toolbar slider, meter, or track gain > control), but does go away if you click in "blank" area, or in the > Selection toolbar. > 2) If a track does not have focus (because you have clicked in the > Selection Toolbar), when you click on any track panel gain slider, > focus is returned to the last track that had focus. > 3) When you click and hold (but do not move) a track gain slider, grey > is drawn in the yellow focus border, but the green lines are not drawn > in the other track. > 4) When you move the slider, green lines are drawn in the other track, > but the grey is (mostly) not drawn in the yellow focus border. > 5) When you manipulate the other slider, the green lines are cleared, > but the grey in the focus border stays, and the green lines appear in > the other track. > > In 1.3.9, add step 4a) View > Mixer Board > 1) The green lines are not drawn when manipulating a gain slider in a > track panel, whether the mixer board is visible or not. > 2) The grey is drawn in the focus border when manipulating a gain > slider in a track panel. > 3) If you manipulate a gain slider in the mixer board, the green lines > are drawn, as well as the grey in the focus border. > 4) The meters are drawn properly in the mixer board > > 1.3.10 seems to behave the same as 1.3.9, Except this is where the > meters start being drawn incorrectly in the mixer board. In 1.3.10 the > mute and solo buttons are drawn above the meters but in 1.3.9 they are > drawn below the meters. > > Summary: > 1.3.7.1: No spurious drawing, and focus border is handled differently > from present. > 1.3.8: Spurious drawing of grey in focus border and green lines in > tracks. > 1.3.9: When using track panel gain slider, spurious drawing of grey in > focus border occurs but not green lines. When using mixer board gain > slider, spurious drawing of grey in focus border and green lines occurs. > > So, unless you used the mixer board, it appeared that the drawing of > the green lines was gone in 1.3.9, leaving the minor annoyance of the > grey being drawn in the yellow focus border. > > -- Bill > > ------------------------------------------------------------------------------ > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality > |
From: Bill W. <bi...@go...> - 2010-11-12 01:56:01
|
On 11-Nov-10, at 8:22 PM, Vaughan Johnson wrote: > On 11/11/2010 6:54 AM, Bill Wharrie wrote: >> >> On 10-Nov-10, at 8:52 PM, Bill Wharrie wrote: >> >>> >>> Guess I could have saved myself some time - the green lines and the >>> drawing into the yellow border are there in 1.3.9 but not 1.3.8. >>> Also, the error drawing the meters in the mixer board is in 1.3.9 >>> but not 1.3.8. >> >> Looks like I should have tested more carefully - sorry. This may not >> be a mixer board issue at all. > > Thanks, Bill. Looks like it should be a separate bug from 252. If > there > isn't already a bug entry for this, please make one and add the image > from your previous message and your discussion of it, below. > > - Vaughan > http://bugzilla.audacityteam.org/show_bug.cgi?id=255 I've left it as Mac OS X. I recall that Gale said he has seen the green lines on Linux. Don't know if this occurs on Windows. -- Bill |
From: Vaughan J. <va...@au...> - 2010-11-12 02:07:53
|
On 11/11/2010 5:55 PM, Bill Wharrie wrote: > > On 11-Nov-10, at 8:22 PM, Vaughan Johnson wrote: > >> On 11/11/2010 6:54 AM, Bill Wharrie wrote: >>> >>> On 10-Nov-10, at 8:52 PM, Bill Wharrie wrote: >>> >>>> >>>> Guess I could have saved myself some time - the green lines and the >>>> drawing into the yellow border are there in 1.3.9 but not 1.3.8. >>>> Also, the error drawing the meters in the mixer board is in 1.3.9 >>>> but not 1.3.8. >>> >>> Looks like I should have tested more carefully - sorry. This may not >>> be a mixer board issue at all. >> >> Thanks, Bill. Looks like it should be a separate bug from 252. If >> there >> isn't already a bug entry for this, please make one and add the image >> from your previous message and your discussion of it, below. >> >> - Vaughan >> > > http://bugzilla.audacityteam.org/show_bug.cgi?id=255 > > I've left it as Mac OS X. I recall that Gale said he has seen the > green lines on Linux. Don't know if this occurs on Windows. > Wow, we're so synchronized I sent my message one minute after this one (which I of course hadn't seen). Bug doesn't occur on Windows XP. Thanks, V |
From: Vaughan J. <va...@au...> - 2010-11-12 01:56:10
|
On 11/11/2010 5:22 PM, Vaughan Johnson wrote: > On 11/11/2010 6:54 AM, Bill Wharrie wrote: >> >> On 10-Nov-10, at 8:52 PM, Bill Wharrie wrote: >> >> Looks like I should have tested more carefully - sorry. This may not >> be a mixer board issue at all. > > Thanks, Bill. Looks like it should be a separate bug from 252. If there > isn't already a bug entry for this, please make one and add the image > from your previous message and your discussion of it, below. > Thanks for adding bug 255, Bill. I think Gale said it happens on Ubuntu, too, but I'll leave it to him to update and prioritize it. - V |
From: Gale A. <ga...@au...> - 2010-11-11 01:53:26
|
| From Vaughan Johnson <va...@au...> | Wed, 10 Nov 2010 17:04:54 -0800 | Subject: [Audacity-quality] Mixer Board issues > On 11/9/2010 6:58 PM, Gale Andrews wrote: > > > > | From Bill Wharrie <bi...@go...> > > | Tue, 9 Nov 2010 14:17:48 -0500 > > | Subject: [Audacity-quality] Mixer Board issues > >> > >> On 3-Nov-10, at 2:48 PM, Gale Andrews wrote: > >> > >> <snip> > >> > >>> I've played around more in Ubuntu and rebooted several times > >>> (and initialised .cfg). I still can't reproduce your 1a) through to > >>> f), > >>> but both of these give a 100% repeatable segfault: > >>> > >>> 1) a) New Project > >>> b) Tracks > Add New > Audio Track > >>> c) Record (i.e. in stereo, which should open a new stereo track) > >>> > >>> 2) a) New Project > >>> b) Tracks > Add New > Audio Track > >>> c) View > Mixer Board > >>> d) Generate > Tone > >>> > >>> If in 1) I replace c) with Generate > Tone, there is never a crash. > >>> My 1) or 2) don't repro in Win 7. So it looks as if it could be an > >>> issue > >>> with Tracks > Add New > Audio Track, but I'm not sure what changed > >>> there since 1.3.12? Can you repro either of my 1) or 2)? > >> > >> > >> More testing on Gale's two sequences. > >> > >> 1) I cannot get this to crash on any of the three machines I have > >> access to. > >> > >> 2) This crashes on all three machines: > >> OS X 10.5.8 PPC G5 > >> OS X 10.4.11 PPC G4 Powerbook > >> OS X 10.4.11 Intel Core Two Duo. > > > > Sorry I've been silent on this. I have though been doing some playing > > around myself and 3) below crashes 100% for me on Win 7 and Ubuntu > > in two scenarios (first) with only USE_MIDI defined (as in released > > builds) and (second) with USE_MIDI and EXPERIMENTAL_MIDI_OUT > > both defined (which allows MIDI playback and adds that "Velocity" > > slider to Mixer Board): > > > > 3) a) Add an audio track (either generate or import will reproduce) > > b) Import a MIDI > > c) View > Mixer Board > > d) Click X top left to remove the MIDI > > e) Edit > Undo > > f) Edit > Redo > > > > It isn't predictable whether the crash will occur in d), e) or f), but one > > of those three will always crash for me. > > > > So we have three "similar, but not the same" crashes. Can you (Bill) > > repro 3)? You only need to test with USE_MIDI on as in the Nightly. > > > > The only common factor for me in all three is "adding a new track" > > (but not necessarily with Tracks > Add New > Audio Track). You have > > a second common factor in Mixer Board. > > I looked into this, and it's another bug introduced by Roger's commit > 10680. When I said it was okay for him to make these changes, it was > with the understanding that they would all be under > EXPERIMENTAL_MIDI_OUT and not threaten our code stability with that > turned off. > > In fixing bug 250 and looking into this, I've found he did a *lot* of it > under USE_MIDI and even more with no flag at all. I'm disappointed in > this and am going to back out his changes. More generally, I wouldn't personally regard USE_MIDI as a must for 2.0. Does this switch on the extra MIDI features that 1.2 doesn't have (MIDI "cut and paste editing" and export) or also control MIDI import? Neither the 1.2 or 1.3.13 current MIDI features are going to seriously impress MIDI users. In fact I think the MIDI "features" in 1.3.13 look very unfinished, and will always do until we at least get stable MIDI playback. > > The "spurious green lines" is obviously less important but I haven't yet > > looked again on Bugzilla. > > Are these also new since his changes? Various ways to create "green lines" have been in Linux builds for most of this year. > >> When launching Audacity after the crash [in 2)] I get the crash recovery > >> dialog. If I choose to recover the project the error log shows: > >> > >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e00000b1.au' > >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e00002d4.au' > >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e000031d.au' > >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e0000334.au' > >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e000077a.au' > >> 14:06:18: Warning: Orphan blockfile: '/var/folders/5-/5-ACi0S52RWwp+ > >> +kNLU2y++++TI/-Tmp-/audacity-Bill/project1651748620/e00/d00/e0000da8.au' > >> 14:06:18: Warning: Project check ignored orphan blockfile(s). They > >> will be deleted when project is saved. > >> 14:06:19: Warning: Project check found file inconsistencies inspecting > >> the loaded project data. > >> > >> And the project window opens with the empty mono audio track. > > > > Bug 20 possibly strikes again: > > http://bugzilla.audacityteam.org/show_bug.cgi?id=20 > > Much more likely a newly introduced bug. Has anyone in testing Bug 20 simulated a crash by trying to make it happen when the autosave file was in course of being written? Am I correct in thinking this could be the core problem? I agree the fact that an orphan is falsely reported could make it newly introduced, but I only did one test. Gale > > On Ubuntu if I run 2) and recover the project after the crash, I get > > an empty mono track as you do. > > > > It should I think recover the tone as it is there in the .au files in /tmp > > (unless you would argue the crash has not left time for the autosave > > file to be written properly). The autosave file only lists one .au file. > > That .au is in the /tmp folder, but it is still reported as an orphan in > > the log, along with five others not in the autosave file. > > > > On Windows, if I force quit after following 2) through, recovery is OK. > > > > I'll add this "failed recovery" scenario to Bug 20, unless Vaughan > > thinks it's unreasonable to recover the tone in this case. > > > > > >> Gale, do we need more testers/reports before raising a bug? Should we > >> ask on the forum? > > > > I don't think so, once you've tested 3). There should be three repeatable > > crashes a developer on the appropriate platform can get their teeth into. > > It just depends if we group them or not; partly this may depend what > > you find with 3). > > > > Help from the Forum testing fixes to these crashes may be good. More > > generally, Crash Recovery (Bug 20) really does need heavy testing on > > Mac with multiple scenarios because two-thirds of the problem reports > > about it were on that platform. Enlisting the Mac Forum to help with > > Bug 20 testing may be a good idea. > > > > > > > > > > > > Gale |