Need testers for Eunhasu Alpha version no.0.5.61

Greetings!

A new Eunhasu Alpha version no. 0.5.61 is now available, it's not officially released yet since many things have been modified as like below, we renamed 'CPU Latency tune' to 'System tune' and added about 5 tuning profiles. We would need your support to test them out and give us some feedback which profile is okay and what would be the meaningless profiles, after your feedback, we would need to remove unnecessary profiles and release the firmware officially.

Version : V0.5.61
  - Date : 04-30-2024
  - Update system config page.
  -      No need to reboot after changing the system tune settings.
  -      Changed the setting item name from 'CPU Latency tune' to 'System tune'.
  -      Added the system tune profiles newly.
  -          hpc-compute
  -          latency-performance(original CPU Latency tune profile)
  -          network-latency
  -          network-throughput
  -          throughput-performance
  - Adjusted Eunhasu service process priority to be normal.
  - Updated MPD config page.
  -      Removed Buffer settings and set 100MB by default
  -      Removed Buffer before play and Period time
  -      Added and cached Buffer size 1GB
  - Updated Eunhasu system service code.
  - Set maximum installed kernel count to be 3 for x86_64, aarch64.

This is how to test the alpha version, 

- Access to the alpha server by following url, http://<your Eunhasu ip address>/upgrade.php?upgrade_server=alpha

- Once done upgrading to the alpha server, then, reboot the device and you are ready to test.

Thank you.

Could you provide a brief description of each of the new system profiles.  Thanks

Bonjour

0.5.61 is now up and running in my SOtM sMS-200UltraNeo. I have set the system profile to hpc-compute without knowing what it entails. Looking foward to get MikeSa question answered.

What is the system profile that is identical or near identical the 0.5.51 version - I would like to have one of the system profile identical to the 0.5.51 version in order to appreciate the change/improvement - if any - in SQ against the other system profiles.

As for the CPU frequency - I exclusively use MPD for Qobuz Studio and JRiver Playback - it is set to 528Mhz as lower frequencies would cause the SOtM to "freeze"...with 0.5.51. But to my ears....312Mhz sounded better but way too unstable with frequent freeze of the SOtM.

With 0.5.61 are there any reasons I should try lower frequencies than 528Mhz again with MPD?

Carcajou

1 hour ago, Carcajou said:

I would like to have one of the system profile identical to the 0.5.51 version in order to appreciate the change/improvement

As described

latency-performance(original CPU Latency tune profile)

Stephano thank you for the clarification. As a baseline for comparison - I will use original CPU Latency tune profile 

Carcajou

I halted my test on 0.5.61 this morning as during the last few days...many of my Qobuz track playbacks have been interrupted and the next track playback would start immediately, this with CPU Frequency at 528Mhz and by using 3 of the System Profiles.

I am not saying this issue is due to 0.5.61 as I will perform many other tests to find out what is the cause.

I have revert to 0.5.51 and I will test the stability of the playback. I playback with Qobuz Studio (Hi Rez) with 0.5.51 for months now and it has been rock solid in terms of stability.

Qobuz playback issues may come from my ISP, my meshed routers that are getting old, my old android phone that my play tricks with Bubble UPnP or Mconnect to control Qobuz...and/or other things

If I enjoy again flawless playback with 0.5.51 for a week...I will try again 0.5.61 and report.

Question for May: As MikeSA, I am very interested to get a description/focus of the multiple System Profiles.

Carcajou

without a description of the profiles, it is difficult to give an opinion, in the meantime, 5.61 works

Over the time I have been testing 5.61 my 200 Neo completely lost the network connection hpc option was operational at the time and needed to be rebooted.  On 2 occasions latency option operational I have needed to restart LMS/Squeezlite.

I use LMS for streaming only no attached drive for music files.

I cannot recall having this issue with 5.51

via the new 5.61

- Roon works without any problem (as usual) but we wonder what this version brings??
- LMS does not work (I do not see the sMS-200)
- MPD/DNLA via MinimServer/Lumin: does not work (I see the sMS200 and MinimServer.. no sound)

1 hour ago, Philippe Bill said:

