Hi there
Had my Wiim pro for about a week now and I'm interested to hear whether others are seeing any of the same issues.
I'm using it for spdif input from my Samsung TV (for all video streaming platforms like Netflix, etc and DVD/Bluray) and for streaming Amazon and Tidal over wifi, both from within the Wiim Pro app and using Tidal/Amazon connect (which is less reliable ie the Wiim doesn't always appear as an available output device from within the Tidal/Amazon apps, but that's another problem).
Right now my biggest issue is distortion when using the spdif input fed from my Samsung TV which occurs on a regular basis about ever half hour or so. Basically the sound starts to deteriorate over several seconds and then breaks down into heavy metallic digital distortion. Usually opening the Wiim home app and switching to wifi source and back to spdif cures it for half an hour or so.
I raised a ticket and noticed that it is a known issue on the Wiim support site. I then had a message from Wiim during the week saying there was a firmware fix going out (4.8.506254) which should address the issue. This firmware was subsequently installed on my Wiim and it seems like the problem has changed as a result but NOT been fixed, as follows:
Now, every 30 min or so, the sound quality starts to deteriorate over several seconds (firstly becomes more sibilant, then noticeably slightly distorted, but less distorted than before) but now it just mutes completely for a couple of seconds before coming good again for the next 30 minutes or so. It's almost as if the Wiim is drifting out of sync with the spdif input, detecting it and then soft muting for a couple of seconds while it restarts/relocks and then unmutes.
So it seems like Wiim are trying to fix the problem but haven't managed to yet... Which is slightly worrying since spdif input should be relatively simple thing for a box with the processing power of the Wiim Pro to cope with...
Would just be interested to know what other people's experiences are of this problem, and whether anyone has noticed a similar change in behaviour since the recent 4.8.506254 firmware upgrade?
Had my Wiim pro for about a week now and I'm interested to hear whether others are seeing any of the same issues.
I'm using it for spdif input from my Samsung TV (for all video streaming platforms like Netflix, etc and DVD/Bluray) and for streaming Amazon and Tidal over wifi, both from within the Wiim Pro app and using Tidal/Amazon connect (which is less reliable ie the Wiim doesn't always appear as an available output device from within the Tidal/Amazon apps, but that's another problem).
Right now my biggest issue is distortion when using the spdif input fed from my Samsung TV which occurs on a regular basis about ever half hour or so. Basically the sound starts to deteriorate over several seconds and then breaks down into heavy metallic digital distortion. Usually opening the Wiim home app and switching to wifi source and back to spdif cures it for half an hour or so.
I raised a ticket and noticed that it is a known issue on the Wiim support site. I then had a message from Wiim during the week saying there was a firmware fix going out (4.8.506254) which should address the issue. This firmware was subsequently installed on my Wiim and it seems like the problem has changed as a result but NOT been fixed, as follows:
Now, every 30 min or so, the sound quality starts to deteriorate over several seconds (firstly becomes more sibilant, then noticeably slightly distorted, but less distorted than before) but now it just mutes completely for a couple of seconds before coming good again for the next 30 minutes or so. It's almost as if the Wiim is drifting out of sync with the spdif input, detecting it and then soft muting for a couple of seconds while it restarts/relocks and then unmutes.
So it seems like Wiim are trying to fix the problem but haven't managed to yet... Which is slightly worrying since spdif input should be relatively simple thing for a box with the processing power of the Wiim Pro to cope with...
Would just be interested to know what other people's experiences are of this problem, and whether anyone has noticed a similar change in behaviour since the recent 4.8.506254 firmware upgrade?