oh..I see
didn`t know that =P. Hope they release other architectures support as soon
as possible!
On Wed, Oct 29, 2008 at 2:41 AM, Evgeny Kuznetsov <email address hidden> wrote:
> Sorry, roxthiaguin, but Flash 10 is only released for x386 machines,
> which is not the only architecture supported by Ubuntu. People using
> other architectures (or should I say "another architecture"?) are still
> forced to use libflashsupport.
>
> --
> Default ALSA device must use PulseAudio, otherwise ALSA applications may
> fail
> https://bugs.launchpad.net/bugs/198453
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in PulseAudio sound server: Confirmed
> Status in "alsa-lib" source package in Ubuntu: Fix Released
> Status in "alsa-plugins" source package in Ubuntu: Fix Released
> Status in "pulseaudio" source package in Ubuntu: Fix Released
> Status in alsa-lib in Ubuntu Hardy: Incomplete
> Status in alsa-plugins in Ubuntu Hardy: Incomplete
> Status in pulseaudio in Ubuntu Hardy: Invalid
>
> Bug description:
> Steps to reproduce:
>
> Run both of these at the same time:
> gst-launch-0.10 audiotestsrc ! pulsesink
> gst-launch-0.10 audiotestsrc ! alsasink
>
> If your default sound device does not support hardware mixing, the second
> command will fail. ALSA cannot use the device while PulseAudio is using it,
> and this affects a lot of applications.
>
> Note that if you run the commands the other way around, alsalib will use
> dmix, and then so will pulseaudio, so there is not as much of a problem this
> way around (except for the fact that dmix and PA are doing the same job, and
> you can not control the ALSA-using apps' volumes and routing with PA.)
>
>
> Resolution:
>
> Follow http://pulseaudio.org/wiki/PerfectSetup#ALSAApplications
> i.e. install /etc/asound.conf with:
>
> pcm.pulse {
> type pulse
> }
> ctl.pulse {
> type pulse
> }
> pcm.!default {
> type pulse
> }
> ctl.!default {
> type pulse
> }
>
> Then, install the package "libasound2-plugins", as it contains the required
> "pcm_pulse" and "ctl_pulse" plugins.
>
> Note, too, that there are some applications that fail with ALSA->Pulse:
>
> SDL* seems to hang with neverball, but that is fixed by installing the
> PulseAudio backend for SDL (libsdl1.2debian-pulseaudio), which will replace
> the default ALSA backend.
> WINE has its own issues with regards to device selection, which I don't
> know a remedy for.
> Skype* also has its own problems, but these aren't fixable by us and should
> not block us, though should be given some consideraton.
>
> * SDL applications (using libsdl1.2-alsa backend), Skype and possibly other
> misbehaving applications work properly with later versions of libasound2 &
> libasound2-plugins from Debian unstable.
>
oh..I see
didn`t know that =P. Hope they release other architectures support as soon
as possible!
On Wed, Oct 29, 2008 at 2:41 AM, Evgeny Kuznetsov <email address hidden> wrote:
> Sorry, roxthiaguin, but Flash 10 is only released for x386 machines, /bugs.launchpad .net/bugs/ 198453 pulseaudio. org/wiki/ PerfectSetup# ALSAApplication s plugins" , as it contains the required 2debian- pulseaudio) , which will replace
> which is not the only architecture supported by Ubuntu. People using
> other architectures (or should I say "another architecture"?) are still
> forced to use libflashsupport.
>
> --
> Default ALSA device must use PulseAudio, otherwise ALSA applications may
> fail
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in PulseAudio sound server: Confirmed
> Status in "alsa-lib" source package in Ubuntu: Fix Released
> Status in "alsa-plugins" source package in Ubuntu: Fix Released
> Status in "pulseaudio" source package in Ubuntu: Fix Released
> Status in alsa-lib in Ubuntu Hardy: Incomplete
> Status in alsa-plugins in Ubuntu Hardy: Incomplete
> Status in pulseaudio in Ubuntu Hardy: Invalid
>
> Bug description:
> Steps to reproduce:
>
> Run both of these at the same time:
> gst-launch-0.10 audiotestsrc ! pulsesink
> gst-launch-0.10 audiotestsrc ! alsasink
>
> If your default sound device does not support hardware mixing, the second
> command will fail. ALSA cannot use the device while PulseAudio is using it,
> and this affects a lot of applications.
>
> Note that if you run the commands the other way around, alsalib will use
> dmix, and then so will pulseaudio, so there is not as much of a problem this
> way around (except for the fact that dmix and PA are doing the same job, and
> you can not control the ALSA-using apps' volumes and routing with PA.)
>
>
> Resolution:
>
> Follow http://
> i.e. install /etc/asound.conf with:
>
> pcm.pulse {
> type pulse
> }
> ctl.pulse {
> type pulse
> }
> pcm.!default {
> type pulse
> }
> ctl.!default {
> type pulse
> }
>
> Then, install the package "libasound2-
> "pcm_pulse" and "ctl_pulse" plugins.
>
> Note, too, that there are some applications that fail with ALSA->Pulse:
>
> SDL* seems to hang with neverball, but that is fixed by installing the
> PulseAudio backend for SDL (libsdl1.
> the default ALSA backend.
> WINE has its own issues with regards to device selection, which I don't
> know a remedy for.
> Skype* also has its own problems, but these aren't fixable by us and should
> not block us, though should be given some consideraton.
>
> * SDL applications (using libsdl1.2-alsa backend), Skype and possibly other
> misbehaving applications work properly with later versions of libasound2 &
> libasound2-plugins from Debian unstable.
>
-- dos.com. br
Thiago Bellini Ribeiro
Programador PHP
www.linuxparato
<email address hidden>
Ribeirão Preto - SP