Fractal Compression

Fractal Compression – the holy grail of compression particularly on video compression, its resolution independent meaning as you scale it at higher resolutions the quality will not degrade this is like vectors but due to vectors not good at showing real or life like images then raster (or bitmap) images are still the one being widely use today, but that can change when fractal video compression becomes possible for everyday use


Encoding Tips for Mini-Size

What you need to encode faster and with quality

– CPU – the more cpu cores you have the faster you can encode, a dual-core CPU
is twice faster against encoding at single-core CPU, and quad-core CPU is 4 times faster against
encoding at single-core CPU, if you use a lot of avisynth filters (some simply call them filters)
other than resize filters then you might notice your multi-core CPU is not using all the cores
this is because avisynth is not designed yet to be multi-threaded, so when your using a lot of
avisynth filters your like encoding at single-core CPU only

– Settings – the higher the quality of the settings the longer/slower the encoding time
but for mini-size encoding its always advisable to set subme=10 (subpixel refinement or motion estimation)
and me=umh (motion estimation), trellis=2, aq-strength=0.6 for highest quality possible
you could get when re-encoding to small size, and if your in megui or staxrip its much easier
you just set preset=veryslow and tune=animation and that will automatically set all the settings of
x264 according to high quality anime compression, and as for encoding mode CRF is only 1-pass
so its faster than 2-pass encoding like average bitrate or filesize mode

– Resolution – the higher the output resolution the longer/slower the encoding time,
for example you encode 2 files with all same settings except that 1 file has output resolution of
576p (1024×576) while the other file has output resolution of 400p (704×400) you will then notice
that 400p is faster to encode than the 576p resolution, this is because part of encoding
is decoding too, in digital video when we say decoding it means playing the video,
but of course x264 wont prompt you with a media player and show you the video playback its
all happening behind the scenes to reserve more computing resources on the encoding process itself

– Software – dont believe a lot of people saying StaxRip is better, MeGUI is great, Handbrake is
awesome, Ripbot264 is super, etc this are all false because all of them uses thesame encoder
to output h264 videos and the name of this h264 encoder is x264, x264 is the best h264 encoder
out there at the moment and that wont change for a long time imo, and btw all those software like
StaxRip, MeGUI, Handbrake, Ripbot264, etc are considered “GUI Front Ends”

– Source – a source file is a video that you want to encode/convert to another format,
the higher the quality of the source file the higher the details youll preserved when you compress or re-encode
the video to small size, lossless video sources are the best like DVD (not DVD rips) and BluRay (not BluRay rips),
the original fansub releases are good sources too, never use rmvb/rm or even youtube videos as source because they
are already over compressed so they already loss too much details

– GPU – dont believe a lot of people saying CUDA encoding is better, yes CUDA based h264 encoders
are blazingly faster when encoding but compared to x264 output at preset=veryslow for example
the CUDA based encoders h264 output files are crap in quality
you can read more about GPU encoding woes here ->
their are plans to port x264 to use the GPU too but so far no updates for it
and yes at the moment x264 is CPU based encoder, so you dont need a powerful GPU to encode fast
with x264 what you need is a multi-core CPU

x264 useful infos
1. qcomp (a x264 option/feature)
– lowers bitrate on high motion scenes
– increases bitrate on low motion scenes

2. qcomp+mbtree (a x264 option/feature)
– lowers bitrate on high motion block that means it will lower bitrate on parts of the scenes that are in high motion not the whole scene
– increases bitrate on high motion block that means it will higher bitrate on parts of the scenes that are in low motion not the whole scene
– so its recommended to always turn on mbtree do note that qcomp=1.0 will disable mbtree

3. frame counts
– the low motion the overall video the lower the frame count and thus lower the bitrate requirement or filesize overall
– the high motion the overall video the higher the frame count and thus higher the bitrate requirement or filesize overall

4. h264/x264 is bad at encoding dark scenes and/or dark areas
– thats why they invented AQ – Adaptive Quantization (a x264 feature/option) to re-allocate the bitrate more on dark areas/spots/scenes but AQ is not really that working efficiently for animation or cartoon videos
nevertheless its still always advisable to use AQ on animation or cartoon content to prevent other compression artifact that is called banding this is what banding looks like

