Page 5 of 9

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 6:16 am
by r0lZ
I did also a quick test, and encoded only a few minutes of the beginning of Pacific Rim (SW decoding). No problem so far. :) I am now encoding it up to the "famous" glitch at 1:06:14, but I'm confident it will work fine. Then, I'll do another test with Flying Swords of Dragon Gate to verify the glitch at 1:23:35, but again I'm pretty sure it will work fine. I hope some peoples will test it with HW acceleration.

However, there have been reports that Pistacho's MVCSource with the latest DLLs from Intel work usually fine but fails on some specific machines (notably a Dell computer, with or without HW decoding, I don't know). That must be tested too, to be sure. But if it passes that test, your DGMVCSource will be the first fully working MVC decoder based on the Intel lib. (In addition to the problem with the Dell, we have also found 2 terrible bugs in Pistacho's MVCSource, not directly related to the Intel lib, that makes it totally unusable in practice.)

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 7:15 am
by r0lZ
Test of Pacific Rim finished. No glitches any more. Perfect with my Intel Core 2 Quad Q8200 CPU. :)
I will now do the test of Dragon Gate and I'll report the result in 3 hours or so...

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 9:54 am
by admin
Good news, guys. Thank you for your testing.
r0lZ wrote:we have also found 2 terrible bugs in Pistacho's MVCSource, not directly related to the Intel lib, that makes it totally unusable in practice.)
I'm curious to know what those bugs are.

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 10:43 am
by r0lZ
admin wrote:I'm curious to know what those bugs are.
They have been discovered by frank and confirmed by me.

1. Its avisynth plugin manipulates the PWD of avisynth (probably so that it can find the Intel lib even if it is not in the Windows PATH). Therefore, some avisynth functions do not work as expected. For example, BD3D2MK3D generates SupTitle() commands when the user wants to hardcode subtitles on the video. The subtitle is in the same directory than the AVS script and therefore its file name is specified without its path in the SupTitle() command. That allows the user to move the entire project to another disc if he thinks that it may require more disc space. That works pretty well with your DGMVCSource and with FRIMSource, but not with Pistacho's MVCSource: SupTitle() issues a warning telling that it cannot find the subtitle file. Obviously, the current directory is not where it should be when MVCSource is used.

2. When a 3DBD with inverted left and right views is converted, it is necessary to change the "mode" parameter of MVCSource to specify to invert the two views (to build a combined SBS or T&B stereo file with the views in the common order: left view first). That works well for the first 45 minutes, but after that, the views are abruptly changed, and you end up with a final movie with a mix of left and right view first! Aaargh!

And I consider also as a (sort of) bug the fact that the DLL cannot be used independently of his BDtoAVCHD program. It installs a lot of things, including DirectShow codecs, and it makes hundreds of changes in the registry. I don't think it's a good thing. But that's another story.

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 10:55 am
by admin
Interesting. Thanks for the explanation. They sound like bad bugs. Doesn't pistacho want to fix them?

Isn't FRIMSource() OK now too, in which case that would be the first. ;)

Lastly, do y'all use Avisynth 2.5.8 or does it work with later versions? In my help file I specify 2.5.8 but I can't remember why I have that there. Update: I just tested with AVS+ and things seem fine.

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 11:08 am
by r0lZ
IMO, Pistacho doesn't want to fix bug 1. He did his DLL to be used with his software and doesn't really want that others use it.
I'm not sure he knows bug 2. I will inform him later, but I want to finish the tests of your DLL first.

BTW, bad news! There is still a problem in Dragon Gate. Exactly like with the previous version. (No pixelisation on the whole movie like with your first beta, but a glitch at 1:23:35.) I have to verify thought. Perhaps I did an error and used the old version of the Intel DLL, or something like that. I have too many versions here! But I think it's really a remaining bug in the latest Intel lib. I'll confirm that later...

Currently, FRIMSource has the same bugs than your last official version. It works relatively well with old Intel libs (excepts the two bugs in Pacific Rim and Dragon Gate), but doesn't support the recent libs. I will test with the latest version of the Intel lib, distributed with your third beta. Maybe it's sufficient to solve the problem. BTW, do you think that a change in your code was necessary, or is it just a bug in the Intel DLL that has just been fixed?

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 11:18 am
by r0lZ
I use avisynth 2.5.8, and I have never tried with other versions. I don't think that avisynth is the cause of the bug.

I have edited my previous post too, to add the last paragraph.

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 11:20 am
by admin
OK, thank you.

I did not have to change any code. I just rebuilt it with INDE 2015 Update 1, and included the very latest libmfxsw32.dll.

Please keep me informed about the Dragon Gate issue. I doubt it is caused by DGMVCSource().

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 11:36 am
by r0lZ
Indeed, DGMVCDecode works most probably well with Dragon Gate. I have just verified my files, and I did an error when editing my scripts. It has used the old version of your decoder. :oops: The glitch is not surprising!
I have just relaunched the encoding, but we have to wait again 3 hours or so for the result.
Then I'll do a test with the old FRIMSource but with the new Intel lib, just to verify if it is sufficient to replace the lib. (I suppose not, because Pistacho's DLL works fine with the Intel lib that produces pixelisation with your first beta and the latest official release of your DLL. But I want to be sure...)

Re: [RESOLVED] DGMVCSource b22 and VC++2012

Posted: Tue Feb 24, 2015 11:42 am
by admin
That's good news. Waiting for your update...
r0lZ wrote: Then I'll do a test with the old FRIMSource but with the new Intel lib, just to verify if it is sufficient to replace the lib. (I suppose not, because Pistacho's DLL works fine with the Intel lib that produces pixelisation with your first beta and the latest official release of your DLL. But I want to be sure...)
I don't know for sure either, but my intuition tells me that FRIM will need to be rebuilt with INDE 2015 Update 1.