Need testers for Eunhasu Alpha version no.0.5.61

I am currently on v0.5.62 streaming Qobuz using LMS/SQ running on my 200 Neo.  528MHz is the minimum that is stable in my set up.  Sometimes the first 5 seconds of the initial track of a new playlist or album will stutter, this does not happen at 720MHz.  System tune Latency performance.

v0.5.62 runs on my SOtM sMS-200 Ultra Neo and Qobuz Studio (CD quality & Hi Res) playback is perfectly stable at 528Mhz via the MPD service. System tune is set to Latency tune. I agree with you Philippe Bell that 528Mhz is the lower usable CPU frequency, as playback at lower frequency in my set up cause the SOtM to "freeze".

Once we get some description of the other System tunes....I will try some of them.

Carcajou

On 6/4/2024 at 10:06 PM, creativepart said:

Yes! This is important info we are missing.

This is the review based on System tune settings of Eunhasu V0.5.62.

We have two systems, and Advanced devices are mainly tested with the settings below.

sMS-200ultra, tX-USBultra, sDP-1000EX, sPA-1000, sNH-10G x 2, sPS-500 x 4, , dCBL-CAT8M x 2, dCBL-CAT7u x 2, dCBL-CAT7e, iSO-CAT7 x3, sCLK-OCX10 x 2, dCBL-BNC50 x 5, mT-1000 x 2, pCBL-SS8 x 5, SOtM' balanced inter cable proto type
And Magico M3 speaker

Player: Roon Ready on a sMS-200ultra, Roon Core on a Test PC.

sMS-200ultra system configuration :
Network DHCP, IPv6 protocol Enable, Link speed 1000BASE-T, Auto negotiation On, CPU frequency 312MHz, Logging Off.

And we’v reviewed by changing System tune with the settings.
We’ve used 4 music files, vocal, string, jazz, and symphony, stored on NAS.

The "No tune" setting is the default setting upto Eunhasu OS V0.5.x and is the sound that many people like as a standard.
By setting the CPU frequency to 312 MHz, you may be able to enjoy music at significantly higher levels than the previous version even with the "No tune" setting.
As you set the System tune, you can feel a significant improvement in all areas, and the differences between each setting are quite small.

The information below is our personal opinions, so please use it for reference only.
It may feel different depending on your system and the music you listen to.

- Hpc-compute: Sounds exciting, tense and progressive 
- Latency performance: Sounds with greater softness, stability, elegance, and beauty
- Network latency: Sounds that provide comfort and easy
- Network throughput: Sounds very standard and east
- Throughput performance: Sound that combines strength, weight, and softness

The best way is of course that you set up and listen to it yourself and enjoy the music with the sound you like best.

On 6/8/2024 at 7:58 PM, Carcajou said:

v0.5.62 runs on my SOtM sMS-200 Ultra Neo and Qobuz Studio (CD quality & Hi Res) playback is perfectly stable at 528Mhz via the MPD service. System tune is set to Latency tune. I agree with you Philippe Bell that 528Mhz is the lower usable CPU frequency, as playback at lower frequency in my set up cause the SOtM to "freeze".

 

Once we get some description of the other System tunes....I will try some of them.

Carcajou

Me too! I have just tried the 200ultra neo but it crashed at 312 after 3-4 seconds

I have just compared my sMS-200Ultra/sPS500 with 4 known more expensive and less expensive drives (RoonReady or MinimServer/Bubble/Lumin), I see no reason to change, the SOtM is a top drive ! and now with this new version of Eunhasu, my opinion remains unchanged ! 🤩

I can't understand why my SOtM 200ultra neo crash at 312 MHz while don't have any issue with configuration of the screen shot. 

It has the same issue with 1000 Link Speed. 

Maybe does depends on HQPlayer upsampling? 

Many of us have noticed that 528 is the minimum (it is already 50% of the maximum..), and this is one of the discoveries of this test phase... 

My sms200 Neo (not Ultra) works fine at 312MHz running NAA, just a single stop after 3 hours 1/2 of continuous playback (but I’m not sure it actually crashed)

1 hour ago, stefano_mbp said:

My sms200 Neo (not Ultra) works fine at 312MHz running NAA

I am using the same settings with my sMS-200 Neo and with similar success. No problem playing hi-res files.

My SOtM sMS-200 Ultra Neo runs now v0.5.62.
The CPU is still running at 144MHz (very pleased that it is still available!!!).
I use Roon Ready, and I see that the sMS-200 is only using 7% CPU-power when playing.
I haven't tested the different tuning. I am on "Latency Performance". No crashes.
Thanks SOtM to keep on improving the firmware.
P.S. I disabled "IPv6" in the settings, as I do not use IPv6 in my home, so that the sMS-200 does not have to put CPU-power in IPv6.

On 6/18/2024 at 4:55 PM, audiobomber said:

I am using the same settings with my sMS-200 Neo and with similar success. No problem playing hi-res files.

On 6/18/2024 at 3:30 PM, stefano_mbp said:

My sms200 Neo (not Ultra) works fine at 312MHz running NAA

@stefano_mbpI shouldn't have said "same settings", because I have IPv6 disabled. 

@fminne, are you using 1000BASE-T or 100BASE-T?

