jack_umidi client name too long

Goran Mekić

unread,

Jun 14, 2018, 6:43:02 PM6/14/18

to

Hello,

I'm trying to get my USB MIDI to work with jack and this is current
result:

# jack_umidi -d /dev/umidi2.0 -n 'umidi'
"M-Audio USB MS1x1 MIDI Interface #0" is too long to be used as a JACK client name.
Please use 33 characters or less.
jack_umidi: Could not connect to the JACK server. Run jackd first?

It behaves the same if I remove "-n umidi". Does anyone know what is the
proper way to use jack_umidi when the device name is long? Thanx!

Regards,
meka

signature.asc

Shane Ambler

unread,

Jun 15, 2018, 1:35:45 AM6/15/18

to

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.

To use a usb midi keyboard I use -

jackd --no-realtime -d oss &
jack_umidi -C /dev/umidi0.0 -B

The "&" for jackd and "-B" for jack_umidi put them in the background so
you can close your terminal and they keep running.

Here is a script I use to automate it -
https://gist.github.com/sambler/67bf0b374d7b9c27e7cec1dd2befbcf2

--
FreeBSD - the place to B...Software Developing

Shane Ambler

_______________________________________________
freebsd-m...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-multimedia
To unsubscribe, send any mail to "freebsd-multime...@freebsd.org"

Goran Mekić

unread,

Jun 15, 2018, 4:47:02 AM6/15/18

to

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.

signature.asc

Shane Ambler

unread,

Jun 16, 2018, 12:17:55 AM6/16/18

to

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.

Goran Mekić

unread,

Jun 16, 2018, 1:16:51 PM6/16/18

to

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.

signature.asc

Hans Petter Selasky

unread,

Jun 17, 2018, 5:57:20 AM6/17/18

to

Maybe the name length can be stripped down?

--HPS

Goran Mekić

unread,

Jun 17, 2018, 6:12:48 AM6/17/18

to

On Sun, Jun 17, 2018 at 11:56:12AM +0200, Hans Petter Selasky wrote:
> Maybe the name length can be stripped down?
>
> --HPS

Maybe, but how? I though -n option will do that, but I get the same
error.

signature.asc

Hans Petter Selasky

unread,

Jun 17, 2018, 6:34:45 AM6/17/18

to

Have a look at the source code. I think the current buffer is bigger
than the limit!