Roon Downsampling Hi-Res Audio on EvoAria Evo One after firmware update (ref#RIS47Q)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· My EvoAria Evo One is now recognized as a Roon Ready/RAAT endpoint, but Roon is downsampling hi-res PCM to 48kHz/16-bit. For example, a Qobuz 192/24 track is converted by Roon from 192→48kHz and 24→16-bit.

Another Evo One owner showed me his Roon Device Setup for the same Roon Ready endpoint. His shows Max PCM up to 768kHz, Max bits per sample 32, and DSD512, and he gets a lossless 192/24 signal path. Those three capability settings are completely absent from Device Setup for my Evo One.

The Evo itself is not limited to 48/16: Symfonium on the same device plays and reports 96/24 correctly. I am definitely using the EvoAria Evo One Roon Ready endpoint, not Android “Default Output,” and the signal path identifies it as Roon Advanced Audio Transport.

I also sometimes lose the Evo One Roon Ready endpoint after powering the DAP off and back on; toggling its Wi-Fi off/on makes it reappear.

My Nucleus Titan is running Roon Server 2.73 build 1695 Early Access; my Remotes are also build 1695 Early Access. Roon OS is 2.1 build 271 Production.

It appears my Evo One may not be reporting/registering its full RAAT capabilities correctly. Can you check what capabilities Roon is receiving from the endpoint and why mine differs from another working Evo One?

Tell us about your home network

· Home network using a Netgear Orbi with satellites. Nucleus Titan and EvoAria Evo One are on the same local network.the Titan is connected to the router by Ethernet. The Evo One connects via Wi-Fi. No unusual network configuration, switches or extenders relevant to this setup.

2

Did you install the firmware update that was released a few days ago?

3

Yes, I did.

4

Hi @Victoria_Carlin,

Thank you for your post.

Diagnostic logs from the server show the EvoAria device announcing itself with a 44.1KHz, 16-bit maximum.

09/29 16:28:31 [Local 09/29 12:28:31] Trace: [EvoAria Evo One () @ 10.168.168.206:37217] [raatclient] GOT [2] {"info":{"protocol_version":"3","unique_id":"7ad2b01743574b5e_null","raat_version":"1.1.47","output_name":"","serial":"","model":"Evo One","auto_name":"","vendor":"EvoAria","vendor_model":"EvoAria Evo One","version":"1.30_20260918-0954"},"flags":{"has_write_chmap":true},"output":{"info":{"config":{"signal_path":[{"quality":"lossless","type":"output","method":"headphones"}],"mqa_support":["renderer","decoder"],"vendor":"EvoAria","vendor_model":"EvoAria Evo One","model":"Evo One","version":"1.30_20260918-0954","device_id":"7ad2b01743574b5e_null","supported_formats":[{"channels":1,"bits_per_sample":16,"sample_type":"pcm","sample_rate":44100},{"channels":2,"bits_per_sample":16,"sample_type":"pcm","sample_rate":44100},{"channels":1,"bits_per_sample":16,"sample_type":"pcm","sample_rate":48000},{"channels":2,"bits_per_sample":16,"sample_type":"pcm","sample_rate":48000}],"code_signing_keys":[{"keypair_name":"evoaria_20260615","public_key":"05d06e49e94e42847765ceb7ddf4d8c7d8d849f77a92bbc0b5f2ccaa3148a4ee"}],"transport":{"enable":"true"}},"mqa_capabilities":["renderer","decoder"]},"supported_formats":"48000/16/1|2,44100/16/1|2"},"platform":[],"source_selection":{"info":[],"is_supported":false},"volume":{"info":{"config":{"signal_path":[{"quality":"lossless","type":"output","method":"headphones"}],"mqa_support":["renderer","decoder"],"vendor":"EvoAria","vendor_model":"EvoAria Evo One","model":"Evo One","version":"1.30_20260918-0954","device_id":"7ad2b01743574b5e_null","supported_formats":[{"channels":1,"bits_per_sample":16,"sample_type":"pcm","sample_rate":44100},{"channels":2,"bits_per_sample":16,"sample_type":"pcm","sample_rate":44100},{"channels":1,"bits_per_sample":16,"sample_type":"pcm","sample_rate":48000},{"channels":2,"bits_per_sample":16,"sample_type":"pcm","sample_rate":48000}],"code_signing_keys":[{"keypair_name":"evoaria_20260615","public_key":"05d06e49e94e42847765ceb7ddf4d8c7d8d849f77a92bbc0b5f2ccaa3148a4ee"}],"transport":{"enable":"true"}}},"is_supported":true},"status":"Success","transport":{"info":{"config":{"enable":"true"}},"is_supported":true,"is_update_artwork_supported":true,"is_update_status_supported":true}}

Device announcements also list blank field entries for uniqueID and deviceID, which ought to be populated.

Roon isn’t imposing this cap and is responding to the Evo One’s firmware announcement of it’s own capabilities. Unfortunately, it’s not within RAAT’s capacity to force the endpoint to correct these omissions.

We recommend reaching out directly to the vendor’s support team. It’s worth trying to reinstall the firmware manually. Power cycle the device a few times. If none of this helps, our team will reach out to EvoAria directly.

Thank you!

5

Thanks, Connor. I tried the manual firmware reinstall, but unfortunately I hit another roadblock.

I downloaded EvoAria’s current v1.3 firmware ZIP and attempted a Local Update from the microSD card, following EvoAria’s instructions and leaving the package zipped. The Evo One recognized the file and gave me the prompt to restart/upgrade, but the installation then failed with simply “Upgrade failed” and no further details.

Since the unit is already running v1.3 from the previous OTA update, I’m wondering whether the local updater simply won’t reinstall the same firmware version over itself.

I considered doing a factory reset, but as I understand it, that would wipe the user configuration while leaving the currently installed v1.3 firmware in place, so I’m not sure that would accomplish the clean firmware reinstall you were suggesting.

EvoAria also still provides the v1.2 full firmware package on their site. One possible route would be to install the v1.2 full package and then install the v1.3 update locally from the SD card. However, I don’t want to attempt a firmware downgrade without confirmation from EvoAria that v1.3 → v1.2 → v1.3 is a supported/safe procedure.

So at this point I’ve been unable to perform the clean v1.3 reinstall. Since your diagnostics show that the Evo is incorrectly announcing only 44.1kHz/16-bit capability and is also sending blank uniqueID and deviceID fields, would you be able to reach out to EvoAria as you mentioned? It would also be helpful to know whether they recommend a factory reset or support the v1.2 → v1.3 reinstall route.

Thanks again for digging into the logs — at least now I know the downsampling wasn’t something I had inadvertently configured in Roon!

6

Hello @Victoria_Carlin,

Thank you for trying the manual update. We cannot say whether the Evo One accepts the same firmware version through the local updater, and we do not know which reinstall route EvoAria supports, so please hold off on downgrading to v1.2 until they confirm it is safe.

We have contacted EvoAria about what the Evo One announces to Roon. At the moment we do not have a timeframe for their reply, and if anything changes we will update this thread. In the meantime, please also contact their support directly and include the log excerpt from our earlier post, since it shows exactly what the Evo One reports to Roon.

7

Thanks Vadim. I have sent my own email to EvoAria support this morning.

8

Hello @Victoria_Carlin

A quick update. We shared your findings with our partners at EvoAria, and they tested an Evo One on firmware 1.21 (V1.21_20260708-1202). On that unit Roon showed the expected sample rate and bit depth, and playback at up to 768 kHz worked normally, both in Roon and on the device. Your unit reports firmware 1.30_20260918-0954, so that test did not reproduce what you are seeing.

Please let us know how 1.30 got onto your Evo One: through the device’s own update, or from a file you downloaded, and from where. EvoAria lists 1.21 as the latest on their side, so we want to confirm which package you are running.

9

I used the OTA update function on the EvoOne on the day it was released or the next day.

I’m not sure how they can say 1.21 is the latest, their own site lists 1.3 to download.

IMG_1263
IMG_12631920×1334 281 KB

10

Hello @Victoria_Carlin

Thank you, that clears it up. Your Evo One got 1.30 through EvoAria’s own update, and their download page also lists firmware v1.3, so you are running a package they publish. The unit our partners tested first was on 1.21, which is why it did not match what you see.

We also tried installing v1.3 on two Evo One units that were on 1.21, and the update failed on both, so the “Upgrade failed” message does not look specific to your unit. We have shared this with EvoAria already, but the firmware is theirs: Roon cannot change what the Evo One announces or roll its firmware back. The next step has to come from EvoAria.

Please contact their support team directly:

. It will help to include these points:

  • The Evo One reports firmware 1.30_20260918-0954 and announces only 44.1 and 48 kHz at 16-bit to Roon, with empty serial and output name fields (the log excerpt from Connor’s earlier post shows this).
  • The same firmware 1.3 package fails with “Upgrade failed” through the local update.
  • Please ask them which reinstall or recovery route they support (factory reset, or 1.2 then 1.3) before you try anything.
11

Thank you I did email EvoAria a few days ago and shared this thread as part of my note, but I haven’t heard back yet. I will send a follow up that includes the specific language you just stated though.

12

I heard from EvoAria. They didn’t really diagnose the issue beyond terming it a system glitch. But they confirmed you can’t go backwards on the firmware releases, and recommended I do the factory reset. After that, it started working appropriately. So, I appear to be fixed for Roon (hopefully Roon and/or EvoAria will get ARC working right for everyone soon, but for now I’m good).