Date: Sat, 16 Jun 2018 13:47:02 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: =?UTF-8?Q?Goran_Meki=c4=87?= <meka@tilda.center> Cc: freebsd-multimedia@freebsd.org Subject: Re: jack_umidi client name too long Message-ID: <2a838efe-7954-4f39-323e-603135e48cc6@ShaneWare.Biz> In-Reply-To: <20180615084612.e6af43xzxx4nmypj@hal9000.cicici.home> References: <20180614224209.huk5nusli4m5ngqn@hal9000.cicici.home> <2cd19236-1475-e374-9427-27dfdfc7ca2c@ShaneWare.Biz> <20180615084612.e6af43xzxx4nmypj@hal9000.cicici.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/06/2018 18:16, Goran Mekić wrote: > On Fri, Jun 15, 2018 at 03:04:04PM +0930, Shane Ambler wrote: >> Not sure if the long name is an error stopping anything or just a >> notice, the following error "Could not connect to the JACK server" >> would be why nothing works. > Jackd is running and if I try with umidi0.0 or umidi1.0 it works and I > can connect to jack. > 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. -- FreeBSD - the place to B...Software Developing Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a838efe-7954-4f39-323e-603135e48cc6>