Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Jaroslav Kysela <perex@suse.cz>
Cc: "Michel Dänzer" <michel@daenzer.net>, alsa-devel@lists.sourceforge.net
Subject: Re: xine with dmix
Date: Wed, 21 Jan 2004 23:41:49 +0000	[thread overview]
Message-ID: <400F0E3D.3010605@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0401212012430.2010@pnote.perex-int.cz>

Jaroslav Kysela wrote:
> On Tue, 20 Jan 2004, Michel Dänzer wrote:
> 
> 
>>On Tue, 2004-01-20 at 17:06, Michel Dänzer wrote:
>>
>>>On Tue, 2004-01-20 at 16:29, Jaroslav Kysela wrote:
>>>
>>>>On Tue, 20 Jan 2004, Michel Dänzer wrote:
>>>>
>>>>Could you try the attached patch? If you add a line 'slowptr yes' to your 
>>>>dmix pcm definition, the snd_pcm_delay() function should be more precise.
>>>
>>>It seems to work perfectly, thank you very much!
>>
>>I have to take that back. :(
>>
>>I had put the slowptr in the wrong place (in the dmixer slave pcm
>>block), and xine silently fell back to using /dev/dsp (alsa-oss doesn't
>>seem to work with it). With the slowptr in the right place, I have now
>>verified that xine uses ALSA with it enabled, but it doesn't seem to
>>enhance sound quality much if at all.
>>
>>Sorry for the false confirmation. Any other ideas?
> 
> 
> Yes, I've tested xine with dmix today and I figured after several hours of 
> looking for totaly another problem, that it was 'snd_pcm_wait()' function 
> which causes trouble in conjunction with the xine ALSA code algorithm.
> 
> The result patch (attached to this mail and available also in CVS) is that
> xine works with dmix even without the slowptr option! So there is no 
> reason to make this option as default.
> 
> I'm happy that the next direct plugin related bug is solved.
> 
> 						Jaroslav
> 

I have tried both your patches, but neither of them fix the problem or 
jerky output. Sound for a short burst, short pause, sound for a short 
burst, short pause etc.

Cheers
James


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

      parent reply	other threads:[~2004-01-21 23:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 14:09 xine with dmix Michel Dänzer
2004-01-20 15:29 ` Jaroslav Kysela
2004-01-20 16:06   ` Michel Dänzer
2004-01-20 16:07     ` Jaroslav Kysela
2004-01-20 16:29       ` Takashi Iwai
2004-01-20 16:39       ` Florian Schmidt
2004-01-20 17:39     ` Michel Dänzer
2004-01-21 19:19       ` Jaroslav Kysela
2004-01-21 21:45         ` Michel Dänzer
2004-01-21 23:15         ` James Courtier-Dutton
2004-01-21 23:41         ` James Courtier-Dutton [this message]

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=400F0E3D.3010605@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=michel@daenzer.net \
    --cc=perex@suse.cz \
    /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