great, thanks
Senior Member
great, thanks
Senior Member
ok, i've now tested it with 2.3.1 and the problem still persists. after starting the media player on my tv and i enter the video section i've got the "no video files" found error for a few times. but after retrying entering it works after a while. and then there's sometimes the "media play" error which i get on trying to return to the root folder of my movie section from time to time. like i've said: it was fixed with your patched samsung a/b/hts patch although i'm using the samsung c device profile. but i had lost the subtitle and resume function... it's bizarre...
Am i the only Samsung c user with this problems?
Last edited by fastbuck; 04-22-2011 at 03:04 AM.
Member
Originally Posted by fastbuck
No you are not alone, I also have a C series and have experienced the "media play" error, don't remember seeing the no video files error.
I am running 2.3.1 and have just been lazy at this stage about chasing it. When it happens the second attempt to browse to the folder has always worked. So annoying but not a show stopper. Having said that a fix would be nice.
Conceiva Staff
We have not seen this problem with v2.3.1 but we will check this out again with our Samsung C-series TV.
Mezzmo Android: Install it on your tablet, smartphone, Android TV or Amazon Fire to browse and stream files from your Mezzmo library to all your devices. Full details at http://www.conceiva.com/products/mez...mo_android.asp
Mezzmo for Kodi Add-on: Install it into Kodi to stream files from your Mezzmo library directly in Kodi. Full details at http://www.mezzmo.com/wiki/doku.php?...odi_user_guide
Mezzmo for Roku App: Install it onto your Roku to stream files from your Mezzmo library. Full details at http://www.mezzmo.com/wiki/doku.php?...oku_user_guide
Wiki: User Guides & Reference Manual at http://www.mezzmo.com/wiki
Facebook: http://www.facebook.com/Mezzmo.DLNA.Server
Twitter: https://twitter.com/conceiva_mezzmo
Web: http://www.mezzmo.com
Member
My only guess about this problem is it may be is a timeout issue. Not 100% sure but I think when it happens is after a period of not using the media feature and my server has powered down the drives that contain the media files. When you first browse to a folder and the server has to start up the drives this can delay things for several seconds and it seems to be when this error appears. As I said once it fails you can go back to the same folder and it works.
Hope that helps.
Posting Permissions
Reply With Quote
Bookmarks