LinuxMusicians

Posted: **Mon Feb 11, 2019 1:49 pm**

Thanks for the new patches for proprietary mode, Drumfix! I'll hopefully get a chance to try them out soon.

Update on the stability of the old firmware version: still works great! I just had a recording session last night, with no issues at all.

I'm optimistic that these patches will allow me to use a new firmware; the touch mixer is pretty cool.

Posted: **Wed Feb 13, 2019 10:22 pm**

Hi, MOTU 1248 user here with the channel hopping problem. I'm so glad I've finally found an appropriate thread for this issue but disappointed that it seems to be a long running problem! I've tried KDE Neon, Neon + KXStudio Repos, Ubuntu 18.10, Ubuntu Studio 18.10, all to no avail.

Posted: **Thu Feb 14, 2019 2:15 pm**

KREAM wrote:Hi, MOTU 1248 user here with the channel hopping problem. I'm so glad I've finally found an appropriate thread for this issue but disappointed that it seems to be a long running problem! I've tried KDE Neon, Neon + KXStudio Repos, Ubuntu 18.10, Ubuntu Studio 18.10, all to no avail.

Did you try the bios regression ?

Posted: **Thu Feb 14, 2019 8:14 pm**

stanlea wrote: Did you try the bios regression ?

I did not since I use the touch mixer regularly during band rehearsal every weekend. I'm going to give Manjaro a shot just to try something that isn't ultimately Ubuntu-based.

Posted: **Fri Mar 15, 2019 9:42 pm**

Hi !

I stumbled upon L-Acoustics which seems to be actively working on an open source AVDECC protocol implementation for all platforms.
(The L-Acoustics gears I've come across so far has been top of the line and superior to anything else I've heard but that is not important in this case but that makes at least me having high hopes they are really putting an effort behind this.)

Their github repo is seemingly very active.
https://github.com/L-Acoustics/avdecc

Is this something that can help us get Motu AVB on linux a huge boost ??

From the github text:
"What is LA_avdecc

LA_avdecc is a set of open source libraries for controlling and monitoring AVB entities using the AVDECC protocol (IEEE 1722.1) compliant to Avnu Milan.

These libraries are written in pure C++17. They can be compiled on Windows, Linux and macOS, using standard development tools (procedure below). Unit tests and sample programs are also provided.

These libraries have already been used indirectly in many musical events throughout the world to control all kinds of AVB entities (list below). L-Acoustics' Network Manager 2.5 (and up) now relies on them for all its AVDECC functionalities in compliance to the Avnu Milan Specifications.

Another benefit is the support of Apple’s native API, which allows control of the input and output AVB streams of a Mac from itself (which is not possible with the libraries using PCAP).

We use GitHub issues for tracking requests and bugs."

and also:

"Tested AVB entities:

L-Acoustics: LA4X, LA12X, P1
Biamp: Tesira Forte
Avid: S6L
MOTU: 112D, 828, Traveller, StageBox16 (my comment here is that Motu Stage-B16 share firmware with Ultralite AVB)
MeyerSound: Galileo GALAXY, CAL
QSC: Q-SYS Cores
Apple: macOS Talker, Listener and Controller (El Capitan and later)
AudioScience: Hono AVB Mini"

Maybe this is news or not..

Cheers

Posted: **Sun Mar 24, 2019 12:12 am**

Greetings all;

I'm new to this forum, but not at all new to Linux audio, or Linux in general.

I think/hope this is big news, here are 2 links that may be of interest. I did a web search for "avdecc" and found this from PreSonus:
"PreSonus StudioLive® Series III console and rack mixers, NSB-series Stageboxes, and EarMix™ 16M Personal Monitor Mixers are fully compliant with the IEEE 1722.1 standard, which is the protocol for discovery, enumeration, connection management, and control of AVB devices, also known as AVDECC." The PreSonus link is here: https://www.presonus.com/learn/technica ... Networking

And this from Pivitec:
"This application can connect streams from talkers to listeners of devices supporting the Audio Video Discovery, Enumeration, Connection management protocol as defined by IEEE 1722.1. It runs on Mac OS X, Windows, and GNU/Linux." The Pivitec link is here: http://www.pivitec.com/avdecc-controller/

I think these are high end applications, but it does look like Linux compatibility is beginning to spread in pro audio hardware. If the LA_avdecc libraries can be integrated into ALSA/Jack, that single integration would (theoretically) open up a world of pro audio hardware...

Posted: **Sun Mar 31, 2019 2:04 pm**

