From: Marek Vasut <marek.vasut@gmail.com>
To: "Fred ." <eldmannen@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: Audio on Linux is a mess
Date: Mon, 20 Oct 2008 18:23:27 +0200 [thread overview]
Message-ID: <200810201823.27422.marek.vasut@gmail.com> (raw)
In-Reply-To: <f188924b0810200741v2982ecb4i2fea9589aa2958a3@mail.gmail.com>
You got what you paid for.
Maybe if you change your attitude and supply some information, someone might
consider looking in your issue, othervise it would be a problem since I
forgot my crystal ball back at home.
On Monday 20 of October 2008 16:41:45 Fred . wrote:
> Yeah, fix the Linux audio so that if an application behaves wrong, or
> does something stupid, then after I close the application, the system
> should be silent.
> It shouldn't continue make sound even after I quit the application.
> And PulseAudio shouldn't crash because one application did something
> even if it was stupid.
>
> On Mon, Oct 20, 2008 at 8:35 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> > On Friday 17 of October 2008 15:24:20 Fred . wrote:
> >> ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect:
> >> Timeout ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to
> >> connect: Timeout AL lib: alsa.c:344: Could not open playback device
> >> 'default': Connection refused AL lib: oss.c:179: Could not open
> >> /dev/dsp: Device or resource busy File
> >> "/var/lib/python-support/python2.5/pyglet/media/drivers/openal/__init__.
> >>py" , line 340, in driver_init_device = alc.alcOpenDevice(device_name)
> >>
> >> Audio on Linux is a mess.
> >> I launch an Python script that uses audio then it breaks, and when the
> >> Python script is closed, I still hear the audio skipping and repeating
> >> like,
> >> "kakakakakakaka" in infinite loop.
> >> And PulseAudio seems to be frozen.
> >> Then I kill PulseAudio and finally the audio noise stops.
> >>
> >> Oh, and I heard OpenAL downsamples stereo to mono on Linux due to a bug.
> >>
> >> Whole audio on Linux is just a big mess.
> >
> > Please behave yourself.
> > Is there any way we can help you (which I doubt, but ...)?
> >
> >> _______________________________________________
> >> Alsa-devel mailing list
> >> Alsa-devel@alsa-project.org
> >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2008-10-20 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 13:24 Audio on Linux is a mess Fred .
2008-10-20 6:35 ` Marek Vasut
[not found] ` <f188924b0810200741v2982ecb4i2fea9589aa2958a3@mail.gmail.com>
2008-10-20 16:23 ` Marek Vasut [this message]
2008-10-20 16:47 ` Robert Vincent Krakora
2008-10-20 15:12 ` Colin Guthrie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200810201823.27422.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=eldmannen@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox