Jump to content


Photo

Playback of one title causing Emby server to freeze up.

playback freeze

Best Answer softworkz , 05 July 2019 - 07:47 PM

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

Go to the full post


  • Please log in to reply
41 replies to this topic

#21 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 05:58 AM

Posted 28 June 2019 - 09:46 PM

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



#22 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 04:19 PM

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. 

Attached Files



#23 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 16166 posts
  • Local time: 08:58 PM
  • LocationWashington State

Posted 05 July 2019 - 04:27 PM

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, 05 July 2019 - 04:30 PM.


#24 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140105 posts
  • Local time: 11:58 PM

Posted 05 July 2019 - 04:37 PM

Did you make sure to reboot?

#25 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 04:39 PM

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? 



#26 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 16166 posts
  • Local time: 08:58 PM
  • LocationWashington State

Posted 05 July 2019 - 04:41 PM

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, 05 July 2019 - 04:43 PM.


#27 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140105 posts
  • Local time: 11:58 PM

Posted 05 July 2019 - 04:42 PM

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

#28 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 05:01 PM

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. 

Attached Files



#29 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 05:58 AM

Posted 05 July 2019 - 05:30 PM

@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, 05 July 2019 - 05:30 PM.


#30 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 16166 posts
  • Local time: 08:58 PM
  • LocationWashington State

Posted 05 July 2019 - 05:40 PM

Logs show some the info.

	Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1
	64-Bit OS: True
	64-Bit Process: True


#31 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 05:42 PM

@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

Attached Files



#32 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 16166 posts
  • Local time: 08:58 PM
  • LocationWashington State

Posted 05 July 2019 - 05:49 PM

Looks like it would be Intel® HD Graphics 2500

 

https://ark.intel.co...e-2-80-ghz.html

 

Driver update

https://www.intel.co...phics-2500.html



#33 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 05:54 PM

Looks like it would be Intel® HD Graphics 2500

 

https://ark.intel.co...e-2-80-ghz.html

 

Driver update

https://www.intel.co...phics-2500.html

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

Attached Files



#34 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 05:58 AM

Posted 05 July 2019 - 06:14 PM

@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-soft...om/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

 

 

 

 



#35 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 07:14 PM

Well I'm not sure what happened there...Attached File  Screenshot.jpg   73.73KB   1 downloads



#36 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 05:58 AM

Posted 05 July 2019 - 07:18 PM

Well I'm not sure what happened there...attachicon.gifScreenshot.jpg

 

You need to use the leftmost box for the search string...



#37 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 07:20 PM

I did it again using the Windows file explorer. Here's what I got. 

Attached Files



#38 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 07:23 PM

Well don't I just feel like a horse's rear end.

Attached Files



#39 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1863 posts
  • Local time: 05:58 AM

Posted 05 July 2019 - 07:47 PM   Best Answer

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


  • ebr likes this

#40 jeflatt OFFLINE  

jeflatt

    Advanced Member

  • Members
  • 66 posts
  • Local time: 12:58 AM

Posted 05 July 2019 - 07:56 PM

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. 







Also tagged with one or more of these keywords: playback, freeze

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users