5. Video Complexity/Compressibility – video can be called complex if it has more stuffs going on. like in a action movie for example it has lots of high motion throughout the video so its less compressible than lets say a drama tv show that has more low motion through out the video. for a more slightly technical explanation the movement in a low motion video will be easy to predict/estimate than the movement on a high motion video. the better the movement prediction or estimation the better the compressibility in terms of quality output. video objects on low motion video (like drama/moe anime) stays longer on screens so this means less bitrate needed overall to put them there and then put the background back. a high motion video (like action anime) will have lots of bits flying all over the screen from car crashes and explosions so that means more bitrate is needed and thus low compressibility and can be considered high complex video

you may wonder x264 feature especially qcomp increases bitrate on low motion scene so that means anime like K-On for example should be high in bitrate/filesize requirement especially when using CRF? the answer is because K-On has like 100% of each episode have low frame count so low frame count means not much bitrate/filesize needed for the overall video and K-On has less video complexity because its a low motion video so thats why if you notice when encoding anime video like K-on you could encode it at ridiculously high resolution with low filesize/bitrate but still will look good because its not just about low frame count (or having low/static motion scenes overall) its also about K-on anime having bright scenes overall and not much dark scenes

more reading:

Encoding mini-size anime useful infos
1. Screens
– 4:3 videos or non-widescreen videos have square shape look when you view it
– 16:9 videos or widescreen videos have rectangular shape look when you view it
more reading:

2. Resolution
– SD means Standard Definition and this is usually 480p
preferred resize for mini-SD anime is 400p (704×400) for widescreen video and for non-widescreen video 384p (512×384) is advice resize
– HD means High Definition and this is usually equal or greater than 720p, but on the fansubbing world HD for widescreen starts at 1024×576 this is because some sources for HDTV are bad looking if they go with 720p and thus fansubbers resize it down to 576p
– preferred resize for mini-HD anime is 576p (1024×576) for widescreen video (on fansubbing terms)
more reading:
– 288p is VCD resolution and we dont use this anymore as its too little on today’s standard desktop resolutions
we dont have desktop resolutions of 800×600 anymore so 288p is small and gets blurry in full screen mode viewing because of the big difference in resolution of your desktop (ex. 1366×768 or 768p) and the 288p video
– upscaling resizing up the video will not only make the video blurry but will loose more details when encoding to mini filesizes
– downscaling or resizing down the video of mini filesize encodes for example 720p resize to 400p will preserved more details and so low bitrate/filesize needs lower resolution to maintain a balance on bitrate allocation
but the downside of downscaling is that it will not be as sharp as the original source
simply because its lower resolution nevertheless if you want to preserved details more on mini size anime then downscaling is for you
– tutorial on resolution calculation -> Resolution Calculation
– the higher the resolution you set your output the longer the encoding time

3. Filesize
for 2-pass encoding of mini size anime:
– SD resolution – 60mb is appropriate in most cases
– HD resolution – 120mb is appropriate in most cases
for CRF encoding of mini size anime
– SD resolution – CRF value 24 to 27 is appropiate in most cases
– HD resoltution – CRF value of 28 to 31 is appropiate in most cases

4. Settings
– you may wonder why lots of fansubs have x264 settings meant for fast/low quality encoding this is because
they compensate it with higher bitrate or lower CRF value
– so for mini-size encoding to compensate with the low bitrate or higher CRF value its advisable to
use x264 settings that are higher or meant for slow/high quality encoding

Video Encoding FAQs for Mini-Size Viewers

what is a video? is a bunch of pictures/images that are sequentially played

what is video encoding? it is the process of converting the video to a specific video format or specification
for playback reasons, encoding can sometimes be referred to as compression too and their are 2 kinds
of compression namely lossy and lossless

what is lossy and lossless compression? lossless compression means that every piece of data on the
video file is preserved but this also means that the filesize of this videos are big, mean while
lossy compression is removing lots of data on a video and thus lowering the filesize of the video
without hurting much the quality of the video compared to the original video

how to shrink the filesize of a video but retaining its quality? you cannot since its the nature
of lossy compression to decrease the quality for the benefit of reducing the filesize, in other words
removing more bitrate will lessen quality and also reduces filesize
how to bring back the (loss) quality of a mini-size video? you cannot since once the quality of the video is lost
the data/information/bits on that video are already removed forever, you may try re-encoding the mini-size video
to lets say higher resolution (or upscaling) and higher filesize but you will never see an increase in quality and
in fact its gonna be more blurry, again its the nature of lossy compression

what is h264? h264 is a standard or video format that is popular right now.
h264 is the best for lossy compression on video at the moment. h264 can be alternatively called as
MPEG-4 Part 10 or AVC (Advance Video Coding)