Drumfix wrote:Ok, here is the pcm.c patch + a 3 quirks for proprietary 24, 32 and 64 channel mode.
Add the quirk that matches the number of channels you want to use. (this is why the file is not a patch file).
The number of channels must match the value you set in the "maxUSBToHost"

Note: the pcm patch is for my old 4.4.0 kernel.

Trying to apply this patch to 4.19 and got the following errors:

Code: Select all

 patch < motu-proprietary_pcm.c.patch
patching file pcm.c
Hunk #1 FAILED at 348.
Hunk #2 FAILED at 808.
Hunk #3 succeeded at 1353 (offset 78 lines).
Hunk #4 succeeded at 1364 (offset 78 lines).
Hunk #5 succeeded at 1388 (offset 78 lines).
Hunk #6 succeeded at 1418 (offset 78 lines).
Hunk #7 succeeded at 1633 (offset 78 lines).
Hunk #8 succeeded at 1704 (offset 59 lines).
Hunk #9 succeeded at 1735 (offset 59 lines).
2 out of 9 hunks FAILED -- saving rejects to file pcm.c.rej

I did not make any changes to the patch file other than dropping the .txt

I did modify quirks-table-h with the appropriate quirk.

What did I do wrong?

Posted: **Sun Mar 31, 2019 6:00 pm**

For 4.19 the first two hunks should be the attached patch.

Posted: **Mon Apr 01, 2019 4:13 pm**

Drumfix wrote:For 4.19 the first two hunks should be the attached patch.

Thank you!

I've had some struggles, first time compiling a kernel, it seems to be compiling fine now. I was getting errors. It seems many "guides" on this process were leaving out a step here or there!

You said the quirk should go "behind" the MOTU fastlane quirk. Am I to interpret that as placing it before or after the existing quirk?

Hopefully before because that it how it is being compiled at the moment.

Posted: **Tue Apr 02, 2019 5:43 pm**

When I did this, I needed to update the line numbers in the patch files, but it was reasonably obvious where the patches belonged. I assumed it was a matter of a slightly different kernel version.

Posted: **Wed Apr 03, 2019 10:50 pm**

I made it through the kernel compilation process with the above patch and quirk applied. I am having trouble setting my 8pre-ES to proprietary mode.

I tried the above curl commands with USB only, tried them with a network cable and changing the curl to reflect the net id on the MOTU. Qjackctrl recognizes that the MOTU is connected, but is unable to start jack. (pasuspender -- jackd)

Code: Select all

