Ultralite AVB

Talk about your MIDI interfaces, microphones, keyboards...

Moderators: khz, MattKingUSA

Musinux
Established Member
Posts: 42
Joined: Sun Jan 14, 2018 8:38 pm

Re: Ultralite AVB

Post by Musinux »

shellwalker wrote: Sun Jan 17, 2021 7:36 pm Good thought!
Well, actually I totally forgot that windows doesn't use class compliant mode, but macOS does, right?

wrl's patch doesn't work for me, as well.
shellwalker
Established Member
Posts: 21
Joined: Sun Jan 03, 2021 1:54 pm

Re: Ultralite AVB

Post by shellwalker »

wrl wrote: Sun Jan 17, 2021 3:38 am Yeah it seems like this approach was a dud. I've got another theory I'm investigating but nothing concrete yet.

-w
Hi,
How is it going so far?
Do you need any help?
MOTU 828mk3, MOTU 828ES, Cakewalk by Bandlab, Kubuntu 20.04
User avatar
stean
Posts: 2
Joined: Sat Jan 30, 2021 4:43 pm

Re: Ultralite AVB

Post by stean »

shellwalker wrote: Tue Jan 12, 2021 12:31 pm This post is aimed at providing a quick and simple guide for testing the kernel patch provided by @wrl.
That patch is aimed at fixing the channel drifting issue and should in theory be applicable to MOTU 828ES as well as Ultralite AVB devices.

Please note: the patch does not (yet) provide a stable solution on all devices. It may or may not work on your device. The purpose of this guide is to help more people test it on their setups in the hope that we can detect similarities between systems that do work and those that don't.

Further note: this guide is built on my own approach, which is Ubuntu based. Further I'm assuming that your system is already configured with the appropriate build tools (gcc compiler, make etc.). Furthermore: you carry all risks by yourself. I'm not responsible for any damage caused by following this recipe.
................................................... etc
[/list]
Hello, Thank you all for the fight with the driver for the Motu Ultralite AVB (es) under Linux. I cannot boot in the next-kernel with the steps from user shellwalker.
Error :

Code: Select all

dracut-initqueue: Warning: dracut-initqueue timeout - starting timout script
....
dracut-initqueue: Warning: could not boot.
Under opensuse tumbleweed, i don´t know how i can install the patch to test the driver under opensuse.

Is there a way to load the snd-usb driver per Linux kernel modules and e.g. modprobe ?

Sorry for my bad english. I am a user and a rookie in Kernelpatching

I will install ubuntu on my old desktop-pc and will test the patch again. :roll:

Greetings from Germany
Motu 896 HD Firewire, MOTU Ultralite AVB es, OS: Opensuse Tumbleweed, Notebook: Acer Nirro 5 (AN 517-51)i7-9750H,
Desktop1: Ryzen 7 2700x, Desktop2: Intel i7- i7-860
stanlea
Established Member
Posts: 630
Joined: Wed Apr 25, 2012 9:49 pm

Re: Ultralite AVB

Post by stanlea »

Code: Select all

studio@studio-ThinkPad-W530:~/linux$ make O=../build_wrl_patch_1
make[1] : on entre dans le répertoire « /home/studio/build_wrl_patch_1 »
  SYNC    include/config/auto.conf.cmd
  GEN     Makefile
  GEN     Makefile
  SYSTBL  arch/x86/include/generated/asm/syscalls_32.h
  SYSHDR  arch/x86/include/generated/asm/unistd_32_ia32.h
  SYSHDR  arch/x86/include/generated/asm/unistd_64_x32.h
  SYSTBL  arch/x86/include/generated/asm/syscalls_64.h
  SYSHDR  arch/x86/include/generated/uapi/asm/unistd_32.h
  SYSHDR  arch/x86/include/generated/uapi/asm/unistd_64.h
  SYSHDR  arch/x86/include/generated/uapi/asm/unistd_x32.h
  HOSTCC  arch/x86/tools/relocs_32.o
  HOSTCC  arch/x86/tools/relocs_64.o
  HOSTCC  arch/x86/tools/relocs_common.o
  HOSTLD  arch/x86/tools/relocs
  HOSTCC  scripts/selinux/genheaders/genheaders
  HOSTCC  scripts/selinux/mdp/mdp
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/sorttable
  HOSTCC  scripts/asn1_compiler
  HOSTCC  scripts/extract-cert
/home/studio/linux/scripts/extract-cert.c:21:10: fatal error: openssl/bio.h: Aucun fichier ou dossier de ce type
   21 | #include <openssl/bio.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.host:95 : scripts/extract-cert] Erreur 1
make[1]: *** [/home/studio/linux/Makefile:1190 : scripts] Erreur 2
make[1] : on quitte le répertoire « /home/studio/build_wrl_patch_1 »
make: *** [Makefile:185 : __sub-make] Erreur 2
/code]
shellwalker
Established Member
Posts: 21
Joined: Sun Jan 03, 2021 1:54 pm

Re: Ultralite AVB

Post by shellwalker »

stanlea wrote: Tue Feb 02, 2021 3:38 pm

Code: Select all

studio@studio-ThinkPad-W530:~/linux$ make O=../build_wrl_patch_1
make[1] : on entre dans le répertoire « /home/studio/build_wrl_patch_1 »
  SYNC    include/config/auto.conf.cmd
  GEN     Makefile
...
  HOSTCC  scripts/extract-cert
/home/studio/linux/scripts/extract-cert.c:21:10: fatal error: openssl/bio.h: Aucun fichier ou dossier de ce type
   21 | #include <openssl/bio.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.host:95 : scripts/extract-cert] Erreur 1
make[1]: *** [/home/studio/linux/Makefile:1190 : scripts] Erreur 2
make[1] : on quitte le répertoire « /home/studio/build_wrl_patch_1 »
make: *** [Makefile:185 : __sub-make] Erreur 2
From https://translate.google.de/?sl=auto&tl ... =translate
I gain that the file bio.h is missing on your system.

A quick google-search shows that the open ssl development package is missing your system.
If I understood correctly, you are using OpenSuse, whose package system I'm not familiar with. But I'm sure you'll be able to find out how to install the libssl-devel package (or whatever it is called on SuSE).
MOTU 828mk3, MOTU 828ES, Cakewalk by Bandlab, Kubuntu 20.04
stanlea
Established Member
Posts: 630
Joined: Wed Apr 25, 2012 9:49 pm

Re: Ultralite AVB

Post by stanlea »

Thanks a lot shellwalker, I'm using Ubuntu 20.04 LTS. Anyway, I'm going to investigate about the missing package.

edit :
compiling and installing went fine finally now here"s is the display of sudo dmesg -Tw

Code: Select all

new high-speed USB device number 9 using ehci-pci
[mer. févr.  3 15:18:53 2021] usb 2-1.8.2: config 1 interface 6 altsetting 1 has a duplicate endpoint with address 0x9, skipping
[mer. févr.  3 15:18:53 2021] usb 2-1.8.2: config 1 interface 7 altsetting 1 has a duplicate endpoint with address 0x87, skipping
[mer. févr.  3 15:18:53 2021] usb 2-1.8.2: New USB device found, idVendor=07fd, idProduct=0005, bcdDevice= 2.00
[mer. févr.  3 15:18:53 2021] usb 2-1.8.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[mer. févr.  3 15:18:53 2021] usb 2-1.8.2: Product: 828ES
[mer. févr.  3 15:18:53 2021] usb 2-1.8.2: Manufacturer: MOTU
[mer. févr.  3 15:18:53 2021] usb 2-1.8.2: SerialNumber: 0001f2fffe00c13b
But now no way to start it with Cadence, here's the log :
Starting jack server...

Code: Select all

