MVCsource v3.0.0 – 3D MVC/AVC/VC-1/MPEG2 Avisynth Source Plugin (Intel Quick Sync)

[pistacho]

Originally Posted by Nico8583

Hi, another question : have you tried your plugin with a new Intel CPU and last Intel Media SDK ? It seems there are bugs with new Intel CPU and hardware acceleration, for example with Intel Haswell Refesh (Core I5 4590S), if we use the lastest Intel Media SDK. We don't know if it's a problem with our decoder or with Intel DLL.
Thanks !

Hi,

I not tested with new hardware but currently are testing with latest Intel HD Graphics drivers and I found a new bug: image corruption (artifacts) on MVC view only. Also I test new driver with old "libmfxhw32.dll" (from old drivers) and corruption are gone.

Seems that culprit of bug is new "libmfxhw32.dll" included with new drivers. Also seems that important changes exists due different file sizes: version 5.14.7.25 (new) has 7.93 MB and old 16.7 MB!

Fortunately I have found a way to fix it and the next version of MVCsource be compatible with the new drivers

Also I have seen the new version consumes less CPU in benchmarks (from 12% downs to 8-5%) in general seems that new drivers has less preprocessing overhead but are more "sensitive" in terms of little variation of input format (are less "robust").

I have also done a new test with Pacific Rim and surprising has gone well! (no glitches or audio out of sync) but still do not know if it's due to the new drivers or the changes I've introduced latest in MVCsource. I need do more tests...

[Nico8583]

Thanks for your response.
If anyone on this thread with a new Intel CPU can post a feedback it could be perfect
Very well for Pacific Rim have you tried without HW acceleration ? I would like to know if it works with SW decode.
Thanks !

[pistacho]

Originally Posted by Nico8583

have you tried without HW acceleration ? I would like to know if it works with SW decode.
Thanks !

Confirmed: Pacific Rim now decodes OK on HW using latest Intel Graphics drivers + latest MVCsource v2.2.2

https://downloadcenter.intel.com/Det...pa&ProdId=3712

Unfortunately, SW decoding has the same problems as before (no glitch but some frames missing -> audio out of sync)

EDIT (Only for clarification PR issues):
- Old Intel drivers + New MVCsouce = Bad decoding
- New Intel drivers + Old MVCsource = Bad decoding
- New Intel drivers + New MVCsource = OK
- SW decoding + New MVCsource = Bad decoding

[pistacho]

Version 2.2.2 (10/25/2014)

• Fixed: Possible image corruption (artifacts on MVC view) using Quick Sync acceleration and latest Intel Graphics drivers 15.33.xx.39xx

[Nico8583]

Thanks for explanation. So the only way to encode Pacific Rim correctly is to get an Intel CPU with HW acceleration, but mine is an AMD

[Nico8583]

Could you explain "the way to fix it", how and why is it necessary to fix ? Also is it necessary to change plugin source code when Intel update SDK or functions/calls are identical and replace with new dll is sufficient ? Thanks !

[pistacho]

Good news for Pacific Rim maniacs:

Version 2.2.3 (11/07/2014)

 - Fixed all Pacific Rim 3D decoding issues (SW mode and HW mode).
 - Full compatible with latest Intel HD Graphics driver’s series.
 - Slightly reduced CPU usage and memory usage (CPU usage downs from 12% to 8% in benchmarks: AVSMeter, HW mode, latest Intel drivers).

Release in progress...

EDIT: Done!

[pistacho]

Version 2.2.4 (11/20/2014)

 - Upgraded to Visual Studio 2013 (no functional changes).

Updated benchmark on first post.

[Nico8583]

Could you explain us the solution for Pacific Rim ? It could be important for FRIM or DGMVCSource...
Thanks !

[frank]

Simple use latest Intel gfx drivers and libmfxsw32.dll (2014/09/14) from Intel INDE2015 / Media SDK 2015.

Pistacho, it is not a fine way to ignore questions at Doom9's forum.

[pistacho]

The problem is that FRIMsource and DGMVCsource not work well with all drivers (with drivers 2 months ago NOT sure).

The funny thing is that everyone said:
- Oh! Last Intel drivers are buggy

Instead of saying:
- Oh! FRIM and DGMVC are buggy

Then the solution you say:

1. Two months ago it was not possible
2. I do not think it will work well for everyone

EDIT:

Originally Posted by frank

Pistacho, it is not a fine way to ignore questions at Doom9's forum.

I think it was evident that the solution was in the drivers:

Originally Posted by pistacho

(Only for clarification PR issues):
- Old Intel drivers + New MVCsouce = Bad decoding
- New Intel drivers + Old MVCsource = Bad decoding
- New Intel drivers + New MVCsource = OK
- SW decoding + New MVCsource = Bad decoding

[Nico8583]

Hi,
r0lZ has found a new bug with Intel Decoder and "Flying Swords of Dragon Gate" movie. At 1:23:35 there is a decoding bug similar to Pacific Rim bug. If you have this ISO you can try it with your decoder.

[pistacho]

Originally Posted by Nico8583

Hi,
r0lZ has found a new bug with Intel Decoder and "Flying Swords of Dragon Gate" movie. At 1:23:35 there is a decoding bug similar to Pacific Rim bug. If you have this ISO you can try it with your decoder.

I not have this BD but if uploads a sample fragment, I can test.

[Nico8583]

Hi,
Thank you but r0lZ has already tried this BD and it works fine for glitches issues with your DLL but now DG and videofan3d have released their updated DLL so we are using it.
However, r0lZ and frank seem to have found few bugs with your DLL, you could find more informations at DG's forum...

[pistacho]

Originally Posted by Nico8583

Hi,
Thank you but r0lZ has already tried this BD and it works fine for glitches issues with your DLL but now DG and videofan3d have released their updated DLL so we are using it.
However, r0lZ and frank seem to have found few bugs with your DLL, you could find more informations at DG's forum...

Thanks, but seems that these (supposed) bugs are not affecting to BDtoAVCHD...

In addition much of the talk in this thread is totally FALSE, e.g.:

...It installs a lot of things, including DirectShow codecs, and it makes hundreds of changes in the registry...

But I have NO desire to discuss this or explain...

[pistacho]

Version 2.4.0 (03/20/2015)

• Updated to Intel Media SDK 2015 Update 1 (no functional changes).

[Nico8583]

No problem, but the left/right swap bug after 65536 frames could be a problem ?!

[pistacho]

This also occurs inside BDtoAVCHD? (All movies has more than 65536 frames)

Please, post more details: command line used, Avisynth version, source used, etc. to reproduce this.

[Nico8583]

I don't have tested myself, sorry, I'm here only to tell you. Contact frank, results are from him.

[pistacho]

Version 2.4.3 (06/13/2015)

• Updated with Avisynth headers v6, due this, older Avisynth versions (2.5.8) are no longer compatible ***is now required Avisynth v2.6.0***.