AvsPmod (x64) - Revision history

Theworm4002: /* Required Components */

2023-06-03T20:14:59Z

Required Components

← Older revision		Revision as of 22:14, 3 June 2023
Line 1:		Line 1:
	==<span style="color:green;">AvsPmod (x64)</span>==		==<span style="color:green;">AvsPmod (x64)</span>==
	===Required Components===		===Required Components===
	Download the Premade [https://mega.nz/file/~~j8lnyZSY~~#~~XxbVwnPhXva3R7SYwn8dpuDYWwdNODF9RyBt4AONEnA~~ Install and Plugin ] folder Bundle		Download the Premade [https://mega.nz/file/Gx8VWApT#hEL1aKwTbgl8lj86u9dEpHI98KVI2bHSIHun3WtKYqE Install and Plugin ] folder Bundle
	<!-- working on this -->		<!-- working on this -->

	===Setting up the environment===		===Setting up the environment===
	<ol>		<ol>

Theworm4002: /* Setting up the ExRelease extraction script */

2022-07-08T19:59:49Z

Setting up the ExRelease extraction script

← Older revision		Revision as of 21:59, 8 July 2022
Line 115:		Line 115:

	===Setting up the ExRelease extraction script ===		===Setting up the ExRelease extraction script ===
	~~'''~~This is a great tool to have working.		This is a great tool to have working.
	Unfortunately, these instructions have not yet been updated from the x86 version. If you can't figure it out just pm theworm4002. ill help you set it up.~~'''~~		Unfortunately, these instructions have not yet been updated from the x86 version. If you can't figure it out just pm theworm4002. ill help you set it up.

	<ol><li>Open Notepad or a text editor of your choice and type <tt>;</tt>.</li>		<ol><li>Open Notepad or a text editor of your choice and type <tt>;</tt>.</li>

Theworm4002: /* Setting up the ExRelease extraction script */

2022-07-08T19:59:23Z

Setting up the ExRelease extraction script

← Older revision		Revision as of 21:59, 8 July 2022
Line 115:		Line 115:

	===Setting up the ExRelease extraction script ===		===Setting up the ExRelease extraction script ===
	This is a great tool to have working.		'''This is a great tool to have working.
	Unfortunately, these instructions have not yet been updated from the x86 version. If you can't figure it out just pm theworm4002. ill help you set it up. ~~you might as well just pm to start as its much simpler with the new setup~~		Unfortunately, these instructions have not yet been updated from the x86 version. If you can't figure it out just pm theworm4002. ill help you set it up.'''

	<ol><li>Open Notepad or a text editor of your choice and type <tt>;</tt>.</li>		<ol><li>Open Notepad or a text editor of your choice and type <tt>;</tt>.</li>

Theworm4002: /* AvsPmod (x64) */

2022-07-08T19:52:19Z

AvsPmod (x64)

← Older revision		Revision as of 21:52, 8 July 2022
Line 114:		Line 114:
	<li>That's it, the extracted files (on default settings) should be in the same folder as the source files. </li></ol>		<li>That's it, the extracted files (on default settings) should be in the same folder as the source files. </li></ol>

	===Setting up the ExRelease extraction script ~~(Deprecated and Complicated)~~===		===Setting up the ExRelease extraction script ===
			This is a great tool to have working.
			Unfortunately, these instructions have not yet been updated from the x86 version. If you can't figure it out just pm theworm4002. ill help you set it up. you might as well just pm to start as its much simpler with the new setup

	<ol><li>Open Notepad or a text editor of your choice and type <tt>;</tt>.</li>		<ol><li>Open Notepad or a text editor of your choice and type <tt>;</tt>.</li>

Theworm4002 at 19:14, 8 July 2022

2022-07-08T19:14:55Z

← Older revision		Revision as of 21:14, 8 July 2022
Line 42:		Line 42:

	<tt>		<tt>
	{{:~~AvsPmod~~}}		{{:AvsPmod_(x64)_Script}}
	</tt>		</tt>

Theworm4002 at 00:27, 5 July 2022

2022-07-05T00:27:22Z

← Older revision		Revision as of 02:27, 5 July 2022
Line 4:		Line 4:
	<!-- working on this -->		<!-- working on this -->
	===Setting up the environment===		===Setting up the environment===
	<ol><li>Install ~~AviSynth~~</li>		<ol>
			<li>Unzip and open the premade [https://mega.nz/file/j8lnyZSY#XxbVwnPhXva3R7SYwn8dpuDYWwdNODF9RyBt4AONEnA Install and Plugin ] folder Bundle in Explorer. <br/>
			(should be named something like "AvsPmod_Setup_Vx.x.x.zip")</li>

	<li>Open ~~your~~ AviSynth ~~plugins~~ directory in Explorer<br />		<li>Install AviSynth+<br />
	Unless you changed the the AviSynth install location, your plugins directory should be<br />		Starting at the root of the Install and Plugin folder extracted archive, the AviSynth+ install is located <tt><span style="color:blue">AvsPmod_Setup_Vx.x.x\AvsPmod_Setup\AviSynthPlus</span></tt>.<br/>
			There should only be 2 things inside the directory: A folder named <tt><span style="color:blue">plugins64+</span></tt>, and <tt><span style="color:blue">AviSynthPlus_3.7.0_20210111_vcredist.exe</span></tt><br/>
			execute the <tt><span style="color:blue">AviSynthPlus_3.7.0_20210111_vcredist.exe</span></tt> file
			</li>

			<li>Open the newly installed AviSynth+ plugins64+ directory in a new Explorer window<br />
			Unless you changed the the AviSynth+ install location, your plugins directory should be<br />
	<span style="color:gray; font-size:80%; line-height:1em;">(enter these into your explorer location bar):</span>		<span style="color:gray; font-size:80%; line-height:1em;">(enter these into your explorer location bar):</span>
	~~<ul><li>[On 64-bit Windows]~~ <tt><span style="color:blue">%ProgramFiles(x86)%\~~AviSynth 2.5\plugins</span></tt></li>~~		<tt><span style="color:blue">%ProgramFiles(x86)\%AviSynth+\plugins64+</span></tt>
	~~<li>[On 32-bit Windows] <tt><span style="color:blue">~~%~~ProgramFiles%\~~AviSynth ~~2.5~~\~~plugins~~</span></tt~~></li></ul~~>
	There should be only 3 files inside the directory: <tt><span style="color:blue">colors_rgb.avsi</span></tt>, <tt><span style="color:blue">DirectShowSource.dll</span></tt>, <tt><span style="color:blue">TCPDeliver.dll</span></tt></li>		There should be only 3 files inside the directory: <tt><span style="color:blue">colors_rgb.avsi</span></tt>, <tt><span style="color:blue">DirectShowSource.dll</span></tt>, <tt><span style="color:blue">TCPDeliver.dll</span></tt></li>

	<li>Open the ~~Dither Avisynth Tools archive (~~<tt><span style="color:blue">~~dither-1.23.0.zip~~</span></tt>~~) and unpack the following files to your AviSynth plugin~~ directory:		<li>Open the <tt><span style="color:blue">plugins64+</span></tt> directory that's next to the AviSynthPlus_3.7.0_20210111_vcredist.exe in the install directory</li>
	~~<ul><li><tt><span style="color:blue">avstp.dll</span></tt></li>~~
	~~<li><tt><span style="color:blue">dither.avsi</span></tt></li>~~
	~~<li><tt><span style="color:blue">dither.dll</span></tt></li>~~
	~~<li><tt><span style="color:blue">mt_xxpand_multi.avsi</span></tt></li></ul>~~

	~~<span style="color:gray; font-size:80%; line-height:1em;">The docs folder inside the archive contains detailed documentation on the dither tools, so you might want to extract this~~ to ~~your AviSynth Docs directory or anywhere else you'll find it in case you need it later</span></li>~~

	~~<li>Open~~ the ~~downloaded ffms2 archive and extract the contents into your Avisynth plugin directory~~
	~~<ul><li><tt><span style="color:blue">ffms2~~.~~dll</span></tt></li>~~
	~~<li><tt><span style="color:blue">ffmsindex~~.exe~~</span></tt></li></ul></li>~~

	~~<li>Open~~ the ~~downloaded masktools archive and extract the correct <tt><span style="color:blue">masktools2.dll</span></tt> to your AviSynth plugin~~ directory~~. If on XP use the file found in the x86_xp Folder, otherwise the x86 folder's file is correct. If you're running a 64bit setup use the x64 files.~~</li>

	<li>~~Open the downloaded SupTitle archive and extract the~~ contents into your Avisynth ~~plugin~~ directory		<li>Copy contents into your Avisynth+ plugin64+ directory<br/>
	~~<ul><li><tt><span style="color:blue">msvcp100.dll</span></tt>~~</li>		Copy all the files from the <tt><span style="color:blue">AvsPmod_Setup_Vx.x.x\AvsPmod_Setup\AviSynthPlus\plugin64+</span></tt> directory to the <tt><span style="color:blue">%ProgramFiles(x86)\%AviSynth+\plugins64+</span></tt> directory</li>
	~~<li>~~<tt><span style="color:blue">~~msvcr100~~.~~dll</span></tt></li>~~
	~~<li><tt><span style="color:blue">SupCore~~.~~dll~~</span></tt>~~</li>~~
	~~<li>~~<tt><span style="color:blue">~~SupTitle.dll~~</span></tt>~~</li></ul>~~</li>

	<li>~~Open~~ the ~~downloaded AvsPmod archive and extract the <tt><span style="color:blue">AvsPmod</span></tt> folder to:~~		<li>Close the <tt><span style="color:blue">%ProgramFiles(x86)\%AviSynth+\plugins64+</span></tt> Explorer window</li>
	~~<ul><li>On 64-bit Windows:~~ <tt><span style="color:blue">%ProgramFiles(x86)%</span></tt>~~</li>~~
	~~<li>On 32-bit Windows: <tt><span style="color:blue">%ProgramFiles%</span></tt></li></ul>~~
	~~Create a shortcut to <tt><span style="color:blue">avspmod.exe</span></tt>, or pin it to the taskbar/start menu~~</li>

	<li>Copy the ~~downloaded~~ <tt><span style="color:blue">~~VSFilter~~.~~dll~~</span></tt> ~~and <span style="color:blue">FFInfoEx.avsi</span> to your Avisynth plugin~~ directory</li~~></ol~~>		<li>Copy the AvsPmod_x64 folder to your desktop <br/>
			The AvsPmod_x64 folder is located in the <tt><span style="color:blue">AvsPmod_Setup_Vx.x.x\AvsPmod_Setup</span></tt> directory
			</li>

	===Getting started with screenshot comparisons===		===Getting started with screenshot comparisons===

Theworm4002 at 20:07, 4 July 2022

2022-07-04T20:07:46Z

@@ Line 1: / Line 1: @@
 ==<span style="color:green;">AvsPmod (x64)</span>==
 ===Required Components===
-====Basic requirements====
+Download the Premade [https://mega.nz/file/j8lnyZSY#XxbVwnPhXva3R7SYwn8dpuDYWwdNODF9RyBt4AONEnA Install and Plugin ] folder Bundle
-{| class="wikitable"
+<!-- working on this -->
 ===Setting up the environment===
 <ol><li>Install AviSynth</li>
@@ Line 221: / Line 122: @@
 <li>Select the tracks you wish to extract. Then click ''Extract''</li>
 <li>That's it, the extracted files (on default settings) should be in the same folder as the source files. </li></ol>
 ===Setting up the ExRelease extraction script (Deprecated and Complicated)===
 <ol><li>Open Notepad or a text editor of your choice and type <tt>;</tt>.</li>

Theworm4002: Created page with "==AvsPmod (x64)== ===Required Components=== ====Basic requirements==== {| class="wikitable" |- ! '''Software''' ! '''Version''' ! |- | AviSy..."

2022-06-25T20:43:36Z

Created page with "==AvsPmod (x64)== ===Required Components=== ====Basic requirements==== {| class="wikitable" |- ! '''Software''' ! '''Version''' ! |- | AviSy..."

New page

==AvsPmod (x64)==
===Required Components===
====Basic requirements====
{| class="wikitable"
|-
! '''Software'''
! '''Version'''
!
|-
| AviSynth
| 2.6
| [http://sourceforge.net/projects/avisynth2/files/AviSynth_Alpha_Releases/AVS%202.6.0%20Alpha%204%20%5B130114%5D/AviSynth_130114.exe Download]
|-
| AvsPmod
| 2.5.1 (+upd. library)
| [https://github.com/AvsPmod/AvsPmod/releases Download]
|-
|Premade Plugin folder
|See below
| [https://mega.nz/file/L4syUTZL#RzM3emjacwNLg04eTMtT6b7PTM5asuLxpetgMN3MH4g Download]
|}

{| class="wikitable mw-collapsible mw-collapsed"
|-
|'''Old Plugin Links'''
|
|
|-
| Dither Avisynth Tools
| 1.23.0
| [http://ldesoras.free.fr/src/avs/dither-1.23.0.zip Download]
|-
| Masktools2
| 2.2.10
| [https://github.com/pinterf/masktools/releases/download/2.2.10/masktools2-v2.2.10.7z Download]
|-
| xy-vsfilter
| 3.0.0.232 (cccp)
| [https://github.com/Cyberbeing/xy-VSFilter/releases Download]
|-
| SUPTitle
| 2.0.8
| [http://www.zachsaw.com/?pg=suptitle_pgs_avisynth_plugin Download]
|-
| FFInfoEx
| r1
| [https://mega.nz/#!ghNk2BZL!l203Hqya2RqziIidwLKS7uDHXwetfSKQCtpp4WiOHqA Download]
|-
| assrender
| found to work better then SUPTitle in some cases
| [https://github.com/pinterf/assrender/releases/ Download]
|}

This tutorial also assumes you're running a '''fully updated Windows 7/8/10''' machine with all recent VC++ distributables, .net Frameworks and whatnot. Things probably also work on Vista/XP and you might even get them to run with Wine on Linux, but you're on your own. The H265 compatible version should work as well as the old version, however if you have problems and don't need to compare H265 then use the old one. It's also recommended to use a fully up to date ffms2 version for H265, but if you're lazy the h264-10bit compatible+H265 compatible should do the job.

Now I'm keeping the old list of plugins around, but instead this time around I'll be compiling a simple plugin archive. Simply extract it into your folder and it ''should'' work.

====Additional requirements for the subtitle extraction script====
{| class="wikitable"
|-
! '''Software'''
! '''Version'''
!
|-
| MKVToolNix
| 19.0.0
| [https://www.fosshub.com/MKVToolNix.html Download]
|}

Deprecated and Complicated extraction method:
{| class="wikitable mw-collapsible mw-collapsed"
|-
! '''Software'''
! '''Version'''
!
|-
| Windows Powershell
| 3.0
| [http://download.microsoft.com/download/E/7/6/E76850B8-DA6E-4FF5-8CCE-A24FC513FD16/Windows6.1-KB2506143-x86.msu Download (x86)] / [http://download.microsoft.com/download/E/7/6/E76850B8-DA6E-4FF5-8CCE-A24FC513FD16/Windows6.1-KB2506143-x64.msu Download (x64)]
Installed by default on Win 8, Win 7 SP1 users need to upgrade. 
No XP/Vista support.
|-
| Microsoft .NET Framework
| 4.5
| [http://download.microsoft.com/download/B/A/4/BA4A7E71-2906-4B2D-A0E1-80CF16844F5F/dotNetFx45_Full_setup.exe Download] (Prerequisite for Powershell 3)
|-
| MKVToolNix
| 6.3.0
| [http://www.downloadbestsoft.com/download/mkvtoolnix-unicode-6.3.0-1-setup.exe Download]
|-
| SIL FontUtils
| 1.00
| [http://scripts.sil.org/cms/scripts/render_download.php?format=file&media_id=TTFontUtils_1_00&filename=TTFontUtils_1_00.exe Download]
|-
| ExRelease
| 0.9.6
| [https://github.com/theworm4002/ExRelease Download]
|-
| ExRelease-Export
| 0.7
| [https://github.com/theworm4002/ExRelease-Export Download]
|}

===Setting up the environment===
<ol><li>Install AviSynth</li>

<li>Open your AviSynth plugins directory in Explorer 
Unless you changed the the AviSynth install location, your plugins directory should be 
(enter these into your explorer location bar):
<ul><li>[On 64-bit Windows] <tt>%ProgramFiles(x86)%\AviSynth 2.5\plugins</tt></li>
<li>[On 32-bit Windows] <tt>%ProgramFiles%\AviSynth 2.5\plugins</tt></li></ul>
There should be only 3 files inside the directory: <tt>colors_rgb.avsi</tt>, <tt>DirectShowSource.dll</tt>, <tt>TCPDeliver.dll</tt></li>

<li>Open the Dither Avisynth Tools archive (<tt>dither-1.23.0.zip</tt>) and unpack the following files to your AviSynth plugin directory:
<ul><li><tt>avstp.dll</tt></li>
<li><tt>dither.avsi</tt></li>
<li><tt>dither.dll</tt></li>
<li><tt>mt_xxpand_multi.avsi</tt></li></ul>

The docs folder inside the archive contains detailed documentation on the dither tools, so you might want to extract this to your AviSynth Docs directory or anywhere else you'll find it in case you need it later</li>

<li>Open the downloaded ffms2 archive and extract the contents into your Avisynth plugin directory
<ul><li><tt>ffms2.dll</tt></li>
<li><tt>ffmsindex.exe</tt></li></ul></li>

<li>Open the downloaded masktools archive and extract the correct <tt>masktools2.dll</tt> to your AviSynth plugin directory. If on XP use the file found in the x86_xp Folder, otherwise the x86 folder's file is correct. If you're running a 64bit setup use the x64 files.</li>

<li>Open the downloaded SupTitle archive and extract the contents into your Avisynth plugin directory
<ul><li><tt>msvcp100.dll</tt></li>
<li><tt>msvcr100.dll</tt></li>
<li><tt>SupCore.dll</tt></li>
<li><tt>SupTitle.dll</tt></li></ul></li>

<li>Open the downloaded AvsPmod archive and extract the <tt>AvsPmod</tt> folder to:
<ul><li>On 64-bit Windows: <tt>%ProgramFiles(x86)%</tt></li>
<li>On 32-bit Windows: <tt>%ProgramFiles%</tt></li></ul>
Create a shortcut to <tt>avspmod.exe</tt>, or pin it to the taskbar/start menu</li>

<li>Copy the downloaded <tt>VSFilter.dll</tt> and FFInfoEx.avsi to your Avisynth plugin directory</li></ol>

===Getting started with screenshot comparisons===
<ol><li>Start AvsPmod and open the settings dialog (''Options > Program settings'')
<ol style="list-style-type:lower-latin;">
<li>On the ''User Sliders'' tab check ''Hide slider window by default'' (The slider window usually only gets in the way)</li>
<li> If you are using more than one screen, it's usually wise to check the ''Seperate preview window'' option, so you can have one screen dedicated to the video and one to the script</li>
<li>On the Misc tab, uncheck the ''Show warning for bad plugin naming at startup'' option</li></ol></li>

<li>Go to ''Options > Snippets'' and click on ''Insert''. Insert the following script template as snippet and give it a tag you will remember 
(Script by Firesledge with a few additions)</li>

<tt>
{{:AvsPmod}}
</tt>

<li>Now that you're all set, let's load the videos to compare.
<ol style="list-style-type:lower-latin;">
<li>Click into the empty script window and hit F7 to get a list of your snippets. Since there's only the one snipped you just created, hit TAB to insert it</li>
<li>Replace <tt>VIDEOFILE</tt> in the first line with the full path to an episode (e.g. C:/MyCoolVideos/Oruchuban Ebichu/Oruchuban Ebichu - 01-02 [Ampeg].avi) of the first release you want to compare and <tt>GROUPNAME</tt> in the last line with the appropriate group tag</li>
<li>Hit F5 to load (or refresh) the video. Loading a file for the first time might take a few seconds, since the file is being indexed first.</li>
<li>Save the script</li>
<li>Hit Ctrl+N or double click next to the current tab to open a new script tab</li>
<li>Repeat from Step '''3a'''</li></ol></li>

<li>Syncing up the releases (easymode)
<ol style="list-style-type:lower-latin;">
<li>Check if the video of all releases matches up, by going through them with Alt+1, Alt+2, Alt+3, ... 
The best way to do is is to seek to the last frame before a scene change, check if it matches up across tabs, then seek to the next frame and check again 
(Seek by using the arrow keys (left/right: 1 frame; up/down: 1 second) or clicking the timeline for larger time distances) 
'''Note: ''' You may find out that not all subsequent frames match up or worse, the releases running out of sync over time. If it's only single frames, just avoid using them for screenshots.
In case of releases running out of sync, you're dealing with either missing sections or different frame rates. Refer to the [Advanced Tutorial TBD] on how to deal with those cases.</li>
<li>Once all releases you want to compare are in sync, right click their tabs and add them to a single group. Make sure the ''Apply offsets'' and ''Offset also bookmarks'' options are checked. 
AvsPmod will now remember the frame offsets between tabs and automatically seek to the right frames on a shared timeline.</li></ol></li>

<li><ol style="list-style-type:lower-latin;">
<li>To reasonably compare screenshots, we need all frame sizes to be of the same resolution. You should have noticed any differences already while syncing up the releases. 
If all resolutions match, skip this step. If they don't, find out the highest resolution by looking at the bottom right of the status bar. 
The information will be in the following format: FrameWidth x FrameHeight (AspectRatio) - Framerate fps - Colorspace</li>
<li>Take the largest width and height among the releases and find the following section in the scripts for all releases that need to be resized:

<pre style="color:brown">upscale_width = 0
upscale_height = 0</pre>
Replace the 0s with the largest FrameWidth and the largest FrameHeight</li>
<li>Hit F5 to refresh the video preview and confirm everything works as expected.</li>
</ol></li>

<li>Select frames for the screenshot comparison
<ol style="list-style-type:lower-latin;">
<li>Find a frame suitable to convey significant information about an aspect of video quality. 
Pick:
<ul><li>one or two frames of a structure that represents what is on the screen most of the episode (to give a general idea about the video quality)</li>
<li>frames from dark scenes</li>
<li>high-detail frames / frames with fine structures</li>
<li>frames with low contrast</li>
<li>frames from high-motion scenes</li>
<li>a frame or two from a fade-in/fade-out</li>
<li>frames that display video artifacts in one ore more releases (refer to [http://forums.bakabt.me/index.php?topic=32193 this] thread on how to spot and identify video artifacts)</li>
<li>at least one frame from the OP and one frame from the ED</li></ul>
Try to get as many B-Frames as possible. Ideally you'd want matching frame types across the different releases. In practice checking this gets more of a waste of time with each additional release you have to compare. Just try to keep the number of B-to-I comparisons low and make sure you don't pick only B-Frames for one release and only P-Frames for the other. A very easy way to avoid this issue is to not pick frames by only looking at one release. This comes with the added benefit of you being more likely to spot video artifacts in ALL releases. (Check the overlay on the top right of the video frame to find the frame type of the current frame.)</li>
<li>Once you've decided on a frame, hit Ctrl+B to bookmark it.</li>
<li>Repeat from '''6a '''for each additional frame 
If you want to check the frames you already bookmarked, hit F2/Shift+F2 to browse through your bookmarks</li></ol></li>

<li>Export screenshots
<ol style="list-style-type:lower-latin;">
<li>Once you're done deciding on frames to screenshot (10-15 is a good number), it's time to export them to PNG. 
Go to ''Macros > Save image sequence'' (make sure ''Select frames'' is set to "Bookmarks" and ''Output format'' to "*.png")</li>
<li>Pick an output directory and basename. 
I recommend using the basename format <tt>%06d_Groupname</tt>. This way your screenshots will (almost) always sort to comparison-friendly order by default. Make sure ''Add the frame number as suffix'' is checked when using <tt>%06d</tt>, otherwise it only counts up rather than inserting the current frame number. 
:::Example of Directory+Basename: Z:\ScreenCompare\Out\%06d_Zurako
You may also want want to check the ''Use always this directory'' option since you need to run this macro for each release seperately.</li>
<li>Click OK. You'll get a confirmation once the export is done.</li>
<li>Repeat from step '''7a''' for every open tab/release</li>
</ol>
</li></ol>

===Using MKVToolnix for subtitle extraction===
<ol><li>Run the MKVToolnix installer. If using the portable version: Extract the archive</li>
<li>The installer will recommend downloading gMKVExtractGUI (portable users: It can be downloaded seperately, just place it in the appropriate folder) at some point. Do that if you don't know what CLI MKVExtract is and how to use it. Probably also do it if you know, I find that it simplifies the extraction.</li>
<li>Run gMKVExtractGUI.exe</li>
<li>Drag and Drop the file(s) that you want to extract the suptitles of.</li>
<li>Select the tracks you wish to extract. Then click ''Extract''</li>
<li>That's it, the extracted files (on default settings) should be in the same folder as the source files. </li></ol>
===Setting up the ExRelease extraction script (Deprecated and Complicated)===
<ol><li>Open Notepad or a text editor of your choice and type <tt>;</tt>.</li>

<li>Install MKVToolNix and copy the path to the destination folder into your notepad document.
<ol style="list-style-type:lower-latin;">
<li>Append a <tt>;</tt> to your notepad document. The contents should now look like this:</li>
;C:\Program Files (x86)\MKVToolNix;
</ol></li>

<li>Install FontUtils and make sure the ''Add installation directory to PATH'' option is checked</li>

<li>Remember your AviSynth plugin directory from the first tutorial? Copy its path to your notepad document and append another ";" 
Unless you changed the the AviSynth install location, your plugins directory should be 
(enter these into your explorer location bar to make them resolve to full paths):
<ul><li>[On 64-bit Windows] <tt>%ProgramFiles(x86)%\AviSynth 2.5\plugins</tt></li>
<li>[On 32-bit Windows] <tt>%ProgramFiles%\AviSynth 2.5\plugins</tt></li></ul>
Make sure you append the full path to your notepad document, so it looks like this:</li>
;C:\Program Files (x86)\MKVToolNix;C:\Program Files (x86)\AviSynth 2.5\plugins;

<li>Unpack the ExRelease archive to
<ul><li><tt>%userprofile%\Documents\WindowsPowerShell\Modules</tt></li></ul></li>

<li>To make the tools you just installed available to the script and the script conveniently available from everywhere, we need to add their locations to your '''PATH '''environment variable
<ol style="list-style-type:lower-latin;">
<li>Hit Win+Pause to open the System Control Panel</li>
<li>Click on ''Advanced System Settings'' (on the left sidebar), which should open the ''System Properties'' Window</li>
<li>Click on ''Environment Variables''</li>
<li>Browse the ''System variables'' until you find the '''Path''' variable. Highlight it and click on ''Edit...''</li>
<li>Click into the ''Variable value'' input field, and hit the End key to move the cursor behind the last entry (which should be your FontUtils path)</li>
<li>Append the contents of your notepad document and hit Enter</li>
<li>Click ''OK ''on the ''Environment Variables'' and ''System Properties'' to save the settings</li>
</ol></li>

<li>Run Windows PowerShell (you'll find it in the programs menu)
<ol style="list-style-type:lower-latin;">
<li>Make sure you are running at least Powershell v3.0. Type
<pre style="color:brown">$PSVersionTable.PSVersion</pre>
into the command prompt and hit enter. If the number under ''Major ''says 3, you're good to go (continue with step '''8''')</li>
<li>If it doesn't, install
<ul><li>[On 64-bit Windows] Windows6.1-KB2506143-x64.msu</li>
<li>[On 32-bit Windows] Windows6.1-KB2506143-x86.msu</li></ul>
If the update fails with ''"The update is not applicable to your computer"'', you need to install the .NET Framework 4.5 (dotNetFx45_Full_setup.exe) first. 
You may need to restart your computer after installing Powershell 3. 
Open Windows PowerShell again and run
<pre style="color:brown">$PSVersionTable.PSVersion</pre>
to confirm you are now running version 3</li></ol></li>

<li>Next, we have to change the execution policy to allow running unsigned scripts. To do this, run
<pre style="color:brown">Set-ExecutionPolicy Bypass -Scope CurrentUser</pre>
and confirm with Y. With this preparations to run the ExRelease script are done.</li></ol>

===Using the ExRelease script to take screenshots with subtitles/typesetting===
The ExRelease script automates a number of thigs you'd otherwise have to do by hand:
<ul><li>Demuxes subtitles from .mkv files</li>
<li>Extracts attached fonts softsubbed releases (which are required to render the subtitles correctly)</li>
<li>Looks for typesetting inside extracted .ass subtiles and writes a text file, which can be imported as bookmarks in AvsPmod</li>
<li>Loads extracted fonts into memory to make them available to the subtitle renderer</li>
<li>Finds the highest resolution of the releases you want to compare</li>
<li>Writes an AviSynth script with all important parameters already set, so you can start taking screenshots right away</li></ul>
 
<ol><li>Open PowerShell</li>
<li>Move or copy all releases you want to compare with each other to a separate folder. The script works on whole directories, so every .mkv file in the folder is going to be processed.</li>
<li>Run the script by typing
<pre style="color:brown;">ExRelease "X:\SomePath\To Love Ru Darkness"</pre>
(Substitute for your comparison directory, of course.)
You can use the Tab key to auto-complete directories or just type "ExRelease" and drag/drop the folder into PowerShell to insert its path.
The script will now process your files and also create indexes, so it's time to go to the fridge and grab a beer.</li>

<li>When the script is done it will ask you if you want it to load fonts now. Answer with Y for yes. 
Fonts remain loaded in memory for the duration of the session (that means until you log out or shut down the computer).
<ol style="list-style-type:lower-latin;">
<li>In case you want to (continue) work on the screenshot comparison after a logout or reboot, run the script again with
<pre style="color:brown;">ExRelease "X:\SomePath\To Love Ru Darkness" -load</pre></li></ol></li>

<li>Open the generated .avs scripts (which reside next to the .mkv files) in AvsPmod. 
If everything went right, all releases should display at the same resolution, subtitles should now be rendered on the frames, and the releases should now have the appropriate group tag next to the frame numbers.</li>

<li>To save you the effort of finding typesetting to compare, ExRelease has already done that for you.
<ol style="list-style-type:lower-latin;">
<li>To import the found typesetting locations as bookmarks, click on ''Macros > Import bookmarks from file'' and pick the .TSChapters.txt saved alongside the release you are comparing.</li>
<li>Repeat this for every other release you are comparing. This is important because you not only want to compare the TS group A did, but also the TS group B did and group a didn't.</li>
<li>Take note that the typesetting detection is very crude and timecodes are somewhat inaccurate, therefore the typesetting may appear a frame before/after the bookmark or e.g. only starts fading in at the bookmark locations. Therefore it's vital to go trough the bookmarks and move them around to get useful screenshots. To remove a bookmark, just press Ctrl+B at the bookmarked location (frame number in red)</li></ol></li>

<li>To unload fonts after you are done with your comparison, run the script with
<pre style="color:brown;">ExRelease "X:\SomePath\To Love Ru Darkness" -unload</pre></li></ol>
 
'''Addendum:''' The script offers a number of advanced parameters that let you customize your workflow. Run
<pre style="color:brown;">Get-Help ExRelease -detailed</pre>
in PowerShell to display its internal help file.