Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: CAG <cag@fsk-hh.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: M-Delta Audiophile 192 (ice1724) Recording
Date: Thu, 31 Jan 2008 18:33:30 +0100	[thread overview]
Message-ID: <47A2066A.1050202@fsk-hh.org> (raw)
In-Reply-To: <s5h7ihp29eu.wl%tiwai@suse.de>



Takashi Iwai schrieb:
> At Thu, 31 Jan 2008 18:11:38 +0100,
> CAG wrote:
>> HI,
>>
>> Takashi Iwai schrieb:
>>> At Thu, 31 Jan 2008 16:44:06 +0100,
>>> CAG wrote:
>>>> Hi,
>>>>
>>>> we ran the alsa-info.sh script to provide more information on our setup:
>>>> http://pastebin.ca/886260
>>>>
>>>> The output of /proc/asound/card0/ice1724 is at
>>>> http://pastebin.ca/884589
>>> Thanks.  One more thing - could you tell how did you test the analog
>>> recording exactly?  I just need to make sure about your test method.
>> Well, we tried with arecord, ecasound, jack & audacity, but in the 
>> alsamixer / mixer gui in kde, at capture there's just one "Multi Track 
>> Peak" without capture switch.
>>
>> What would be the best record method to test ?
> 
> Usually arecord is the best as a primary test.
> Simply run
> 	% arecord -fdat -vv somefile.wav
> To avoid any possible bugs in alsa-lib, also try
> 	% arecord -Dplughw:0 -fdat -vv somefile.wav
We will try.

> 
>>> The patch below enables AK4114, and possibly fixes some ADC setup.
>>> Give it a try.
>> Cool! we will try it this evening and give a feedback. It is a patch for 
>> 1.0.16rc2 or 1.0.15 ?
> 
> For 1.0.16rc2.  Don't forget to update alsa-lib and alsa-utils, too.

All right, but I can't find alsa-utils-1.0.16rc2.tar.bz2 on the website. 
There's just a link for 
ftp://ftp.alsa-project.org/pub/utils/alsa-utils-1.0.16rc1.tar.bz2

Do we find them anywhere else ?


Toast

> 
> 
> Takashi

  reply	other threads:[~2008-01-31 17:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 12:29 M-Delta Audiophile 192 (ice1724) Recording CAG
2008-01-30 12:07 ` Takashi Iwai
2008-01-30 13:52   ` CAG
2008-01-31 15:44   ` CAG
2008-01-31 16:16     ` Takashi Iwai
2008-01-31 17:12       ` CAG
     [not found]       ` <47A2014A.1040107@fsk-hh.org>
2008-01-31 17:26         ` Takashi Iwai
2008-01-31 17:33           ` CAG [this message]
2008-01-31 17:36             ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2008-01-31 22:06 Computer AG im FSK
2008-01-31 22:51 ` Computer AG im FSK
2008-02-01 12:17   ` Takashi Iwai
2008-02-04 14:31     ` CAG
2008-02-04 15:04       ` Takashi Iwai
2008-02-04 17:37         ` CAG

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=47A2066A.1050202@fsk-hh.org \
    --to=cag@fsk-hh.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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