7 hours ago, fminne said:

The CPU is still running at 144MHz

Can May or anyone explain why the frequency of the CPU in the SMS200 Ultra Neo makes any difference to the sound quality? Logic would seem to say that the faster the CPU can process complex high resolution files the better... not the opposite.

15 hours ago, audiobomber said:

are you using 1000BASE-T or 100BASE-T?

I use 100BASE-T.

12 hours ago, creativepart said:

why the frequency of the CPU in the SMS200 Ultra Neo makes any difference to the sound quality?

Easy and short explanation: the CPU can induce power-fluctuations. The higher the frequencies of the induced power-fluctuations, the more difficult it will be to eliminate them. And that qoes hand in hand with the SQ. So lower CPU-clock can result in better SQ.

There is a bug between the management of "Volume limits" in Roon (built 1432) and Eunhasu (5.62).. diagnosis: no sound output.. solution: I tried everything without success... finally solution : a new 5.62 SD card !! (or better, don't change in Roon "Volume limits"!!?)

On 6/28/2024 at 1:25 AM, fminne said:

Easy and short explanation: the CPU can induce power-fluctuations. The higher the frequencies of the induced power-fluctuations, the more difficult it will be to eliminate them. And that qoes hand in hand with the SQ. So lower CPU-clock can result in better SQ.

I finally got around to lowering the CPU frequency from 528 to 144mhz and I'm pretty surprised on the difference in sound. Everything is sharper, clearer and more defined. It's almost like I got a new DAC.

can you explain the configuration that allows 144Mhz ? via Roon or UPnP?

29 minutes ago, Philippe Bill said:

can you explain the configuration that allows 144Mhz ? via Roon or UPnP?

I've reverted back to just using Roon without any upsampling. I used to use HQ Player and upsample everything. But after getting an NOS DAC I decided I pretty much preferred running everything at whatever native output that Qobuz via Roon provides. At this time, I'm very happy with this simple setup. No filters, No upsampling, no convolution or anything. Just Roon Ready active in the SMS200 Ultra Neo output via an Audioquest Diamond USB to my Holo Audio Spring3 KTE DAC.

So, that's the configuration of 144Mhz on my SoTM (or is it SOtM i've seen it both ways)

Roon. But perhaps a very importand sidenote, my SOtM sMS 200 Ultra Neo is always powered on 24/7. I don't know if this makes any difference, but this is how mine is working perfectly as Roon endpoint at 144MHz.

I am too currenly trying 144Mhz on my SOtM Ultra Neo by streaming 16/44.1 from Qobuz (Keith Jarrett - A multitude of Angels)...and compared to the frequency I normally use of 528Mhz.......144Mhz sounds really better....more harmonics are audible...everything is clearer. I use the UDP/DLNA service in the SOtM to stream Qobuz Studio.

I made sure no browsers in my laptop or tablets run euhansu....

I am very surprised it works at 144Mhz....as my SOtM would rapidly freeze when I tested 328Mhz thus why I settled for 528Mhz up to now.

I will perform more listening over the courses of the next few days with higher resolution material from Qobuz or JRiver..and I will posts my impression about the stability and the sound quality

Carcajou

1 hour ago, Carcajou said:

144Mhz sounds really better....more harmonics are audible...everything is clearer.

+1 (with Roon)

No glitches after 5 hours of Qobuz streaming 16/44.1 to 24/192 music files with the CPU at 144Mhz via the MPD/DLNA SOtM service.

It sounds really better than 528Mhz.

Right now John Scofield "uncle john's band" in 24/96 never sounded this good than now via my Aqua La Voce S3 dac with the SOtM Ultra Neo cpu running at 144Mhz

I think I have discovered why my tests at 328Mhz failed weeks ago (the SOtM kept "freezing"): In Microsoft edge of one of my laptops...a startup tab was opening euhasu by default. So the SOtM was trying to play music and update euhasu at the same time - which I read - is not recommended.

Now euhasu is not started up in any tab of the browsers of my multiple devices.

SOtM, thank you for your excellent work and drive in improving existing products for your clients.

Carcajou

In my set up DXD (24/352.8) playback is a no go with the SOtM CPU frequency at 144Mhz as the listening is marred by either small hiccups on some recordings to unbearable interruptions of the music playback on other recordings. This with the UPD/DLNA service fed from music files from JRiver. Same files playback of DXD files at cpu frequency 528Mhz is perfect.

Tomorrow I will try the same playback at the CPU frequency of 312Mhz.....

But I can say, in my set up, 144Mhz works perfectly with files from 16/44.1 to 24/192 (source Qobuz or JRiver)

Carcajou

DXD (24/352.8) is a no go at 312Mhz (UDP/DLNA service) in my set up as digital noises can be heard.

Since I mostly listen music via Qobuz Studio Streaming 16/44.1 to 24/192 - I will set the CPU at 144Mhz

If I want to listen to a DXD recording (rare occurence) - I will change the CPU frequency to 528Mhz as DXD playback is flawless at that cpu frequency.

Carcajou

15 minutes ago, Carcajou said:

If I want to listen to a DXD recording (rare occurence) - I will change the CPU frequency to 528Mhz as DXD playback is flawless at that cpu frequency.

or transcode at source/server level ?