This is what it should look like in the end (works only on EVR normal) )ĭefault Telecine works perfect even on EVR Custom :) Though the correct telecine to 24.30 (evil_tree Mpeg-2 1080i 29.970 sample) is problematic also with it on EVR it does 0.30 fps to much it seems (interlace flags off) :( This is the most awesome Decoder for Quicksync currently (except overhead being not DXVA2 Native is huuuge depending on stream see here after bugs ) :) Perfect awesome it doesn't allow Mpeg-2 Studio Profile connection and so fallbacks like it should be :) Superb news my sample.ts (H.264) (EVR Custom) issue is history with this, perfect telecined 23.976 :) PS: You should mention that it's 32 Bit in your post ) I tried alot but i don't get it stable with EVR and Intels Decoder (it doesn't matter which splitter the tree pan doesn't get smooth hardware decoded also with Microsofts DTV-Decoder no go, the only solution for this sample is the Lav based Framework on EVR it gets perfectly smooth then perfectly telecined)Īnd then there is my issue with my sample.ts (also telecined though H.264) on EVR custom but im not so sure if this is a Intel fault though Software decoding again works fine but Hardware fails with EVR Custom see a Video of this issue (Btw made with Quicksync ) ) <- Fixed with FFdshow for Quicksync :) Though it's cool that you (Intel) now also want to optimize based on samples like Nvidia did in the early days :)įirst thing you should look this sample Of course it looks totally different for H.264 (there is the biggest save compared to the Worlds most Performant Software Decoders, but again if we come to the 10 Bit 4:2:2 and 4:4:4 or Lossless area everything fals apart again)īut also VC-1 im not sure at least WMV3 seems not to perform much better on Quicksync then again Libavcodecs decoder on the CPU :)Ī follow up on that terminating overhead further Nice work Eric though i guess it wont do any better then Intels own Decoder sample in IMSDK 3 least for Mpeg-2 it seems questionable if the hassle with different setups is worth it from my meassuring it saves somewhere 1W on my Core I5-2400 compared to ffmpegs decoder, though you will have all the hassle with Mpeg-2 Studio 4:2:2 switching as the Intel Decoder is same as Nvidias also not capable of doing this with DXVA :) * For the latest cutting edge FFDShow builds download my builds Intel QuickSync Decoder SourceForge home page () May break a broken clip or two but save many others. * Changed: AnnexB type packets (AVC in TS files) is not pre-processed and sent to the HW decoder directly. * Bugfix - time stamps handling was causing A/V delay. * Bugfix - time stamps are passed 'as is' when TS manipulation is off. * Bugfix - frames were sometime treated as interlaced. Version 0.45 is out with the following changes: Open FFDShow configuration dialog and select 'Intel Quicksync' from the codec page for the desired formats (H264/VC1/MPEG2). * Resolutions greater than 1080p aren't supported in SandyBridge.Ģ. * After a seek in a TS file, a corruption is seen for a few frames. * Frame rate is wrong or incorrect aspect ratio: Haali Media Splitter is sending corrupt time stamps or aspect ratio. Some versions of Lucid Virtu will cause video playback in 64 bit player to display frames out of order. Download drivers from your OEM website or directly from Intel's download center (). * Jumpy playback or heavy corruption on many clips are the result of drivers obtained from Windows Update. Should work in Vista but I can't test this. Intel GPU must either be the primary GPU, extended display or use Lucid Virtu.ģ. Older platforms will not work and no plans to support them.Ģ. SandyBridge (2nd Generation Core i3/i5/i7/celeron/pentium) or newer. Share via your favorite file share sites. Software (OS, driver version, player, splitter, etc.)ģ. If something is broken, please provide me with a detailed report including (after reading the known issues section below) :Ģ. To report a bug report or feature request, please post in this thread. If your system meets the requirements, I'd appreciate stability feedback with assorted quality and sources of video content. * Support headless iGPU (Intel GPU disconnected from display) on Windows 8 and newer. * HW deinterlacing -auto or forced, with half or full (50/60p) output rate * HW decode using Intel's high performance QuickSync engine. Nowadays, the Intel QuickSync Decoder is officially integrated in FFDShow, LAV Video Decoder and PotPlayer. To do so, I decided to embed the Intel QuickSync technology introduced in SandyBridge into the widely popular FFDShow video decoder filter. The project name is Intel QuickSync Decoder. My name is Eric Gur and I've taken upon myself a side project at my Intel position to make the Intel SandyBridge (or newer) hardware accelerated video decoding technology freely accessible to everyone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |