since I spent so much time finding a cool usb-interface for linux, I hope I can help somebody else with this.
I'm using a Ultralite AVB with ALSA and/or JACK 1 with some problems.
Jack1 latency is down to 2.9ms@44100Hz (64/3) without any xruns. Jack2 has some xruns no matter what the latency is...
To keep this short, here's a pro/con list:
- Low Latency
- 24in/24out with alsa running smooth
- nice ethernet based web interface (no need for drivers!)
- has json-api --> script based volume/mute/route/whateveryouwant !
- nice sounding dac / dsp mixes without any noise/coloring even with strange values (1% volume in kodi and the mixers routed with multiple +12dB to the speakers)
- "random" bit-crusher like playback errors when using processing with jack or high load, with and without xruns (probably due to incorrect delay settings or other problems with the alsa kernel driver)
- display is always on (will mod hw, trim-poti or switch...)
- unmutable cracks when input-rate changes (mind your tweeters)
- switching sample rate (i.e. with jack) will not work at first attempt, starting jack like 3 times makes it switch
- sample rate after power-on is not reliable set at what you want
- hw-controls not usable for much (json+python could fix this...i.e. reading main-vol and writing to json-something)
- has to be started by pressing the power button several seconds (nogo for rack usage)
- json interface does no or only little sanity checking for anything (mind your tweeters and your neighbors, don't change unknown systemsettings)
- startup time is about 30sec
- partially loses configuration when the interface crashes or the power cable gets unplugged accidently (backup your settings)
Note that most of these problems exist for windows and especially macOS users as well (see http://www.motunation.com/forum/ for many unsolved pita problems with nearly all MOTU products).
Right now (18/06), I'm using the Ultralite just as a mixer with web interface.
It's powered up all the time and I do things like setting sample rate before my tv/speakers get powered on.
I'm still somehow happy with it, mainly because I don't really "do" anything with it but changing volume...
This interface would ROCK given just a few bugfixes from MOTU .
Update june 2020
I'll try to summarize at least some things pointed out in this thread until now.
- USB cables can go bad, if it worked before or it doesn't work at all, try to change it.
- You might have less xruns on different USB ports, use
Code: Select all
$ lsusb -t -v
- If you're using USB 2.0, you have to change (irq)priorities: viewtopic.php?f=6&t=18046&p=117396&hili ... ty#p117396.
Ultralite AVB ES
Since 2020(?) there is an Ultralite AVB ES version, which will not work good without a kernel patch. Downgrading is not possible. It has the ESS sabre32 as DAC.
- To use AVB you need a NIC with intel's i210 chipset, see https://github.com/Drumfix/avb4linux. This is restricted to 8 channels.
- Maybe the real difference between "old/working" and"new/broken" firmware is mentioned here viewtopic.php?p=118176#p118176.
Everything below is for the non-ES version
- 1.2.9+479 is the last version which will not need a kernel patch to avoid channel hopping, but has no touch console. Bitcrush might occur.
- 1.3.2+520 1.3.4+558 (+touch console) should work OK, as well (not for me) viewtopic.php?p=116259#p116259.
- Also, as cross-reference see https://lists.linuxaudio.org/archives/l ... 12631.html if you have problems with your Ultralite AVB when dual-booting windows and linux. Maybe such problems could also arise from a single windows boot you don't know about (i.e. if you bought it second hand).
Thanks to drumfix, there seems to be a possibility for a kernel patch in the near future.