mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Edward Tandi <ed@efix.biz>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	perex@suse.cz, alsa-devel@lists.sourceforge.net,
	Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
	Rob Love <rml@ximian.com>, Andrew Morton <akpm@osdl.org>,
	Stan Bubrouski <stan@ccs.neu.edu>
Subject: Re: OSS sound emulation broken between 2.6.0-test2 and test3
Date: Sat, 27 Dec 2003 16:33:11 +0200	[thread overview]
Message-ID: <1072535590.12308.250.camel@nosferatu.lan> (raw)
In-Reply-To: <1072530488.2906.1.camel@wires.home.biz>

[-- Attachment #1: Type: text/plain, Size: 2070 bytes --]

On Sat, 2003-12-27 at 15:08, Edward Tandi wrote:
> On Sat, 2003-12-27 at 12:24, Martin Schlemmer wrote:
> > On Sat, 2003-12-27 at 13:44, Edward Tandi wrote:
> > > On Sat, 2003-12-27 at 11:11, Martin Schlemmer wrote:
> > > > On Sat, 2003-12-27 at 09:50, Martin J. Bligh wrote:
> > > > > Something appears to have broken OSS sound emulation between 
> > > > > test2 and test3. Best I can tell (despite the appearance of the BK logs), 
> > > > > that included ALSA updates 0.9.5 and 0.9.6. Hopefully someone who
> > > > > understands the sound architecture better than I can fix this?
> > > > > 
> > > > 
> > > > I wont say I understand it, but a quick look seems the major change is
> > > > the addition of the 'whole-frag' and 'no-silence' opts.  You might try
> > > > the following to revert what 'no-silence' change at least does:
> > > > 
> > > > --
> > > >  # echo 'xmms 0 0 no-silence' > /proc/asound/card0/pcm0p/oss
> > > >  # echo 'xmms 0 0 whole-frag' > /proc/asound/card0/pcm0p/oss
> > > > --
> > > 
> > > Thanks, that fixes it for me. I too have been seeing terrible problems
> > > with XMMS since the early 2.6 pre- kernels.
> > > 
> > > Because it only happens in XMMS I thought it was one of those
> > > application bugs brought out by scheduler changes. I now use Zinf BTW
> > > -It's better for large music collections (although not as stable or
> > > flash).
> > > 
> > 
> > Can you check which one actually fixes it ?
> 
> Yes, its the 'whole-frag' line.
> 

Well, I can't say I can see why. In snd_pcm_oss_write1 where the change
for whole-frag was, I cannot see a race or such.  The only possible
causes I can see, is that:
1) xmms's scheduling gets screwed due to the short writes
2) some drivers may have issues with getting short writes all the time.

Only problem with 2), is that Zinf works fine for you, so I guess the
only thing to assume is that either Zinf do not use OSS, but ALSA
interface, or that 1) is indeed the correct answer.  What version of
XMMS do you use btw?


-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-12-27 14:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26 21:55 2.6.0 sound output - wierd effects Martin J. Bligh
2003-12-26 22:27 ` Sven-Haegar Koch
2003-12-27 16:14   ` Martin J. Bligh
2003-12-26 22:52 ` Martin Schlemmer
2003-12-26 23:00   ` Martin J. Bligh
2003-12-26 23:17     ` Martin Schlemmer
2003-12-26 23:24       ` Martin J. Bligh
2003-12-26 23:50         ` Martin Schlemmer
2003-12-26 23:59           ` Martin J. Bligh
2003-12-27  0:44             ` Martin Schlemmer
2003-12-27  0:53             ` Martin Schlemmer
2003-12-27  4:34               ` Martin J. Bligh
2003-12-27 11:12                 ` Martin Schlemmer
2003-12-27 16:17                   ` Martin J. Bligh
2003-12-27  4:48             ` Stan Bubrouski
2003-12-27  4:57               ` Rob Love
2003-12-27  5:02                 ` Martin J. Bligh
2003-12-27  5:10                   ` Rob Love
2003-12-27  5:45                     ` Stan Bubrouski
2003-12-27 22:44                     ` szonyi calin
2003-12-27  7:50               ` OSS sound emulation broken between 2.6.0-test2 and test3 Martin J. Bligh
2003-12-27 11:11                 ` Martin Schlemmer
2003-12-27 11:44                   ` Edward Tandi
2003-12-27 12:24                     ` Martin Schlemmer
2003-12-27 13:08                       ` Edward Tandi
2003-12-27 14:33                         ` Martin Schlemmer [this message]
2003-12-27 16:55                           ` Edward Tandi
2003-12-27 17:22                             ` Martin Schlemmer
2003-12-27 21:56                             ` Henrik Storner
2003-12-27 22:51                               ` Edward Tandi
2003-12-27 18:35                     ` Martin J. Bligh
2003-12-27 19:56                       ` Jaroslav Kysela
2003-12-27 20:12                         ` Martin J. Bligh
2003-12-27 20:25                       ` Martin Schlemmer
2003-12-27 20:44                         ` Martin Schlemmer
2003-12-28  0:27                           ` Martin J. Bligh
2004-01-03  0:53                     ` Chris Shafer
2004-01-03 22:23                       ` Martin Schlemmer
2003-12-28  5:06                 ` Joshua Schmidlkofer
2003-12-26 22:59 ` 2.6.0 sound output - wierd effects Sander Sweers
2003-12-26 23:02   ` Martin J. Bligh

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=1072535590.12308.250.camel@nosferatu.lan \
    --to=azarah@nosferatu.za.org \
    --cc=akpm@osdl.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ed@efix.biz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=perex@suse.cz \
    --cc=rml@ximian.com \
    --cc=stan@ccs.neu.edu \
    /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

all inboxes | Powered by JetHome®