what is x264? x264 is an encoder that implements the h264 standard, so simply means x264 outputs h264 video files

what is a source file? a source file is a video that you want to encode/convert to another format,
the higher the quality of the source file the higher the details youll preserved when lossy compressing/encoding
the video to small size, lossless video sources are the best like DVD and BluRay

what is ripping? is the process of copying video content from digital media like DVD and BluRay disc
to a computer storage device like a harddisk, you may have notice terms like DVD-Rip or BluRay-Rip this means that this videos came from DVD or BluRay sources that they encode it to either lossless or lossy compression methods
but usually lossy compressions like fansubs releases that are in .mkv or .mp4 containers for example

what is video container? video containers can be explained like a organize cabinet and like a organize cabinet
it has drawers that occupies a specific thing like for example drawer 1 has all pencils and drawer 2
has all erasers, etc. So same thing for video containers like .mkv and .mp4, for example .mkv as video container
can include soft-subtitles, the video or other videos, the audio or any other audio. in the Fansubs and
Warez world .mkv is the most use container because its open source meaning its constantly being developed
and maintained. A lot of people mistook .mkv as a format, the reason for your high quality video
in small size is not .mkv the real format that is responsible for all your awe is h264 through the use
of x264 encoder

why use x264 and not CUDA/GPU h264 encoders or Nero AVC encoder to output h264 video files?
well x264 is open source and because its open source it is constantly being developed and maintained
until perfected or until a new video format exceeds the h264 format. Dont be fooled by those
GPU/CUDA based encoders they maybe fast on encoding but the quality compared to x264 is totally bad

what is MeGUI, StaxRip, Handbrake, etc? this softwares are called front-ends to encoders like x264
people sometimes mistook this softwares as the encoders themselves but they are not. This softwares
are just GUI for encoders like the x264 encoder for example

why mini-size videos are small compared to fansubs? as you might know fansubs and any
other mini-size anime encoders uses x264 so primarily their is no trick on making the filesize small
its just that mini-size encoders lowers the bitrate/filesize of the video at the cost of quality loss
compared to the fansubs releases video quality

what are the sources use by mini-size encoders to encode to mini-size? usually mini-size encoders
use the fansubs releases that are in sizes like 150+ mb to 450+ mb for a 24 minute video

why not all mini-size encodes have thesame video quality? primarily because not all video have thesame
video complexity, when we say video complexity we refer to its compressibility, a video episode that contains
lots of action and explosions for example is hard to compress because it needs lot of bitrate/filesize
to maintain quality than a video episode that has lots of low motion scenes like talking anime character that have only his/her face moving for example, so an anime episode video that has lots of low motion scenes can be referred
to as less complex video and thus can be compressed greatly in good video quality and small-filesize

x264 Basics

*** the higher the resolution of your output the higher the filesize it needs
*** the lower the resolution of your output the lower the filesize it needs

for example a specific anime episode is encoded with same settings and same encoder and same video source but different 
resolution, at SD resolution it gave around 30mb for example but at HD it gives around 60mb 
(not the actual filesizes but the gist of it that HD needs high filesize is a fact)
the higher the resolution output the longer the encoding time too
the lower the resolution output the faster the encoding time too
Lossy Compression – x264 is mainly about lossy compression meaning it removes data like redundant data
to lower the filesize output, so in other words lossy compression sacrifices quality to get lower filesize, this also mean
that on each re-encode of a video source you do with x264 the quality will degrade, so this fact will tell you that its impossible to retain the same quality of a bigger video file when you re-encode (transrating) it to smaller video file or same video filesize as the original, the point of lossy compression is to reduce the filesize while maintaining a tolerable video quality
Lossless Compression – is the opposite of lossy compression that it retains the quality of the video no matter how many
times you re-encode since it does not remove video data like redundant video data, but non-removal of data also means
the filesize output of lossless compression are big/huge
Dark Scenes – x264 like any other DCT (Discrete Cosine Transform) base video compression is bad at compressing dark scenes
you will normally find that when encoding to mini-size (ultra low bitrates) the usual complain is that dark scenes have bad quality
nothing much you can do about this since its just the nature of DCT base video compression, other DCT base video compression that became popular are XVID, DIVX, WMV, RMVB, VP8, etc
their are 2 kinds of encoding mode (or Rate Control) on x264 they are CRF (Constant Rate Factor) and 2-pass (Multi-Pass encoding) 

