alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: John Rigg <aldev@sound-man.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Need help: My .asoundrc no longer works.
Date: Sun, 21 Jan 2007 20:02:37 +0000	[thread overview]
Message-ID: <20070121200237.GA2893@localhost.localdomain> (raw)
In-Reply-To: <75b66ecd0701200846q5499ccb0o5ba10c6a301d7b73@mail.gmail.com>

On Sat, Jan 20, 2007 at 11:46:22AM -0500, Lee Revell wrote:
> On 1/20/07, John Rigg wrote:
> >You shouldn't need the plug converter if you specify the slaves channels
> >correctly. The ice1712 has 12 inputs and 10 outputs (regardless of how
> >many physical inputs/outputs your card has) and this needs to be
> >set explicitly in .asoundrc using separate playback and capture device
> >definitions. See here for explanation:
> 
> How could the above .asoundrc work given that the ICE1712 and EMU10K1
> devices are not synced at the hardware level?

Good question. I'm not familiar with the SBLive!, but I 
assumed (perhaps wrongly) that it had at least an S/PDIF output that
could be linked to the Delta's S/PDIF input.

jackd can actually run for a surprising length of time with unsynced
cards without alsa_pcm xrun messages (unlike jackdmp which produces a
slew of read errors), but I wouldn't expect to get a usable recording.

John

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2007-01-21 20:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20  0:39 Need help: My .asoundrc no longer works Tim
2007-01-20 14:01 ` John Rigg
2007-01-20 22:06   ` Tim
     [not found]   ` <75b66ecd0701200846q5499ccb0o5ba10c6a301d7b73@mail.gmail.com>
2007-01-21 20:02     ` John Rigg [this message]
2007-01-27  1:04       ` Tim
2007-01-22 14:06 ` Takashi Iwai
2007-01-26  1:28   ` Tim
2007-01-26 23:26     ` ice1712 IPGA and ADC controls Alan Horstmann
2007-01-27  0:42       ` Tim
2007-01-27 12:38       ` John Rigg
2007-01-28 20:54         ` Tim
2007-01-29  9:09           ` Alan Horstmann
2007-01-29  9:47             ` Fons Adriaensen
2007-01-29 16:36               ` Takashi Iwai
2007-01-28 22:59         ` Alan Horstmann
2007-01-29 12:16           ` Takashi Iwai
2007-01-29 17:07             ` Alan Horstmann
2007-01-29 17:12               ` Takashi Iwai
2007-01-29 19:15             ` John Rigg
2007-01-30  6:18               ` Tim
2007-01-30 11:14                 ` Takashi Iwai
2007-01-30 23:01                   ` Tim
2007-01-31  8:48                     ` Takashi Iwai
2007-01-31 10:33                       ` Takashi Iwai
2007-01-31 21:48                         ` Fons Adriaensen
2007-02-01 11:32                           ` Takashi Iwai
2007-02-01  5:01                         ` Tim
2007-02-01 10:08                           ` Alan Horstmann
2007-02-01 10:10                   ` Alan Horstmann
2007-02-01 12:10                     ` Takashi Iwai
2007-01-31 10:42                 ` John Rigg
2007-01-30 23:23     ` Need help: My .asoundrc no longer works Tim

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=20070121200237.GA2893@localhost.localdomain \
    --to=aldev@sound-man.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).