Thread: [Audacity-devel] Mac OS X: Crash in prefs
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Matt B. <mbr...@cs...> - 2004-12-14 16:46:52
|
Several users have reported this problem: Audacity crashes under Mac OS X when clicking "OK" in the Preferences window. Can any Mac developers take a look at this? If you can't reproduce the bug, a memory-debugging tool (like Electric Fence or Valgrind) might help. I also suspect the bug is in wxWidgets, since that's been the case with many platform-specific crashes. ---------- Forwarded message ---------- From: Jeffrey Tveraas To: audacity-help Date: Tue, 14 Dec 2004 Subject: Audacity 1.2.3 crashes I have been unable to use your software without it crashing right away whenever I attempt to alter any of the preferences. i am using a Mac G4/733 with 1.12 GB of RAM and OS 10.3.4. I make sure nothing else is running when I open your app. It's kinda like that old joke about "doctor, it hurts whenever I do "this"...so don't do that!". I wish I could be more specific but it doesn't seem to matter which preferences I try to adjust, once I click on "OK" it sits there for a second and then just disappears. Can you offer any suggestions? |
From: Otto W. <ott...@or...> - 2004-12-14 17:20:46
|
Matt Brubeck wrote: > > Can any Mac developers take a look at this? If you can't reproduce the > bug, a memory-debugging tool (like Electric Fence or Valgrind) might > help. I also suspect the bug is in wxWidgets, since that's been the > case with many platform-specific crashes. > It depends what features are used in the prefs. I've discovered two crashes within wxWidgets 2.4.2 GTK which probably also are in MacOSX. One is when a notebook page is removed (deleted), sometimes only when it's the last. There is a fix in my demo sample at wxGuide (see BuildInfo.txt). The other is when in a combobox its entries are removed (cleared). So far there isn't a fix neither for 2.4.2 nor 2.5.3 I simply disabled all dynamic handling of combobox entries when __WXGTK__. Again see the demo sample. O. Wyss -- Development of frame buffer drivers: http://linux-fbdev.sf.net Sample code snippets for wxWidgets: http://wxcode.sf.net How to build well-designed applications: http://wxguide.sf.net Desktop with a consistent look and feel: http://wyodesktop.sf.net |
From: Bill P. <dub...@ya...> - 2004-12-14 17:52:37
|
Hi, I can't reproduce the bug either in the release binary or my own build (using wx 2.5.3). Electric Fence appears to be a 2.6 GB download, and the PPC version of Valgrind is experimental... perhaps I can try building in CodeWarrior or Xcode and using either's step debugger unless anyone has some other ideas (command-line gdb? which I have no experience with...) - Bill --- Matt Brubeck <mbr...@cs...> wrote: > Several users have reported this problem: Audacity crashes under Mac OS > X when clicking "OK" in the Preferences window. > > Can any Mac developers take a look at this? If you can't reproduce the > bug, a memory-debugging tool (like Electric Fence or Valgrind) might > help. I also suspect the bug is in wxWidgets, since that's been the > case with many platform-specific crashes. > > ---------- Forwarded message ---------- > From: Jeffrey Tveraas > To: audacity-help > Date: Tue, 14 Dec 2004 > Subject: Audacity 1.2.3 crashes > > I have been unable to use your software without it crashing right away > whenever I attempt to alter any of the preferences. i am using a Mac > G4/733 with 1.12 GB of RAM and OS 10.3.4. I make sure nothing else is > running when I open your app. It's kinda like that old joke about > "doctor, it hurts whenever I do "this"...so don't do that!". I wish I > could be more specific but it doesn't seem to matter which preferences > I try to adjust, once I click on "OK" it sits there for a second and > then just disappears. Can you offer any suggestions? > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Audacity-devel mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail |
From: Matt B. <mbr...@cs...> - 2004-12-14 18:05:23
|
Bill Preder wrote: > Electric Fence appears to be a 2.6 GB download, and the PPC version of > Valgrind is experimental... No, Electric Fence is actually quite tiny. :) It's the United States census map that's 2.6 GB: http://perens.com/FreeSoftware/ However, e-fence is pretty limited for memory debugging. Valgrind-style systems are much more useful, but I don't know if there's a good free one yet for Mac OS X/PowerPC. I'll try running Valgrind on Linux/i386, but this won't catch the bug if it's in Mac-specific wxWidgets code. |
From: Bill P. <dub...@ya...> - 2004-12-14 18:22:08
|
er, I knew that, I was just testing you! ;-) Now for some coffee... - Bill --- Matt Brubeck <mbr...@cs...> wrote: > > No, Electric Fence is actually quite tiny. :) It's the United States > census map that's 2.6 GB: > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail |
From: Dominic M. <do...@au...> - 2004-12-14 19:08:00
|
On Dec 14, 2004, at 8:46 AM, Matt Brubeck wrote: > Several users have reported this problem: Audacity crashes under Mac > OS > X when clicking "OK" in the Preferences window. I think that the probem might be as simple as a system that doesn't have any input devices that were recognized. Audacity is trying to access the 0th or -1st element of an array that has zero items in it. Could anyone reproduce this on Linux? Temporarily rename /dev/dsp so that there are no detected audio devices, and see if that crashes? If not, perhaps the best solution would be for me to post a version of Audacity that includes gdb's debugging information. Then when it crashes, the user just needs to click on the "More info" button and copy and paste the stack trace into an email to us. (Yay for Apple for making it so easy for non-programmers to send useful crash reports!) - Dominic > Can any Mac developers take a look at this? If you can't reproduce the > bug, a memory-debugging tool (like Electric Fence or Valgrind) might > help. I also suspect the bug is in wxWidgets, since that's been the > case with many platform-specific crashes. > > ---------- Forwarded message ---------- > From: Jeffrey Tveraas > To: audacity-help > Date: Tue, 14 Dec 2004 > Subject: Audacity 1.2.3 crashes > > I have been unable to use your software without it crashing right away > whenever I attempt to alter any of the preferences. i am using a Mac > G4/733 with 1.12 GB of RAM and OS 10.3.4. I make sure nothing else is > running when I open your app. It's kinda like that old joke about > "doctor, it hurts whenever I do "this"...so don't do that!". I wish I > could be more specific but it doesn't seem to matter which preferences > I try to adjust, once I click on "OK" it sits there for a second and > then just disappears. Can you offer any suggestions? > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Audacity-devel mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Otto W. <ott...@or...> - 2004-12-14 20:27:26
|
Dominic Mazzoni wrote: > > If not, perhaps the best solution would be for me to post a version of > Audacity that includes gdb's debugging information. Then when it > crashes, the user just needs to click on the "More info" button and > copy and paste the stack trace into an email to us. (Yay for Apple for > making it so easy for non-programmers to send useful crash reports!) > Or use wxCrashPrint from wxCode "http://wxcode.sourceforge.net/index.php?page=complist.php". O. Wyss -- Development of frame buffer drivers: http://linux-fbdev.sf.net Sample code snippets for wxWidgets: http://wxcode.sf.net How to build well-designed applications: http://wxguide.sf.net Desktop with a consistent look and feel: http://wyodesktop.sf.net |
From: Dave F. <dav...@da...> - 2004-12-14 20:37:44
|
On Tuesday 14 December 2004 01:07 pm, Dominic Mazzoni wrote: > crashes, the user just needs to click on the "More info" button and > copy and paste the stack trace into an email to us. (Yay for Apple for > making it so easy for non-programmers to send useful crash reports!) So OS X really is a cheap ripoff of KDE? *dodge* Sorry, my brain just returned, looks like it's starting to produce it's own acetylchloramine again, and I'm in a playful mood. Dave -- Visit my website! http://www.davefancella.com/?event=em Rascal, am I? Take THAT! -- Errol Flynn |
From: <xip...@xi...> - 2004-12-14 22:06:35
|
On Tue, Dec 14, 2004 at 11:07:55AM -0800, Dominic Mazzoni wrote: > On Dec 14, 2004, at 8:46 AM, Matt Brubeck wrote: > >Several users have reported this problem: Audacity crashes under Mac > >OS > >X when clicking "OK" in the Preferences window. > > I think that the probem might be as simple as a system that doesn't > have any input devices that were recognized. Audacity is trying to > access the 0th or -1st element of an array that has zero items in it. I patched exactly that bug on HEAD in July and mentioned it to others at the time, but it looks like we all might have forgotten to apply a fix to the 1.2 branch. Assumign that's what it is. Monty |
From: Shane M. <smu...@ob...> - 2004-12-16 05:40:46
|
One thing that often happens when you are transcribing recorded sound is that it never plays at the speed you want it to. It is either too fast (i.e., dictated speech), or too slow (searching for a single quote in a 50-min lecture). I have added a slider and a button to the transcription toolbar on CVS head that allows you to playback at a set speed. This is still experimental, and I encourage people to make any changes they wish and figure out ways to improve it. I don't know if having a separate 'play-at-speed' play button is the best idea; maybe it should route through the normal play button. This just speeds up playback, like if you were slowing down/speeding up a cassette tape. It is not really hooked in to the whole control toolbar logic right now, and so may cause problems in various ways, and may not work perfectly with pause/stop/etc. It works by making an invisible time track whose values get set by the slider. It gets passed into the whole audioIO machinery that deals with timetrack shifting. Currently, the start/stop times are correct, but the cursor doesn't get warped correctly--I would have to make the time track accessible to the trackpanel in some way for this to work out. Here are some of the notes on the changes: * ASliders can now take on the different lwslider forms (new constructor), and there is a new slider style: SPEED_SLIDER, which goes from 0 to 5 continuously. * I #ifdef'ed out that pragma warning in Track.h that was causing a thousand warning messages during compile time on linux. #pragma is supposed to be compiler-specific, so it should probably be our practice to make sure they only get used by the compiler they are intended for. But, they were not documented, so I'm not sure why they were in there or what they were for. * The MakeButton function in ToolBar overlayed an image onto a button, with a specified offset adjustment. For boring but necessary reasons, I changed the logic so that it automatically centers the icon on the button, and then adjusts from there using the old offset parameters, which can get set to 0 (or +/- 1 if you want to monkey with things). I think I fixed everything that was affected, but things may look strange on the Mac or something, and could need tweaking. * It would be nice for sliders to have a manual value entry dialog available via double-click or ctrl-click or something. * It would also be cool to have a log-scale slider. Stm... |
From: David R. S. <sk...@wa...> - 2004-12-16 07:59:17
|
As someone who uses a screen reader with Audacity and all other computer apps, I appreciate making Audacity more keyboard-command friendly. I like your idea of being able to slow down and speed up audio playback. Especially if this could be integrated with ability to set start and end markers using the keyboard. And made so that those markers cannot be disturbed except with _deliberate_ reassignment of the marker positions. thanks David On Wed, 15 Dec 2004, Shane Mueller wrote: > One thing that often happens when you are transcribing recorded sound is > that it never plays at the speed you want it to. It is either too fast > (i.e., dictated speech), or too slow (searching for a single quote in a > 50-min lecture). > > I have added a slider and a button to the transcription toolbar on CVS > head that allows you to playback at a set speed. This is still > experimental, and I encourage people to make any changes they wish and > figure out ways to improve it. I don't know if having a separate > 'play-at-speed' play button is the best idea; maybe it should route > through the normal play button. This just speeds up playback, like if > you were slowing down/speeding up a cassette tape. It is not really > hooked in to the whole control toolbar logic right now, and so may cause > problems in various ways, and may not work perfectly with > pause/stop/etc. > > It works by making an invisible time track whose values get set by the > slider. It gets passed into the whole audioIO machinery that deals with > timetrack shifting. Currently, the start/stop times are correct, but > the cursor doesn't get warped correctly--I would have to make the time > track accessible to the trackpanel in some way for this to work out. > > Here are some of the notes on the changes: > > * ASliders can now take on the different lwslider forms (new > constructor), and there is a new slider style: SPEED_SLIDER, which goes > from 0 to 5 continuously. > > * I #ifdef'ed out that pragma warning in Track.h that was causing a > thousand warning messages during compile time on linux. #pragma is > supposed to be compiler-specific, so it should probably be our practice > to make sure they only get used by the compiler they are intended for. > But, they were not documented, so I'm not sure why they were in there or > what they were for. > > * The MakeButton function in ToolBar overlayed an image onto a button, > with a specified offset adjustment. For boring but necessary reasons, I > changed the logic so that it automatically centers the icon on the > button, and then adjusts from there using the old offset parameters, > which can get set to 0 (or +/- 1 if you want to monkey with things). I > think I fixed everything that was affected, but things may look strange > on the Mac or something, and could need tweaking. > > * It would be nice for sliders to have a manual value entry dialog > available via double-click or ctrl-click or something. > > * It would also be cool to have a log-scale slider. > > Stm... > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Audacity-devel mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > -- |
From: Vaughan J. <vjo...@co...> - 2004-12-16 23:04:04
|
Cool, Shane. I can't get the slider back to 1.0x, but the feature sure seems useful. Be nice if it could do the speed change while playing. -Vaughan |