search

cporrasa / xy-vsfilter

Automatically exported from code.google.com/p/xy-vsfilter
0 stars 0 forks source link

Crash on certain script #176

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
(Issue originally from 
http://forum.doom9.org/showthread.php?p=1657057#post1657057)

What steps will reproduce the problem?
1. Play the video clip from the link using xy-Vsfilter or XySubFilter
2. MPC-HC will crashat certain point (black wall of text)

What is the expected output? What do you see instead?
A wall of text (blurred a bit) on black background. It doesn't crash when using 
MPC-HC's ISR

What version of the product are you using? On what operating system?
MPC-HC/xy-Vsfilter included with CCCP 2013-11-27. Windows 7 x64

Link to the video clip:
http://www.mediafire.com/download/n1f05xpa3fobvq8/madVR+Crash+Resources.zip

Original issue reported on code.google.com by ratei.th...@gmail.com on 18 Dec 2013 at 8:29

GoogleCodeExporter commented 8 years ago 
This crash occurs because of a failure in the GDI32 backend (i.e. Microsoft 
bug) when GetTextExtentPoint32W is requested for Myriad Pro at 300pt.

This crash will be fixed in our next release, but unfortunately the black 
opaque boxes which trigger this GDI32 failure cannot be rendered. Libass is 
able to render the black opaque boxes, but the positions are completely 
incorrect. That said, since no ASS subtitle render is capable of rendering this 
typesetting 100% correctly, I'd consider this script broken.

What appears to have happened here, is someone used the "Resample Resolution" 
function in Aegisub to resize the original 704x396 typesetting to 1280x720, 
without actually testing the end result.

Original comment by cyber.sp...@gmail.com on 8 Feb 2014 at 3:06

GoogleCodeExporter commented 8 years ago 
Unfortunately, the commits which fixed this issue had to be backed out shortly 
before Beta2 because they were causing crashes in other samples. I had hoped to 
have them resolved before pushing out Beta2, but this wasn't possible because 
of lack of time. This issue should truly be fixed by the time we release Beta3.

Original comment by cyber.sp...@gmail.com on 8 Mar 2014 at 11:16

GoogleCodeExporter commented 8 years ago 
Issue 194 has been merged into this issue.

Original comment by cyber.sp...@gmail.com on 14 Feb 2015 at 10:19