Jump to content


  • Content Count

  • Joined

  • Last visited

About Bricki

  • Rank

Recent Profile Visitors

901 profile views
  1. The NUC is my roon endpoint. The SMS-200 was in roon ready mode πŸ‘
  2. I wholeheartedly agree with you about the importance of good power supplies. The only surplus equipment I have is my SMS-200. If I get a new PSU (I have my eyes on the farad super 3) then my sps500 will go to my router. I can only afford one new piece of equipment in the next 12 months so I am carefully considering my next move😁. Options high on the list are: -farad super 3 -lps1.2 -Etheregen -CSS P215 kit speaker -mini itx build -more furutech goodies😁
  3. Listening impressions SMS-200 (latest 4.6 update) vs Celeron NUC7 (audiolinux) The software for both of these has changed considerably since I last did this comparison, so I thought it was worth a revisit. Both are powered by an sps500 with JSSG360 DC cable and furutech TCS21 ac cable. Ethernet connection to the server is bridged and running in half duplex mode at 10mbps. With a 1 meter Supra cat8 with JSSG360. The SMS-200 This is the original sms-200 non ultra with no neo upgrade Pros: -has a blacker background with more focused images. -has a slightly more refined or lower noise feel about the presentation -has a bit more depth to the soundstage Cons: -despite the more focused image outlines the image itself somehow seems flatter and digitally smeared. I know this sounds like a contradiction, but it's like a nicely focused caricature vs the NUC that is a slightly out of focus but more natural image of the original recording. -less dynamic -has a flatter less colourful tone -has smaller images -although it has more depth to the soundstage it feels smaller with less width The NUC The NUC is in an akasa fanless case running the latest audiolinux headless mini 140 with the 5.2 BFQ kernel in ramroot with isolated cores and acpi CPU scaling driver. Pros: -has a much more natural sound -has larger images and soundstage -piano, guitar and brass instruments sound much more like the real thing with less digital smearing and a more analogue sound. Live recordings are particularly good with a feeling as if the output from the sound desk is plugged into my amp. -has a more colourful tone that makes everything seem more alive. -makes me want to listen to music more and not change tracks but listen to a whole album -more captivating -more dynamic -lyrics are more easily discerned Cons: -the background seems slightly more gray and less black -the images aren't quite as focused in their outlines -doesn't sound quite as refined in the presentation Final thoughts Although the software on both devices has changed for the better, the NUC is still the better sounding of the 2 in my system. It gets deeper into recordings and lets you hear things you didn't even know were there. It makes me wish I had more financial resources to get more powerful hardware πŸ˜πŸ‘
  4. Thanks heaps for that 😁...it was just enough to get me over the lineπŸ‘
  5. Ok thanks for that... Yeah I have already tried the clean system option in the menu and I still have the issue with ramroot... The clean system option did reduce the root file system size down to the 3240MB in the photo above
  6. With my fresh USB stick of the mini 140 image and all packages and menu updated with kernel to 5.2 I am struggling to get ramroot working with my endpoint. Besides installing another 4gb of RAM is there anything else I can do? I have deleted roonserver and freed up a little more space .... Can I delete hqplayer etc? All I need is roonbridge... What is the hqplayer file name? I tried yaourt -R hqplayer but it wasn't found?
  7. Ok I finally had a chance to try isolated cores again on my server... I now remember why I liked it so much the first time πŸ˜πŸ‘...I can't even remember why I stopped using it... I think I had trouble getting it working again after the NUMA off kernel update or something... That was a while back... Next step will be to get my NUC endpoint working again... I've just got a fresh USB stick and I'm trying to remember all the tweaks I had working 🧐😁
  8. Ok😁. I will try it again as I've made a heap of changes since the last time I had isolated cores working... I will try on my server tonight with the SMS-200 as endpoint (which with the latest 4.6 update has come a long way).
  9. Ok thanks...πŸ‘ after some of the updates I decided I was better off without isolated cores... At least on the Celeron... Do you still use isolated cores?
  10. Ok thanks. I'll check when I get home tonight... I had to pull it out for the time being and replace it with my SMS-200... But the 5.2 kernel is working well on the server πŸ‘
  11. I installed the BFQ 5.2 kernel on my server and endpoint... the server worked fine... However the endpoint now won't start roonbridge.. I only have 4GB of RAM in the Celeron nuc so maybe this has finally become a problem. @lmitche do you still only have 4GB of RAM in your endpoint? I might just have to try with a fresh install...
  12. Yes I like what I hear as well... clarity is improved as if a layer of murkiness has been stripped away... After selecting acpi on my Celeron NUC in the menu under the scaling driver field I have written " noorunknowncpufreqdriverisactiveonthiscpu" However I still got an increase in clarity and I haven't even put ramroot back on and it already sounds better
  13. Has anyone tried reducing USB transfer speeds with similar effect? For example if we reduce our USB transfer speeds for music storage on our server, perhaps there could be some gains there. I assume this is possible somehow in Linux but I wouldn't know where to begin 🀣. USB 3.0 controllers do seem to have better signal integrity and sound better but if we can reduce their speed back to USB 2.0 there might be some further SQ gains. Just a thought
  14. Ok I have changed down to 100Mb/s on my server for the connection to my endpoint and I can hear an improvement already... quite a nice improvement, a lot less subtle than I was expecting...next I will change the speed for my connection from server back to router. Thanks to @Dev for the info πŸ˜πŸ‘
  • Create New...