Quote:
Originally Posted by
loweroctaves
β‘οΈ
Hello new here, i just received my neumann mt48 and I got to be honest for the price tag Iβm a little frustrated with what Iβm dealing with. First off let me tell you the kind of music Iβm making, Iβm making electronic Hip Hop indie music. As of right now the Midi compatibility on this thing is absolutely terrible. and if you use a lot of soft synths you probably want to avoid this unit until they get it situated. All my plug-ins are getting drop notes or frozen notes and itβs driving me crazy probably going to have to return it and go back to using my Arturia interface. Second problem is I have a Mac Studio M 1 that is very powerful and I have to run this at 32 samples because the latency on this is atrocious and if I use a higher rate and try to record any of my analog synths I get cracking and popping like crazy. Which is crazy because my cheap Arturia audiofuse is vastly superior in this department and has no problem with any soft synths or recording. Itβs absolutely ridiculous that theyβre not using thunderbolt. I got to say though the headphone amps on this thing are amazing and put arturias and apollo x8 to shame, Iβm using the NDH 30 and seinnheiser 660s headphones and really enjoy them. As many have mentioned, it is very clean to the point of to clean for me. If youβre doing electronic and hip-hop, it is very sterile sounding. Yes the unit runs hot but so does my audiofuse.no big deal. Because this unit is so new i havenβt heard many problems yet so Iβm curious is there anyone here that has the new Neumann mt 48 and having midi problems? Think im just gonna return it and wait it out.
"MIDI problems"...that's not really the case with any audio interface. MIDI is separate; the interface just sees a data stream from the DAW, it doesn't really "know" what's coming into it, it just sees an audio stream. By the time it reaches the driver, there's no midi information involved.
What you describe sounds like some sort of data stream error - it's weird that you're saying a low buffer size works, a high buffer size gets clicks/pops (normally it'd be the other way round). Also whilst some people are very latency sensitive, most DAWs (you don't say what you're using) are very usable even up to a 128 buffer - they often automatically put the soft synth in record down to a low buffer anyway - so it's also odd there's an issue with latency.
Sounds like some problem with the driver for sure, but I don't think it's soft-synth related.
(also - not using TB doesn't necessarily mean issues, plenty of great USB interfaces, TB can be better for high IO counts sure but this shouldn't be an issue).