*** CRF (Target Quality) is average quality but filesize varies
*** 2-pass (Target FileSize) is average filesize but quality varies 

let me give an example suppose you have one specific video source, same settings, but different resolutions
so if you encode at 720p and CRF=26 for example that video will output higher filesize
than when you encode it at 480p and CRF=26 since its Target Quality and to achieve that target/level
of quality the bitrate will increase if the resolution will increase 
while if you encode using 2-pass at 400kbps and at 720p it will have same output filesize
as when you encode using 2-pass at 400kbps and at 480p this is because 2-pass is considered as
Target Filesize meaning it does not care how the quality will look like it only cares that the
filesize intended for 400kbps is achieve no matter what the resolution is
CRF behaves like this, the higher the CRF value set the lower the quality thus lower the filesize, while the lower the CRF value set the higher the quality thus the higher the filesize, read more below to find other things about CRF
2-pass behaves like this, the higher the bitrate set the higher quality thus the higher filesize, while the lower the bitrate set the lower the quality thus the lower the filesize
their is no encoding mode for average quality and average filesize at thesame time because of 
video complexity, when we say video complexity it refers to compressibility
high motion scenes need higher bitrate and thus high filesize on that scene and 
low motion scenes need less bitrate and thus low filesize on that scene, the number 
of high motion and low motion scenes varies from every video and thus video compressibility 
varies from show to show, episode to episode, scene to scene

*** video complexity is the reason why in CRF (Target Quality) encoding the filesize vary a lot too
*** video complexity is the reason why in 2-pass (Target Quality) encoding the quality vary a lot too

high motion scenes examples: scenes that has fast pace action with explosions, scenes like opening songs that has a lot of background moving along with characters dancing 
low motion scenes examples: scenes where anime faces and only lips are moving, scenes that have slow moving to static non-moving backgrounds
CRF is average quality; CRF encoding means your guessing on its filesize output
2-pass is average size; 2-pass encoding means your guessing on its quality output
2-pass is CRF too, whats different in 2-pass is that it picks a CRF value that 
will target the file size you want
CRF is average quality if you constantly using a specific CRF value to a given 
resolution like for a 400p you always use CRF=26 no matter what video you re-encode then that 
is how you do CRF encoding
CRF is not constant quality if your always changing the CRF value to a given 
resolution just to target a specific filesize, this kind of CRF encoding is called manual 2-pass, so its better if 
you stick to 2-pass mode if your always changing your CRF value on a specific 
resolution just to attain the filesize you want
“Presets” are x264 options that are adjusted according to the tradeoff between compression and encoding time/speed, 
so if you set the preset at a slower value then youll end up with slower encoding but at the benefit of more 
reduce filesize, and if you set this at a faster encoding preset then youll end up with a bigger filesize output, 
its not highly recommended to use the “Placebo” on the “Presets” since it just give around 1% compression gain compared 
to “Very Slow” on most cases and at the cost of a whopping double to triple encoding time compared to “Very Slow”
“Tunes” option, the “Tunes” are x264 options that further adjust the settings of x264 according to what is the video 
source your encoding, so if your re-encoding any 2D videos like anime or cartoons then set “Tunes” to “Animation”
but if your re-encoding a live-action film with real-life footages then go with “Tunes” set to “Film”, 3D or CGI 
animations are considered on “Film” settings of “Tunes”
and the point of Presets and Tunes of x264 is to decrease the learning difficulty on the many/various settings available 
on x264, back in the old days when their is no Presets and Tunes, their are endless debates about the best settings for 
x264 and endless tweaking of values that just made people more confuse and argue a lot
so its better you stick with Presets and Tunes and do not delve much on to tweaking more 
since the Presets and Tunes already tweak those many/various settings of x264 accordingly

“Profiles” specify which features/settings/options of H264 are allowed (or not allowed), Profiles are needed to make sure 
your video file will play fine on a certain decoder (or device/hardware player, ex. xbox, PS3, mobile phones, etc)
the profile “Baseline” is the good choice for low power devices like mobile phone playback, the profile “Main” 
is mainly for standard definition (SD) TV broadcast, while profile “High” is for any applications that is powerful 
such as a laptop or desktop PC kind/like of devices
“Levels” put further restrictions on other properties of the video, these restrictions include the maximum resolution, 
the maximum bitrate, the maximum framerate (for a given resolution) and the maximum number of reference frames. 
In order play your H264 video on a specific device/hardware player
you do not have to be concerned about Profiles and Levels if your only playing videos on modern computers
that are using software players like VLC Player, CCCP, K-Lite, MPC-HC Player, etc
Profiles and Levels are just settings restrictions to achieve smooth playback on a target Hardware Player or Device
software players usually don't have such restrictions, as long as your CPU is powerful enough

