All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikael Magnusson <mikaelmagnusson@glocalnet.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: SBLive! change of front channel routing broke wavetable synth?
Date: Wed, 18 Jan 2006 00:17:48 +0100	[thread overview]
Message-ID: <43CD7B1C.7050104@glocalnet.net> (raw)
In-Reply-To: <1137533552.19678.38.camel@mindpipe>

Lee Revell wrote:
> Several SBLive! users are reporting that the wavetable synth is silent
> in recent ALSA versions.  I know that the wavetable synth output is
> routed by the driver to the front channels (as we have had user requests
> to allow it to output to the rear channels or all speakers in a 5.1
> setup).
> 
> Is it possible that the recent change in the routing of front channels
> from FXBUS 0,1 to FXBUS 8,9 has broken the wavetable synth?  It would
> explain why I cannot reproduce the problem on my Audigy.
> 
> Lee
> 

I use ALSA version 1.0.10, and I don't experience any problems with the 
wavetable synth on SBLive 5.1 [SB0060]. I usually run ld10k1, which 
resets the dsp program, but I verified that the synth also works after 
reloading the modules without starting ld10k1.

/Mikael


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

      reply	other threads:[~2006-01-17 23:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 21:32 SBLive! change of front channel routing broke wavetable synth? Lee Revell
2006-01-17 23:17 ` Mikael Magnusson [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=43CD7B1C.7050104@glocalnet.net \
    --to=mikaelmagnusson@glocalnet.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rlrevell@joe-job.com \
    /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.