Jump to content

Playback of one title causing Emby server to freeze up.


jeflatt
Go to solution Solved by softworkz,

Recommended Posts

Happy2Play

Still having the same issue with Gran Torino though. (this is the only movie which has this issue still).

 

Are you saying you have other VC1 content with PSG subtitles that plays fine with HWA?  Could it just be a encoding issue on this items?

Edited by Happy2Play
Link to comment
Share on other sites

It might mean that your gpu doesn't support the features that we are using although @@softworkz can provide more insight. Thanks.

Link to comment
Share on other sites

jeflatt

Are you saying you have other VC1 content with PSG subtitles that plays fine with HWA?  Could it just be a encoding issue on this items?

Well now it gets interesting. Yes and no. I just ripped 2 movies that came in a package together as a "double feature". Both movies are VC1 with PGS subtitles. One played fine, the other caused the freeze up. 

EmbyServer.txt

ffmpeg-transcode-failed.txt

ffmpeg-transcode-succeeded.txt

Link to comment
Share on other sites

@jeflat - it seems your graphics driver hasn't changed

 

  • What is your exact CPU model?
  • What OS version?
  • 32bit or 64bit Windows?
  • What's your Intel drivers version?
    • Open Device Manager
    • Under "Display Adapters", what's the full name of the "Intel HD Graphics...."
    • Right click and select "Properties"
    • Switch to the "Driver" tab
    • Create screenshot and post it

Thanks

Edited by softworkz
Link to comment
Share on other sites

Happy2Play

Logs show some the info.

	Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1
	64-Bit OS: True
	64-Bit Process: True
Link to comment
Share on other sites

jeflatt

@jeflat - it seems your graphics driver hasn't changed

 

  • What is your exact CPU model?
  • What OS version?
  • 32bit or 64bit Windows?
  • What's your Intel drivers version?
    • Open Device Manager
    • Under "Display Adapters", what's the full name of the "Intel HD Graphics...."
    • Right click and select "Properties"
    • Switch to the "Driver" tab
    • Create screenshot and post it

Thanks

post-1770-0-30773800-1562362916_thumb.jpg

Link to comment
Share on other sites

Happy2Play
jeflatt

That's what is installed now. That's the update I did when it was mentioned that my driver was out of date. 

post-1770-0-92123400-1562363685_thumb.jpg

Link to comment
Share on other sites

@@jeflatt - Thanks for posting the info. You're driver is actually "new enough" from looking at the driver date. 

 

It's possible though, that Intel hasn't fixed the known issue in case of your specific driver as your CPU is quite a bit old.

 

Another possibility is that the driver installation/update didn't work out as it should have.

 

To check this, you could do the following:

 

  • Download https://www.jam-software.com/ultrasearch/
    It's the fastest file search I know and it's 100% reliable as it doesn't use indexing
    .
  • Select your system drive
    .
  • Uncheck "Use Exclude Filter"
    .
  • Search for this: *mfx*hw*.dll
    .
  • After searching is done, sort by 'Path'
    ,
  • Right-click column headers and add column 'File Version'
    .
  • Post a screenshot

 

To make it a little easier, here's the result of that procedure on my system:

 

5d1fcbbb28ac7_usearch.jpg

 

 

 

 

Link to comment
Share on other sites

  • Solution

Thanks for your patience. With the information you provided I was able to put the puzzle together.

 

Unfortunately I don't have good news for you.

 

With the information you provided I could verify that those dlls on your system are the "right" ones, meaning those bundled with the driver package.

I verified this by downloading the exact same driver package that you're using (18.33.48.5069, Driver version 10.18.10.5069).

 

Even tough the driver had been released in May 2019, the "included QuickSync" is in fact quite outdated - probably because the Intel GPU is not compatible with later versions.

 

You can see that the included "QuickSync dll" (I call it like that for simplicity) is from 2015, Media SDK version 5.x:

 

5d1fe0c9be752_quicksync_1_11.jpg

 

 

In case there's still any doubt about whether it might be a mistake, you just need to look at the signatures of the file:

 

5d1fe11278e50_quicksync_1_11b.jpg

 

The dll was originally signed in 2015 and signed in January 2019 for inclusion in the driver package.

 

 

 

Conclusion

 

I'm afraid, but there's nothing we can do in this case..

  • Like 1
Link to comment
Share on other sites

jeflatt

I should be the one thanking you for your patience. Looks like I need to start thinking about upgrading some of the hardware in my computer. 

Link to comment
Share on other sites

Happy2Play

@@jeflatt
 
Do you still have a issue if you disable VC1 Decoding?
 
Dashboard-Transcoding "Enable hardware acceleration when available: Advanced"

  • Like 1
Link to comment
Share on other sites

jeflatt

No! I checked all the boxes except the two VC-1 options, and the movie plays now. Thanks for the suggestion.

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...