Loading of UUEncoded fonts from ASS files is fixed.

As noted, MPC-HC's internal subtitle renderer should be used instead in case you play such files. These also remove the A (ANSI/non-unicode code page) Windows API usage, which also breaks non-unicode subtitle parsing.

Various ASS parsing improvements by Plorkyeran.

Various fixes included in the updated FFmpeg.

FFmpeg used in LAV now uses native win32 threads instead of a pthreads wrapper.

LAV Video can now use the Media Foundation WMV9 decoder instead of the old DMO decoder.

LAV Video now supports VP7 video (for the two of you out there with samples).

PGS subpicture parsing improved in LAV Splitter.

Minor fixes and improvements in general.

UI language selection has been moved to the options in MPC-HC.

The Play→Filters filter listing can now be easily copied to the clipboard, there is now a button for that in the top of the listing.

This is one of the oldest standing bugs there were regarding the ISR, and we all thank kasper93 for the effort he put into fixing this after Daemon404 successfully trolled people regarding it.

Anamorphic ASS is now handled correctly in the internal subtitle renderer.

MPC-HC no longer crashes during quick seeks with PGS subpictures when the internal subtitle renderer was used.Or you can reduce the HW acceleration of the primary graphics card, which will also force the player to software rendering, but on all screens. Workarounds are to make the DisplayLink adapter primary (as you have found) because then the application reads the DisplayLink level of HW acceleration and drops back to software rendering. This means that when you open the player, it will assume that it has full hardware acceleration, and then fail to work when you drag to a DisplayLink screen, as it doesn't drop back to not using hardware acceleration. We correctly report the level of hardware acceleration we support, however many applications check the hardware acceleration level of the primary display, or the display that the application starts on, and then assume that all other displays have the same HW acceleration. This is because we are a just a software based graphics card on Windows XP, so cannot use hardware acceleration. This is due to the DisplayLink screens not supporting hardware acceleration on Windows XP.

Cccp project net