Anybody having issues with artsd consuming 100% cpu and continually restarting with the latest update?
On Friday 29 April 2005 22:09, tim_mcmullen@comcast.net wrote:
Anybody having issues with artsd consuming 100% cpu and continually restarting with the latest update?
doesn't artsd always do that? ;)
no, really... arts is a bad thing to use... better use applications that use alsa directly and not with a daemon! the same for esd
freddy
you don't get it.. kde and gnome where designed so that their applications work transparently over the network. if you don't use esd or arts, network transparent audio is not available. you'll probably never see true gnome or kde apps using alsa directly. what you might see is new and better sound servers become available. its too bad the alsa guys don't just add some kind of NAS to their official software distribution and make it work flawlessly with their drivers/sound.
----- Original Message ----- From: "Frederick Alexander Thomssen" ml-fedora@fathomssen.de To: "Development discussions related to Fedora Core" fedora-devel-list@redhat.com Sent: Friday, April 29, 2005 3:14 PM Subject: Re: ARTSD
On Friday 29 April 2005 22:09, tim_mcmullen@comcast.net wrote:
Anybody having issues with artsd consuming 100% cpu and continually restarting with the latest update?
doesn't artsd always do that? ;)
no, really... arts is a bad thing to use... better use applications that use alsa directly and not with a daemon! the same for esd
freddy
-- Frederick Alexander Thomssen
-- fedora-devel-list mailing list fedora-devel-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-devel-list
On Friday 29 April 2005 17:56, Matthew Lenz wrote:
you don't get it.. kde and gnome where designed so that their applications work transparently over the network. if you don't use esd or arts, network transparent audio is not available. you'll probably never see true gnome or kde apps using alsa directly. what you might see is new and better sound servers become available. its too bad the alsa guys don't just add some kind of NAS to their official software distribution and make it work flawlessly with their drivers/sound.
Arts was most definately not designed to work transparently over the network. rather than send the file for processing, arts will send a filename over the network, so unless you tell arts to use NAS or ESD, it's useless for network audio. I agree it would be great to have alsa do that though
On Sat, Apr 30, 2005 at 06:54:41PM -0500, Richard June wrote:
Arts was most definately not designed to work transparently over the network. rather than send the file for processing, arts will send a filename over the network, so unless you tell arts to use NAS or ESD, it's useless for network audio. I agree it would be great to have alsa do that though
AFAIK ALSA is Linux specific whereas gnome and kde are cross-platform. So the important thing isn't to have alsa do network audio. It's to have a cross platform API that addresses the present shortcomings (Alan posts about those nearly every time this comes up.) Then it can be implemented on Linux and other platforms in whatever form makes sense.
-Toshio
On Sun, 2005-05-01 at 05:26 -0700, Toshio Kuratomi wrote:
AFAIK ALSA is Linux specific whereas gnome and kde are cross-platform. So the important thing isn't to have alsa do network audio. It's to have a cross platform API that addresses the present shortcomings (Alan posts about those nearly every time this comes up.) Then it can be implemented on Linux and other platforms in whatever form makes sense.
Well, the solution that GNOME seems to have converged on is to use Gstreamer and use whatever default output method Gstreamer is set up for. On many desktop systems, using the Gstreamer alsasink output plugin would be the best; in other cases you can either use e.g. esd or some other sound server which can provide network transparency. At least some KDE programs use Gstreamer as well, and apparently there is talk of using Gstreamer pretty much as the default audio solution for KDE 4. So it seems that Gstreamer can fulfill the role of being _the_ audio API that desktop apps use.
/Per
On Sun, 2005-05-01 at 10:28 -0700, Per Bjornsson wrote:
On Sun, 2005-05-01 at 05:26 -0700, Toshio Kuratomi wrote:
AFAIK ALSA is Linux specific whereas gnome and kde are cross-platform. So the important thing isn't to have alsa do network audio. It's to have a cross platform API that addresses the present shortcomings (Alan posts about those nearly every time this comes up.) Then it can be implemented on Linux and other platforms in whatever form makes sense.
Well, the solution that GNOME seems to have converged on is to use Gstreamer and use whatever default output method Gstreamer is set up for. On many desktop systems, using the Gstreamer alsasink output plugin would be the best; in other cases you can either use e.g. esd or some other sound server which can provide network transparency. At least some KDE programs use Gstreamer as well, and apparently there is talk of using Gstreamer pretty much as the default audio solution for KDE 4. So it seems that Gstreamer can fulfill the role of being _the_ audio API that desktop apps use.
/Per
-- Per Bjornsson perbj@stanford.edu Ph.D. Candidate, Department of Applied Physics, Stanford University
FYI, it looks like the issue with artsd going mental has departed. Thanks to whomever looked into it and repaired the problem!
Sean
On Fri, 2005-04-29 at 20:09 +0000, tim_mcmullen@comcast.net wrote:
Anybody having issues with artsd consuming 100% cpu and continually restarting with the latest update?
I seem to be, I ran k3b yesterday and the call out to artsd seemed to be failing. I also noted the same behavior(it kept restarting when it was killed) that you are seeing.
Sean
-
Frederick Alexander Thomssen -
Matthew Lenz -
Per Bjornsson -
Richard June -
Sean Bruno -
tim_mcmullen＠comcast.net -
Toshio Kuratomi