[Gwc-general] Odd error (only every other time I playback) using
gwc with pulseaudio on ubuntu 12.10
From: Chris G. <cl...@is...> - 2013-01-24 13:59:53
|
I have just installed Gnome Wave Cleaner version 0.21-17 on my xubuntu 12.10 system, it works very well for me but there is one odd little bug I would like to clear up. When I use the icons to start and stop playing a section of a recording they work one time and then fail with two pop-up errors:- Warning audio_device_open: pa_simple_new then Warning Failed to open output device default:, check settings->miscellaneous for device information If I click OK on both of these then the next time I click the Play icon it plays OK. I have tried changing the device in settings->miscellaneous from /dev/dsp to default: but it seems to have made no difference. While I'm about it what's the correct device to use when using gwc with pulseaudio, I couldn't find any information on this. -- Chris Green |
From: John C. <ci...@pu...> - 2013-01-24 16:05:04
|
I seem to remember this happened a few years ago and in my case was caused by the KDE notification timeout defaulting to something too long, like 5 seconds or so. Because of that, the audio system really was temporarily busy, but for no useful reason. After I changed the KDE event notification timeout to 1 second, all was well from then on. Something to check. Not sure if other window managers have something similar. John Cirillo On 1/24/2013 8:59 AM, Chris Green wrote: > I have just installed Gnome Wave Cleaner version 0.21-17 on my xubuntu > 12.10 system, it works very well for me but there is one odd little > bug I would like to clear up. > > When I use the icons to start and stop playing a section of a recording > they work one time and then fail with two pop-up errors:- > > Warning > audio_device_open: pa_simple_new > > then > > Warning > Failed to open output device default:, check settings->miscellaneous > for device information > > > If I click OK on both of these then the next time I click the Play icon > it plays OK. > > I have tried changing the device in settings->miscellaneous from > /dev/dsp to default: but it seems to have made no difference. > > While I'm about it what's the correct device to use when using gwc with > pulseaudio, I couldn't find any information on this. > |
From: John C. <ci...@pu...> - 2013-01-24 18:54:58
|
On 1/24/2013 12:07 PM, Chris Green wrote: > On Thu, Jan 24, 2013 at 11:04:58AM -0500, John Cirillo wrote: >> I seem to remember this happened a few years ago and in my >> case was caused by the KDE >> notification timeout defaulting to something too long, like >> 5 seconds or so. >> Because of that, the audio system really was temporarily >> busy, but for no useful reason. >> After I changed the KDE event notification timeout to 1 >> second, all was well from then on. >> Something to check. Not sure if other window managers have >> something similar. >> > I don't run KDE but I do have a KDE application (k3b) so it *might* be > the KDE event notification. Do you know where I might be able to see > and/or change the KDE event notification timeout without the KDE GUI > running? > I don't think that the KDE sound system nor notification system is running if you aren't using KDE. Doesn't matter if you have some KDE apps installed. But as to where KDE sets this, I couldn't find it. I tried changing my timeout from within the GUI and couldn't find any altered config file either in the .kde directory under my user, or in /usr/share/kde4. Sorry. John >> On 1/24/2013 8:59 AM, Chris Green wrote: >>> I have just installed Gnome Wave Cleaner version 0.21-17 on my xubuntu >>> 12.10 system, it works very well for me but there is one odd little >>> bug I would like to clear up. >>> >>> When I use the icons to start and stop playing a section of a recording >>> they work one time and then fail with two pop-up errors:- >>> >>> Warning >>> audio_device_open: pa_simple_new >>> >>> then >>> >>> Warning >>> Failed to open output device default:, check settings->miscellaneous >>> for device information >>> >>> >>> If I click OK on both of these then the next time I click the Play icon >>> it plays OK. >>> >>> I have tried changing the device in settings->miscellaneous from >>> /dev/dsp to default: but it seems to have made no difference. >>> >>> While I'm about it what's the correct device to use when using gwc with >>> pulseaudio, I couldn't find any information on this. >>> > |
From: jeff w. <we...@ya...> - 2013-01-28 01:30:08
|
Hi Chris, I think John Cirillo was on the right track, sort of. But I think also the way GWC connect to pulse audio might have a bug. I hadn't compiled and run gwc for a while, and I just did on my Fedora Core 17 machine, running the gnome window manager. With nothing else running, I have no problems with playback. But, if I crank up a streaming application (like grooveshark), in firefox, I get the same problem you have described, play only works every other time. If I get a chance, I'll poke around at the pulse audio code for GWC. When I imlemented it pulse audio was still pretty young so I didn't work too hard at it. Maybe there is an error return that the code can sense and attempt a reconnect to the audio driver automatically instead of just failing and popping up the error dialog. Thanks for trying GWC and especially thanks for reporting the problem! Cheers, Jeff ________________________________ From: Chris Green <cl...@is...> To: gwc...@li... Sent: Friday, January 25, 2013 7:09 AM Subject: Re: [Gwc-general] Odd error (only every other time I playback) using gwc with pulseaudio on ubuntu 12.10 On Thu, Jan 24, 2013 at 01:54:44PM -0500, John Cirillo wrote: > On 1/24/2013 12:07 PM, Chris Green wrote: > > On Thu, Jan 24, 2013 at 11:04:58AM -0500, John Cirillo wrote: > >> I seem to remember this happened a few years ago and in my > >> case was caused by the KDE > >> notification timeout defaulting to something too long, like > >> 5 seconds or so. > >> Because of that, the audio system really was temporarily > >> busy, but for no useful reason. > >> After I changed the KDE event notification timeout to 1 > >> second, all was well from then on. > >> Something to check. Not sure if other window managers have > >> something similar. > >> > > I don't run KDE but I do have a KDE application (k3b) so it *might* be > > the KDE event notification. Do you know where I might be able to see > > and/or change the KDE event notification timeout without the KDE GUI > > running? > > > I don't think that the KDE sound system nor notification > system is running if you aren't using KDE. Doesn't matter > if you have some KDE apps installed. But as to where KDE > sets this, I couldn't find it. I tried changing my timeout > from within the GUI and couldn't find any altered config > file either in the .kde directory under my user, or in > /usr/share/kde4. Sorry. > OK, thanks for looking anyway. -- Chris Green ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Gwc-general mailing list Gwc...@li... https://lists.sourceforge.net/lists/listinfo/gwc-general |
From: jeff w. <we...@ya...> - 2013-02-02 03:04:58
|
I just uploaded 0.21-18 to sourceforge. I found a bug in the way gwc was connecting to pulse audio and checking for the failure to connect. This explains the mysterious and erratic messages gwc was generating about not opening the pulse audio every other time, but only under certain circumstances. Give it a try when you can. Cheers, Jeff ________________________________ From: Chris Green <cl...@is...> To: "gwc...@li..." <gwc...@li...> Sent: Monday, January 28, 2013 1:33 AM Subject: Re: [Gwc-general] Odd error (only every other time I playback) using gwc with pulseaudio on ubuntu 12.10 On Sun, Jan 27, 2013 at 05:30:00PM -0800, jeff welty wrote: > Hi Chris, > I think John Cirillo was on the right track, sort of. But I think also > the way GWC connect to pulse audio might have a bug. I hadn't compiled > and run gwc for a while, and I just did on my Fedora Core 17 machine, > running the gnome window manager. > With nothing else running, I have no problems with playback. > But, if I crank up a streaming application (like grooveshark), in firefox, > I get the same problem you have described, play only works every other > time. Thanks for taking a look. It's not quite as consistently 'every other time' as I originally thought and *seems* to act rather differently if I use the space bar to start and stop rather than the icons. It still happens using the space bar though. I think (among other things) I have Music Player Daemon running on the same system so there's at least one other pulseaudio client, I might try stopping it (MPD) to see if that fixes it. > If I get a chance, I'll poke around at the pulse audio code for GWC. When > I imlemented it pulse audio was still pretty young so I didn't work too > hard at it. Maybe there is an error return that the code can sense and > attempt a reconnect to the audio driver automatically instead of just > failing and popping up the error dialog. > Thanks for trying GWC and especially thanks for reporting the problem! If there's anything I can do to help investigate/debug then please ask. -- Chris Green ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Gwc-general mailing list Gwc...@li... https://lists.sourceforge.net/lists/listinfo/gwc-general |
From: jeff w. <we...@ya...> - 2013-02-02 14:31:50
|
When you run the configure script, by default gwc will use the ALSA sound driver. So find the pulse audio development libraries (not sure what they are called on ubuntu), then try: "configure --enable-pa" (configure should print a little message about using pulse audio, if it doesn't then you don't have the correct pulse audio development libs installed) Once that succeeds, do: "rm *.o" "make" ________________________________ From: Chris Green <cl...@is...> To: "gwc...@li..." <gwc...@li...> Sent: Saturday, February 2, 2013 4:26 AM Subject: Re: [Gwc-general] Odd error (only every other time I playback) using gwc with pulseaudio on ubuntu 12.10 On Fri, Feb 01, 2013 at 07:04:47PM -0800, jeff welty wrote: > I just uploaded 0.21-18 to sourceforge. I found a bug in the way gwc was > connecting to pulse audio and checking for the failure to connect. This > explains the mysterious and erratic messages gwc was generating about not > opening the pulse audio every other time, but only under certain > circumstances. > Give it a try when you can. Thanks! It took a while to get all the required dependencies as I needed lots of xxxx-dev packages where I only had the basic libraries. In particular libgnomeui-dev pulled in dozens of further dependencies. However once configure had done its worst it built OK and.... oh dear, now it just fails every time I try playback, with the message:- Failed to open Pulse audio output device, recommend internet search about pulse audion configuration for your OS Wierdly the default version 0.21-17 is now working faultlessly however often I start and stop playback! -- Chris Green ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Gwc-general mailing list Gwc...@li... https://lists.sourceforge.net/lists/listinfo/gwc-general |
From: Chris G. <cl...@is...> - 2013-02-02 16:06:18
|
On Sat, Feb 02, 2013 at 06:31:42AM -0800, jeff welty wrote: > When you run the configure script, by default gwc will use the ALSA sound > driver. > So find the pulse audio development libraries (not sure what they are > called on ubuntu), then try: > "configure --enable-pa" Ah! :-) > (configure should print a little message about using pulse audio, if it > doesn't then you don't have the correct pulse audio development libs > installed) Exactly, I had to install libpulse-dev. It would be good if configure output an error if you ask for --enable-pa and the library/headers aren't there. > Once that succeeds, do: > "rm *.o" > "make" > Yes, I have a fully working 0.21-18 now and I'm not getting any errors. When run from the command line it reports:- Current stack limit: 8388608 bytes libsndfile Version: libsndfile-1.0.25 1 0 25 Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device ... ... Which looks quite encouraging. Thanks for all the help and hard work! -- Chris Green |
From: Chris G. <cl...@is...> - 2013-01-24 17:07:31
|
On Thu, Jan 24, 2013 at 11:04:58AM -0500, John Cirillo wrote: > I seem to remember this happened a few years ago and in my > case was caused by the KDE > notification timeout defaulting to something too long, like > 5 seconds or so. > Because of that, the audio system really was temporarily > busy, but for no useful reason. > After I changed the KDE event notification timeout to 1 > second, all was well from then on. > Something to check. Not sure if other window managers have > something similar. > I don't run KDE but I do have a KDE application (k3b) so it *might* be the KDE event notification. Do you know where I might be able to see and/or change the KDE event notification timeout without the KDE GUI running? > On 1/24/2013 8:59 AM, Chris Green wrote: > > I have just installed Gnome Wave Cleaner version 0.21-17 on my xubuntu > > 12.10 system, it works very well for me but there is one odd little > > bug I would like to clear up. > > > > When I use the icons to start and stop playing a section of a recording > > they work one time and then fail with two pop-up errors:- > > > > Warning > > audio_device_open: pa_simple_new > > > > then > > > > Warning > > Failed to open output device default:, check settings->miscellaneous > > for device information > > > > > > If I click OK on both of these then the next time I click the Play icon > > it plays OK. > > > > I have tried changing the device in settings->miscellaneous from > > /dev/dsp to default: but it seems to have made no difference. > > > > While I'm about it what's the correct device to use when using gwc with > > pulseaudio, I couldn't find any information on this. > > -- Chris Green |
From: Chris G. <cl...@is...> - 2013-01-25 15:09:30
|
On Thu, Jan 24, 2013 at 01:54:44PM -0500, John Cirillo wrote: > On 1/24/2013 12:07 PM, Chris Green wrote: > > On Thu, Jan 24, 2013 at 11:04:58AM -0500, John Cirillo wrote: > >> I seem to remember this happened a few years ago and in my > >> case was caused by the KDE > >> notification timeout defaulting to something too long, like > >> 5 seconds or so. > >> Because of that, the audio system really was temporarily > >> busy, but for no useful reason. > >> After I changed the KDE event notification timeout to 1 > >> second, all was well from then on. > >> Something to check. Not sure if other window managers have > >> something similar. > >> > > I don't run KDE but I do have a KDE application (k3b) so it *might* be > > the KDE event notification. Do you know where I might be able to see > > and/or change the KDE event notification timeout without the KDE GUI > > running? > > > I don't think that the KDE sound system nor notification > system is running if you aren't using KDE. Doesn't matter > if you have some KDE apps installed. But as to where KDE > sets this, I couldn't find it. I tried changing my timeout > from within the GUI and couldn't find any altered config > file either in the .kde directory under my user, or in > /usr/share/kde4. Sorry. > OK, thanks for looking anyway. -- Chris Green |
From: Chris G. <cl...@is...> - 2013-01-28 09:33:38
|
On Sun, Jan 27, 2013 at 05:30:00PM -0800, jeff welty wrote: > Hi Chris, > I think John Cirillo was on the right track, sort of. But I think also > the way GWC connect to pulse audio might have a bug. I hadn't compiled > and run gwc for a while, and I just did on my Fedora Core 17 machine, > running the gnome window manager. > With nothing else running, I have no problems with playback. > But, if I crank up a streaming application (like grooveshark), in firefox, > I get the same problem you have described, play only works every other > time. Thanks for taking a look. It's not quite as consistently 'every other time' as I originally thought and *seems* to act rather differently if I use the space bar to start and stop rather than the icons. It still happens using the space bar though. I think (among other things) I have Music Player Daemon running on the same system so there's at least one other pulseaudio client, I might try stopping it (MPD) to see if that fixes it. > If I get a chance, I'll poke around at the pulse audio code for GWC. When > I imlemented it pulse audio was still pretty young so I didn't work too > hard at it. Maybe there is an error return that the code can sense and > attempt a reconnect to the audio driver automatically instead of just > failing and popping up the error dialog. > Thanks for trying GWC and especially thanks for reporting the problem! If there's anything I can do to help investigate/debug then please ask. -- Chris Green |
From: Chris G. <cl...@is...> - 2013-02-02 12:26:57
|
On Fri, Feb 01, 2013 at 07:04:47PM -0800, jeff welty wrote: > I just uploaded 0.21-18 to sourceforge. I found a bug in the way gwc was > connecting to pulse audio and checking for the failure to connect. This > explains the mysterious and erratic messages gwc was generating about not > opening the pulse audio every other time, but only under certain > circumstances. > Give it a try when you can. Thanks! It took a while to get all the required dependencies as I needed lots of xxxx-dev packages where I only had the basic libraries. In particular libgnomeui-dev pulled in dozens of further dependencies. However once configure had done its worst it built OK and.... oh dear, now it just fails every time I try playback, with the message:- Failed to open Pulse audio output device, recommend internet search about pulse audion configuration for your OS Wierdly the default version 0.21-17 is now working faultlessly however often I start and stop playback! -- Chris Green |
From: jeff w. <we...@ya...> - 2013-02-03 19:26:10
|
Yay! Looks like there is still a bug in the warning message printed out making you think gwc is using the pulsaudio device, when it really is using alsa from the configure. I'll think about that a little bit too, but it's an annoyance, not a showstopper for the moment. Thanks for being a tester! Happy denoising! Jeff ________________________________ From: Chris Green <cl...@is...> To: "gwc...@li..." <gwc...@li...> Sent: Saturday, February 2, 2013 8:06 AM Subject: Re: [Gwc-general] Odd error (only every other time I playback) using gwc with pulseaudio on ubuntu 12.10 On Sat, Feb 02, 2013 at 06:31:42AM -0800, jeff welty wrote: > When you run the configure script, by default gwc will use the ALSA sound > driver. > So find the pulse audio development libraries (not sure what they are > called on ubuntu), then try: > "configure --enable-pa" Ah! :-) > (configure should print a little message about using pulse audio, if it > doesn't then you don't have the correct pulse audio development libs > installed) Exactly, I had to install libpulse-dev. It would be good if configure output an error if you ask for --enable-pa and the library/headers aren't there. > Once that succeeds, do: > "rm *.o" > "make" > Yes, I have a fully working 0.21-18 now and I'm not getting any errors. When run from the command line it reports:- Current stack limit: 8388608 bytes libsndfile Version: libsndfile-1.0.25 1 0 25 Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device Closing the Pulse audio device Open the Pulse audio device ... ... Which looks quite encouraging. Thanks for all the help and hard work! -- Chris Green ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Gwc-general mailing list Gwc...@li... https://lists.sourceforge.net/lists/listinfo/gwc-general |