Resolution Calculation

before we start never ever upscale for example your source is just 480p and you want it 720p that is wrong thinking, you will only make the video blurry 

ok back to the main guide if your wandering how to get properly the resize resolution of a source video here is the simple way

for example you got a source of 1280×960
then lets say you want to downsize to 576p:
1280 = 960
x = 576
then cross multiply:
x960 = 737280
x = 768
so its:
to check:
1280/960 = 1.333
768/576 = 1.333
1.333 = 1.333
so your 576p resolution is 768×576

for example you got a source of 1280×720
then lets say you want to downsize to 400p
1280 = 720
x = 400
then cross multiply:
x720 = 512000
x = 711
so its:
to check:
1280/720 = 1.77
711×400 = 1.77
1.77 = 1.77
so your 400p resolution is 711×400

for example you got a source of 1280×720
then lets say you want to downsize to 480p
1280 = 720
x = 480
then cross multiply:
x720 = 614400
x = 853
so its:
to check:
1280/720 = 1.77
853/480 = 1.77
1.77 = 1.77
so your 480p resolution is 853×480

thats it you got it now

MeGUI One-Click Tutorial

MeGUI One Click feature tutorial/guide
the newest MeGUI can automatically add the subtitles to the resulting mkv file output
so the “One Click” feature of MeGUI is looking as simple as Handbrake although MeGUI is still
more buggy or have lots of random errors that youll encounter, nevertheless i like the 
audio encoding of it as you can set the decoder to FFAudioSource (and Output Channels to mono)
for better encoding of FLAC 6 channels to as low as 32kbps using vorbis/ogg audio format for example
lets begin
install it and install .net framework 3.5 SP1 (if megui fail to run)
and install avisynth too ->
run MeGUI (after all installations and updates) and at the bottom click “One-Click” button besides “AutoEncode” button
on the Input/Output area browse for your input file and choose your output location
on the Audio area just click the “downward arrow” button to select your audio
on the Target area click “Config” besides the “OneClick profile” 
now your on the “Encoding Setup”
on “Output Resolution” inputbox it accepts Width (not Height)
– so if you have a 16:9 (widescreen) source video and want 360p 
you will enter 640 on the inputbox to get 640×360 output resolution
– so if you have a 4:3 (non-widescreen or squarescreen) source video and want 384p
you will enter 512 on the inputbox to get 512×384 output resolution
NOTE: to know simple resolution calculation see this -> Resolution Calculation
uncheck “Automatic Deinterlacing” we do not need any filtering because
fansubs are already filtered and filtering them more will be (mostly) a waste of time 
on “Container Type” tab just select MKV, we will always use MKV to ensure
that subtitles will be included on the output
now go back to the “Encoding Setup” tab and select “*scratchpad*” on the combobox 
and then click “Config” besides “Avisynth profile” 
on the “Template” tab delete others besides <input> and <resize> make sure 
that <input> is at the top of <resize> and then click “OK” button
now go back to the “Encoding Setup” tab and select “x264: *scratchpad*” on the combobox
and then click “Config” besides “Video Preset”
on “Presets” slider select “Very Slow” this means higher settings for more compression
but at the cost of very slow encoding, if you want faster but still have some 
good compression then go for “Medium” 
on “Tunings” area select “Animation”
on “Modes” area go for “Targeting quality” and set 26 on the “Quality” inputbox 
and then click “OK” button
NOTE: the “Modes” area will be overidden if you set a filesize on 
“Target” area -> “Filesize” the screenshot is below
now go back to the “Encoding Setup” tab and select “Vorbis: *scratchpad*” on the combobox
and then click “Config” besides “Audio Codec”
on “Preferred Decoder” select “FFAudioSource”
on “Output Channels” select “Convert to Mono”
NOTE: you may ask why mono or 1 channel instead of stereo sound that is 2 channel? 
the answer is to ensure low bitrate encoding and processing of FLAC audio
especially those problematic FLAC 6 channels (or 5.1 surround audio)
do note that more audio channel means more bitrate needed so a 32kbps to 48kbps audio 
will likely to cause some errors if its more than 1 channel
on “Ogg Vorbis options” slider set it to -1.0 this will ensure 32kbps of audio output
as long as its mono or 1 channel then click “OK” button
now go back to the “Encoding Setup” tab and click “OK” button
now click “Go!” button and go to “Queue” tab and press “Start” button
thats it encoding will begin and thats the end of this little tutorial

