Moderators: raboof, MattKingUSA, khz
@buonamorte.records mentioned this in the epic Ultralite AVB thread. It seems to me a step forward for Linux music -- a big manufacturer writing a kernel module.
https://www.merging.com/products/alsa_r ... s67_driver
It means a super high end interface like the new Neumann MT48 interface will have actual Linux support. Yes, you read that right!
I think it's interesting that when Linux support arrived, it was for a generalised, device independent format like AES 67. Merging's strapline is 'audio for the networking age', and Linux has been able to do networked audio since forever. Now the normal folks are waking up to that like it's some twenty first century miracle, and Linux is suitable to take advantage of networked audio hardware.
I'm thinking about selling my motu hardware and buy this new interface...i think it's great to have someone thinking about linux users and making an alsa driver!!
Hi,
I've wrote to Neumann to be sure about linux compatibility before a purchase. I'm now waiting for the answer but I've another question: does avb will be compatible with aes67? Does my actual motu device will be interoperable with the neumann mt48? I've read some stuff that seems to be open to this possibilities, other not. I'm confused...
Well, I was already wondering how much of a problem would it be to make RME AVB tool https://rme-audio.com/avb-tool.html or AVB-interfaced 12Mic https://rme-audio.com/12mic.html actually work.,
buonamorte.records wrote: ↑Sat Aug 19, 2023 10:32 amHi,
I've wrote to Neumann to be sure about linux compatibility before a purchase. I'm now waiting for the answer ...
And did you get any?
The MT48 is only tested to work on Mac and Windows 10/11 operating systems, it is not tested nor developed for Linux.
in this way, they're losing money...surely my money...
buonamorte.records wrote: ↑Sun Aug 27, 2023 9:43 am
Uhm, well then... its not clear to me whats their own page https://www.merging.com/products/alsa_r ... r#overview about. If their answer was "only tested to work on Mac and Windows 10/11 operating systems, it is not tested nor developed for Linux" then it does not make sense to me.
Just because Merging has an AES67 Linux driver doesn't mean other manufacturers will officially support Linux. AES67 is an Audio Engineering Society standard so as long as the device supports the standard it should work. Only thing you could do with the Neumann device is get one and try it.
Or get one of Merging's own devices - https://www.merging.com/products/interfaces
Merging is now part of Neumann. More correctly Sennheiser bought Neumann in 1991, and Merging last year. The MT48 interface is based on the Merging Anubis.
The MT48 manual can be downloaded on this page. The way they expect people to use it is as a USB interface. In the manual there is the usual "works on Mac without drivers, but install our proprietary crap for full functionality." This means there is a degree of class compliance. It may be worth asking Neumann exactly what functionality is lost when using the MT48 without the proprietary software, called 'MT48 Toolkit'.
When it was advertised the marketing said that all functions were accessible from the touchscreen on the interface itself, which would be good for Linux. Also there is a remote control app that uses a web browser, which would also be good for Linux. Unfortunately the way the manual tells us to access the web app is through MT48 Toolkit.
References to the ethernet port describe connecting other interfaces, particularly Merging interfaces, and putting the MT48 onto your network so the remote control app can be used. There is no mention of using AES67 as the primary connection to the computer. You would think it would work using the Merging ALSA driver, but you really would have to try it, and it may be fiddly.
Hi All,
I bought a Neumann MT48 hoping it would work anyway since it's advertised as Class Compliant but sadly I'm afraid it doesn't play nice with Linux.
It is seen by my computer but when I try to connect to it with Jack it gives me this message :
Code: Select all
Thu Mar 14 16:27:07 2024: Starting jack server...
Thu Mar 14 16:27:07 2024: JACK server starting in realtime mode with priority 99
Thu Mar 14 16:27:07 2024: self-connect-mode is "Don't restrict self connect requests"
Thu Mar 14 16:27:07 2024: Acquired audio card Audio4
Thu Mar 14 16:27:07 2024: creating alsa driver ... hw:MT48,0|hw:MT48,0|512|2|48000|32|16|hwmon|hwmeter|-|32bit
Thu Mar 14 16:27:07 2024: configuring for 48000Hz, period = 512 frames (10.7 ms), buffer = 2 periods
Thu Mar 14 16:27:07 2024: ERROR: ALSA: no playback configurations available (Invalid argument)
Thu Mar 14 16:27:07 2024: ERROR: ALSA: cannot configure capture channel
Thu Mar 14 16:27:07 2024: Released audio card Audio4
Thu Mar 14 16:27:07 2024: ERROR: Cannot initialize driver
Thu Mar 14 16:27:07 2024: ERROR: JackServer::Open failed with -1
Thu Mar 14 16:27:07 2024: ERROR: Failed to open serverI have tried different configurations to no avail.
If someone here have an idea for something I could try, let me know (I'm on a *buntu 22.04 base), otherwise I'll have to send it back I guess.
eamonn wrote: ↑Thu Mar 14, 2024 3:38 pmCode: Select all
Thu Mar 14 16:27:07 2024: Starting jack server... Thu Mar 14 16:27:07 2024: JACK server starting in realtime mode with priority 99 Thu Mar 14 16:27:07 2024: self-connect-mode is "Don't restrict self connect requests" Thu Mar 14 16:27:07 2024: Acquired audio card Audio4 Thu Mar 14 16:27:07 2024: creating alsa driver ... hw:MT48,0|hw:MT48,0|512|2|48000|32|16|hwmon|hwmeter|-|32bit Thu Mar 14 16:27:07 2024: configuring for 48000Hz, period = 512 frames (10.7 ms), buffer = 2 periods Thu Mar 14 16:27:07 2024: ERROR: ALSA: no playback configurations available (Invalid argument) Thu Mar 14 16:27:07 2024: ERROR: ALSA: cannot configure capture channel Thu Mar 14 16:27:07 2024: Released audio card Audio4 Thu Mar 14 16:27:07 2024: ERROR: Cannot initialize driver Thu Mar 14 16:27:07 2024: ERROR: JackServer::Open failed with -1 Thu Mar 14 16:27:07 2024: ERROR: Failed to open serverI have tried different configurations to no avail.
If someone here have an idea for something I could try, let me know (I'm on a *buntu 22.04 base), otherwise I'll have to send it back I guess.
What happens if you omit ",0":
Code: Select all
jackd -dalsa -r48000 -p256 -n3 -d hw:MT48Make sure no other process uses this interface. Sometimes Pulseaudio gets in the way.
Linux – MOTU UltraLite AVB – Qtractor – http://suedwestlicht.saar.de/
Hi Bluebell,
Thanks for your reply.
I don't think pulseaudio is using the interface since I don't see it in the PA menus.
I tried to start Jack with your recommended configuration and got this message :
Code: Select all
jackd -dalsa -r48000 -p256 -n3 -d hw:MT48
jackdmp 1.9.20
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2021 Filipe Coelho.
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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio4
creating alsa driver ... hw:MT48|hw:MT48|256|3|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 3 periods
ALSA: no playback configurations available (Invalid argument)
ALSA: cannot configure capture channel
Released audio card Audio4
audio_reservation_finish
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
I don't see any reason it wouldn't work if it really is class compliant, this is frustrating.