Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000862]: emu10k1 always has random clicks in wavetable MIDI synth playback but never in PCM playback
Date: Wed, 13 Apr 2005 22:01:34 +0200	[thread overview]
Message-ID: <394568894a47cdffae6cd1d90c176ba6@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=862> 
======================================================================
Reported By:                Will
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   862
Category:                   PCI - emu10k1
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               
Kernel Version:             2.6.10
======================================================================
Date Submitted:             01-30-2005 15:24 CET
Last Modified:              04-13-2005 22:01 CEST
======================================================================
Summary:                    emu10k1 always has random clicks in wavetable MIDI
synth playback but never in PCM playback
Description: 
An Audigy 2 LS 5.1 PCI soundcard with emu10k1 chipset (the PCI id is
1102:0004 (rev 04)) always has random clicks in wavetable MIDI synth
playback but never in PCM playback using any version of alsa-driver. I
think this clicking is probably an emu10k1 driver bug.

It makes no difference which driver or kernel is used; the problem exists
with alsa-driver-CVS, alsa-driver-1.0.8, and all previous versions since
before alsa-driver-0.9.7 and with all mainline kernel versions of Linux
2.4.x and Linux 2.6.x including 2.6.10. 

It makes no difference which kernel is used (2.4.x or 2.6.x). I recently
started using CONFIG_ACPI_* with CONFIG_PCI_[GO]BIOS in 2.6.10 but it
makes no difference. I use the default PCI latencies.

It makes no difference whether or not the emu10k1 IRQ is shared and the
clicking is exactly the same regardless of which other device shares the
IRQ, e.g. "IRQ 17: 78129 IO-APIC-level  libata, EMU10K1" or "IRQ 16: 9554 
IO-APIC-level  eth0, EMU10K1".

From: Lee Revell <rlrevell AT ...>
Subject: Re: [Alsa-devel] [PATCH] emu10k1 multichannel support
Date: Sat, 29 Jan 2005 16:28:47 -0500
To: William <walsac3 AT ...>
Message-Id: <1107034127.24676.55.camel@krustophenia.net>
Content-Type: text/plain

(sorry for the late reply)

On Wed, 2005-01-19 at 19:16 +0000, William wrote:
>
> I'll mention the following in case you might be interested to look at
it.
> An issue that's been around since the very beginning of the emu10k1
driver
> is that playing a MIDI file on the wavetable often produces a
> rapid but irregular sequence of very noticeable clicks at a
> rate of 2 or 3 per second continuing for up to about 10 seconds.
> The clicking starts happening once every minute or so but without any
> clear pattern - it doesn't seem to be depend much on the contents of the
MIDI
> files.
>
> Interestingly I never hear any clicks when using the PCM and
> a soft synth like fluidsynth or timidity as an alternative method
> of MIDI playback, which is why I think it might be a bug (haven't
checked
> whether something similar has already been logged on the bugtracker).
> I had a brief look into it, but didn't find anything conclusive in the
code.
> One possibly interesting feature was I notice that I could trigger lots
of
> clicks if I tried doing real-time variable attenuation of already
playing
> notes via update_voice(vp, SNDRV_EMUX_UPDATE_VOLUME) in
emu10k1_callback.c

I would actually be interested in looking at this.  I have noticed some
areas in the code where things are commented out for odd reasons.
Specifically the samples cache is not cleared like it is for PCM voices.
If you have time please file an ALSA bug report (you can just copy and
paste this message).

> By the way, do you know the original purpose of
snd_emu10k1_sum_vol_attn()
> in emu10k1/io.c which has just been removed in alsa-driver-1.0.8?
> The cumulative volume conversion algorithm in that function
> seems like it would probably have been based on the original emu10k1
chipset
> documentation provided by Creative during its open-source era.
> It seems like a useful function to keep around for future extensions of
> the emu10k1 driver.  Maybe it should be re-instated.
>
> >From the 1.0.8 announcement:
>
>     - Summary: ALSA PCI drivers: misc cleanups
>       The patch below does the following cleanups under sound/pci/ :
>       - remove the following unused global functions:
>         - emu10k1/io.c: snd_emu10k1_sum_vol_attn
>

Yes, I asked Takashi about this and he said it just does some simple
calculation.  Check the alsa-devel archive.  But, maybe there's
something to it.  It could be related to your clicking problem.

I have heard something similar when using PCM at really low latencies.

Lee

======================================================================

----------------------------------------------------------------------
 jdthood - 04-13-05 22:01 
----------------------------------------------------------------------
Submitter: Do you have any new information about the problem?

Issue History
Date Modified  Username       Field                    Change              
======================================================================
01-30-05 15:24 Will           New Issue                                    
01-30-05 15:24 Will           Kernel Version            => 2.6.10          
04-13-05 22:01 jdthood        Note Added: 0004480                          
======================================================================




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-04-13 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 20:01 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-18 23:30 [ALSA - driver 0000862]: emu10k1 always has random clicks in wavetable MIDI synth playback but never in PCM playback bugtrack
2006-07-18 12:39 bugtrack
2006-03-16 10:56 bugtrack
2005-12-31  2:30 bugtrack
2005-08-08 15:32 bugtrack
2005-08-08 13:20 bugtrack
2005-04-14 20:01 bugtrack
2005-04-14 13:20 bugtrack
2005-04-13 20:26 bugtrack
2005-01-30 14:24 bugtrack

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=394568894a47cdffae6cd1d90c176ba6@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /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