Lets not mix up bugs:
-
playing one corrupt file results in no playback of any proper file afterwards
this bug has been around for ages and can only be fixed by power-cycling (and by not playing crappy files in the first place) -
some MP4s are not played back in 2.02.32 while others do just fine (demo file here)
solution: rename to m4v or remux or downgrade to 2.01.86 till this if fixed (already done on the “new” WD TV in 1.02.17, no idea why backporting it to the Live Streaming takes so long) -
playing any proper file right after bootup results in “Unable to play selected file. Please see the User Manual for a list of supported formats”.
This bug seems to have been introduced with the 2.x firmware and is also present on the current WD TV. It’s not reproducible but it appears to be connected to the TV not being tuned to the WDTV during boot
solution: powercycle or apply KAD79’s reset everything script. -
some files stop playing after any number of minutes (usually ~30)
So far there’s been no proper description on how to reproduce this: what file type was played? Was it played from USB/NAS/Wifi or standby (which seems to be playing a major role in some issues)?
It might be an overheating issue which is weird cause I’m almost exclusively playing uncompressed high bitrate BD rips and haven’t seen this happen ever, not even after long video nights of 5-6 hours continuous playback (and despite the WDTV gettig quite warm to the touch). Maybe it’s the “3 hours energy saving Auto shutdown” that’s somehow active and interfering after a standby? -
boot loop/no playback without Internet connection
It currently seems to apply to the Live Streaming only. Either you can’t playback any files or the player loops when it is connected to your network but not to the Internet. It’s not reproducible so as with #4 we’d need more info. Until then you should disconnect the player during bootup.
What we need is people trying to narrow things down as much as possible.
