Jump to content

Playback of one title causing Emby server to freeze up.


jeflatt
Go to solution Solved by softworkz,

Recommended Posts

jeflatt

I just purchased Gran Torino (2008) on blu ray, and ripped the movie to my server as a .mkv file using MakeMKV. The file plays without issue on VLC media player. When I try to play the movie on Emby, however, the server freezes up. I originally tried playing the movie on the Roku app (beta version and regular), and the Retrieving purple bar would fill about 1/3 of the way and then just hang forever (I let it go about 5 minutes). So I thought it might be the Emby Roku app, so I tried again with the Chrome browser web app, and the say thing happened. Only instead of the purple bar, the web app has a spinning circle that just goes on and on. I thought there might be something wrong with the file, so I deleted the entire folder, emptied the recycle bin, and rebooted the computer. Then ripped the file again. No difference. This is the only movie that has this problem. Others play just fine. My computer is running Windows 7.

Log Jeflatt 6-6-2019.txt

Link to comment
Share on other sites

Hi there, can you please attach the emby server log as well? Also what is your G: drive?

Link to comment
Share on other sites

jeflatt

I did attach the server log in the original message. If what I attached isn't correct, then I'm not sure what you're looking for, That was the log from the last time the event occurred. If you're looking for something different, you'll need to be more specific. I need the Idiot's Guide version.  :)

 

My G: Drive is my external RAID system where I store all of my movies/TV shows. It's a 5 disk (10TB each), RAID 5 system connected to my server computer through a USB 3.0 port.

Link to comment
Share on other sites

Hi, that is the ffmpeg transcoding log. Next to that will be the main emby server log. can you supply that as well? Thanks.

Link to comment
Share on other sites

jeflatt

I grabbed all the log files out of there. Hopefully that will have what you're looking for.

 

On another note, I had another problem start up in just the last few days. It seems like 1 in 3 movies I watch won't play fully. They play for some time and then just stop for no reason. Some for an hour, some for a few minutes, some just don't start at all. And these are all movies I've watched on here previously without any issues. Not sure if any of those are captured in the logs there as well.

Emby Server Log.txt

Emby Server Log 2.txt

ffmpeg Log1.txt

Hardware Detection Log.txt

Link to comment
Share on other sites

@@jeflatt, as a test, if you disable hardware acceleration in server transcoding settings, does that have an impact?

  • Like 1
Link to comment
Share on other sites

jeflatt

It does have an impact! The movie played just like it's supposed to. Well at least for as much as I watched. I haven't sat through the whole thing yet, but the first few minutes played just fine. 

I'm still having the issue with certain titles just stopping themselves at certain times. I have figured out at the very least that that is a Roku app issue, as the movies play just fine through the Chrome browser. I should probably start a new topic in the Roku forums for that now though.

Link to comment
Share on other sites

Regarding hardware acceleration, if you'd like to try turning it back on, I would suggest installing the latest drivers first, making sure windows is fully up to date, and then rebooting your machine. Then see if that helps.

 

@@softworkz may also have some insight. Thanks.

Link to comment
Share on other sites

jeflatt

@jefflat - did you shorten or truncate the ffmpeg logs that you've posted?

No. At least not intentionally. I selected the log, which displayed the text in a new Chrome tab. Then I right-clicked and selected Save-As. The only save option was a .txt file. That's it. Unless that process somehow truncated the log without me realizing it, you got the whole thing.

Link to comment
Share on other sites

I've just been wondering because that truncation looks more like a crash. (ffmpeg log in post #5).

At least it does not match the description "plays for a while then freezes".

 

Please note that Emby sometimes creates multiple ffmpeg logs per playback attempt (unfortunately), so it might be better just to look at the creation dates of the log files and zip all the recent ones up after you've encountered the problem.

Link to comment
Share on other sites

jeflatt

@@softworkz Sorry if there was any confusion, but it never played. It would just freeze/crash during the loading process. Never got to the first frame.

Link to comment
Share on other sites

@@softworkz Sorry if there was any confusion, but it never played. It would just freeze/crash during the loading process. Never got to the first frame.

 

