But they are using a standalone src chip to do this, not DSP or FPGA.
SRC = DSP
But they are using a standalone src chip to do this, not DSP or FPGA.
Does anyone have any idea why all those blue capacitors appeared? Could it be that they weren't needed before?These two articles displays r1.6 internals
声卡领域的产业革命已悄然降临,这一切始于 MOTU UltraLite mk5 - Midifan:我们关注电脑音乐
声卡领域的产业革命已悄然降临,这一切始于 MOTU UltraLite mk5,midifan:我们关注电脑音乐m.midifan.comMOTU UltraLite MK5 звуковой интерфейс
MOTU UltraLite MK5 – профессиональный звуковой интерфейс с двумя предусилителями, микшером и аппаратным DSPprosound.ixbt.com
This video shows r3 pcb
Mk5 Teardown • DcSoundOp
MOTU Ultralite mk5 teardown in 4k with data-sheets linked in the description and lots of hi-res angles of the electronics inside!www.dcsoundop.com
They also change the FPGA from Altera MAX10 to Lattice LFEU5, emm......Does anyone have any idea why all those blue capacitors appeared?
They are next to the 6 input sockets and there's 12 of them, so 2 per input. So very likely due to the switch from AKM to ESS analog-to-digital converters.Does anyone have any idea why all those blue capacitors appeared? Could it be that they weren't needed before?
Back to this topic... I don't understand what happens if I have, example, a toslink source at 44.1kHz connected to Mk5 set at 96kHz.SRC = DSP
Back to this topic... I don't understand what happens if I have, example, a toslink source at 44.1kHz connected to Mk5 set at 96kHz.
No signal is acquired? Or the internal DSP performs the src?
Ok, thanks.If you have clock source set to optical and the Mk5 rate set to 96 kHz and send a 44.1 kHz signal via TOSLINK it won’t lock and you will get no output.
If you have the clock source set to internal and the Mk5 rate set to 96 kHz and send a 44.1 kHz signal via TOSLINK you will get output but it will sound terrible as described here -> https://www.audiosciencereview.com/...s/rpi4-camilladsp-tutorial.29656/post-1575493. Not sure what is actually occurring but needless to say operating in this manner is not recommended.
Michael
I've had dropouts in Windows that Motu support was unable to troubleshoot.Hello everyone... I am considering buying the MK5 but am a bit worried regarding the Windows driver issues.
You guys seem to be pretty knowledgeable so I would appreciate any recommendation on that topic.
I am planning to use it as an interface to feed the model1 dj mixer... so i will not have to run it on 192kHz... but I like the number of outputs and couldn`t find anything comparable in that range.
Do you know if MOTUs techguys "finally" released an update that makes their product flawlessly work with windows?
Is it depending on the way the interface is used (like being an 192-only-issue) or is it rather an overall incompatibility issue?
Thank you Michael
Don't worry about this problem in advance. Surely your PC will be completely different from mine. The problem itself I believe was caused by the Dell motherboard. The Intel DTM driver is very popular and probably won't cause problems if the hardware is right.Thank you Davide for your reply... was it some specific driver that you uninstalled...a quick search on google only showed DTT driverS (dynamic tuning technology) which I am not familiar with and it seems there are more than one... do you remember which one you uninstalled?
Specifically, I don't know of an equivalent model. The manufacturer are always the same anyway... try to see what Apogee, Universal Audio, Antelope, Audient, Focusrite, etc offer. Maybe look at Thomann website if you're in EU so you can see them all together compared by price and features.I see... thx again... one last question... as it is not a nice precondition to get a piece of hardware that seems to be prone to (maybe) not work properly with windows, i would appreciate any recommendations on alternative interfaces which come with comperable specs - so do you know any that has around 5-6 outs plus midi and is in that price range or a little lower?
NOTE: If you are using a macOS or Windows computer with your UltraLite, there is a simple way to do this (although quite obscure, I found it in this forum). Just:
*Your computer's ip address works as well. However, since it might change from time to time, the network name might be easier to remember.
- Take note of the network name of your computer*. Here are instructions on how to do it.
- Run the CueMix 5 app from your iPad/iPhone
- In the welcome screen, click on "IP Connect". Replace the IP there with your computer's network name, plus :1281. You should end up with something like this computer-name.local:1281
I also tried following those instructions but it never worked. In any case it would be inconvenient to control from a smartphone in my opinion...Earlier someone posted a link to this guide:
I'm having no luck with this.
The Mk5 is connected via USB to a Windows 10 PC, and I'm trying to connect to it from an iPhone on the same network. I think it might have something to do with iOS's local network permission system, however the prompt to allow local network access isn't popping up when I'm trying to use the CueMix app. Furthermore, CueMix isn't even present in the iOS settings app, so I cannot manually give it permission.
I've tried both the PC's name and its IP address. The guide shows ".local" between the name and :1281, while other discussions I found exclude the ".local". Does anyone know the significance? I tried both with and without.