You miss the point; I mean a manufacturer can test on virtually every Mac available and 100% qualify for use on that computer.

Whereas it’s impossible to do the same thing for pc configs, so it’s always guesswork to a point.

At the end user point, if your pc has a problem and you trace it to eg the graphics card, yes fixing it might be easier. But a situation like that on a Mac will require a patch from the manufacturer, and chances re they’ll make that fix cos it’ll be impacting lots of people.

If you get what I’m saying now - I’m not talking about in the field, I’m talking about point of manufacture.

Hey sir. Do you still have issues? Can I DM you? I am also having a lot of issues with soft synths and being able to play a reasonable amount of tracks, almost regardless of buffer size. I love the sound of the MT 48 I hope I don’t have to return it. :(

I’m still on a prism orpheus but might have to upgrade due to Apple getting rid of thunderbolt support.

How would you rate the sound quality and conversion of the Neumann vs the prism?

I love the sound quality of both units. I think the preamps on the Neumann have a bit of beautiful colour to them, while the Prism seems to be a bit more neutral. I wish I could have taken the Neumann out into the field a bit more to run it through it's paces but the stability issues prevented that, so I can't really comment on the Neumann universally. My experience with the Neumann was basically limited to me and my guitar, while the Prism has done everything (operas, orchestra, piano, chamber, solo...). They are both very high end units so I think you'd really have to work with the Neumann for a while to see if it's a suitable replacement for your Orpheus. However, IMO I can't see anyone being disappointed with either in the sound quality department. The Neumann headphone amp struck me as slightly different also, with that same sort of colour to them as the preamps, but again, you'd really have to try it to see. Good luck!

Do you have higher latency with Metric Halo MKIV than on RME? is that why you use the RME for direct daw connection?

I have Metric Halos MKIII and I'm really curious on other interfaces like MT48 or Anubis to offer a lower latency interface. But in the end, and for the price, MH should just be able to make as low-latency interfaces as any brand, it's a bummer to share another ecosystem to control aggregate interfaces.

Update on this. I unplugged the ethernet cable (POE) and went back to USB connection (direct to computer) and USB power. That was working fine, even with the latest firmware. But suddenly now I can't connect it that way - the remote management software says that the IP address can't be found. I tried deleting the MT-48 network device and restarting, but I still keep getting that message. If I connect it back to ethernet it works. Computer is M1 MacBook Pro running Sonoma OS 14.2.1.

I opened a support ticket with Neumann, we'll see.

To be clear, I was still able play audio through the device, but could not open the Toolkit

They responded that I should try initializing the unit (hold down talk and mute while restarting), and if that didn't work (it didn't) try uninstalling the software. However, they do not provide an uninstaller (AFAIK), so I had to search for and nuke everything related to the app. Here is how it went:

I deleted everything I could find on the Mac hard disk related to the Toolkit.

I could not delete this - the system wouldn’t allow it:

/Library/SystemExtensions/6FF507AC-6F99-41BF-BB25-EC16CF9AC8FD/com.merging.dext.NeumannMT48USBAudioLowLatency.dext

After deleting everything else, I shut down the computer, disconnected the MT-48 from ethernet, and started it back up by initializing it. Then I connected it to the computer via USB-C port, and started up the computer. Then I reinstalled the Toolkit, version MT48ToolKit_Mac_1.5.7_56838.

Then I restarted the computer. Upon restart, there was no MT-48 icon in the Mac menu bar. Opening it from /Applicarions gave me a message that it was running in the menu bar, but it wasn’t. Digging down into the Application bundle I ran this from a terminal: /Applications/NeumannMT48.app/Contents/MacOS/NeumannMT48

Here was the output:

Last login: Sun Jan 21 10:39:43 on console
/Applications/NeumannMT48.app/Contents/MacOS/NeumannMT48 ; exit;
JimM1Max:~ jimweisbin$ /Applications/NeumannMT48.app/Contents/MacOS/NeumannMT48 ; exit;
2024-01-21 10:43:08.105 NeumannMT48[1416:14972] -[ExtensionManager initForBundleId:]: <ExtensionManager com.merging.dext.NeumannMT48USBAudioLatency>
2024-01-21 10:43:08.105 NeumannMT48[1416:14972] -[ExtensionManager initForBundleId:]: <ExtensionManager com.merging.dext.NeumannMT48USBAudioLowLatency>
2024-01-21 10:43:08.105 NeumannMT48[1416:14972] Turn off agent
2024-01-21 10:43:08.118 NeumannMT48[1416:14972] SMLoginItemSetEnabled failed
2024-01-21 10:43:08.118 NeumannMT48[1416:14972] -[AppDelegate Helper_InstallLoginItem:] done
2024-01-21 10:43:08.118 NeumannMT48[1416:14972] Turn on agent
2024-01-21 10:43:08.136 NeumannMT48[1416:14972] SMLoginItemSetEnabled failed
...

You can see there were some things that “failed” in there.

So then I found this:

/Applications/NeumannMT48.app/Contents/Library/LoginItems/NeumannMT48Agent.app

I manually added that to Startup Items and restarted. Now it appears in the menu bar, but I still got this message:

Unable to retrieve IP address of device
MT48_000821.local

So I went into the MT-48 ethernet settings and set it at a manual address of 10.1.1.2, with a mask of 255.255.255.0, and a gateway of 10.1.1.1 - none of these actually exist on my network. Then I went into the Mac, added the Neumann MT-48 back as a network device, and set the Mac to address 10.1.1.3, same gateway as above. Then restarted. That worked - now I can access the Toolkit without the unit being connected to my LAN network. However, if I ever want to reconnect it to the LAN, I will have to set the MT-48 to DHCP mode and that might break this whole setup. (Why would I do that? Well then if connected to LAN, I could access the controls remotely from another computer or iPad, which could be useful in some situations).

