All of lore.kernel.org
 help / color / mirror / Atom feed
From: Remy Bruno <remy.bruno@trinnov.com>
To: alsa-devel@lists.sourceforge.net
Subject: RME HDSP
Date: Tue, 20 Jun 2006 12:18:04 +0200	[thread overview]
Message-ID: <20060620101804.GA617@trinnov.com> (raw)

Hello,

I noticed that the driver hdsp.c now uses by default the "precise_ptr" mode of
the RME HDSP cards. However, at least with the last release of the RME HDSP
9652, this makes the sound scratchy (probably sound repeatedly interrupted by
short silence). It took me some time to find that this precise_ptr was the
cause of the trouble (sound is OK if I switch this off). So maybe it would be
advisable to switch back to no precise_ptr by default, letting the user the
possibility to activate it using the card controls. I imagine other people have
or will have the same problem as I have.

As I got no reply from my last message, I would just like to report again the
bug I found in hdsp.c:
there is a bug in the begining of function snd_hdsp_proc_read() of file
alsa-kernel/pci/rme9652/hdsp.c: a pair of "{}" is missing after the first "if"

if (hdsp_check_for_iobox (hdsp))
        {
                snd_iprintf(buffer, "No I/O box connected.\nPlease connect one and upload firmware.\n");
                return;
        }

The consequence was that the "return" statement was done systematically and so
the file "hdsp" always seemed to be empty.

Regards,

Remy BRUNO

             reply	other threads:[~2006-06-20 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 10:18 Remy Bruno [this message]
2006-06-20 16:16 ` RME HDSP Lee Revell
2006-06-20 16:18   ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2003-07-28 17:01 Daniel Sheltraw
2003-07-28 18:10 ` Paul Davis
2002-06-30  6:07 RME hdsp Orm Finnendahl

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=20060620101804.GA617@trinnov.com \
    --to=remy.bruno@trinnov.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.