Wed Feb  3 15:20:38 2021: JACK server starting in realtime mode with priority 10
Wed Feb  3 15:20:38 2021: self-connect-mode is "Don't restrict self connect requests"
Wed Feb  3 15:20:38 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:38 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:38 2021: creating alsa driver ... hw:D828ES,0|hw:D828ES,0|128|3|48000|24|24|hwmon|hwmeter|-|32bit
Wed Feb  3 15:20:38 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:38 2021: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Wed Feb  3 15:20:38 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:38 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:38 2021: ERROR: Cannot initialize driver
Wed Feb  3 15:20:38 2021: ERROR: JackServer::Open failed with -1
Wed Feb  3 15:20:38 2021: ERROR: Failed to open server
Wed Feb  3 15:20:48 2021: ------------------
Wed Feb  3 15:20:48 2021: Controller activated. Version 1.9.17 (0+) built on Thu Jan 14 12:21:05 2021
Wed Feb  3 15:20:48 2021: Loading settings from "/home/studio/.config/jack/conf.xml" using expat_2.2.9 ...
Wed Feb  3 15:20:48 2021: setting parameter 'engine':'driver':'(null)' to value "alsa"
Wed Feb  3 15:20:48 2021: setting parameter 'engine':'realtime':'(null)' to value "true"
Wed Feb  3 15:20:48 2021: setting parameter 'engine':'verbose':'(null)' to value "false"
Wed Feb  3 15:20:48 2021: setting parameter 'engine':'client-timeout':'(null)' to value "500"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'netone':'period' to value "128"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'device' to value "hw:0"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'capture' to value "hw:D828ES,0"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'playback' to value "hw:D828ES,0"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'rate' to value "48000"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'period' to value "128"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'nperiods' to value "3"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'hwmon' to value "true"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'hwmeter' to value "true"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'duplex' to value "true"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'softmode' to value "false"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'monitor' to value "true"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'dither' to value "n"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'inchannels' to value "24"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'outchannels' to value "24"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'shorts' to value "false"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'alsa':'midi-driver' to value "seq"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'firewire':'period' to value "128"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'dummy':'capture' to value "24"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'dummy':'playback' to value "24"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'dummy':'rate' to value "48000"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'dummy':'monitor' to value "true"
Wed Feb  3 15:20:48 2021: setting parameter 'drivers':'dummy':'period' to value "256"
Wed Feb  3 15:20:48 2021: Listening for D-Bus messages
Wed Feb  3 15:20:52 2021: Starting jack server...
Wed Feb  3 15:20:52 2021: JACK server starting in realtime mode with priority 10
Wed Feb  3 15:20:52 2021: self-connect-mode is "Don't restrict self connect requests"
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: creating alsa driver ... hw:D828ES,0|hw:D828ES,0|128|3|48000|24|24|hwmon|hwmeter|-|32bit
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: ERROR: Cannot initialize driver
Wed Feb  3 15:20:52 2021: ERROR: JackServer::Open failed with -1
Wed Feb  3 15:20:52 2021: ERROR: Failed to open server

shellwalker
Established Member
Posts: 21
Joined: Sun Jan 03, 2021 1:54 pm

Re: Ultralite AVB

Post by shellwalker »

stanlea wrote: Wed Feb 03, 2021 10:00 am ...
But now no way to start it with Cadence, here's the log :
Starting jack server...

Code: Select all

Wed Feb  3 15:20:38 2021: JACK server starting in realtime mode with priority 10
Wed Feb  3 15:20:38 2021: self-connect-mode is "Don't restrict self connect requests"
Wed Feb  3 15:20:38 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:38 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:38 2021: creating alsa driver ... hw:D828ES,0|hw:D828ES,0|128|3|48000|24|24|hwmon|hwmeter|-|32bit
...
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: creating alsa driver ... hw:D828ES,0|hw:D828ES,0|128|3|48000|24|24|hwmon|hwmeter|-|32bit
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: ERROR: control open "hw:D828ES" (No such device)
Wed Feb  3 15:20:52 2021: ERROR: Cannot initialize driver
Wed Feb  3 15:20:52 2021: ERROR: JackServer::Open failed with -1
Wed Feb  3 15:20:52 2021: ERROR: Failed to open server

Sorry I can't help you here. Never used Cadence b4 and I don't have much experience with jack either. I use Ardour for my tests.
At least it seems that the MOTU device as such has been somehow recognized by the system, otherwise it would not show up in the logs, right?
Just a thought: could it be that some other application is competing with the device access?
MOTU 828mk3, MOTU 828ES, Cakewalk by Bandlab, Kubuntu 20.04
stanlea
Established Member
Posts: 630
Joined: Wed Apr 25, 2012 9:49 pm

Re: Ultralite AVB

Post by stanlea »

