alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: John Rigg <aldev2@jrigg.co.uk>
To: "Jörg Müller" <joerg.mueller7744@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Cannot combine audio devices with more than 64	channels
Date: Wed, 8 Feb 2017 16:20:12 +0000	[thread overview]
Message-ID: <20170208162012.GA26820@localhost.localdomain> (raw)
In-Reply-To: <CAKw=HF10J=Sr=qrR6yTB_m3yznDh8boUv_qP1MKN75SXFth40w@mail.gmail.com>

On Wed, Feb 08, 2017 at 03:12:37PM +0100, Jörg Müller wrote:
> John Rigg informed me about the port-max-option of Jack. So I tried
> running the following commands:
> jackd --port-max 1024 -d alsa -C madifx_record_all -P madifx_playback_all
> jackd -p 1024 -d alsa -C madifx_record_all -P madifx_playback_all
> jackd -p1024 -d alsa -C madifx_record_all -P madifx_playback_all
> 
> I also tried ommiting either the option of -C or of -P. But I keep
> getting the same error:
> jackd: ../linux/alsa/JackAlsaDriver.cpp:122: virtual int
> Jack::JackAlsaDriver::Attach(): Assertion `fCaptureChannels < 256'
> failed.
> 
> So does that mean jackd doesn't recognize the parameter -p 1024?

I just tried jackd -p1024 here and there's no error message. I don't
have the hardware to easily test that many ports. I'm using pcm_multi
with three ice1712 cards and that accepts the jackd -p1024 option.
I tried adding jack clients until the default 256 ports was exceeded,
and there's no problem (tried up to 324 ports so far).

In jack2/common/JackGlobals.h it has the following:
#ifndefine PORT_NUM_MAX
#define PORT_NUM_MAX 4096
#endif

It looks like there's a restriction on driver capture and/or
playback channels somewhere, but you might have to grep through
the alsa and jack2 source code to find it.

John

  parent reply	other threads:[~2017-02-08 16:50 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
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 [this message]
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=20170208162012.GA26820@localhost.localdomain \
    --to=aldev2@jrigg.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=joerg.mueller7744@gmail.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;
as well as URLs for NNTP newsgroup(s).