via the new 5.61

- Roon works without any problem (as usual) but we wonder what this version brings??
- LMS does not work (I do not see the sMS-200)
- MPD/DNLA via MinimServer/Lumin: does not work (I see the sMS200 and MinimServer.. no sound)

 

All is working fine here … Which is the installed version of MPD and LMS?

You can eventually update them by removing and reinstalling them

Bonjour to all

I have downgraded to 0.5.51 for a week and at the beginning of the week I was still experimenting issues with MPD Qobuz Studio playback - the track playing would be interrupted and the next track playback would start immediately. This with the SOtM controlled by Bubble UPnP and MConnect and via playback in the android phone via UAPP to a dragonfly dac.

I then put all my attention on my old android phone which control the SOtM via Bubble UPnP. I believed I had too much stuff running at once in that old android phone. Once I kept the number of apps running to a very limited number....the playback has been flawless with the SOtM with 0.5.51.

This morning I will put back 0.5.61 in action and I will report later this week.

MPD 0.23.15

UPMPDCLI 1.8.9

CPU frequency of 528Mhz

HPC-Compute profile

SOtM sMS-200 Ultra Neo

Carcajou

Ok...I put 0.5.61 back into my SOtM sMS-200 Ultra Neo ans I performed a quick test

Versions/Parameters:

Qobuz Studio

Euhasu 0.5.61 alpha

MPD 23.15

Profile: HPC-Compute

Frequency 528Mhz

The playback of the Qobuz 24/192 recording stopped after a few minutes of the first track to immediately start the playback of the next track. I rebooted the SOtM and the android phone with Bubble UPnP and started again the playback of the same recording: Same same playback issue.

I put back 0.5.51 with CPU Latency "on" and MPD 23.13 into the SOtM and started the same recording playback....no issue at all...it works flawlessly.

Carcajou

I've updated to the 5.61 Alpha firmware and had no issues. I've tested only Roon, LMS/SQ and NAA. All have worked normally.

I'm using CPU frequency: 528 and System tune: CPU Latency

Right now I'm using LMS/SQ every day and having no issues of note.

Bonjour

I have read documented issues with Bubble UPnP like the issue I currently experience - a track playing is stopped in the middle and then the playback continue to with the next track.

I will work to resolve that issue - that I feel is NOT related to 0.5.61 - I will only come back here once I feel I have a very stable playback set up with 0.5.51

Carcajou

Bonjour

I now run Mconnect into my Android phone to control my SOtM with 0.5.61 at 528Mhz and Latency Performance profile. I was able to enjoy long symphonies movement without any issues during several listening sessions. It sounded as good as with 0.5.51.

MayfromSOtM, as someone else asked above - What are we testing? Stability of the multiple profiles or their Sound Quality. Also please provide a description/focus of each profile.

Carcajou

Hello a

On 5/16/2024 at 1:58 AM, Carcajou said:

Bonjour

I now run Mconnect into my Android phone to control my SOtM with 0.5.61 at 528Mhz and Latency Performance profile. I was able to enjoy long symphonies movement without any issues during several listening sessions. It sounded as good as with 0.5.51.

MayfromSOtM, as someone else asked above - What are we testing? Stability of the multiple profiles or their Sound Quality. Also please provide a description/focus of each profile.

Carcajou

Sorry to take some time to respond, had fixed the issue what you've experienced, please try out the v.0.5.62 in the alpha server, https://www.sotm-audio.com/sotmwp/english/eunhasu-v0-5-62-알파버전/

We’ve prepared and uploaded V0.5.62 on our Alpha server. The V0.5.62 solves and improves playback problems when used Qobuz and etc with setting at 312Mhz or lower frequencies.

The V0.5.62 is the same as the  V0.5.61 version, but in the V0.5.62, the update cycle of the Eunhasu Web gui start screen has been changed depending on the CPU frequency setting.

The basic update cycle is 5 seconds, if the CPU frequency is slow, this basic update cycle becomes loaded and causes the CPU to stop or the music to stop playing. However, in the V0.5.62, if the CPU frequency is slow, this update cycle is lengthened, and the update is automatically set not to be updated at the frequencies below 528 MHz.

