Jump to content
IGNORED

Euphony OS w/Stylus player setup and issues thread


Recommended Posts

I'm using Euphony/Stylus installed onto Optane and RamRoot on Apacer RAM. I have both full song buffer and cache enabled. Since the tracks are being played from Optane and RAM does this mean that it doesn't matter where the song files are coming from.

 

I've been using an SD Card to avoid issues with SSD and Hard Drive. However, it is of course pretty slow, and my song files are upscaled PCM768KHz so are about 1GB each. 

 

Would I not lose any SQ using a faster drive?

 

Link to comment

This is the message I got from Željko:

 

"I often hear that people avoid SSDs because they think SSD is noisy even when not being actively read but that probably varies from one SSD to the next and I don't really expect you will be able to hear the difference when playing from RAM unless your system is already ultra resolving."

 

I spent some time comparing an external SD Card and SSD. My system is very resolving, and I do think there is a slight difference. There did seem to be a–slightly–excited upper mid/highs which is consistent with increased noise. It also just sounds a bit more clear. However, as he said, playing from RAM, it was not a major difference. 

 

Since the audio file is not playing directly from SSD but RAM, we are talking about just the noise emission of having it plugged in and powered. 

Link to comment

Thanks Dave, 

There are a few things to consider here, one is that you're comparing a SDCard, SSD connected locally and the HD was connected over network. Did you try connecting a HD directly to the NUC and were the results the same?

 

Also, in your second post you mentioned you moved to RAM mode. I assume you mean RamRoot. However, in your tests were you caching to an Optane drive and buffering 100% song to RAM before playback. 

 

This is the use case that I'm trying to test. The question is: if audio files sound different played directly from SDCard, SSD, or HD, does this difference hold when the files are no longer being played directly but from cache/RAM?

Link to comment
  • 2 weeks later...
  • 2 weeks later...
  • 3 weeks later...

I'm continuing to play around with core isolation while I listen and make changes to my system. I've found it is just not a matter of giving gstp as many cores as you can. At least if you are only working with 8 cores or less. The more you devote to gstp the more the sound gets solid and defined. However, like with processing speed, it can come at the cost of bringing out more edge and unwanted brightness. I've backed off from 0-2 gstp 2-7 to 0-2 gstp 3-7. 

 

This is right for my current configuration, but of course this is all so system dependent. Calibrating the isolation on Euphony is interesting. As long as you have a highly resolving system the changes are immediately apparent. I've even found a difference between default and 0-7 stylus 0-7 gstp 0-7, the latter being more clear but less fluid. 

 

Some might think of the changes as subtle and unnecessary, but if you've come this far, having this bit of tuning is very satisfying. 

Link to comment
  • 2 weeks later...

Cosmetic changes in case anyone is interested:

 

- Play que is now dark grey instead of light grey. 

- Track selection bar is now flat teal color

- Background album art is darker and less distracting

- Now playing cover art resolution has bumped up from 300px, though still not full quality. 

 

Anwar's notes above say:  "Use original cover for Playing now screen" 

Anyone know what this means? Original cover art always showed for me in the Playing now screen. 

 

 

Link to comment
  • 2 weeks later...

The first range of core numbers are for general processing of Euphony. Then comes stylus, and next Roon, HQP, etc. I don't use either so I forget the process names. However, once you hit apply, you'll get the screen that shows the processes and core assignments. Roon should be easy to identify. "gstp" is the actual playback processor and so, personally, I've found that giving it more cores is beneficial, up till the point it causes harshness. 

 

The image below is a good starting point. Along with some others, I haven't found isolating stylus did much and that devoting cores to gstp did a lot. So what I posted above (0 gstp 1-7) gives one core to everything including stylus and reserves 7 cores for gstp. This seems extreme to me even as I'm doing it so it may not work well in other systems.

 

Good luck and report back if you can!

 

654193123_ScreenShot2020-10-25at10_16_06PM.thumb.png.844a631dd4f784d10e7ee7f335474645.png

 

 

1783236870_ScreenShot2020-10-25at10_13_48PM.thumb.png.c75228bcc2c85a10db247ad1bbdf3724.png


 

Link to comment
1 hour ago, TheAttorney said:

So good news, and now the better news: Whilst I broadly agree with your findings, I think I've found an even better combination than [0 gstp 1-7]. To my ears, [0-1 gstp 1-7] gives even more of the above SQ benefits, plus the further bonus of a significantly lower temperature for physical core 0. The temperatures are now more balanced across the cores, which isn't intuitive because it's the same physical core 0 in both cases. And virtual core 1 is now sharing gstp with everything else. Core Isolation moves in mysterious ways.

 

First of all, I know you must be a lawyer because you use the term "whilst" (grin). I do love the English language. 

 

Awesome! I'll try out 0-1 gstp 1-7 tonight. If I can improve SQ and lower temps that's a good day. Though you are quite right it is mysterious with so many system specific factors. I'm always at 3.9-4.2GHz so the results may vary. 

 

Isn't it a kick in head how core isolation affects SQ as much as it does? Also, I'm amazed that you can just adjust these parameters in real time and hear the changes. If you had to reboot each time I would constantly be questioning if I'm hearing the changes correctly. As it is it's just so handy to be able to assign cores whilst listening (I couldn't resist because of the assonance between 'whilst' and 'listening.' I do love the English language). 

Link to comment

I tried out 0-1 gstp 1-7, and the temps got displaced to the first two cores. So 1 went down and 2 went up; both are low 60s. This is welcome.

 

To my ears the sound suffered slightly. It's really subtle, but it sounded smaller and flatter to me. 0 gstp 1-7 still sounds a bit larger and more vivid to me. 

 

This could just be my system or psychology. This is complicated, however, my guess is sill that the more cores you dedicate to gstp the better. Thinking simply, sharing core 1 reduces isolation. 

Link to comment

Thanks for letting us know. I'm doing the update right now. Euphony is really putting out the updates. 

 

Please report if you hear any changes to sound.

 

Here is the latest changeling:

 

20201102
- WARNING for users on version less than 2020-10-05: TIDAL has changed authorization process and TIDAL will stop working sometimes mid December unless you update.
- Added processing of CUE playlist files
- Reorganization of Settings page
- Added some system info fields
- Added some Music DB stats
- Added some Summus specific UI changes
- Euphony launch page improvement: started audio service is displayed in addition to hostname
- Youtube playback fix
- Fixed adding multiple network drives
- Fixed Tidal expire problem
- Fixed Tidal authorization from native Android/iOS applications (they are updated - download the latest version)
- Fixed the problem when additional internal drives won't remount on startup
- Fixed radio playback mode
Link to comment

Upsampling to higher sample rates does not automatically mean better sound. Actually, it's the opposite for the basic filters that come with most apps. Unnecessary upsampling will only make the sound worse, and the further you get from the source frequency the more error you introduce.

 

The computationally heavy algorithms implemented in HQP and Mscaler are incredibly complex and are of a different nature. They don't only increase the sample rate, but attempt to reconstruct the original waveform. So, in their case the more samples you can give it the more accurate they become. 

 

Unfortunately, the readily available sampling filters (e.g., SoX) are not free/cheap ways to mimic the results of HQP/MSc. It's not their purpose/design. You want to use them only for simple corrections: 48KHz to 44.1KHz. 

Link to comment

As to loading songs to memory, no features have been removed as you know, just reorganized. 

 

The loading to RAM, "buffer before play," is in: Settings > Music service > Other music options.

 

You can load the tracks to a cache if you have a fast drive with "Use cache" in: Settings > Library > Miscellaneous. 

 

 

Link to comment
  • 2 months later...
  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...