Page 2 of 2

Re: DGDecodeNV <=> DGDecodeIM Different Frame On Same ID

Posted: Wed Apr 01, 2015 2:42 pm
by nixo
Hi,

Thank you for this. I've been testing the x86 .dll with Avisynth+ and haven't had any issues.

Re: DGDecodeNV <=> DGDecodeIM Different Frame On Same ID

Posted: Wed Apr 01, 2015 3:09 pm
by admin
Great to hear, nixo, thank you for your test results. VPP support is going fine and you'll have deinterlacing, etc., soon.

Re: DGDecodeNV <=> DGDecodeIM Different Frame On Same ID

Posted: Thu Apr 02, 2015 9:20 am
by admin
I successfully implemented the VPP, however, when I enable deinterlacing RunFrameVPPAsync() returns an error that crashes everything. It happens with the out-of-the-box sample code also. I have posted a query about this at the Intel forum, and hopefully a solution will be forthcoming.

Re: DGDecodeNV <=> DGDecodeIM Different Frame On Same ID

Posted: Fri Apr 03, 2015 6:45 pm
by admin
Oy, I thought things were looking up for Intel support but after their reply, I am having doubts again. OK, let's wait to see what "the team" says, but my experience is that when you get a reply like that, you're not going to hear from them again any time soon. I hope they prove me wrong about that! Sometimes it's good to be wrong. :P

Re: DGDecodeNV <=> DGDecodeIM Different Frame On Same ID

Posted: Tue Apr 07, 2015 11:00 am
by admin
It doesn't look good for getting VPP functionality working any time soon, due to lack of Intel support. So I have linked b50 as the release version. I'm marking this thread as RESOLVED, however, because the mismatch with DGDecNV has been resolved.