You are not logged in or registered. Please login or register to use the full functionality of this board...
Forum Home
Intel Quicksync issue - Printable Version

+- Forum Home (http://shark007.net/forum)
+-- Forum: Forum Listing (/Forum-Forum-Listing)
+--- Forum: Win7codecs (/Forum-Win7codecs)
+--- Thread: Intel Quicksync issue (/Thread-Intel-Quicksync-issue)



Intel Quicksync issue - networkguy66 - 02-19-2012 08:52 AM

Hey guys/Shark-

(Shark, ty for your help in my previous thread. Issue solved.)

My new issue is...Ive got my codecs set to use Intel Quicksync for H264 playback via ffdshow on my HTPC. It works...but only with one movie. For example, I'll start the movie, and hover my mouse over the ffdshow icon in my tray and see thats its being decoded via quicksync. However, after the movie is done, and I fire up another movie, it shows decoding via libavcodec. I'll stop the movie, open up sharkcodec with admin privileges, open up the ffdshow video settings, and sure enough Intel Quicksync is showing. I'll change it to libavcodec, save, change it back to Intel Quicksync, save, then exit. Restart the movie and it now shows Intel Quicksync in the ffdshow icon again.

I sas last night theres a new update to the codec pack, so Im using the version just before the newest one (from last week).

Any ideas?


RE: Intel Quicksync issue - Shark007 - 02-19-2012 08:59 AM

Intel QuickSync is a Work in Progress.
FFDshow and LAV both use the same decoder for QuickSync.

The latest release also has an updated QuickSync decoder.
The next version will have an even newer decoder than the last.
Please install the latest revisions before asking for assistance for something that MAY be resolved already.

the LAV decoder also has a QuickSync option that you can select under hardware acceleration.

Bottomline, there is nothing I can do to improve QuickSync decoding. I didnt write the codec.
Installing current releases is your best bet towards a resolution.


RE: Intel Quicksync issue - networkguy66 - 02-19-2012 09:02 AM

(02-19-2012 08:59 AM)Shark007 Wrote:  Intel QuickSync is a Work in Progress.
FFDshow and LAV both use the same decoder for QuickSync.

The latest release also has an updated QuickSync decoder.
The next version will have an even newer decoder than the last.
Please install the latest revisions before asking for assistance for something that MAY be resolved already.

the LAV decoder also has a QuickSync option that you can select under hardware acceleration.

Bottomline, there is nothing I can do to improve QuickSync decoding. I didnt write the codec.
Installing current releases is your best bet towards a resolution.

Thanks Shark...somehow I knew that would be the answer lol. Since Ive got everything all set up properly (except this issue) is there a problem with saving my setting, uninstalling current version, installing newest version, then restoring settings?


RE: Intel Quicksync issue - Shark007 - 02-19-2012 09:06 AM

The Save/Restore settings feature is currently broken.
It is a huge undertaking to fix. i estimate 8-12hrs of continous prgramming to fix it.
I do not have the time to dedicate to this single feature at this time.

Installation of a new version will currently reset to defaults.
Once I fix the Save/Restore feature, you'll be asked if wish to restore or reset defaults.


RE: Intel Quicksync issue - networkguy66 - 02-19-2012 09:15 AM

(02-19-2012 09:06 AM)Shark007 Wrote:  The Save/Restore settings feature is currently broken.
It is a huge undertaking to fix. i estimate 8-12hrs of continous prgramming to fix it.
I do not have the time to dedicate to this single feature at this time.

Installation of a new version will currently reset to defaults.
Once I fix the Save/Restore feature, you'll be asked if wish to restore or reset defaults.

Oh! I didnt know that. OK no problem. Thanks again.


RE: Intel Quicksync issue - McoreD - 02-20-2012 06:53 AM

(02-19-2012 09:06 AM)Shark007 Wrote:  The Save/Restore settings feature is currently broken.
It is a huge undertaking to fix. i estimate 8-12hrs of continous prgramming to fix it.
I do not have the time to dedicate to this single feature at this time.

It would have been a Zero Time issue if the program was written in C# for example. I would be more than happy to help write one if you ever decide to go down that path.