Server Version#: 1.19.5.3112
Player Version#: Samsung TV 5.1.2
NAS: Synology DS216PLAY
Tizen Version: 3
Samsung TV : 2017 65MU6100W
My older AVI files wont play on the 5.1.2 app, for example MPEG-4 video + MP3 Audio
Playback Error The file associated with this item is not accessible by the server. Please verify that the file exists and that the necessary drive is available.
Settings Leave Early Access rolled back to 5.1.0 playback works again, so some bug has been introduced between 5.1.0 and 5.1.2 that impacts AVI playback.
I have got exactly the same error. The only workaround is to created and optimized version (for TV)
I hope they will fix this soon, as most of my movie collection is in that format.
The error message suggests that the file has moved or is inaccessible which is rubbish.
What might be happening is that Direct Play is not working and my Plex Server does not have hardware transcoding capability so that causes playback failure.
If they changed something to do with Direct Play for AVI format in 5.1.2 that would explain it.
Server Version#: 1.20.1.3252
Player Version#: Samsung TV 5.1.3
NAS#: My Cloud Ex2 Ultra
Tizen Version: 2.4
Samsung TV : 2016 Ks8000
Same problem, since the new preview version (very happy with most of changes) was installed the avi files are not possible to reproduce. With previous version all worked.
The iPad client works fine, as usual. So, it’s the tv client…
Same problem in 5.2.1 on my TV 2020 - I have found that disabling direct play and direct stream resolves the problem though - and even then, the file is not transcoded. Very strange.
Anyone have any news on this? I’ve got three LG TV’s, all slightly different models/years but all have this same error when trying to playback avi files since the client was updated.
This was the only thread I could find that mentioned this particular issue and as I’m sure you’ve noticed having read the entire thread before commenting on just the last post, others before me have already posted above that it’s affecting the Samsung, LG and Android Smart TV clients so it’s not necessarily platform specific but something that’s changed in the base-code for the Smart TV clients.
If you would be so kind as to point me to the LG thread I should have posted this in I’ll happily go over there instead, or if you’ve got any useful information to contribute that may help those who have posted here resolve the issue at hand then I’m sure it would be very welcome by all.
@Kong I haven’t had this issue, nor do I own LG products. But if I did, I wouldn’t wait for a tread to be started to address the issue, I would create it.
Best of luck in getting your issue resolved, as it only makes the user experience better for us all.