All of lore.kernel.org
 help / color / mirror / Atom feed
From: Remi Bernhard <rgbmlist2@free.fr>
To: alsa-devel@lists.sourceforge.net
Subject: Re: [ALSA - driver 0000377]: AudioTrak MAYA44 USB is detected, but doesn't work.
Date: Sun, 14 Nov 2004 13:20:35 +0100	[thread overview]
Message-ID: <20041114132035.774be451@localhost> (raw)
In-Reply-To: <fa667dd6f6c4e0c190237bbbe5427d38@bugtrack.alsa-project.org>

Hello,

> ----------------------------------------------------------------------
>  TheMuso - 11-10-04 22:36 
> ----------------------------------------------------------------------
> Ok, changing the number to 11 allows the card to work properly. It now
> appears in /proc/asound with all info regarding the card, and the
> playback and capture devices. Alsamixer works, and I can even get
> sound through it.
> 
> Thanks a lot Clemens, much appreciated.
> 
> I guess I have to close this bug now?
> 

I'd like to know what is the best latency (or buffer size) you get with
this card and jackd ?

Regards,
	Remi.


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8

  reply	other threads:[~2004-11-14 12:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 21:36 [ALSA - driver 0000377]: AudioTrak MAYA44 USB is detected, but doesn't work bugtrack
2004-11-14 12:20 ` Remi Bernhard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-11  8:22 bugtrack
2004-11-11  8:22 bugtrack
2004-11-10 12:49 bugtrack
2004-11-10 10:26 bugtrack
2004-11-10  8:56 bugtrack
2004-09-20 13:14 bugtrack
2004-09-03  1:42 bugtrack
2004-08-20  9:18 bugtrack
2004-08-15 10:14 bugtrack
2004-07-17  1:03 noreply
2004-07-16 14:59 noreply
2004-07-15 11:41 noreply
2004-07-15  6:59 noreply
2004-07-14 22:42 noreply
2004-07-14 17:27 noreply

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=20041114132035.774be451@localhost \
    --to=rgbmlist2@free.fr \
    --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.