[...]. It seems like 1 in 3 movies I watch won't play fully. They play for some time and then just stop for no reason. Some for an hour, some for a few minutes, [...]

 

I'm afraid, but now I'm _really_ confused...

Link to comment
Share on other sites

jeflatt

Yes, yes, my bad. I was having two issues. The first one Luke took care of, and that's what the logs I attached were about. The second one is limited to just the Roku app. I'm attaching new logs for that one here. I played one movie that stops immediately after loading. Then played it again. Then I played a different movie that stops after 2:29. And I played that one again as well, again stopping at 2:29. I've noticed this happening on several movies, but those two are the quickest to stop so I chose those for the logs.

embyserver.txt

hardware_detection-63695974147.txt

hardware_detection-63695974148.txt

Link to comment
Share on other sites

 

 I'm attaching new logs for that one here.

  1. I played one movie that stops immediately after loading.
  2. Then played it again.
  3. Then I played a different movie that stops after 2:29.
  4. And I played that one again as well, again stopping at 2:29. 

 

 

Could we start over with:

  • ONE problem
  • ONE problem description (expected/actual behavior)
  • ONE ffmpeg log (covering exactly the described situation)

    (or multiple in case multiple ones were created at the same time)

PS: HW detection log is constant, no need to resend. 

Link to comment
Share on other sites

jeflatt

I'm very sorry about the confusion. I only mentioned the second issue "in passing", and said that I needed to start a new topic in the Roku forums to address that issue specifically. I just hadn't done it yet before you started looking into it on this thread. I'll get it done right now.

Link to comment
Share on other sites

Ok so this issue is all set which we isolated to hardware acceleration. Were you going to try what i mentioned earlier?

Link to comment
Share on other sites

  • 2 weeks later...
jeflatt

@@Luke

 

I did try that. I have Windows set to automatically update, so there were no updates to install there. I also checked all the drivers through the Control Panel, with Windows saying that I was using the most current driver. I have not yet gone to the length to look at the specific serial numbers of every component in my computer and seeing if there is a new driver available from the manufacturer's website that perhaps Windows didn't find. That's my next step. Are there any drivers in particular I should start with? I.e. since my movies are ripped onto a hard drive, the driver for the optical drive shouldn't really play into this. 

Link to comment
Share on other sites

Video card drivers are what i would start with. Let us know how you get on. Thanks.

Link to comment
Share on other sites

@@Luke

 

I did try that. I have Windows set to automatically update, so there were no updates to install there. I also checked all the drivers through the Control Panel, with Windows saying that I was using the most current driver. I have not yet gone to the length to look at the specific serial numbers of every component in my computer and seeing if there is a new driver available from the manufacturer's website that perhaps Windows didn't find. That's my next step. Are there any drivers in particular I should start with? I.e. since my movies are ripped onto a hard drive, the driver for the optical drive shouldn't really play into this. 

 

I took another look at the hw detection log:

"Message": "Initialize MFX session: API version is 1.27, implementation version is 1.11"

Your graphics driver is in fact quite outdated. Go to the Intel website and look for the latest driver for your GPU/CPU.

No need to look at any other drivers.

Link to comment
Share on other sites

jeflatt

My video driver was out of date, but it is up to date now. I used the Intel auto-detection software to check all my Intel related drivers, and they are all up to date now. Still having the same issue with Gran Torino though. (this is the only movie which has this issue still) Here are the latest logs from trying to play it. 

 

The movie did play fine with the hardware acceleration turned off, if I hadn't mentioned it before. 

EmbyServer.txt

ffmpeg-transcode.txt

Hardware-Detection.txt

Link to comment
Share on other sites

Happy2Play

It would appear there was not change when updating the driver then.

"Message": "Initialize MFX session: API version is 1.27, implementation version is 1.11"

The movie did play fine with the hardware acceleration turned off, if I hadn't mentioned it before.

​So is it a hardware and/or driver limitation?

Edited by Happy2Play
Link to comment
Share on other sites

jeflatt

Did you make sure to reboot?

Yes, I've rebooted several times. I'm not familiar with what the "API version" means. Is there something that I'm missing on updating my drivers? 

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...