Re: Port number limitation
Hannes Helmholz <[email protected]> Fri, 23 Aug 2019 13:36:13 +0200
| Newsgroups | gmane.comp.audio.jackit |
|---|---|
| Organization | Chalmers University of Technology |
| Message-ID | <[email protected]> |
--===============6198894428692535159== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Ru4EyvfZw5GbIopvRUvT37BhMBEhVBXLZ" --Ru4EyvfZw5GbIopvRUvT37BhMBEhVBXLZ Content-Type: multipart/mixed; boundary="rZN0WVrNjFvO0pJYbdYdcWVjMaVsO5HYg"; protected-headers="v1" From: Hannes Helmholz <[email protected]> To: [email protected] Message-ID: <[email protected]> Subject: Re: [Jack-Devel] Port number limitation References: <[email protected]> <[email protected]> In-Reply-To: <[email protected]> --rZN0WVrNjFvO0pJYbdYdcWVjMaVsO5HYg Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2019-08-21 22:52, John Rigg wrote: > On Mon, Aug 19, 2019 at 08:54:04PM +0200, Hannes Helmholz wrote: >> I have noticed the JACK server limitation of port numbers in some >> specific applications ("Maximum number of output ports is reached for >> application ref =3D 2"). I have noticed the "-p" / "--port-max" parame= ter >> and was able to artificially scale down or up the available number. Bu= t, >> I seem to have reached and upper limit at around 800. Due to possibly >> already existing ports like system input and output I am not certain o= f >> the exact number. >=20 > jack_lsp should show a list of all ports. > =20 >> To be fair, the available number is high enough for general use cases >> (also for me). But in these certain conditions it definitely limits my= >> possibilities without an apparent workaround. >> >> Is there a way monitor if the port-max is passed correctly? Or where t= he >> limitation arises otherwise? Or how to possibly circumvent it? >=20 > In jack2 (don't know about jack1) PORT_NUM_MAX is set in > JackConstants.h. It's currently set to 4096. >=20 > There are other numbers in JackConstants.h like DRIVER_PORT_NUM > (currently 256 which is too small for multiple MADI cards, > for example). >=20 > If you can't get enough ports you might have to raise one or > more of those numbers and recompile. >=20 > John > _______________________________________________ > Jack-Devel mailing list > [email protected] > http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >=20 Ahh, thank you for the hint. The wall I was actually running into here was PORT_NUM_FOR_CLIENT being 768. What is the reasoning for these limits, since just like that they seem very arbitrary? But at least there is a known source for the limitations now. :) Sadly recompiling is certainly not trivial, mostly because I need to work with OSX and eventually Windows. Which both are not officially supported atm, I believe. In case I manage, should it be feasible to raise some of the limits? Or what might happen that I will have to look out for? /Hannes --rZN0WVrNjFvO0pJYbdYdcWVjMaVsO5HYg-- --Ru4EyvfZw5GbIopvRUvT37BhMBEhVBXLZ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE42VH5m+QxPUYEbsqOET9smFm3aMFAl1fz60ACgkQOET9smFm 3aP9lg//XPHVXrVAjOoGc82sA5WQXGXJr0AmwbtP9+/KPVLePpHLpsnSnw/GkkPv 7jTK3agMobzYH8oTK2U0/abbfdNBszzabQ7Z+7NrwygBr4FS0v40QduYCvXERyPP AVNd6NYxRkXhirl4YSwjsr8euXAxRfgijRqQQTwNCS7RE4pJOG70x1+5Qb0jMguD zElDzoszrLizdqK2FxmbMYSS0xRQVQlHqr5HPfUC8yAMtlWHjGvK8ebMidh+le62 JdNHzZAQr/VwuhNI9jq+YDrKzpNbc/YU5lnabcuL+iELM+oskvESBd9UpHYGsQum JzXdRp5FLKI33lDxw7Bueqw1lmv65uevwF60Zfkht0qejOrEgJ+LugnPmU7YJpUy OWV5Jnh+DH+sBhy/EkrVNi/F7Li2jjz9/cmH4I03h5FkCUy+iEAO23Mk1/uBPLCs qJEm5DNe5zM/L6970dc8NgHr+9pWAzpixFnAF53s+K2FCmpPqOAKji+dWvvlQNZI hRz1BVYO0/kIV204H6WC2PnnAqkFzM8+BA6Opd1UYdMRHTJgnTS5qWNNgerJwaBd qk/EyN0qmI7oGEdc8GNe66ILKSy/oIBHR1NXlzSR+5vZKTSBmBABeyBg3uyU6IOo 5xsox+qP5KhB56mfFPQ6cFIx9tLRjrxQhJEtRrh2qr2puWeqbgs= =/hEF -----END PGP SIGNATURE----- --Ru4EyvfZw5GbIopvRUvT37BhMBEhVBXLZ-- --===============6198894428692535159== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Jack-Devel mailing list [email protected] http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org --===============6198894428692535159==--