<div dir="ltr">Hey :) Thanks a lot for taking the time to reply :)<br>The irc channel seems kind of... too quiet, so i'll also give the pastebin link here... I've highlighted the error messages:<br><br><a href="http://bcm.pastebin.com/m13401731">http://bcm.pastebin.com/m13401731</a><br>
<br>I got kind of confused when trying to reach to a conclusion.<br><br><div class="gmail_quote">On Tue, Jul 15, 2008 at 11:13 AM, Colin Guthrie <<a href="mailto:gmane@colin.guthr.ie">gmane@colin.guthr.ie</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello Kostas,<br>
<div class="Ih2E3d"><br>
Kostas Gerontis wrote:<br>
> Hello everyone, i'm new to this list :)<br>
<br>
</div>Welcome :)<br>
<div><div></div><div class="Wj3C7c"><br>
> Basically, the reason that I signed up here has to do with finding a<br>
> solution for the following problem:<br>
><br>
> I have a soundcard M-Audio Audiophile 24/96 and I can't get it to work<br>
> properly with Pulse Audio, both in Ubuntu Hardy and Fedora 9.<br>
><br>
> I add myself in the 3 Pulseaudio groups, I enable everything in the<br>
> Pulseaudio Preferences (if i don't, the testing section of Gnome sound<br>
> preferences will give me an error ). It seems to work, I can see the<br>
> monitor doing something when sound is played, but I can't hear it. The<br>
> sound works nice when I switch to Alsa only. I believe the problem is<br>
> related to Rtp, since it's the only output recognized, as I can see in<br>
> PulseAudio Manager. I'd really appreciate any help. Let me note here<br>
> that when the login screen appears, a sound can be heard. I can also<br>
> hear sounds with flash videos and VideoLan media player, but probably<br>
> because they bypass Pulse Audio settings somehow and use Alsa by default...?<br>
<br>
</div></div>There is a chance that when your system starts, some sort of system<br>
device, using ALSA problably is getting access to the audio hardware and<br>
when pulse starts up, it cannot get control of it. Pulse needs to get<br>
control of the hardware during startup to initialise itself. It will<br>
release it again shortly afterwards to let pure alsa apps function as<br>
normal (albeit blocking pluse output).<br>
<br>
Generally it's recommeneded to route alsa's "default" output to<br>
pulseaudio and thus everything works nicely together.<br>
<br>
Anyway, to help debug your problem, once you've logged in, kill the<br>
running pulseaudio process (pulseaudio -k) and start a new one with<br>
pulseaudio -vvv and paste the output to a pastebin somewhere and put the<br>
link in this mail..<br>
<br>
You can also join us on IRC over at #pulseaudio on Freenode which may be<br>
a little more interactive :)<br>
<br>
Take care<br>
<br>
Col<br>
<br>
_______________________________________________<br>
pulseaudio-discuss mailing list<br>
<a href="mailto:pulseaudio-discuss@mail.0pointer.de">pulseaudio-discuss@mail.0pointer.de</a><br>
<a href="https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss" target="_blank">https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss</a><br>
</blockquote></div><br></div>