Houzieftm1979 0 Posted May 10, 2017 Share Posted May 10, 2017 Hi. I'm recently experiencing getting an error on various tv shows I'm watching where the video drops out and I get the error "Video Error An unexpected problem (But not server timeout or HTTP error) has been detected". Is this an Emby problem or is it a problem with my Internet etc? Link to comment Share on other sites More sharing options...
ebr 14912 Posted May 10, 2017 Share Posted May 10, 2017 Could be the video itself, could be bandwidth problems could be a number of things. Best thing to do is reproduce a specific example and provide the information in How to Report a Problem. Thanks! Link to comment Share on other sites More sharing options...
bmhanson 1 Posted October 31, 2017 Share Posted October 31, 2017 I have been getting this error quite a bit lately also. It does seem to be something with the file as I can seem to recreate it at will with the ones it has an issue with. It happens pretty frequently and my wife has started getting really irritated. :-) I will try and get the time tomorrow to send in the specifics. It only seems to happen on the Roku app. I have not tested the fire stick yet though. but on Android and my surface through the web interface it works fine. Plus direct playback of the file in a player shows no issue either. Link to comment Share on other sites More sharing options...
Luke 37062 Posted October 31, 2017 Share Posted October 31, 2017 I have been getting this error quite a bit lately also. It does seem to be something with the file as I can seem to recreate it at will with the ones it has an issue with. It happens pretty frequently and my wife has started getting really irritated. :-) I will try and get the time tomorrow to send in the specifics. It only seems to happen on the Roku app. I have not tested the fire stick yet though. but on Android and my surface through the web interface it works fine. Plus direct playback of the file in a player shows no issue either. Hi there @@bmhanson, can you please provide the info requested in post #2? Thanks ! Link to comment Share on other sites More sharing options...
bmhanson 1 Posted October 31, 2017 Share Posted October 31, 2017 That was the specifics I said I would send today if I had time. This is one of the files that seems to have the issue consistently and I can recreate at will. Attaching the server log Basically all I am doing is playing the show and all of the sudden it pops up the error message. "Video error. An unexpected problem (but not server timeout or http error) has been detected" I am not doing anything special or unusual. The file name in this instance is "Scorpion - S04E06 - Queen Scary HDTV-720p.mkv" Let me know what else you need and if i need to try and get you more examples. Link to comment Share on other sites More sharing options...
ebr 14912 Posted October 31, 2017 Share Posted October 31, 2017 Well a server, ffmpeg and in-app log as detailed in the above post is what we would need to see. However, if instead, you can provide me with that file via dropbox or something like that, I can see if I can reproduce it. Thanks. Link to comment Share on other sites More sharing options...
bmhanson 1 Posted October 31, 2017 Share Posted October 31, 2017 Well a server, ffmpeg and in-app log as detailed in the above post is what we would need to see. However, if instead, you can provide me with that file via dropbox or something like that, I can see if I can reproduce it. Thanks. Sorry. I thought i had attached the server log. I expect i actually missed clicking the "Attach this file" button. Let me try again. :-) I did not capture the app log as the link said for playback issues attac the server log. I did not look at the app issue section because I am having a playback problem. I can try and get that as well. As for ffmpeg I am attaching that her as well. Still want the file? Does it have to be dropbox as long as you can download it? I may have to see if my account there is still active. emby-serverlog-2017-10-31.txt emby-ffmpeg-2017-10-31.txt Link to comment Share on other sites More sharing options...
ebr 14912 Posted October 31, 2017 Share Posted October 31, 2017 Anything that doesn't force me to create an account with it is fine for getting the file to me. You can PM a link if you like. Thanks. Link to comment Share on other sites More sharing options...
speechles 1917 Posted October 31, 2017 Share Posted October 31, 2017 (edited) frame= 7627 fps=243 q=-1.0 Lsize=N/A time=00:05:18.26 bitrate=N/A speed=10.1x video:103220kB audio:12433kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown Something with the file is bad. Notice its ending at 5:18:26 which isnt normal for a scorpion episode. Those usually want the requisite 22 minutes of usable runtime to throw in some outlandish dialog to go with its equally far fetched plots. So my guess is you need a par2 for usenet, force recheck for torrent, or a recapture if you snagged this off your own hardware. In any case, the problem 100% isn't with emby or any of its many dependencies. If this plays correctly on other players those players are direct playing. They have to be, because ffmpeg when transcoding cuts off at 5:18:26. So the player within whatever else is playing it must be able to play the file directly and work through the incorrect runtime, or whatever the problem is... Edited October 31, 2017 by speechles Link to comment Share on other sites More sharing options...
bmhanson 1 Posted October 31, 2017 Share Posted October 31, 2017 Working on getting it uploaded now. will PM you the link when it is ready. Just to make it more confusing this morning some of the files that were previously giving errors are not anymore. Including this one that gave the error earlier today. I did see some errors in that log indicating a file was in use by another process. I think it was one of the transcoding files. Not sure if that is normal. Pure guess work, but I am betting when the server transcodes the file on the fly it writes small files that the app then picks up and processes. The app likely reading ahead and buffering to make sure the playback is smooth and not waiting on IO operations on the next file. I expect while it is not optimal, it is not unusual that there is some collision and the app tries to read a file that is not finished being written to yet. Maybe a symptom in a slowdown on the host machine in transcoding. And likely there is retry logic to try and read the file again if such collision happens. Am I anywhere in the ballpark? If so what is the retry limit? 2 by chance? Just curious because i see that error for the same .ts file 3 times prior to the playback stopping. Link to comment Share on other sites More sharing options...
bmhanson 1 Posted October 31, 2017 Share Posted October 31, 2017 frame= 7627 fps=243 q=-1.0 Lsize=N/A time=00:05:18.26 bitrate=N/A speed=10.1x video:103220kB audio:12433kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown Something with the file is bad. Notice its ending at 5:18:26 which isnt normal for a scorpion episode. Those usually want the requisite 22 minutes of usable runtime to throw in some outlandish dialog to go with its equally far fetched plots. So my guess is you need a par2 for usenet, force recheck for torrent, or a recapture if you snagged this off your own hardware. In any case, the problem 100% isn't with emby or any of its many dependencies. If this plays correctly on other players those players are direct playing. They have to be, because ffmpeg when transcoding cuts off at 5:18:26. So the player within whatever else is playing it must be able to play the file directly and work through the incorrect runtime, or whatever the problem is... ok. I will buy that as a reason. Not sure why it seems to be working when i play it now now though in the Roku app. And I have never seen this in Android or through the web interface. I just played that exact file through with no issues in emby. Any tools you might recommend to validate the file? Link to comment Share on other sites More sharing options...
ebr 14912 Posted October 31, 2017 Share Posted October 31, 2017 ok. I will buy that as a reason. Not sure why it seems to be working when i play it now now though in the Roku app. And I have never seen this in Android or through the web interface. I just played that exact file through with no issues in emby. Any tools you might recommend to validate the file? ffmpeg sees the duration just fine: Duration: 00:39:50.85, start: 0.000000, bitrate: 3680 kb/s I have played this file now on my Roku both by direct playing and by transcoding (by setting the bitrate lower in the app) and it plays fine for me. I have to believe this is some sort of environmental issue either with the network or server load which is why it is not consistent. 1 Link to comment Share on other sites More sharing options...
bmhanson 1 Posted October 31, 2017 Share Posted October 31, 2017 OK. Thanks. I will take a look internally more and see if i can find any server issues. Just strange to have started popping up out of the blue. I have not really touched the server for a while. But I am not ruling that out as an issue, especially since it is Windows and there is no telling what Microsoft has done. I should wipe and redo it as Linux but that is a project I have little time for. Plus the outage would practically kill my wife and kids. I did notice that a couple days ago it updated to the version 3.2.35.0. Now I can not recreate the issue at will. Were there any changes in this latest release that might have impacted performance for transcoding, etc? Just curious. Also I am still curious about my retry question above. I posted a little earlier. Not that it matters much in the long run but it will bug me. Link to comment Share on other sites More sharing options...
speechles 1917 Posted October 31, 2017 Share Posted October 31, 2017 (edited) I've seen this happen when the roku becomes what I call "terminal dipshit mode" and it errors on alot of things until it is reset, aka restart device. If you use the "magnifying glass" search button on the remote, this changes the audio mixer. The same happens if you press the * key 4 times real quick. Now the full crazy-talking audio guide is enabled. It starts reading buttons and useless text too. But it also messes with the audio mixer causing issues. Sound might go wavering now loud to soft to loud to soft, or might always be too low forever after. Disabling audio guide wont fix it. What fixes it is never use search or the audio guide, ever. There are also issues with certain SG render functions which cause issues forever after if used. Supposedly.. firmware OS 8.0 fixes these problems.. supposedly.. but supposedly is a word we use when roku updates things and that is not usually synonymous with actually fixing things...their fix just makes it work now in that area where the problem was, but now breaks it in one or multiple areas that were fine before. Roku is like that drunken uncle who can't keep his hands off things. Breaks things, blames the pets for it, sits back down. Pretends the mess isn't his responsibility. Totally a roku thing to do.. LOL If you use the blue neon roku app, it has a setting for maximum retries, this can be set as high as 99. This will attempt to work through errors endlessly until the count is met, so use a number as ridiculous as 99... but with the caveat it might mean alot of the same error dialogs just pop up in a row 99 times and you have to press OK to clear them 99 times. Who knows what might happen??!.. but you can find out by changing that retry value up as high as it goes. The blue neon app still uses the old roku SDK framework, uses a different video node to spawn the video player within, so sometimes that slight difference means something. Other times it means absolutely nothing. Your mileage may vary, absolutely no warranty of fitness implied explicitly or implicitly. Let me know if you need explaining on anything blue neon related. Edited October 31, 2017 by speechles Link to comment Share on other sites More sharing options...
bmhanson 1 Posted October 31, 2017 Share Posted October 31, 2017 Thanks. Hopefully this can be resolved with the official app, but I have downloaded blue neon to test just in case. I will be keeping a closer eye on the server as well if it happens again to see if i can correlate it to anything. Link to comment Share on other sites More sharing options...
bmhanson 1 Posted November 3, 2017 Share Posted November 3, 2017 Ok. Just to close this out I believe the issue has been resolved and as reported does appear to be a server issue vs an Emby one. I will not know for sure if my issue is settled till I run for a while. I actually found this Tuesday but did not get a chance to post. For the curious my heatsink fan died and the system was getting kinda toasty. CPU temp was getting over 70 degrees celsius at idle. Needless to say I shut it down till I got the replacement fan. Now I am back to just over 20 degrees celsius at idle. I have not load tested it yet. Moral of the story folks, don't forget to check your hardware monitor if you are having weird, unexplainable issues. 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