Thanks for the help. For now, I'll keep my previous kernel, it works well enough for my needs.
buonamorte.records
Established Member
Posts: 31
Joined: Tue Apr 07, 2020 4:31 am

Re: Ultralite AVB

Post by buonamorte.records »

Hi LinMusicians,
I own a good working 828es and I'm going to buy a Ultralite AVB or a 624 AVB with a switch. I'm using the first firmware on AVL-MX or Kubuntu 20.04. I use to wait the turning on of the interface, then I turn on the laptop (Acer Nitro 5). I can do some tests but I need to know exactly what you need to know...
shellwalker
Established Member
Posts: 21
Joined: Sun Jan 03, 2021 1:54 pm

Re: Ultralite AVB

Post by shellwalker »

buonamorte.records wrote: Fri Feb 05, 2021 1:57 am Hi LinMusicians,
I own a good working 828es and I'm going to buy a Ultralite AVB or a 624 AVB with a switch. I'm using the first firmware on AVL-MX or Kubuntu 20.04. I use to wait the turning on of the interface, then I turn on the laptop (Acer Nitro 5). I can do some tests but I need to know exactly what you need to know...
Hi buonamorte,
in a nut-shell here's the current status:
  • We are fighting the so-called channel drifting issue under Class Compliant mode - i.e. the interface does work somehow, but the outgoing signal sometimes ceases to be heard on the assigned channel, but reappears, if at all, on some other channel (and may also for some time sound distorted).
  • @drumfix provided something for the Ultralite AVB (though I'm not sure were to find that, and I've not tried it out myself on my 828ES) and it seems to require an Intel i210 nic and uses the "Windows USB" mode instead of the class compliant mode. Someone please correct me if I got it all wrong...!! ;-)
  • As far as I could tell from the foregoing discussions, @drumfix' change actually did not work for some that did try it out.
  • My understanding of the discussions so far is that the issue may be related to a bad or missing implementation in the linux kernel for supporting USB "implicit feedback mode" (whatever that is...) which MOTU appears to have activated in later firmware version.
  • @wrl had a new idea and provided a corresponding patch which appeared to work on his system quite reliably.
  • But @wrl's patch did not work on my system and also does not on work for @root2 either. Not sure what the testing results for @Musinux were.
  • @wrl said he has another idea (viewtopic.php?p=128041#p128041), but we've not seen an update on this yet. Keeping our fingers crossed ;-)
Do you happen to have kernel dev experience and/or USB protocol expertise? If yes, then it would be great if you could jump in and help debug/fix stuff.
Of course simply testing and providing feedback on your results is also appreciated!
Testing instructions for @wrl's "first" approach can be found here: viewtopic.php?p=127891#p127891
I've not seen comprehensive step-by-step testing instructions for drumfix' approach. I guess for that you'll have to read through the whole thread and gather all pieces together. But it may be worth it (and if/while you are at it, maybe you could even create that comprehensive how-to-guide for the drumfix approach? :P )
MOTU 828mk3, MOTU 828ES, Cakewalk by Bandlab, Kubuntu 20.04
ahellquist
Established Member
Posts: 58
Joined: Mon Jul 01, 2013 12:28 am

Re: Ultralite AVB

Post by ahellquist »

buonamorte.records wrote: Fri Feb 05, 2021 1:57 am Hi LinMusicians,
I own a good working 828es and I'm going to buy a Ultralite AVB or a 624 AVB with a switch. I'm using the first firmware on AVL-MX or Kubuntu 20.04. I use to wait the turning on of the interface, then I turn on the laptop (Acer Nitro 5). I can do some tests but I need to know exactly what you need to know...
Consider buying a Presonus avb switch instead of the one Motu makes. It is much more rigid than the Motu.
User avatar
stean
Posts: 2
Joined: Sat Jan 30, 2021 4:43 pm

Re: Ultralite AVB

Post by stean »

shellwalker wrote: Fri Feb 05, 2021 8:21 am
Hi buonamorte,
in a nut-shell here's the current status:
  • We are fighting the so-called channel drifting issue under Class Compliant mode - i.e. the interface does work somehow, but the outgoing signal sometimes ceases to be heard on the assigned channel, but reappears, if at all, on some other channel (and may also for some time sound distorted).
  • @drumfix provided something for the Ultralite AVB (though I'm not sure were to find that, and I've not tried it out myself on my 828ES) and it seems to require an Intel i210 nic and uses the "Windows USB" mode instead of the class compliant mode. Someone please correct me if I got it all wrong...!! ;-)
  • As far as I could tell from the foregoing discussions, @drumfix' change actually did not work for some that did try it out.
  • My understanding of the discussions so far is that the issue may be related to a bad or missing implementation in the linux kernel for supporting USB "implicit feedback mode" (whatever that is...) which MOTU appears to have activated in later firmware version.
  • @wrl had a new idea and provided a corresponding patch which appeared to work on his system quite reliably.
  • But @wrl's patch did not work on my system and also does not on work for @root2 either. Not sure what the testing results for @Musinux were.
  • @wrl said he has another idea (viewtopic.php?p=128041#p128041), but we've not seen an update on this yet. Keeping our fingers crossed ;-)
Yes We NEED an comprehensible (in german : nachvollziehbarer) NEW STEP-By-STEP- Way.

Requirement for Testing:

A) Base System : New 5.11 Kernel with an Easy-To-Patch-Mode (USB Linux System (Pendrive) where excellent; nobody wont kill the own running system)
B) Same Informationsystems (e.g. dsmeg, Alsa, Journal -d etc...) about Hardwarere recognation, Erros and Results ....
C) Cross-Connection to other "Construction sites" in these forum (e.g. Moti828es, and other Devices witch similar Problem ( e.g. implicit feedback)
D) A general "Audio-Test-Benchmark", with check the Quality , Stability , Use of Channels and Midi, Soundserver/ Applikations (Alsa, Pulse, Jack)
E) then compatibility with other Linux-derivatives / Distros
F) a general Feedback Information of succees or defeat

