From owner-freebsd-multimedia@freebsd.org  Sun Jun 17 09:56:31 2018
Return-Path: <owner-freebsd-multimedia@freebsd.org>
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 A39DD1018128
 for <freebsd-multimedia@mailman.ysv.freebsd.org>;
 Sun, 17 Jun 2018 09:56:31 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 31FA16803C
 for <freebsd-multimedia@freebsd.org>; Sun, 17 Jun 2018 09:56:30 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.128.70])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id BD3B626037E;
 Sun, 17 Jun 2018 11:56:27 +0200 (CEST)
Subject: Re: jack_umidi client name too long
To: =?UTF-8?Q?Goran_Meki=c4=87?= <meka@tilda.center>,
 Shane Ambler <FreeBSD@ShaneWare.Biz>
Cc: freebsd-multimedia@freebsd.org
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>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <53dbe3eb-4cef-bb84-1502-e69d8816bfef@selasky.org>
Date: Sun, 17 Jun 2018 11:56:12 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180616171340.oyuyj4r25ehih3xc@thinker.my.domain>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-multimedia@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Multimedia discussions <freebsd-multimedia.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-multimedia>, 
 <mailto:freebsd-multimedia-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-multimedia/>
List-Post: <mailto:freebsd-multimedia@freebsd.org>
List-Help: <mailto:freebsd-multimedia-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-multimedia>, 
 <mailto:freebsd-multimedia-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2018 09:56:31 -0000

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