Jump to content
IGNORED

SOtM smS-200 unveiled at Munich Hi-End


Recommended Posts

This isn't very helpful to people having problems, but I have to say that mine has worked fine with no issues. I upgraded by burning an SD card image using Windows. The interface maybe slightly more laggy but not enough to notice. I'm using dlna mode and at first found the sound quality better in the bass, but had a very slight hard metallic top. I set the buffer to 100% which is what I had before and the top end seemed to improve. The bass has more detail and it's just cleaner and more realistic and seems deeper. My system isn't full range so this improvement is welcome and surprising. No stuttering and if anything slightly more stable than before when changing tracks (some previous versions haven't done so well with this). 

I'm still in 4.5 and I get a constant flashing light so I'll upgrade to 4.5.1 soon but I'm a bit worried to reading all this!

 

Anyway, I just wanted to balance out the narrative as often people with issues stay silent while those with are more vocal.

Link to comment

I also had no problems, no stutter. I'm hesitant to mention this stuff as I'm very much an amateur. Be careful to format the SD card correctly (not mac disk utility) use SD formatter or a specialist program. Download is slow but no problem. It went on an average 8 GB card. Balenetcher for writing the image worked for me.

 

When you re-load, it is effectively a new machine and will likely get a different IP address from the router, so do a scan of your system to pick it up, the use the web browser access to configure it.

 

Cups of tea and biscuits also help.

 

Link to comment
23 hours ago, Always.Learning said:

These instructions in the link two posts above appear to assume one is using Windows OS. I wonder if there are any comparable instructions that would work with Mac OS?

 

Yes, and it is much more easier with MacOS : http://docs.sotm-audio.com/doku.php?id=en:eunhasu:burn_sdcard_image#macos

Mac Mini server running Audirvana+

SOtM SMS-200 neo ultra w/ external clock output linked to a tX-USBhubEX 
SOtM SPS-500 powering both streamer and USB reclocker with Ghent Audio Y DC cable

Wyred4Sound DAC2DSDse w/femto clock

Audia flight FL TWO

B&W CM10S2

Link to comment

To add to the above, I have spent quite a bit of time on 0.4.5.1 now.  As mentioned in an earlier post, this was via burning an image to a micro SD card via a Windows PC.  (ScanDisk 16GB)  Most of my listening has been with HQPlayer NAA and this works fine and is stutter free.  Yesterday I tried Roon RAAT, using the 0.2 buffer and 0.05 Resync delay as recommended by @octaviars earlier in the thread.  I only tried this for an hour or so, but during this time it was 100% stutter free.  On and off I have also used the Shairport mode, this too seems to work OK.

 

So everything seems to work OK for me, but then again I have not been using the playback options that appear to be problematic for others.  For those still struggling, I can only hope SOtM get there act together and provide a stable update.

Windows 11 PC, Roon, HQPlayer, Focus Fidelity convolutions, iFi Zen Stream, Paul Hynes SR4, Mutec REF10, Mutec MC3+USB, Devialet 1000Pro, KEF Blade.  Plus Pro-Ject Signature 12 TT for playing my 'legacy' vinyl collection. Desktop system; RME ADI-2 DAC fs, Meze Empyrean headphones.

Link to comment
3 hours ago, Traildog said:

I'm using dlna mode and at first found the sound quality better in the bass, but had a very slight hard metallic top. I set the buffer to 100% which is what I had before and the top end seemed to improve. The bass has more detail and it's just cleaner and more realistic and seems deeper. My system isn't full range so this improvement is welcome and surprising.

2

Interesting comments.  My system is "full range" but if you look at my post on P56 you will see that we have similar observations regarding both the bass and treble differences.  When you say you have set the buffer to 100% in DLNA mode, are you referring to the buffer before play setting in Eunhasu?  I might give this a try with JRIver when I get some free time.

Windows 11 PC, Roon, HQPlayer, Focus Fidelity convolutions, iFi Zen Stream, Paul Hynes SR4, Mutec REF10, Mutec MC3+USB, Devialet 1000Pro, KEF Blade.  Plus Pro-Ject Signature 12 TT for playing my 'legacy' vinyl collection. Desktop system; RME ADI-2 DAC fs, Meze Empyrean headphones.

Link to comment

Yes, I'm referring to the buffer before play in Eunhasu. I felt it improved the hardness, although I cannot say it got rid of it completely. It could be that I've become accustomed to it and I haven't referred back to the old card yet, so it'll be interesting to hear your thoughts should you try it. Overall I'm quite happy with the sound, though I must admit to being slightly unsure at first.

Link to comment

Problem with update: There is something that might be ininteresting.

I use wlan with my sms 200 Ultra. After all updates in the last 1,5 years wlan worked before and after the update (via Eunhasu). But after updating from 4.22 to 4.51 via imageUSB I had to setup the sms 200 Ultra as a new utility. Meaning I had to start with LAN-cable, activating the wlan-function in Eunhasu (selecting wlan network with password) and not before that, it worked with wlan.

Link to comment

One slightly curious observation. I checked for updates in Eunhasu yesterday, V0.4.5.1 was still the latest. I clicked on the kernel update, it updated and rebooted. Now I have just noticed that the "blinking light syndrome" has stopped. I have no idea if this is due to the kernel update or just a coincidence.

Windows 11 PC, Roon, HQPlayer, Focus Fidelity convolutions, iFi Zen Stream, Paul Hynes SR4, Mutec REF10, Mutec MC3+USB, Devialet 1000Pro, KEF Blade.  Plus Pro-Ject Signature 12 TT for playing my 'legacy' vinyl collection. Desktop system; RME ADI-2 DAC fs, Meze Empyrean headphones.

Link to comment
6 hours ago, Confused said:

One slightly curious observation. I checked for updates in Eunhasu yesterday, V0.4.5.1 was still the latest. I clicked on the kernel update, it updated and rebooted. Now I have just noticed that the "blinking light syndrome" has stopped. I have no idea if this is due to the kernel update or just a coincidence.

 

What I observed is that the blinking lights is a random behaviour. Out of 10 time I’ve booted the player about 3-4 times the blinking lights disappear. And if its there when its boot up - I find using the reboot function in eunhasu takes care of it quite well. 

Link to comment
8 hours ago, SYM said:

 

What I observed is that the blinking lights is a random behavior. Out of 10 time I’ve booted the player about 3-4 times the blinking lights disappear. And if its there when its boot up - I find using the reboot function in eunhasu takes care of it quite well. 

Ah, interesting.  So this suggests that I solved the the blinking issue just because I happened to reboot at the weekend.  As it happens, i was reconfirming some stuff in my hifi rack on Sunday morning.  During this time I had the sMS-200Ulta unplugged for maybe half an hour, then was disconnected / reconnected about ten minutes after that, as I sorted some things out.  so it had a few reboots that morning.  I will keep an eye on this to see if there is some kind of a pattern.  It always puzzles me when electronic kit exhibits seemingly random behavior.

Windows 11 PC, Roon, HQPlayer, Focus Fidelity convolutions, iFi Zen Stream, Paul Hynes SR4, Mutec REF10, Mutec MC3+USB, Devialet 1000Pro, KEF Blade.  Plus Pro-Ject Signature 12 TT for playing my 'legacy' vinyl collection. Desktop system; RME ADI-2 DAC fs, Meze Empyrean headphones.

Link to comment
11 hours ago, Confused said:

Ah, interesting.  So this suggests that I solved the the blinking issue just because I happened to reboot at the weekend.  As it happens, i was reconfirming some stuff in my hifi rack on Sunday morning.  During this time I had the sMS-200Ulta unplugged for maybe half an hour, then was disconnected / reconnected about ten minutes after that, as I sorted some things out.  so it had a few reboots that morning.  I will keep an eye on this to see if there is some kind of a pattern.  It always puzzles me when electronic kit exhibits seemingly random behavior.

 

I happened to power down the ultra by accident awhile ago (the sps500’s button is super sensitive). Powering it up again and the blinking light is back. I reboot the player via eunhasu - still the same blinking light. 

 

I power cycle the ultra manually again and the blinking light disappear. This is weird. It is  completely random. Those with blinking light problem can try to either reboot or power cycle the player. Works for me. Just sharing this useless findings 😛

Link to comment

V0.4.5.2 has landed .........

Windows 11 PC, Roon, HQPlayer, Focus Fidelity convolutions, iFi Zen Stream, Paul Hynes SR4, Mutec REF10, Mutec MC3+USB, Devialet 1000Pro, KEF Blade.  Plus Pro-Ject Signature 12 TT for playing my 'legacy' vinyl collection. Desktop system; RME ADI-2 DAC fs, Meze Empyrean headphones.

Link to comment
6 minutes ago, Confused said:

V0.4.5.2 has landed .........

 

Downloaded and burnt to my SD card.

 

Roon works as it should but Eunhasu is still very slow and unresponsive. 

Main system
TAD D1000mk2, TAD M2500mk2, TAD CE-1, Ansuz Mainz 8 C2, Ansuz Darkz D-TC, 
Qobuz Studio -> Roon ROCK on NUC -> Uptone etherREGEN -> dCS Network Bridge -> AES/EBU -> DAC
HD Plex 200W PSU (4 rail for ISP fiber, router, etherREGEN and NUC)
 
Second system
Qobuz Studio -> Devialet Silver Phantom, Devialet Tree
Link to comment

Guess the blinking lights problem persists on 0.4.52

Librespot is super unstable on this release - keeps disconnecting

@may.park - Please do ensure that proper testing is done before releasing the next firmware. This is quite embarrassing for the company - as within a span of 1 month - 3 releases and each has got it own problem. 

Link to comment

@Cloth Ears you need to download and burn the image to the SD card. 

 

At the bottom of this page is the link to download 4.5.2

 

http://docs.sotm-audio.com/doku.php?id=en:eunhasu:burn_sdcard_image

 

I installed 4.5.2 yesterday and all was fine with Roon but this morning the blinking light syndrome was back 😡 will do a reboot later today to see if it goes away.

 

 

Main system
TAD D1000mk2, TAD M2500mk2, TAD CE-1, Ansuz Mainz 8 C2, Ansuz Darkz D-TC, 
Qobuz Studio -> Roon ROCK on NUC -> Uptone etherREGEN -> dCS Network Bridge -> AES/EBU -> DAC
HD Plex 200W PSU (4 rail for ISP fiber, router, etherREGEN and NUC)
 
Second system
Qobuz Studio -> Devialet Silver Phantom, Devialet Tree
Link to comment

It's a free upgrade and you are not forced into it and can easily roll back to older versions if it's not working for you in your particular use case. I think there needs to be some perspective on this. You bought something which works, you can continue to use it as you bought it. This is a free improvement, getting upset about it seems over the top to me.

 

Link to comment
1 minute ago, Traildog said:

It's a free upgrade and you are not forced into it and can easily roll back to older versions if it's not working for you in your particular use case. I think there needs to be some perspective on this. You bought something which works, you can continue to use it as you bought it. This is a free improvement, getting upset about it seems over the top to me.

 

 

There are a few of us who purchased this and needed the upgraded firmware for full native DSD support.  Granted, it now works for my DAC, but still pops and crackles.  Not impressed given the money spent...

 

SoTM support have asked me to upgrade it again, and its not resolved the matter either.

Link to comment
1 hour ago, Traildog said:

It's a free upgrade and you are not forced into it and can easily roll back to older versions if it's not working for you in your particular use case. I think there needs to be some perspective on this. You bought something which works, you can continue to use it as you bought it. This is a free improvement, getting upset about it seems over the top to me.

 

 

Absolutely agree - just hope that they can label experimental release with the "beta" tag. Then we'll decide if we wanna get adventurous. 

For your information - 4.52 has been pulled out completely now. They're back on 4.51. This only goes to show 1 thing and 1 thing only - 4.52 is a mistake and its also acknowledged by SoTM. No point defending their position here

Link to comment
14 hours ago, SYM said:

@may.park - Please do ensure that proper testing is done before releasing the next firmware. This is quite embarrassing for the company - as within a span of 1 month - 3 releases and each has got it own problem. 

I have used my sms-200 since 4.14. I've noticed that firmware updates after a lull period are always followed by another update or two to fix issues in the previous version. Version 4.5 has to be the worst yet for bugs.

 

I am using 4.51 successfully now, but I had to replace my older Audiolab 24/96 DAC. It was stopping every time resolution changed (i.e. going from 16/44 to 24/88, music would stop, sometimes would not restart). 

Main System: QNAP TS-451+ NAS > Silent Angel Bonn N8 > Sonore opticalModule Deluxe v2 > Corning SMF with Finisar FTLF1318P3BTL SFPs > Uptone EtherREGEN > exaSound PlayPoint and e32 Mk-II DAC > Meitner MTR-101 Plus monoblocks > Bamberg S5-MTM sealed standmount speakers. 

Crown XLi 1500 powering  AV123 Rocket UFW10 stereo subwoofers

Upgraded power on all switches, renderer and DAC. 

 

Link to comment

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...