Volker Armin Hemmann writes:
> On Freitag 08 Mai 2009, Alex Schuster wrote:
> > But still, /dev/dsp is busy with amarok running.
> hmm, I have to admit, I have no idea.
Me too. Well, thanks anyway for your support. I will live with that for a
while, there are worse things I will need to take ca
On Freitag 08 Mai 2009, Alex Schuster wrote:
> Volker Armin Hemmann writes:
> > On Freitag 08 Mai 2009, Alex Schuster wrote:
> > > The backend is still set to Xine. As devices I have "HDA ATI SB (HDA
> > > Generic)", "HDA ATI HDMI, ATI HDMI (HDMI Audio Output)", "Jack Audio
> > > Connection Kit" an
Volker Armin Hemmann writes:
> On Freitag 08 Mai 2009, Alex Schuster wrote:
> > The backend is still set to Xine. As devices I have "HDA ATI SB (HDA
> > Generic)", "HDA ATI HDMI, ATI HDMI (HDMI Audio Output)", "Jack Audio
> > Connection Kit" and "Esound (ESD)" listed. All except for the 2nd one
>
On Freitag 08 Mai 2009, Alex Schuster wrote:
> Volker Armin Hemmann writes:
> > when you go to the multimedia settings in system settings - are those ok?
> > right devices? xine set?
>
> The backend is still set to Xine. As devices I have "HDA ATI SB (HDA
> Generic)", "HDA ATI HDMI, ATI HDMI (HDMI
Volker Armin Hemmann writes:
> when you go to the multimedia settings in system settings - are those ok?
> right devices? xine set?
The backend is still set to Xine. As devices I have "HDA ATI SB (HDA
Generic)", "HDA ATI HDMI, ATI HDMI (HDMI Audio Output)", "Jack Audio
Connection Kit" and "Esou
On Freitag 08 Mai 2009, Alex Schuster wrote:
> Volker Armin Hemmann writes:
> > On Mittwoch 06 Mai 2009, Alex Schuster wrote:
> > > Volker Armin Hemmann writes:
> > > > On Dienstag 05 Mai 2009, Alex Schuster wrote:
> > > > > I cannot access /dev/dsp once Amarok 2 has started playback, even
> > > >
Volker Armin Hemmann writes:
> On Mittwoch 06 Mai 2009, Alex Schuster wrote:
> > Volker Armin Hemmann writes:
> > > On Dienstag 05 Mai 2009, Alex Schuster wrote:
> > > > I cannot access /dev/dsp once Amarok 2 has started playback, even
> > > > if the playback was stopped. I have to close Amarok, t
On Mittwoch 06 Mai 2009, Alex Schuster wrote:
> Volker Armin Hemmann writes:
> > On Dienstag 05 Mai 2009, Alex Schuster wrote:
> > > I cannot access /dev/dsp once Amarok 2 has started playback, even if
> > > the playback was stopped. I have to close Amarok, then /dev/dsp is
> > > accessible again.
Volker Armin Hemmann writes:
> On Dienstag 05 Mai 2009, Alex Schuster wrote:
> > I cannot access /dev/dsp once Amarok 2 has started playback, even if
> > the playback was stopped. I have to close Amarok, then /dev/dsp is
> > accessible again. Does anyone know why this is?
[...]
> no problem here.
On Dienstag 05 Mai 2009, Alex Schuster wrote:
> Hi there!
>
> I cannot access /dev/dsp once Amarok 2 has started playback, even if the
> playback was stopped. I have to close Amarok, then /dev/dsp is accessible
> again. Does anyone know why this is?
>
> This happens in KDE4, 2.6.28-tuxonice-r3 kern
Hi there!
I cannot access /dev/dsp once Amarok 2 has started playback, even if the
playback was stopped. I have to close Amarok, then /dev/dsp is accessible
again. Does anyone know why this is?
This happens in KDE4, 2.6.28-tuxonice-r3 kernel, audio device according to
lspci is "ATI Technologie
11 matches
Mail list logo
