Another peculiarity I've discovered with using the S3. I'm listening in a near-field setup, and all my gear stays on and often goes to sleep due to some degree of inactivity. Some things wake up properly and recover with no issue, or me having to take action. I use roon with my music library on a NAS. Network --> TransportPi --> S3 (Opt-IN) --> Preamp --> Vibelink amp. I often will pause roon playback and do something else away from NF listening desk. When I get back, I press play on my roon remote(software) and nothing. Roon shows the track playing, but nothing is coming from my amp.
I've learned this behavior has to do with how the S3 auto-detects a signal on the input. In particular, the HDMI/Opt input. The S3 shares the electrical connection internally between the HDMI port and the Opt port. Under normal listening I have to press the HDMI/Opt button on the front panel twice. The 2nd press switches the input from the HDMI(default) to the Optical. Very odd action, but it works - most of the time. However, after the S3 'falls to sleep' due to signal inactivity, and I start my roon track playing again I hear nothing... because, when the HDMI/Opt port wakes up and senses my track playing once again it, wait for it....defaults to the HDMI port and not the optical port. The only fix I know of, is to cycle through the inputs(like normal), and then press the HDMI/Opt button twice to get it switched back to optical and finally get the music playing.
This is not a big deal, but I thought I would share in case someone else has runs up against a similar sequence of events and can't get their music back. Maybe this is a built-in feature and not a bug!