Handbrake Tutorial

mainly for low size or mini size h264 video format encoding of fansubs using x264 encoder in mkv or mp4 container 

TIP: if your ripping a encrypted DVD then install libdvdcss here is a guide – 

getting handbrake
go to
click “Downloads” and go to “Nightly Builds”
NOTE: we are using Nightly Builds because its more updated so less bugs and more updated encoding tools

installing handbrake
clicking “Nightly Builds” will take you here
then download something that says “WindowsGUI” or “Win GUI”
then install it and open it

encoding with handbrake

click “Tools” menu and then click “Options” and then click “Output Files”
click “Browse” button and browse the desktop folder for example as your default output folder then click “Close”
click “High Profile” on “Presets” pane
click “Container” drop down box select “MKV”
NOTE: we select MKV to select Vorbis audio later on when encoding with audio because AAC of Handbrake
is not NeroAAC so Vorbis audio wins in here for good quality on low bitrate
go to “Picture” tab (Resolution tab) and select “None” on “Anamorphic” drop down box
then check “Keep Aspect Ratio” now on “Height” input box put 400 or 360
now the “Width” will be calculated automatically
NOTE: 400 as height is 400p so 360 as height is 360p

go to “Video” tab set “Video Codec” to “H.264(x264)” then set “Framerate (FPS)” to “Same as source”
then make sure that “Variable Framerate” is selected and then choose your encoding mode on “Qaulity”
i prefer “Constant Quality” or CRF
if you prefer “Constant Quality” take note that filesize will vary but quality will
be almost consistent through out the video for a given CRF value
and its a faster way of encoding too because its 1-pass
“Constant Quality” or CRF values good ranges are from 24 – 28 i prefer value of 26
in CRF the higher the value the lesser the quality but lesser the filesize
in CRF the lesser the value the higher the quality but higher the filesize
in CRF filesize will be less too if you set a low reolution thats why we set Resolution that
is in average 360p like 640×360 (for 16:9) or 512×384 (for 4:3)
if you prefer or “Avg bitrate” make sure to check “2-pass encoding”
and check “Turbo first Pass”
NOTE: in “Avg bitrate” good values are betweeen 300-450 bitrate

set x264 Preset to “Very Slow”
NOTE: the slower the x264 preset the better the quality and the smaller the filesize but “Placebo” preset is a waste of time
set x264 Tune to “Animation”
NOTE: we choose “Animation” as the preset since we are encoding anime/cartoons or cel shaded videos but if your encoding live action movies/series then choose “Film”
set H.264 Profile to “High”
set H.264 Level to “Auto”

go to “Audio” tab click “Clear” button to remove all the audio on the queue
click “Add Track” then “Add New Track”

on “Source” drop down box select an audio you want to add
on “Codec” drop down box select “Vorbis” 
on “Mixdown: drop down box select “Mono”
on “Bitrate” drop down box select “48” (this means you will encode the audio in 48 bitrate)
NOTE: for multi-audio (like dual-audio) you do same steps just click “Add Track” again and do the steps again
NOTE: take note that the first audio you put on the queue will be the default audio
when you play the reencoded file
NOTE: we set “Mixdown” to “Mono” and at 48kbps audio to ensure that we can encode sources that are FLAC and in 6 channels

go to “Subtitles” tab then click “Add Track” then click “Add New Track”

on the “Source” drop down box select a subtitle of your choice
in this case i select a SSA/ASS subtitle then i check the “Burn In” checkbox for Hardsubbed
or “Default” checkbox for Softsubbed
Hardsubbed – means the subtitles are irreversibly part of the video so you cannot turn off this or extract this kind of subs
Softsubbed – means the subtitles are just part of the video like a text display that can easily be turn off or turn on back again and this kind of subtitles can be extracted

then press “Start” button to start encoding
alternatively you can click “Add to Queue” then start encoding from “Show Queue”
the “Add to Queue” function is good if your gonna encode a lot of videos

so thats it happy encoding with Handbrake

to speed up more the reencoding of fansub anime
go to “Video Filters” tab and set it all to “Off”