From owner-freebsd-multimedia@freebsd.org Sat Jun 16 04:17:07 2018 Return-Path: Delivered-To: freebsd-multimedia@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B03401008C8A for ; Sat, 16 Jun 2018 04:17:07 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by mx1.freebsd.org (Postfix) with ESMTP id E651B72D98 for ; Sat, 16 Jun 2018 04:17:06 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp121-45-90-218.bras1.adl6.internode.on.net (HELO leader.local) ([121.45.90.218]) by ipmail06.adl2.internode.on.net with ESMTP; 16 Jun 2018 13:47:04 +0930 Subject: Re: jack_umidi client name too long To: =?UTF-8?Q?Goran_Meki=c4=87?= Cc: freebsd-multimedia@freebsd.org References: <20180614224209.huk5nusli4m5ngqn@hal9000.cicici.home> <2cd19236-1475-e374-9427-27dfdfc7ca2c@ShaneWare.Biz> <20180615084612.e6af43xzxx4nmypj@hal9000.cicici.home> From: Shane Ambler Message-ID: <2a838efe-7954-4f39-323e-603135e48cc6@ShaneWare.Biz> Date: Sat, 16 Jun 2018 13:47:02 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180615084612.e6af43xzxx4nmypj@hal9000.cicici.home> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jun 2018 04:17:07 -0000 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