All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Phillips <rustyp@freeshell.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Omnistudio USB
Date: Fri, 14 Jan 2005 12:01:10 -0500	[thread overview]
Message-ID: <1105722071.1897.9.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.HPX.4.33n.0501141230020.25187-100000@studcom.urz.uni-halle.de>

Using the current CVS I can apply most of that patch at fuzziness level
3 (which could still cause problems), but not the last hunk.  I can
probably figure it out and patch manually.

But if it's easy for you to do, could you tell me what you're actually
patching if not the current CVS (at cvs.alsa-project.org)?

Thanks!

Rusty Phillips
			
On Fri, 2005-01-14 at 12:34 +0100, Clemens Ladisch wrote:
> Rusty Phillips wrote:
> > Okay, I've been trying most of my testing with the first two channels.
> >
> > However, I just figured out that recording and playback works on
> > channels #3 and #4 at 96000.
> 
> The first two channels use an additional 16-bit interface, probably
> for compatibility with the Windows USB Audio driver.
> 
> Please try the patch below.
> 
> 
> HTH
> Clemens
> 




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  reply	other threads:[~2005-01-14 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12  5:13 Omnistudio USB Rusty Phillips
2005-01-12  9:02 ` Clemens Ladisch
2005-01-12 17:48   ` Rusty Phillips
2005-01-12 20:50   ` Rusty Phillips
2005-01-14 11:34     ` Clemens Ladisch
2005-01-14 17:01       ` Rusty Phillips [this message]
2005-01-14 18:12         ` Clemens Ladisch
2005-01-14 20:07       ` Rusty Phillips

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=1105722071.1897.9.camel@localhost.localdomain \
    --to=rustyp@freeshell.org \
    --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.