18:49:06.112 Statistics reset.
18:49:06.132 ALSA connection change.
Cannot read socket fd = 24 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open qjackctl client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
18:49:11.185 ALSA connection graph change.
18:49:23.888 JACK is starting...
18:49:23.889 /usr/bin/pasuspender -- jackd -P97 -t50000 -dalsa -r44100 -p256 -n3 -D -Chw:AVB -Phw:AVB -i24 -o24
Cannot read socket fd = 24 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open qjackctl client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
18:49:23.936 JACK was started with PID=8079.
`default' server already active
Failed to open server
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
18:49:23.945 JACK was stopped
18:49:31.142 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info.
Cannot read socket fd = 24 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open qjackctl client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock

Where do I go next?

Posted: **Thu Apr 04, 2019 12:32 am**

The interface shows up in the list of connected USB devices but ifconfig does not list any USB devices.

In the 8Pre-ES settings, it shows USB2 mode, so it looks like it's already in proprietary mode, but I don't know if the channel count is correct.

EDIT: After no success connecting directly, I connected the interface to a router and was able to pass the curl commands to set mode and number of channels. I'm still unable to get jack to work with it. Jack does work with onboard audio.

EDIT: EDIT: Rolled back to 4.15 with no patches. Able to start jack with the 8pre-ES, but not without channel swapping. There must be something wrong with either the patch, the quirk or the way that I applied them to 4.19

Posted: **Fri Apr 05, 2019 10:43 pm**

Compiled the 4.19 kernel and applied the real-time patch. Was able to play audio through reaper for quite a while before the channels began to swap.

Added the pcm.c patch and quirk, recompiled. Unable to start jack, keep getting "Cannot use real-time scheduling (RR/97)(1: Operation not permitted)
AcquireSelfRealTime error
Could not connect to JACK server as client. - Overall operation failed. - Server communication error."

Code: Select all

18:32:44.228 Statistics reset.
18:32:44.282 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
18:32:44.354 ALSA connection graph change.
18:32:59.249 JACK is starting...
18:32:59.249 /usr/bin/pasuspender -- jackd -P97 -t50000 -dalsa -r44100 -p512 -n3 -D -Chw:AVB,0 -Phw:AVB,0 -i24 -o24
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
18:32:59.334 JACK was started with PID=4056.
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 97
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio2
creating alsa driver ... hw:AVB,0|hw:AVB,0|512|3|44100|24|24|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 512 frames (11.6 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
ALSA: use 3 periods for playback
Cannot use real-time scheduling (RR/97)(1: Operation not permitted)
AcquireSelfRealTime error
18:33:06.476 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info.
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client
Cannot open qjackctl client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
Unknown request 4294967295
CheckSize error size = 0 Size() = 12
CheckRead error
18:33:08.529 JACK is stopping...
18:33:08.583 JACK was stopped
18:33:08.587 JACK has crashed.
Jack main caught signal 15

I am at a loss what to do. I've definitely learned my way around linux a bit more the past few days, but am anxious to get back to making music. I love this interface, but being so new, it does not have older firmware versions available that are stable with linux.

Any insight would be greatly appreciated, otherwise it is back to Windows find another interface that works out of the box.

Posted: **Fri Apr 05, 2019 10:45 pm**

Compiled the 4.19 kernel and applied the real-time patch. Was able to play audio through reaper for quite a while before the channels began to swap.

Added the pcm.c patch and quirk, recompiled. Unable to start jack, keep getting "Cannot use real-time scheduling (RR/97)(1: Operation not permitted)
AcquireSelfRealTime error
Could not connect to JACK server as client. - Overall operation failed. - Server communication error."

Code: Select all

18:32:44.228 Statistics reset.
18:32:44.282 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
18:32:44.354 ALSA connection graph change.
18:32:59.249 JACK is starting...
18:32:59.249 /usr/bin/pasuspender -- jackd -P97 -t50000 -dalsa -r44100 -p512 -n3 -D -Chw:AVB,0 -Phw:AVB,0 -i24 -o24
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
18:32:59.334 JACK was started with PID=4056.
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 97
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio2
creating alsa driver ... hw:AVB,0|hw:AVB,0|512|3|44100|24|24|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 512 frames (11.6 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
ALSA: use 3 periods for playback
Cannot use real-time scheduling (RR/97)(1: Operation not permitted)
AcquireSelfRealTime error
18:33:06.476 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info.
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client
Cannot open qjackctl client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
Unknown request 4294967295
CheckSize error size = 0 Size() = 12
CheckRead error
18:33:08.529 JACK is stopping...
18:33:08.583 JACK was stopped
18:33:08.587 JACK has crashed.
Jack main caught signal 15

I am at a loss what to do. I've definitely learned my way around linux a bit more the past few days, but am anxious to get back to making music. I love this interface, but being so new, it does not have older firmware versions available that are stable with linux.

Any insight would be greatly appreciated, otherwise it is back to Windows or find another interface that works out of the box.

Posted: **Fri Apr 05, 2019 10:46 pm**

supereb wrote:Compiled the 4.19 kernel and applied the real-time patch. Was able to play audio through reaper for quite a while before the channels began to swap.

Added the pcm.c patch and quirk, recompiled. Unable to start jack, keep getting "Cannot use real-time scheduling (RR/97)(1: Operation not permitted)
AcquireSelfRealTime error
Could not connect to JACK server as client. - Overall operation failed. - Server communication error."

Code: Select all

18:32:44.228 Statistics reset.
18:32:44.282 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
18:32:44.354 ALSA connection graph change.
18:32:59.249 JACK is starting...
18:32:59.249 /usr/bin/pasuspender -- jackd -P97 -t50000 -dalsa -r44100 -p512 -n3 -D -Chw:AVB,0 -Phw:AVB,0 -i24 -o24
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
18:32:59.334 JACK was started with PID=4056.
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 97
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio2
creating alsa driver ... hw:AVB,0|hw:AVB,0|512|3|44100|24|24|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 512 frames (11.6 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format
ALSA: use 3 periods for playback
Cannot use real-time scheduling (RR/97)(1: Operation not permitted)
AcquireSelfRealTime error
18:33:06.476 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info.
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client
Cannot open qjackctl client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
Unknown request 4294967295
CheckSize error size = 0 Size() = 12
CheckRead error
18:33:08.529 JACK is stopping...
18:33:08.583 JACK was stopped
18:33:08.587 JACK has crashed.
Jack main caught signal 15

I am at a loss what to do. I've definitely learned my way around linux a bit more the past few days, but am anxious to get back to making music. I love this interface, but being so new, it does not have older firmware versions available that are stable with linux.

Any insight would be greatly appreciated, otherwise it is back to Windows or find another interface that works with Linux out of the box.

LinuxMusicians

Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB

Re: Ultralite AVB