From: Takashi Iwai <tiwai@suse.de>
To: John Anderson <panic-alsa@semiosix.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Problems with USB driver and Swissonic USB Studio
Date: Fri, 19 Jul 2002 13:20:49 +0200 [thread overview]
Message-ID: <s5hit3cq7zi.wl@alsa2.suse.de> (raw)
In-Reply-To: <1027076078.1745.20.camel@groovious>
At 19 Jul 2002 12:54:38 +0200,
John Anderson wrote:
>
> On Fri, 2002-07-19 at 12:29, Takashi Iwai wrote:
> > At 19 Jul 2002 12:20:21 +0200, John Anderson wrote:
> > >
> > > I'm using a Swissonic USB Studio.
> > >
> > > With an older CVS version (from around 29th June), playback and capture
> > > were pretty much OK, except for a ticking (the repetitive peaks issue?)
> > > and some noise. Using the latest CVS version:
> > >
> > > aplay -D studio /mnt/spare/music/test.wav
> > > Playing WAVE '/mnt/spare/music/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
> > > aplay: set_params:737: Broken configuration for this PCM: no configurations available
> >
> > perhaps you'll need to update also alsa-lib from cvs.
>
> Did that already.
hmm, do you see any kernel messages from alsa drivers?
(you might need to compile it via --with-debug=full option.)
if there is a message regarding unknown ioctl, then the alsa-library
doesn't match with the alsa driver. something wrong happened during
alsa-lib installation, such as wrong path, etc.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-19 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 10:20 Problems with USB driver and Swissonic USB Studio John Anderson
2002-07-19 10:29 ` Takashi Iwai
2002-07-19 10:54 ` John Anderson
2002-07-19 11:20 ` Takashi Iwai [this message]
2002-07-19 12:08 ` John Anderson
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=s5hit3cq7zi.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=panic-alsa@semiosix.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