Date: Sun, 17 Jun 2018 11:56:12 +0200 From: Hans Petter Selasky <hps@selasky.org> To: =?UTF-8?Q?Goran_Meki=c4=87?= <meka@tilda.center>, Shane Ambler <FreeBSD@ShaneWare.Biz> Cc: freebsd-multimedia@freebsd.org Subject: Re: jack_umidi client name too long Message-ID: <53dbe3eb-4cef-bb84-1502-e69d8816bfef@selasky.org> In-Reply-To: <20180616171340.oyuyj4r25ehih3xc@thinker.my.domain> References: <20180614224209.huk5nusli4m5ngqn@hal9000.cicici.home> <2cd19236-1475-e374-9427-27dfdfc7ca2c@ShaneWare.Biz> <20180615084612.e6af43xzxx4nmypj@hal9000.cicici.home> <2a838efe-7954-4f39-323e-603135e48cc6@ShaneWare.Biz> <20180616171340.oyuyj4r25ehih3xc@thinker.my.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/16/18 19:13, Goran Mekić wrote: > On Sat, Jun 16, 2018 at 01:47:02PM +0930, Shane Ambler wrote: >> You originally tried /dev/umidi2.0 - this has to match the actual device >> node created for it, which can change every time you attach the device. >> You'll notice in the script I linked to that I grep for umidi devices so >> I don't have to manually look for the correct ID each time. > > I do have 3 USB devices, and umidi2.0 is hooked the last. My point was > that it works with other devices, hence jackd is started and jack_lsp > lists that port. I thought that -n option would do the trick, but I get > the same error. > Maybe the name length can be stripped down? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53dbe3eb-4cef-bb84-1502-e69d8816bfef>