From: Takashi Iwai <tiwai@suse.de>
To: Patrick Shirkey <pshirkey@boosthardware.com>
Cc: Jaroslav Kysela <perex@suse.cz>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>,
jackit-devel@lists.sourceforge.net
Subject: Re: quattro multi plugin.
Date: Mon, 22 Jul 2002 13:10:24 +0200 [thread overview]
Message-ID: <s5hwuroow67.wl@alsa2.suse.de> (raw)
In-Reply-To: <3D3BD760.7060606@boosthardware.com>
At Mon, 22 Jul 2002 18:58:56 +0900,
Patrick Shirkey wrote:
>
> Jaroslav Kysela wrote:
> >
> > Please, try again. I've just added missing support for 24-bit samples to
> > one alsa-lib's function.
> >
>
> Things seem to be getting worse with jack at least. I cannot use the
> 96000hz setting because that requires jack to have 24 bit support which
> it doesn't yet. 32 or 16bit are supported.
you can use 32bit if it's accessed via plug layer.
alsa-lib converts from 32 to 24bit.
(you need anyway route layer, so the latency stays as before.)
> So If I use the .asoundrc that takashi sent I get an instant hang with
> only two channels being found and if I use my one I get the same but
> with four channels being found.
>
> By instant hang I mean:
>
> ----
> jackd -v -d alsa -d q4b
> jackd 0.37.1
> Copyright 2001-2002 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
>
> 611 waiting for signals
> creating alsa driver ... q4b|1024|2|48000|swmon
> new client: alsa_pcm, id = 1 type 1 @ 0x8067930 fd = 14
> port alsa_pcm:in_1 buf shm key 0x164398c5 at offset 4096 bi = 0x8066d00
> registered port alsa_pcm:in_1, offset = 4096
> port alsa_pcm:in_2 buf shm key 0x164398c5 at offset 8192 bi = 0x8066d10
> registered port alsa_pcm:in_2, offset = 8192
> port alsa_pcm:in_3 buf shm key 0x164398c5 at offset 12288 bi = 0x8066d20
> registered port alsa_pcm:in_3, offset = 12288
> port alsa_pcm:in_4 buf shm key 0x164398c5 at offset 16384 bi = 0x8066d30
> registered port alsa_pcm:in_4, offset = 16384
> registered port alsa_pcm:out_1, offset = 0
> registered port alsa_pcm:out_2, offset = 0
> registered port alsa_pcm:out_3, offset = 0
> registered port alsa_pcm:out_4, offset = 0
> -- jack_rechain_graph():
> client alsa_pcm: inprocess client, execution_order=0.
> ----
>
> Then my system locks hard.
hmm... could you simply try playback of 4 channels?
you can find a sample wav in
http://www.tsp.ece.mcgill.ca/Docs/AudioFormats/WAVE/WAVE.html
or, try 4 channel recording via aplay.
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-22 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 7:11 quattro multi plugin Patrick Shirkey
2002-07-19 8:42 ` Patrick Shirkey
2002-07-19 13:56 ` Patrick Shirkey
2002-07-19 17:51 ` Takashi Iwai
2002-07-19 23:44 ` Thorsten Haas
2002-07-20 16:09 ` Patrick Shirkey
2002-07-20 16:22 ` Patrick Shirkey
2002-07-20 16:41 ` Patrick Shirkey
2002-07-21 8:20 ` Jaroslav Kysela
2002-07-22 9:58 ` Patrick Shirkey
2002-07-22 11:10 ` Takashi Iwai [this message]
2002-07-22 11:21 ` Patrick Shirkey
2002-07-28 8:14 ` quattro multi plugin - 4 channel recording Patrick Shirkey
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=s5hwuroow67.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jackit-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=pshirkey@boosthardware.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