In my opinion there are some serious problems with the Toolkit software, and maybe the firmware, as you can see from above. I hope this gets fixed.

I'm on MacBook Air 15 with M2 and latest Sonoma. Toolkit will not start and does not appear in menubar. Did reinstall and install again. No luck. Under security, kernel extensions is allowed. Any help?

See my post just above this one. I had to set the MT-48 at a manual IP address (doesn't matter what address as long as it's not auto-dhcp) and also force the app to start at login. Support got back to me but they were not of any help. They did say that a new firmware is coming soon.

I did it the way you suggested. It works like this. With the latest version 1.6.2 b7529 it works now without the workaround.

Does anyone else have the problem that the sample rate is not adjusted under Windows 11 / WASAPI, e.g. in foobar2000, Audirvana, Musicbee, Winyl etc.? The last set sample rate is retained. If I want to listen to music under WASAPI that simply sounds better to my ears than Asio, then I have to find a correct transfer to the player via Asio beforehand. If I then switch to WASAPI, the album is also played at the correct sample rate. However, if the next album has a different sample rate, the sample rate is no longer changed under wasapi. everything is fine under asio. i have just written to neumann's service department about this.

The incorrect setting under WASAPI seems to be a system-wide problem. In foobar there is even an error message and nothing is played. I first have to go via Asio, switch back to WASAPI, then foobar will also play.
Other programmes like musicbee are more merciful, they simply continue playing new albums with a different sample rate in the previously played sample rate.

I had the exact same problem for a couple of days and maybe I can help someone experiencing the same issue. What helped in my case was pulling the network cable. I had the MT 48 connected via a network switch to my KH 80 and a wifi repeater. If I understand correctly, when the MT 48 is connected to a router it provides internet to the computer rather than the computer being connected via wifi. Maybe that was causing problems

For anyone like me who was searching to find RTL's here's my results

Hi all,

Is it possible to power the MT48 fully from a macbook via two usb-c cables? Would be super good not have to lug an extra psu around.

In terms of sound quality, how does it stand up to the Prisms?

Looking to get one of these soon. Did the new firmware arrive and are people still having issues?

Never had any audio issues with mine, new firmware didn’t change that either.

Just tried this - didn't work for me (MacBook Pro M1 on a charger)

Were you able to resolve the issues described in your post?
If so, how?

Not at all.
I had a few emails with Neumann where they asked me to do all the usual stuff (reboot, swap cable, update). Nothing worked. Another issue not mentioned above was the phantom power turning on with the unit, even when it was turned off at the end of the previous session. I managed to catch it behaving this way on video and sent it to them. They replied with a while later admitting it was some sort of glitch, but by then I had returned the unit. So no, it was left unresolved.

Did you happen to notice another error; when the "Remote control" indicators freeze for a moment while the card is working, but then continue to work?

Also, showing the message "MT48 is offline" appear on the "Remote control" screen for a while?

ps. Did you have an Apple or Windows computer?

Actually no I didn't have any of the issues you mentioned. Just a random blip in the audio file every couple minutes, and the 48V randomly turning on.

Ok, I will ask another way;
is there anyone here using a Neumann MT48 + WINDOWS PC
for daily recording sessions as a work horse WITHOUT ANY ERRORS?

In recording and playback sessions that are measured in hours,
not 10 min watching a youtube influencer tests...

And the second question - for both Windows and MAC users;
what date and TIME does the "Remote Control" application show you?
I would like to hear the answer from those users whose application date/time does not match according to the UTC protocol.

This is not a fault. It happens because Neumann uses its own network adapter while in USB mode in Windows and it will conflict with another network adapter (in my case wifi) in the same IP range.

My MT48 had exactly the same issue with the 'remote controller' (windows app) continually stopping and starting from the outset, that was using a windows 10 PC. With the following warning "MT48 1.6.3.8608 Ethernet adapters subnet conflict wifi adapter shares same subnet 169.254.0.0 with Neumann MT48."

Look at this link that Neumann (Holger) sent me:

https://merging.atlassian.net/wiki/s...esses+conflict

To sort the issue, Neumann recommended using a fixed IP address in MT48 settings > Network in manual mode. Incidentally, my wifi adapter was using a dynamic IP rather than fixed and I never got around to doing the above fix.

I had read about network adapter conflict.
Just to make sure, I took the laptop and uninstalled all the wifi/lan/bluetooth drivers,
leaving only the Neuman MT48 network adapter.

Didn't help!

p.s. are you still using MT48 with Windows and no problems?

No longer using it, sorry..

I’m getting the same popping and static noises in my headphones. Here’s the funny thing I plugged in Apple original white wired pods with the jack adapter and I don’t get no pops or static noises, but it sounds horrible. I’m sending my unit back.

I know I'm a bit late to the party, but the MT 48 is essentially a rebadged Merging Anubis (non-premium variant), so it includes a lot of the same engineering as the Merging Hapi, definitely the same top-quality preamps and signal path.

That's not true. I've been running Merging hardware (Hapi + Horus + Anubis) over the years, never on anything else than gigabit ethernet. I've hit issues with PTP, multicast etc., but never with gigabit ethernet itself, the ports on the devices are gigabit and that's what they're designed to run on.

Yes, I'm not sure why I wrote that its obviously incorrect - most likely I meant that 10GbE is not optimal, which is true.