[Lu88]

Regarding that claim... We do have to say something.

Here's some frequency measurements of MIAD-01 playing a local white noise file with some common streaming software.

As you can see from the FFT spectrum graph, by Nyquist theorem NetEase and QQ music is bypassing the 48khz src , while Hiby and Poweramp is having some problem(the graph goes down on 24khz, which is half the sampling freq).



For Hiby music and poweramp, they were suffering an SRC, probably because of built in limiter etc.

But that's still in normal range. NetEase and QQ use phone's hires signal path by default(One of the features of newer Android, developer can just utilize it)
Since Hiby and Poweramp are having problem, we did some research on them, and It turns out Poweramp use the original signal path(OpenSL ES) by default.


We adjusted the Poweramp settings to Hires Output and test Poweramp again, we can notice a dramatic improvement in test result:

Then we choose a competitor product that claims to bypass SRC globally:
Test result of aftermarket software on that device:
Poweramp software:



Hiby software:



Long story short:
Our conclusion is that the competitor product only bypasses SRC on the built in Hiby software either. If a third party software is not utilizing HiRes signal path, It will suffer from SRC.

Our stance on this matter is that Despite Android had added Hires support, It is up to the software developer to utilize that output option, NOT the hardware. If the software itself doesn’t specifically assign it to hires signal path, it will suffer SRC. Please select a software that utilizes the Hires audio channel.

Acouding to @Audiosentinel , he tested with both MIAD01's native music player and Hiby music player, and got the same results.
https://www.head-fi.org/threads/loo...martphone-miad01.972582/page-14#post-18123587

Does it mean that currently the native music player also doesn't utilize the HiRes signal path and suffers from SRC?

 

[Vamp898]

Acouding to @Audiosentinel , he tested with both MIAD01's native music player and Hiby music player, and got the same results.
https://www.head-fi.org/threads/loo...martphone-miad01.972582/page-14#post-18123587

Does it mean that currently the native music player also doesn't utilize the HiRes signal path and suffers from SRC?

The Native Music Player is, as far as i know, just a stock music Player unrelated to Moondrop.

At least that is what i understood. I tested it and noticed, this is just an average Android Stock Player.

I tested the FiiO Player App (which is pretty good) as well as the Sony App and some OpenSource Players from F-Droid and they all were Hi-Res Audio capable.

I did not test the Stock player as i personally considered it some crappy stock Android Player unrelated to Hifi Audio

 

[Danx3k]

Has anyone tried Tidal, Qobuz or Apple Music to see if they bypass the SRC?

 

[Vamp898]

Has anyone tried Tidal, Qobuz or Apple Music to see if they bypass the SRC?

Afaik Tidal only supports Bit Perfect output with external USB DAC and even then not always.

Some DAPs suffer the issue that even when you plug an external DAC, Tidal will down convert to 16/48

 

[Danx3k]

Afaik Tidal only supports Bit Perfect output with external USB DAC and even then not always.

Some DAPs suffer the issue that even when you plug an external DAC, Tidal will down convert to 16/48

I've used Tidal on my R6P2 and my previous R6G3 and never had that issue with Tidal playing directly from the device

 

[Vamp898]

I've used Tidal on my R6P2 and my previous R6G3 and never had that issue with Tidal playing directly from the device

Die you measure if the output actually is High Res Audio? It won't tell you on it's own^^ it will just play the music and downscale it.

 

[Danx3k]

Die you measure if the output actually is High Res Audio? It won't tell you on it's own^^ it will just play the music and downscale it.

It shows in the top right corner of the screen on android what it’s outputting. So 192khz etc this also matches with what it shows if I connect my RU6 to it, as it shows the sample rate.

 

[Vamp898]

It shows in the top right corner of the screen on android what it’s outputting. So 192khz etc this also matches with what it shows if I connect my RU6 to it, as it shows the sample rate.

? this whole argument exists, because what is shown in the Software is not what is coming out of the device.

Just because the App says 192kHz doesn't mean there is a 192kHz signal coming out of the headphone jack.

What is sent to an USB DAC is unrelated to what comes out from the jack

 

[PotatoBlin]

Regarding that claim... We do have to say something.

Here's some frequency measurements of MIAD-01 playing a local white noise file with some common streaming software.

As you can see from the FFT spectrum graph, by Nyquist theorem NetEase and QQ music is bypassing the 48khz src , while Hiby and Poweramp is having some problem(the graph goes down on 24khz, which is half the sampling freq).



For Hiby music and poweramp, they were suffering an SRC, probably because of built in limiter etc.

But that's still in normal range. NetEase and QQ use phone's hires signal path by default(One of the features of newer Android, developer can just utilize it)
Since Hiby and Poweramp are having problem, we did some research on them, and It turns out Poweramp use the original signal path(OpenSL ES) by default.


We adjusted the Poweramp settings to Hires Output and test Poweramp again, we can notice a dramatic improvement in test result:

Then we choose a competitor product that claims to bypass SRC globally:
Test result of aftermarket software on that device:
Poweramp software:



Hiby software:



Long story short:
Our conclusion is that the competitor product only bypasses SRC on the built in Hiby software either. If a third party software is not utilizing HiRes signal path, It will suffer from SRC.

Our stance on this matter is that Despite Android had added Hires support, It is up to the software developer to utilize that output option, NOT the hardware. If the software itself doesn’t specifically assign it to hires signal path, it will suffer SRC. Please select a software that utilizes the Hires audio channel.

Just registered to share my understandings...
TLDR: The device does not provide any SRC bypass above native android 14 devices. Global Android SRC bypass does not exist in the Miad.

There's generally two ways to bypass the Android SRC. The new way is the new Android 14 feature: so-called bit-perfect, which is essentially an android native attribute that the application can set, and then the digital audio data will go directly to USB. The old way is often known as "Application Audio exclusive mode," which I believe is the AAudio Exclusive mode, this is basically the same thing but achieved using different APIs. (The new way is probably more convenient for developers?) The two ways are up to the applications developers to implement. This info perfectly aligned with the Moondrop reply I quoted. However, the elephant in the room is that Moondrop didn't do anything on the OS level to circumvent/bypass the Android SRC and still rely on application to do the port selection, aka if app does not support the bypass, then audio is not bypassed. Well, speaking of global bypass, I imagine that it could be very difficult, not money efficient, but achievable as Android itself is open-sourced. It's definitely what the target consumer of this product would love to have, but in the end it's the company's decision to tell if it's worth the effort.

The slick thing is Moondrop's product page never claim that it supports global SRC bypass, as it only states that it "Bypass the underlying SRC of Android." Which it really does, but almost every Android 14 phone with the right apps (as well as older phones with the right apps) does too.

Please point out and correct me if I made any mistakes.

 

[lordearl]

Just registered to share my understandings...
TLDR: The device does not provide any SRC bypass above native android 14 devices. Global Android SRC bypass does not exist in the Miad.

There's generally two ways to bypass the Android SRC. The new way is the new Android 14 feature: so-called bit-perfect, which is essentially an android native attribute that the application can set, and then the digital audio data will go directly to USB. The old way is often known as "Application Audio exclusive mode," which I believe is the AAudio Exclusive mode, this is basically the same thing but achieved using different APIs. (The new way is probably more convenient for developers?) The two ways are up to the applications developers to implement. This info perfectly aligned with the Moondrop reply I quoted. However, the elephant in the room is that Moondrop didn't do anything on the OS level to circumvent/bypass the Android SRC and still rely on application to do the port selection, aka if app does not support the bypass, then audio is not bypassed. Well, speaking of global bypass, I imagine that it could be very difficult, not money efficient, but achievable as Android itself is open-sourced. It's definitely what the target consumer of this product would love to have, but in the end it's the company's decision to tell if it's worth the effort.

The slick thing is Moondrop's product page never claim that it supports global SRC bypass, as it only states that it "Bypass the underlying SRC of Android." Which it really does, but almost every Android 14 phone with the right apps (as well as older phones with the right apps) does too.

Please point out and correct me if I made any mistakes.

Good summary.

The fact is that every DAP and dongle user who migrated to the MIAD01 would have expected to see global SRC bypass.

At the very least, having support for USB AUDIO PLAYER PRO in bit-perfect mode would have been acceptable.

Instead, the device relies on software implementation to achieve the desired outcome. And arguably there is not enough support for this device yet.

Some users may not be too fussed about it because it still sounds great, but the purists will stick to their DAPs and dongles I think.

 

[orcinus]

SRC bypass issue will be addressed in a mid-June update.
https://weibo.com/6453113311/Og7dmAAap

 

[XTF1]

SRC bypass issue will be addressed in a mid-June update.
https://weibo.com/6453113311/Og7dmAAap

Interesting… if my machine translation is correct, this may be a Moondrop problem in the end, but some of the SRC bypass issues are caused by “unexpected” behaviors of PowerAmp (forcing some Android default settings that then affect every app) and HiBy music (using features from a different Android API).

It looks like Moondrop is “learning” about the complexity (the mess?) of Android audio. The fact that they are willing to fix/improve the MIAD01 software to “adapt” to the various app. is a big + for Moondrop IMO…

 

[Vamp898]

I took the time and posted a review for my MIAD01 https://www.head-fi.org/showcase/mo...obile-audio-device.27192/reviews#review-34040

 

[Larethio]

Glad to see the SRC problem is getting attention. I was wanting this to replace my old Atnt V60.

It would need a otterbox-level case also. In the meantime I might find someone with a 3d printer.

 

[Vamp898]

SRC bypass works as expected on my MIAD01. I was requested to test it and it works without issues. I tested with the FiiO Music App and Phonograph Plus