datikaa 0 Posted July 3, 2016 Share Posted July 3, 2016 Hi there! For some reason, there are cases where my newly added media is recognised and it's metadata is downloaded, but it's media info is empty. With empty media info the app I'm using (Emby for Android TV) is kinda useless, as I can't change audio or subtitles, or even rewind the media. What I've figured out from the log is that ffmpeg can't read the media: 2016-07-03 23:35:43.5507 Info MediaEncoder: Killing ffmpeg process 2016-07-03 23:35:44.0003 Error App: Error in ffprobe ... ffprobe failed - streams and format are both null. At any time, a manual refresh on the media solves it. Any suggestions? Log.txt Link to comment Share on other sites More sharing options...
Luke 37336 Posted July 3, 2016 Share Posted July 3, 2016 once in a while that will happen. if you are copying a new file into your media location, it could be that it tried to probe before the file had finished copying. 1 Link to comment Share on other sites More sharing options...
JeremyFr79 228 Posted July 3, 2016 Share Posted July 3, 2016 once in a while that will happen. if you are copying a new file into your media location, it could be that it tried to probe before the file had finished copying. This is exactly the issue I've seen in the past, easily fixed by doing a refresh on the object, 2 seconds and everything is filled in. Link to comment Share on other sites More sharing options...
datikaa 0 Posted July 3, 2016 Author Share Posted July 3, 2016 Well, if that's the case, I can live with it, but I would like to note, that I'm noticing this for like the past few weeks. Before that, never happend (also I'm on beta, If any help). Link to comment Share on other sites More sharing options...
DarWun 269 Posted July 4, 2016 Share Posted July 4, 2016 (edited) Well, if that's the case, I can live with it, but I would like to note, that I'm noticing this for like the past few weeks. Before that, never happend (also I'm on beta, If any help). I've had this happen a number of times for the reason cited earlier in this post. It was easy to fix with a rescan. But after updating to Beta v 3.1.53.0, Emby failed to detect media characteristics for fifteen mpeg-2 files I added to my library. Emby wasn't started until after the files were copied to the storage location. So ffprobe shouldn't have any problems scanning the files. Rescanning did not resolve the issue. I posted about it here: http://emby.media/community/index.php?/topic/36500-media-characteristics-not-detected-beta-31530/. Luke responded quickly to identify that the issue would be resolved in the next beta build, but a manual rescan would be required for any affected files after updating. Sure enough, everything went back to normal after updating to Beta v 3.1.54.0. I noticed in the log you attached to your post that you were running Beta v 3.1.54.0 when you encountered the error. So the above may not apply. But I figured I'd pass the information on as it might explain why you have been noticing the issue over the past couple of weeks. Edited July 4, 2016 by DarWun Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now