Please test it at a low frequency and report if there seems any problems.

Version : V0.5.62
– Date : 06-02-2024
– Updated the system config page.
– No need to reboot after changing the system tune settings.
– Changed the setting item name from ‘CPU Latency tune’ to ‘System tune’.
– Added new system tune profiles.
—>hpc-compute
—>latency-performance(original CPU Latency tune profile).
—>network-latency.
—>network-throughput.
—>throughput-performance.
– Adjusted Eunhasu service process priority to be normal.
– Updated MPD config page.
—>Removed the buffer settings & set 100MB by default.
—>Removed the buffer before play & Period time.
—>Added & cached buffer size 1GB.
– Updated Eunhasu Web GUI home page reflash time per the CPU frequency.
—>5 secs : 960MHz =<, 7 secs : 912Mhz =<, 10 secs : 864MHz =<,
—>30 secs : 720MHz =<, 60 secs : 528MHz =<, No refresh : 528Mhz >
– Updated Eunhasu system service code.
– Set maximum installed kernel count to be 3 for x86_64, aarch64.

Also, when set to the low CPU frequency, it is recommended not using Eunhasu Web GUI.

Additionally, the V0.5.61 has a code that raised the priority when running each music playback app to improve music playback interruptions, but this was removed in the V0.5.62. This update only applies to those who have installed V0.5.61. After updating to V0.5.62, please uninstall and reinstall the app you want to use before using it to apply the change correctly.

Thank you

Bonjour May

I have updated my sMS-200 Ultra Neo to V0.5.62. I will start my Qobuz listening tests with the  CPU frequency at "Performance" and System tune to "Latency performance". And over the course of the following days....I will gradually lower the CPU frequency. Once I get a stable playback at 528Mhz or lower - I will try other System tune settings.

I will also disable Bubble UPnP Proxy service in my Android phone...as this option was the only way to get Qobuz playback uninterrupted into the SOtM. This service was helpful but I do not like the idea to have my Android phone in the middle of the Qobuz to SOtM music stream.

Once I get some listening hours completed...I will report in a few days.

Thank you May

Carcajou

can you explain the differences heard between :
—>hpc-compute
—>latency-performance
—>network-latency.
—>network-throughput.
—>throughput-performance.

1 hour ago, Philippe Bill said:

can you explain the differences heard between :
—>hpc-compute
—>latency-performance
—>network-latency.
—>network-throughput.
—>throughput-performance.

Yes! This is important info we are missing.

Bonjour to all

It looks like V0.5.62 fixed the Qobuz playback interruptions issue I was experimenting and the reason I joined this forum.

Up to now, I have listened to more than 10 hrs of Hi Res music streamed from Qobuz  - the playback was flawless. This with Bubble UPnP proxy disabled.

CPU Frequency: Performance for about 8 hrs and for the last 2 hours at 528Mhz

System tune: Latency performance

I will try other system tune shortly

May - as asked by others - please provide a description of the focus of each System tunes

Carcajou

On 6/4/2024 at 8:41 PM, Philippe Bill said:

can you explain the differences heard between :
—>hpc-compute
—>latency-performance
—>network-latency.
—>network-throughput.
—>throughput-performance.

yes, will update soon!

my current stetting :

bravo SOtM for the continuous improvement of the software ! 🤩

Bonjour to all

In my set up, as with v0.5.51, Qobuz playback (v0.5.62) of a 24/96 album at 312Mhz "froze" the SOtM after a few minutes of playback. The music stopped, the front green light stop flashing to network traffic..and the front switch would not power off the SOtM. I had to recycle OFF ON via the power supply switch (SBooster).

No browser windows were showing Euhasu at the time of the interruption (just to insure the SOtM would not try to update the GUI)

System tune: Latency performance

I do enjoy flawless Qobuz playback with the CPU frequency at 528Mhz with Latency performance System tune.

Carcajou

4 hours ago, Carcajou said:

Bat 312Mhz "froze" the SOtM after a few minutes of playback.

yes, as explained above it seems that 528Mhz is the minimum..