Thank You Mr. Shellwalker for your honest words and for your diligence

sorry for my bad english
Motu 896 HD Firewire, MOTU Ultralite AVB es, OS: Opensuse Tumbleweed, Notebook: Acer Nirro 5 (AN 517-51)i7-9750H,
Desktop1: Ryzen 7 2700x, Desktop2: Intel i7- i7-860
buonamorte.records
Established Member
Posts: 31
Joined: Tue Apr 07, 2020 4:31 am

Re: Ultralite AVB

Post by buonamorte.records »

Hi @shellwalker , @ahellquist @stean . Thank you all for your replies!

I don't have so much technical experience on usb but I can surely try this stuff, give info or write an how to.

The big question, for me, is that my 828es works great with the first firmware and waiting for a complete startup before turning on the laptop.

After 7-8 hours, sometimes, the sound begins to do something strange, but I can save and restart and everything is fine..

So, if I've understood, you with the 828es are using a newer firmware, right?
shellwalker
Established Member
Posts: 21
Joined: Sun Jan 03, 2021 1:54 pm

Re: Ultralite AVB

Post by shellwalker »

buonamorte.records wrote: Sat Feb 06, 2021 11:51 pm Hi @shellwalker , @ahellquist @stean . Thank you all for your replies!

After 7-8 hours, sometimes, the sound begins to do something strange, but I can save and restart and everything is fine..

So, if I've understood, you with the 828es are using a newer firmware, right?
My unit came with v1.3.4+172 (Release Date 2018-08-01) pre-installed. That showed the drifting issue.
I've upgraded to v1.3.5+181 (Release Date 2019-05-13) which also shows the drifting issue.
Check at MOTU to see details about your firmware version here: https://motu.com/techsupport/technotes/ ... echangelog

I would guess that the strange sound you hear after 7-8 hours may be the drifting issue as well, however with some mid-term stability....
MOTU 828mk3, MOTU 828ES, Cakewalk by Bandlab, Kubuntu 20.04
buonamorte.records
Established Member
Posts: 31
Joined: Tue Apr 07, 2020 4:31 am

Re: Ultralite AVB

Post by buonamorte.records »

Hi @shellwalker ,
I'm using this: v1.3.2+59 (Release Date 2017-10-20)
The 7/8 hours problem happens only sometimes, usually it works out of the box...
Ah, no way to use the touch console, obviously...but all other stuff works, also the adat port (with an audient asp800)
I'm going to make some test as soon as possible!
Post Reply