From: John Rigg <aldev2@jrigg.co.uk>
To: alsa-devel@alsa-project.org
Subject: Re: Cannot combine audio devices with more than 64 channels
Date: Tue, 31 Jan 2017 17:58:05 +0000 [thread overview]
Message-ID: <20170131175805.GA16643@localhost.localdomain> (raw)
In-Reply-To: <CAKw=HF1kZ12YOUuBX0MmiyYsPqQ68kafP-cVmWA8FP0dHOAuDw@mail.gmail.com>
On Tue, Jan 31, 2017 at 06:18:48PM +0100, Jörg Müller wrote:
> I applied the patch to my system and it fixed the error!
>
> However, I get the following error which seems to be caused by a code
> not being able to handle more than 256 channels:
> > wfs@wfs16:~$ jackd -R -d alsa -C madifx_record_all -P madifx_playback_all
> > jackdmp 1.9.10
> > Copyright 2001-2005 Paul Davis and others.
> > Copyright 2004-2014 Grame.
> > jackdmp 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
> > no message buffer overruns
> > no message buffer overruns
> > no message buffer overruns
> > JACK server starting in realtime mode with priority 10
> > self-connect-mode is "Don't restrict self connect requests"
> > audio_reservation_init
> > Acquire audio card Audio0
> > creating alsa driver ... madifx_playback_all|madifx_record_all|1024|2|48000|0|0|nomon|swmeter|-|32bit
> > configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
> > ALSA: final selected sample format for capture: 32bit float little-endian
> > ALSA: use 8 periods for capture
> > ALSA: final selected sample format for playback: 32bit float little-endian
> > ALSA: use 8 periods for playback
> > jackd: ../linux/alsa/JackAlsaDriver.cpp:122: virtual int Jack::JackAlsaDriver::Attach(): Assertion `fCaptureChannels < 256' failed.
> > Aborted (core dumped)
>
> What could be the problem here?
jackd only allows 256 ports maximum by default. Try using -p option
to increase it, eg. to 512:
jackd -R -p512 -d alsa....etc
BTW you don't need to specify -R on recent jackd versions as it's
realtime by default (use -r if you don't want realtime).
John
next prev parent reply other threads:[~2017-01-31 18:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 14:14 [Alsa-Devel] Cannot combine audio devices with more than 64 channels Jörg Müller
2017-01-26 16:12 ` Takashi Iwai
2017-01-26 16:13 ` Clemens Ladisch
2017-01-27 11:08 ` Takashi Iwai
2017-01-27 13:03 ` Jörg Müller
2017-01-27 13:16 ` Takashi Iwai
2017-01-27 23:14 ` Takashi Sakamoto
2017-01-31 17:00 ` Jörg Müller
2017-01-27 20:25 ` John Rigg
2017-01-31 17:18 ` Jörg Müller
2017-01-31 17:58 ` John Rigg [this message]
2017-01-31 18:46 ` Takashi Iwai
[not found] ` <20170131193159.GA17070@localhost.localdomain>
2017-02-08 14:12 ` Jörg Müller
2017-02-08 16:12 ` John Rigg
2017-02-08 16:20 ` John Rigg
2017-02-08 16:31 ` John Rigg
2017-02-08 17:22 ` Jörg Müller
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=20170131175805.GA16643@localhost.localdomain \
--to=aldev2@jrigg.co.uk \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).