<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>featured - OCFreaks!</title>
	<atom:link href="https://www.ocfreaks.com/tag/featured/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.ocfreaks.com/tag/featured/</link>
	<description>Overclocking , Gaming , Technology , Robotics &#38; DIY!</description>
	<lastBuildDate>Sun, 09 Jul 2017 14:52:43 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.6.4</generator>
<site xmlns="com-wordpress:feed-additions:1">42777727</site>	<item>
		<title>DIY 3D Printer Build Chapter 1: The Nightmare</title>
		<link>https://www.ocfreaks.com/diy-3d-printer-build-chapter-1-nightmare/</link>
					<comments>https://www.ocfreaks.com/diy-3d-printer-build-chapter-1-nightmare/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Team OCFreaks!]]></dc:creator>
		<pubDate>Sat, 18 Mar 2017 13:55:33 +0000</pubDate>
				<category><![CDATA[Projects & DIY]]></category>
		<category><![CDATA[3D-Printer]]></category>
		<category><![CDATA[featured]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2675</guid>

					<description><![CDATA[<p>A short story of the nightmare that was our first diy 3D Printer kit build and why, later on we decided to build our own custom diy 3D Printer from scratch.</p>
<p>The post <a href="https://www.ocfreaks.com/diy-3d-printer-build-chapter-1-nightmare/">DIY 3D Printer Build Chapter 1: The Nightmare</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/diy_3dp_title_small.jpg" alt="diy 3dp title" width="300px" height="232px"></p>
<p class="compact">3D printing is a technology that has taken the DIYing world by storm in these past couple of years. New companies manufacturing 3D printers and DIY 3D Printer kits have been popping up (and going down, too) like crazy. We* have to admit, in it&#8217;s concept, it is a pretty great idea.</p>
<p class="compact">We just recently were bit by the 3D printing bug. So, powered by our DIY-ers genes, we decided to purchase one of those cheap 3D printer (Prusa i3) kits. It seemed like a really sweet deal, the whole kit along with 2kg ABS filament coming for 23,500 INR. That, friends, turned out to be a pretty dumb move on our part. The kit was riddled with a horrendous amount of issues. Where do I even begin?!?!:</p>
<ol>
<li>The printed parts were, putting it plain and simply, unusable. Not only was the print quality bad (that I can actually forgive), but even functionally speaking, a lot of the (clamping) holes in the parts were filled. When inquired, the seller told us that it was just the &#8220;support structures&#8221; that can be easily removed. Who does he think we are, kindergarten children playing with our first Lego sets that he could fool so easily?!?! We dont know if anyone reading this has ever tried drilling into small irregularly shaped parts (that too, made of ABS) before, but trust us, it ain&#8217;t easy!!! This itself meant that we had to modify (in some cases, reprint) the 90% of the parts.
<div id="toplevel" class="imgal" style="background: none; border: none; padding: 0px; margin-top: 20px;">
<div class="col" style="padding-right: 25px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_1.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_1.jpg" alt="Bad 3D Printed Parts" width="300px" height="215px"></a>
</div>
</div>
<div class="col">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_2.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_2.jpg" alt="Bad 3D Printed Parts" width="300px" height="215px"></a>
</div>
</div>
</div>
<div id="toplevel" class="imgal" style="background: none; border: none; padding: 0px;">
<div class="col" style="padding-right: 25px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_3.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_3.jpg" width="300px" height="208px" alt="Bad 3D Printed Parts"></a>
</div>
</div>
<div class="col">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_6.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_6.jpg" width="300px" height="208px" alt="Bad 3D Printed Parts"></a>
</div>
</div>
</div>
<div id="toplevel" class="imgal" style="background: none; border: none; padding: 0px;">
<div class="col" style="padding-right: 25px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_4.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_4.jpg" width="300px" height="239px" alt="Bad 3D Printed Parts"></a>
</div>
</div>
<div class="col">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_5.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_3dp_parts_5.jpg" width="300px" height="239px" alt="Bad 3D Printed Parts"></a>
</div>
</div>
</div>
</li>
<li>The hotend(the part that extrudes molten Plastic) was again, unusable. The Hotend is a part that has to be manufactured with utmost precision and tight tolerances. A good Hotend can make an otherwise bad 3D printer OK. But a bad Hotend can make an otherwise (mechanically speaking) excellent printer unusable. A lot of engineering goes into designing a hotend, so most manufacturers just make one following one of the many existing Open Source Designs. So, imagine our surprise on finding that the hotend provided in the kit was not conforming to any of the popular designs found online, and was just a PEEK rod and a brass part (comprising of heater block and 0.4mm nozzle) put together.
<div id="toplevel" class="imgal" style="background: none; border: none; padding: 0px; margin-top: 20px;">
<div class="col" style="padding-right: 25px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_hotend_1.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_hotend_1.jpg" width="300px" height="312px" alt="Bad Hotend"></a>
</div>
</div>
<div class="col">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_hotend_3.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_hotend_3.jpg" width="300px" height="312px" alt="Bad Hotend"></a>
</div>
</div>
</div>
</li>
<div>
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_hotend_2.jpg" target="_blank"><img decoding="async" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/bad_hotend_2.jpg" width="600px" height="375px" alt="Bad Hotend" style="margin-left: 2px;"></a>
</div>
</li>
<li class="">The feeder mechanism(the part that pushes the plastic filament through the hotend) was a joke. Leaving the botched print jobs aside, the design was flawed in a number of ways.</li>
<li>The filament that we got with the kit was utter shit(if you&#8217;ll pardon my French). The quality was really bad and the filament diameter was uneven.
<div id="toplevel" class="imgal" style="background: none; border: none; padding: 0px; margin-top: 20px;">
<div class="col" style="padding-right: 15px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/filament_1.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/filament_1.jpg" width="200px" height="133px" alt="Filament Diameter Variance"></a>
</div>
</div>
<div class="col" style="padding-right: 15px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/filament_2.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/filament_2.jpg" width="200px" height="133px" alt="Filament Diameter Variance"></a>
</div>
</div>
<div class="col">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/filament_3.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/filament_3.jpg" width="200px" height="133px" alt="Filament Diameter Variance"></a>
</div>
</div>
</div>
</li>
<li>The pins in the electronics (Arduino Mega+RAMPS) were not properly soldered in multiple places, leading to a whole bunch of wierd issues.</li>
</ol>
<p class="compact">Despite of all these shortcomings, we decided to go forward and assemble the printer, reassuring ourselves that we have not wasted our money. Have a look at the end result.</p>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/prefinal_build.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/prefinal_build.jpg" width="600px" height="499px" alt="During Assembly"></a>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/final_build.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/final_build.jpg" width="600px" height="440px" alt="Final Build"></a>
</div>
<p>Heres a few images of the (horrible) print quality:</p>
<div id="toplevel" class="aligncenter imgal" style="background: none; border: none; padding: 0px;">
<div class="col" style="padding-right: 25px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/print_quality_1.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/print_quality_1.jpg" width="300px" height="225px" alt="Print Quality"></a>
</div>
</div>
<div class="col">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/print_quality_2.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/print_quality_2.jpg" width="300px" height="225px" alt="Print Quality"></a>
</div>
</div>
</div>
<div id="toplevel" class="aligncenter imgal" style="background: none; border: none; padding: 0px;">
<div class="col" style="padding-right: 25px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/print_quality_3.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/print_quality_3.jpg" width="300px" height="225px" alt="Print Quality"></a>
</div>
</div>
<div class="col">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/print_quality_4.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/print_quality_4.jpg" width="300px" height="225px" alt="Print Quality"></a>
</div>
</div>
</div>
<p>Here&#8217;s a few images of the (much more bearable) print quality after upgrading to an all metal hotend(which seems to be an E3D V5 clone) and a custom extruder design:</p>
<div id="toplevel" class="aligncenter imgal" style="background: none; border: none; padding: 0px;">
<div class="col" style="padding-right: 15px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/metal_hotend_print_quality_1.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/metal_hotend_print_quality_1.jpg" width="200px" height="150px" alt="All metal Hotend Print Quality"></a>
</div>
</div>
<div class="col" style="padding-right: 15px">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/metal_hotend_print_quality_2.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/metal_hotend_print_quality_2.jpg" width="200px" height="150px" alt="All metal Hotend Print Quality"></a>
</div>
</div>
<div class="col">
<div class="image">
<a href="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/metal_hotend_print_quality_3.jpg" target="_blank"><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/projects/diy_3dp_build_ch_1/metal_hotend_print_quality_3.jpg" width="200px" height="150px" alt="All metal Hotend Print Quality"></a>
</div>
</div>
</div>
<p class="compact">Now, we know many of you might laugh seeing this. We don&#8217;t blame you, even we would!!! But trust us, if you know what we went through, you will admit that this is quite an accomplishment! We had to redesign the whole feeder mechanism, and reprint many other parts (on another cheap 3D printer. Someone up there must really hate us!!!) too on account of the botched print jobs.</p>
<p class="compact">After suffering through this whole ordeal, we decided to make our own 3D printer. The goals we had set in our mind was:</p>
<ol>
<li>Make it as reasonably priced as possible, while at the same time not compromising one bit on quality.</li>
<li>Address many common issues faced by a lot of the cheap 3D printers available on the market.</li>
<li>Keep the number of 3D printed parts used down to a minimum. This was as much a necessity (we did not have a 3D printer readily at our disposal) as a goal.</li>
<li>The design should be both modular and scalable.</li>
</ol>
<p class="compact">Keep tuned for more details on this build.</p>
<div class="special sp_blue notestar spaced"><b>Note:</b> We wont be revealing the Identity of the seller. Suffice it to say that we feel it would be immoral of us to put down an apparently new seller. We do hope however, that he steps up his game. If he doesn&#8217;t, he&#8217;ll only have himself to blame for all the customer complaints and potential lawsuits.</div>
<div class="special sp_blue notestar spaced"><b>Note:</b> This article is by no means a criticism of Prusa i3. Far from it. The Prusa i3 does have numerous design flaws, but when made properly, it can be a really good 3D printer in it&#8217;s own right. This is a criticism of all those sellers out there who cut corners on quality just to win in the race to sell the cheapest 3D printer.</div>
<div class="special sp_blue notestar spaced"><b>Note:</b> We started our first Prusa build back in Jan 2015 and tried to optimize it till April 2015 after which we gave up.  We slowly started our own custom DIY 3D printer build during July-August 2015 and completed it around end of september 2015.</div>
<p>*Not the royal &#8220;We&#8221;. The 3D printer build was a joint project of Saby D&#8217;silva and Umang Gajera. Hence,  all the usage of &#8220;we&#8221;.</p>
<p>The post <a href="https://www.ocfreaks.com/diy-3d-printer-build-chapter-1-nightmare/">DIY 3D Printer Build Chapter 1: The Nightmare</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/diy-3d-printer-build-chapter-1-nightmare/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2675</post-id>	</item>
		<item>
		<title>KZ ED special edition &#038; ES earphones review</title>
		<link>https://www.ocfreaks.com/kz-ed-special-edition-es-earphones-review/</link>
					<comments>https://www.ocfreaks.com/kz-ed-special-edition-es-earphones-review/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Saby D'silva]]></dc:creator>
		<pubDate>Sat, 04 Mar 2017 12:39:28 +0000</pubDate>
				<category><![CDATA[Reviews]]></category>
		<category><![CDATA[audio]]></category>
		<category><![CDATA[earphones]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[Review]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2666</guid>

					<description><![CDATA[<p>A relatively unknown brand, KZ Acoustics, has been getting quite some traction lately for providing quality earphones at Super cheap prices. How good are their earphones? Well, lets find out.</p>
<p>The post <a href="https://www.ocfreaks.com/kz-ed-special-edition-es-earphones-review/">KZ ED special edition &#038; ES earphones review</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p class="compact" style="padding-top: 10px;">A relatively unknown brand, KZ Acoustics, has been getting quite some traction lately for providing quality earphones at Super cheap prices. I&#8217;ve  bought their ED Special Edition and ES earphones off a deal on AliExpress where they both came in a pack for a mere 14.75$!(Almost 2 years back!) But how good are these earphones? Well, lets find out. </p>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Specifications</h2>
<h3 class="label" style="position: relative; top: 10px; border: 1px solid #999999">KZ ED</h3>
<table style="width: 400px; height: 350px">
<tr>
<td style="vertical-align: middle";><b>Wearing Style</b></td>
<td style="vertical-align: middle";>In-Ear</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Driver Type</b></td>
<td style="vertical-align: middle";>Dynamic, N45 Neodymium</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Driver Size</b></td>
<td style="vertical-align: middle";>7mm</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Frequency range</b></td>
<td style="vertical-align: middle";>20-20000Hz</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Impedance</b></td>
<td style="vertical-align: middle";>16O</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Sensitivity</b></td>
<td style="vertical-align: middle";>108±3dB</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Cable length</b></td>
<td style="vertical-align: middle";>1.2m</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Connector</b></td>
<td style="vertical-align: middle";>Gold-plated 3.5mm L-Bent plug</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Weight</b></td>
<td style="vertical-align: middle";>17g</td>
</tr>
</table>
<h3 class="label" style="position: relative; top: 10px; border: 1px solid #999999">KZ ES</h3>
<table style="width: 400px; height: 350px">
<tr>
<td style="vertical-align: middle";><b>Wearing Style</b></td>
<td style="vertical-align: middle";>In-Ear</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Driver Type</b></td>
<td style="vertical-align: middle";>Unknown</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Driver Size</b></td>
<td style="vertical-align: middle";>Unknown</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Frequency range</b></td>
<td style="vertical-align: middle";>Unknown</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Impedance</b></td>
<td style="vertical-align: middle";>18 O</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Sensitivity</b></td>
<td style="vertical-align: middle";>98 + 2dB</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Cable length</b></td>
<td style="vertical-align: middle";>1.2M + 5CM</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Connector</b></td>
<td style="vertical-align: middle";>Gold-plated 3.5mm L-Bent plug</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Weight</b></td>
<td style="vertical-align: middle";>20g</td>
</tr>
</table>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Packing and Accessories:</h2>
<p class="compact">The earphones came in separate cardboard boxes. For 14.75$, I really wasn&#8217;t expecting a whole lot of accessories (provided that I got 2 earphones at this price). So, I wasn&#8217;t disappointed (or pleasantly surprised ;-)) when I opened the box to find only the earphones with multiple pairs of silicone buds.</p>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/package.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/package.jpg" alt="Packing_Front" height="682px" width="600px"></a><i>Packing</i>
</div>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/kz_ed_and_es.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/kz_ed_and_es.jpg" alt="ES (on the left) and ED (on the right)" height="484px" width="600px"></a><i>ES (on the left) and ED (on the right)</i>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/kz_ed_es_bud_closeup.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/kz_ed_es_bud_closeup.jpg" alt="Silicone Buds" height="300px" width="600px"></a><i>Silicone Buds (Left: ES; Right: ED)</i>
</div>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Build Quality:</h2>
<p class="compact">Both the earphones come with an inline mic and a single button remote. The cables are of fairly decent quality with negligible memory. They are sheathed in a translucent dark brown sleeve. The silicone earbuds provided with these earphones are pretty comfortable and fit snugly in the ear. The driver housing is the only distinguisishing feature (physically speaking) between the two earphones. In ES the drivers are housed in a cylindrical metal casing with a dark grey glossy finish. In ED the housing is a slightly tapered black colored cylinder with a diamond knurled outer surface, a meshed back and a gold finish nearing the nozzle. While The ED also has Red and Blue rings indicating the left and Right positions, the ES has straighforward L and R markings on the housing surface.</p>
<p class="compact">Overall, both appear to be well built and somewhat durable.</p>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/kz_ed_es_driver_housing_closeup.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/kz_ed_es_driver_housing_closeup.jpg" alt="Driver Housing" height="214px" width="600px"></a><i>Driver Housing (Left: ES; Right: ED)</i>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/kz_ed_es_nozzle_closeup.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/kz_ed_es_earphones/kz_ed_es_nozzle_closeup.jpg" alt="Nozzle" height="246px" width="600px"></a><i>Nozzle (Left: ES; Right: ED)</i>
</div>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Performance:</h2>
<p class="compact">This is the part where the differences between the two start to emerge.</p>
<p class="compact">The performance of ES was a letdown. While the bass output was clear and punchy, heavily recessed mids and a bland treble performance ruined the whole deal for me. Compared to what most IEMs at this price range offer, I really wouldn&#8217;t call this outright terrible. Just mediocre, reiterating how cheap I got it for.</p>
<p class="compact">On the other hand, the ED, boy oh boy did it surprise me. After listening to the ES, I was preparing myself for another disappointment. I am happy to admit that I was wrong in thinking so. The bass was as clear and booming as can be and the mids and sub bass were slightly recessed. The treble output, while not as sharp as I&#8217;d like it to be, wasn&#8217;t that bad either. And the soundstage was as wide as can be expected in a low cost IEM.</p>
<p class="compact">To sum it up, while the ES has a more bassy sound signature, the ED has a more neutral tone that is just slightly prejudiced towards the bass.</p>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Conclusion:</h2>
<p class="compact">Now, the million dollar question that begs to be asked is are these worth it? About the ES, it really isn&#8217;t the only earphone on the market with a sound signature that is biased towards the lower frequencies, so I can&#8217;t in my right conscience recommend it. The ED, however, is honestly a pretty good IEM. A quick price check on AliExpress shows the ED priced between 8-15$. Anything below 10$, this earphone is the real deal, a steal. I know I sound like a telemarketer here, but trust me, I wouldn&#8217;t be saying this if it weren&#8217;t so. Above that however, it comes dangerously close to the price of Soundmagic&#8217;s ES18S. Between the two of them at that price point, the ES18S does have a slightly warmer sound signature and has more spark on the treble . Overall, it is the better performer. But then again the ED does surpass the ES18S in terms of build quality. So, it all comes down to preference. With that said, Kudos to KZ Acoustics for making a ridiculously low priced IEM that would put many higher priced ones to shame.</p>
<h3 class="label" style="position: relative;top: 20px;left:10px;">KZ ED</h3>
<div class="proconbox">
<div class="probox">
<ul class="pros">
<li>Good Bass Performance</li>
<li>Soundstage isn&#8217;t half bad</li>
<li>Good build quality and aesthetically pleasing (matter of opinion)</li>
<li>Comes with an inline Mic</li>
<li>AMAZING Value for Money</li>
</ul>
</div>
<div class="conbox">
<ul class="cons">
<li>Incoherent Left and Right Markings (b.L.ue and .R.ed? REALLY?!?!)</li>
<li>Nothing else for the price</li>
</ul>
</div>
<div style="clear: both"></div>
</div>
<h3 class="label" style="position: relative;top: 20px;left:10px;">KZ ES</h3>
<div class="proconbox">
<div class="probox">
<ul class="pros">
<li>Good Bass Performance</li>
<li>Good build quality and aesthetically pleasing (matter of opinion)</li>
<li>Comes with an inline Mic</li>
</ul>
</div>
<div class="conbox">
<ul class="cons">
<li>Terribly lacking in the mids and treble department</li>
<li>The paint on the housing tends to peel off with time</li>
</ul>
</div>
</div>
<div class="special sp_blue notestar spaced">Note: These earphones are only worth it if you buy them from AliExpress (or any other Chinese online stores), because as far as I know, it is the only place where you could get it at the listed price. However, there are plenty of sellers on AliExpress that sell fake stuff. So, if you are intent on purchasing these, be sure to buy them from the official <a href="https://kziems.aliexpress.com/store/1358152" tareget=_blank>KZ Acoustics store</a>.</div>
<div class="scorecard">
<header>
<div class="left title_area">
<h2 class="title">KZ ED Special Edition+ES Pack</p>
<h2></div>
<div class="logo_area">
<div class="logo_box">
<div class="ocf-icon-logo"></div>
</div>
</div>
<div class="centerline"></div>
</header>
<div class="review-region">
<div class="text">While the ED is a spectacular earphone for the price, the ES is a letdown that unfortunately ruins the price–performance ratio of the whole package. If I were to rate the two individually (which is only fair given how good an earphone the ED is), I&#8217;d give the <strong>ED 4.5/5</strong> and the <strong>ES 2/5</strong> (assuming the ED priced at $8 and the ES at $6.75). But since this is a review of the pack, I&#8217;ll give it a <strong>3.5/5</strong>.</div>
<div class="right score">
<div class="score_box">
<div class="star-rating_area">
<div class="star-rating"><span style="height: inherit; width: 65%;"></span></div>
</div>
<div class="mark_area">3.25/5</div>
<div class="score-title_area">GREAT!!!</div>
</p></div>
</p></div>
</div>
</div>
<p>The post <a href="https://www.ocfreaks.com/kz-ed-special-edition-es-earphones-review/">KZ ED special edition &#038; ES earphones review</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/kz-ed-special-edition-es-earphones-review/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2666</post-id>	</item>
		<item>
		<title>AMD Ryzen Official Release and Pre Order</title>
		<link>https://www.ocfreaks.com/amd-ryzen-official-release-pre-order/</link>
					<comments>https://www.ocfreaks.com/amd-ryzen-official-release-pre-order/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Saby D'silva]]></dc:creator>
		<pubDate>Wed, 22 Feb 2017 20:03:09 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[AMD]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[featured]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2646</guid>

					<description><![CDATA[<p>Ryzen CPUs officially released by AMD in San Francisco Tech Event and now available for pre-order. Also new benchmarks, Specs and features revealed.</p>
<p>The post <a href="https://www.ocfreaks.com/amd-ryzen-official-release-pre-order/">AMD Ryzen Official Release and Pre Order</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" src="https://www.ocfreaks.com/imgs/common_title/amd_ryzen.jpg" width="375px" height="291px" class="aligncenter" /></p>
<p class="compact">For many PC enthusiasts looking to upgrade their rigs lately, the wait for AMD&#8217;s new Ryzen processors has been a sweet agony. Adding salt to the wound, heartless AMD has been providing potential buyers with juicy tidbits at just the right intervals to keep them from moving on. How much pain can an enthusiast take?!?! Well folks, I&#8217;m pleased to tell you the wait is finally over.</p>
<p class="compact">AMD has formally announced the release of Ryzen CPUs on a tech event held in San Francisco today, and they would reach the market on March 2nd. Initially, only the three Ryzen 7 CPUs (1800X, Ryzen 7 1700X and Ryzen 7 1700) will be released. The release of the rest of the lineup would follow thereafter.</p>
<p>In this event, AMD has also disclosed some new information about these processors that we were not privy to.</p>
<h2 class="shead" style="padding-top: 20px">52% Better IPC</h2>
<p class="compact">After the bulldozer fiasco, AMD decided that it would be much better to start with a clean slate. If you go by their words, this approach has worked wonders for them. Their target of 40% improvement in IPC over their previous chips (Excavator) was not only met, but exceeded! The Ryzen CPUs have 52% more IPC than the Excavator chips. Looks like Jim Keller (and his team, of course) has done it again!</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_goals_exceeded.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_goals_exceeded.jpg" alt="Ryzen Goals Exceeded" width="100%"></a>
</div>
<p style="text-align:right; font-size:13px;">Source: AMD</p>
<h2 class="shead" style="padding-top: 20px">Die Shot</h2>
<p class="compact">AMD has revealed a die shot of Ryzen processors. Built on a 14nm process node, the 8 core Ryzen CPU consists of 4.8 billion transistors and 2000m of signal wiring. The AMD team responsible for Ryzen has reportedly spent two million engineering hours over the architecture. Looking at the benchmark results (that are revealed till now), it looks like all that hard work has finally paid off.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_dieshot.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_dieshot.jpg" alt="Ryzen dieshot" width="100%"></a>
</div>
<p style="text-align:right; font-size:13px;">Source: AMD</p>
<h2 class="shead" style="padding-top: 20px">Benchmark Demos</h2>
<p class="compact">AMD CEO Lisa Su showed three demos pitting Ryzen 7 1700X against Intels Core i7-6800K. The demos run included Cinebench, HandBrake, and a 4K gaming session. See how Ryzen fared in these tests below:</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_cinebench.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_cinebench.jpg" alt="ryzen cinebench performance" width="610px"></a>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_cinebench_ptp.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_cinebench_ptp.jpg" alt="ryzen cinebench performance per dollar" width="610px"></a>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_handbrake.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_handbrake.jpg" alt="ryzen handbrake performance" width="610px"></a>
</div>
<p style="text-align:right; font-size:13px;">Source: <a href="https://www.pcper.com/news/Processors/AMD-Ryzen-Pre-order-Starts-Today-Specs-and-Performance-Revealed">pcper</a></p>
<p class="compact">In the 4K Gaming Session, AMD showed a Ryzen (Ryzen 7 1800X) processor and an Intel Broadwell-E (Core i7-6900K) processor running a demo version of Sniper Elite 4 side by side. The average frame rate (70-80 FPS) was similar on both the systems and the differences, if any, were imperceptible.</p>
<p class="compact">From all this, it can be seen how Intel has a serious competitor on it&#8217;s hands in the form of Ryzen.</p>
<h2 class="shead" style="padding-top: 20px">Retail Packing and Coolers</h2>
<p class="compact">AMD also unveiled the retail packaging and their new Wraith Spire Heat Sink Fans for select Ryzen processors. Have a look below:</p>
<div class="spaced image" style="display: inline-block; float: left">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_box1.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_box1.jpg" alt="Ryzen boxart 1" height="290px" width="342px"></a>
</div>
<div class="spaced image" style="display: inline-block; float: right">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_box2.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_box2.jpg" alt="Ryzen boxart 2" height="290px" width="301px"></a>
</div>
<div style="clear: both"></div>
<div class="spaced image" style="display: inline-block; float: left">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_wraith_cooler1.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_wraith_cooler1.jpg" alt="Ryzen Wraith Cooler 1" height="200px" width="209px"></a>
</div>
<div class="spaced image" style="display: inline-block; float: left">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_wraith_cooler2.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_wraith_cooler2.jpg" alt="Ryzen Wraith Cooler 2" height="200px" width="227px"></a>
</div>
<div class="spaced image" style="display: inline-block; float: left">
<a href="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_wraith_cooler3.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/news/ryzen_official_preorder/ryzen_wraith_cooler3.jpg" alt="Ryzen Wraith Cooler 3" height="200px" width="195px"></a>
</div>
<div style="clear: both"></div>
<p style="text-align:right; font-size:13px;">Source: AMD</p>
<p class="aligncenter compact">Apart from all this, here is some more miscellaneous information about the Ryzen 7 processors and AM4 Mobo Chipsets that AMD was kind enough to share:</p>
<table class="compact">
<thead>
<tr style="border-top:1px solid #999;">
<th style="border-right:1px solid #999;border-left:1px solid #999;">AMD Ryzen CPU</th>
<th style="border-right:1px solid #999;">Cores/Threads</th>
<th style="border-right:1px solid #999;">L3</th>
<th style="border-right:1px solid #999;">TDP</th>
<th style="border-right:1px solid #999;">Base</th>
<th style="border-right:1px solid #999;">Turbo</th>
<th style="border-right:1px solid #999;">XFR</th>
<th style="border-right:1px solid #999;">HSF Included</th>
<th style="border-right:1px solid #999;">Price</th>
</tr>
</thead>
<tbody>
<tr>
<td>AMD Ryzen 7 1800X</td>
<td>8/16</td>
<td>16MB</td>
<td>95W</td>
<td>3.6GHz</td>
<td>4.0GHz</td>
<td>4.0GHz+</td>
<td>No</td>
<td>$499</td>
</tr>
<tr>
<td>AMD Ryzen 7 1700X</td>
<td>8/16</td>
<td>16MB</td>
<td>95W</td>
<td>3.4GHz</td>
<td>3.8GHz</td>
<td>3.8GHz+</td>
<td>No</td>
<td>$399</td>
</tr>
<tr>
<td>AMD Ryzen 7 1700</td>
<td>8/16</td>
<td>16MB</td>
<td>65W</td>
<td>3.0GHz</td>
<td>3.7GHz</td>
<td>No</td>
<td>Yes – Wraith Spire</td>
<td>$329</td>
</tr>
</tbody>
</table>
<p style="text-align:right; font-size:13px;">Source: <a href="http://www.legitreviews.com/amd-ryzen-pre-orders-start-today_191572">legitreviews</a></p>
<table class="compact" style="width: 100%">
<thead>
<tr style="border-top:1px solid #999;">
<th style="border-right:1px solid #999;border-left:1px solid #999;"> </th>
<th style="border-right:1px solid #999;">X370</th>
<th style="border-right:1px solid #999;">B350</th>
<th style="border-right:1px solid #999;">A320</th>
<th style="border-right:1px solid #999;">X300</th>
</tr>
</thead>
<tbody>
<tr>
<td>PCIe 3 Lanes</td>
<td>24</td>
<td>24</td>
<td>TBA</td>
<td>TBA</td>
</tr>
<tr>
<td>CrossfireX/SLI</td>
<td>2-Way SLI</td>
<td>TBC</td>
<td>N/A</td>
<td>N/A</td>
</tr>
<tr>
<td>PCIe 2 Lanes</td>
<td>8</td>
<td>6</td>
<td>TBA</td>
<td>TBA</td>
</tr>
<tr>
<td>USB 3.1</td>
<td>2</td>
<td>2</td>
<td>TBA</td>
<td>TBA</td>
</tr>
<tr>
<td>USB 3.0</td>
<td>8</td>
<td>4</td>
<td>TBA</td>
<td>TBA</td>
</tr>
<tr>
<td>USB 2.0</td>
<td>6</td>
<td>6</td>
<td>TBA</td>
<td>TBA</td>
</tr>
<tr>
</table>
<p style="text-align:right; font-size:13px;">Source: <a href="http://wccftech.com/amd-ryzen-7-1800x-1700x-official-launch/">wccftech</a></p>
<p class="compact">Ryzen 7 CPUs and AM4 Mobos are now officially available for pre order at following prices:</p>
<h3><strong>Amazon:</strong></h3>
<p><a href="https://www.amazon.com/AMD-YD180XBCAEWOF-Ryzen-1800X-Processor/dp/B06W9JXK4G" target="_blank">Ryzen 7 1800X &#8211; $499 &#8211; Amazon.com</a><br />
<a href="https://www.amazon.com/AMD-YD170XBCAEWOF-Ryzen-1700X-Processor/dp/B06X3W9NGG" target="_blank">Ryzen 7 1700X &#8211; $399 &#8211; Amazon.com</a><br />
<a href="https://www.amazon.com/AMD-YD1700BBAEBOX-Processor-Wraith-Cooler/dp/B06WP5YCX6" target="_blank">Ryzen 7 1700 &#8211; $329 &#8211; Amazon.com</a></p>
<p><a href="https://www.amazon.com/ROG-Crosshair-VI-Hero-Motherboard/dp/B06W2L6GBX" target="_blank">ASUS ROG Crosshair VI Hero &#8211; $255 &#8211; Amazon.com</a><br />
<a href="https://www.amazon.com/Prime-X370-Pro-Ryzen-Motherboard-Lighting/dp/B06WD4N297" target="_blank">ASUS Prime X370-Pro &#8211; $170 &#8211; Amazon.com</a><br />
<a href="https://www.amazon.com/ASUS-Prime-B350-Plus-Ryzen-Motherboard/dp/B06X416NJ1" target="_blank">ASUS Prime B350-Plus &#8211; $99.99 &#8211; Amazon.com</a><br />
<a href="https://www.amazon.com/Prime-B350M-CSM-Ryzen-Motherboard/dp/B06WRWZNJC" target="_blank">ASUS Prime B350M-A/CSM &#8211; $89.99 &#8211; Amazon.com</a></p>
<p><a href="https://www.amazon.com/MSI-X370-XPOWER-GAMING-TITANIUM/dp/B06WLNZ1JH" target="_blank">MSI X370 XPOWER GAMING TITANIUM &#8211; $299.99</a></p>
<p><a href="https://www.amazon.com/Gigabyte-GIGABYTE-GA-AX370-Gaming-Motherboard-Motherboards/dp/B06WLMWYMF" target="_blank">Gigabyte GA-AX370-Gaming 5 &#8211; 194.99$</a><br />
<a href="https://www.amazon.com/Gigabyte-GIGABYTE-GA-AB350-Gaming-Motherboard-Motherboards/dp/B06VWHXK94" target="_blank">Gigabyte GA-AB350-Gaming 3 &#8211; 109.99$</a></p>
<h3><strong>Newegg:</strong></h3>
<p><a href="https://www.newegg.com/Product/Product.aspx?Item=N82E16819113430" target="_blank">AMD RYZEN 7 1800X 3.6 GHz (4.0 GHz Turbo)</a><br />
<a href="https://www.newegg.com/Product/Product.aspx?Item=N82E16819113429" target="_blank">AMD RYZEN 7 1700X 3.4 GHz (3.8 GHz Turbo)</a><br />
<a href="https://www.newegg.com/Product/Product.aspx?Item=N82E16819113428" target="_blank">AMD RYZEN 7 1700 3.0 GHz (3.7 GHz Turbo)</a></p>
<p><a href="https://www.newegg.com/Product/Product.aspx?Item=N82E16813138444" target="_blank">BIOSTAR X370GT7 &#8211; $209.99</a><br />
<a href="https://www.newegg.com/Product/Product.aspx?Item=N82E16813138445" target="_blank">BIOSTAR X370GT5 &#8211; $149.99</a><br />
<a href="https://www.newegg.com/Product/Product.aspx?Item=N82E16813138446" target="_blank">BIOSTAR B350GT5 &#8211; $129.99</a></p>
<p class="compact">Now, before anyone jumps the gun seeing all this and indulges in their fanboyish whims by pre-ordering, I urge you to remember that the only benchmark results available of Ryzen CPUs as of now are either from AMD themselves (which could be cherry picked) or from unofficial leaks (which could very well be fake). So, it would be better if you wait till some reviews of them show up. You did wait till now, what&#8217;s another 1.5-2 weeks.</p>
<p class="compact">You can have a look at the Ryzen Launch Event below:</p>
<div class="spaced video_wrap">
<iframe width="600" height="338" src="http://www.youtube.com/embed/1v44wWAOHn8" style="display: block; margin: auto;">&lt;br /&gt;<br />
</iframe>
</div>
<p>Source(s): <a href="https://www.pcper.com/news/Processors/AMD-Ryzen-Pre-order-Starts-Today-Specs-and-Performance-Revealed">pcper</a>, <a href="http://wccftech.com/amd-ryzen-7-1800x-1700x-official-launch/">wccftech</a>, <a href="http://www.legitreviews.com/amd-ryzen-pre-orders-start-today_191572">legitreviews</a></p>
<p>The post <a href="https://www.ocfreaks.com/amd-ryzen-official-release-pre-order/">AMD Ryzen Official Release and Pre Order</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/amd-ryzen-official-release-pre-order/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2646</post-id>	</item>
		<item>
		<title>ISRO creates history by launching 104 satellites in one go!</title>
		<link>https://www.ocfreaks.com/isro-launches-104-satellites/</link>
					<comments>https://www.ocfreaks.com/isro-launches-104-satellites/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Umang Gajera]]></dc:creator>
		<pubDate>Thu, 16 Feb 2017 05:06:52 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[news]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2636</guid>

					<description><![CDATA[<p>The Indian Space Research Organisation has created a history in space research by launching 104 satellites using its Polar Satellite Launch Vehicle (PSLV)-C37 (XL Variant).</p>
<p>The post <a href="https://www.ocfreaks.com/isro-launches-104-satellites/">ISRO creates history by launching 104 satellites in one go!</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img fetchpriority="high" decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/news/pslv_c37_launch.jpg" alt="pslv c37 launch" width="600" height="375" /></p>
<p>The Indian Space Research Organisation i.e. ISRO has created a history in space research by launching 104 satellites using its Polar Satellite Launch Vehicle (PSLV)-C37 (XL Variant). PSLV&#8217;s 39th flight successfully lifted off at 9.28am 15th Feb 2017 from Satish Dhawan Space Center in Sriharikota. The total weight of all the 104 satellites was 1378 kg.</p>
<p>Check out the official PSLV-C37 Lift off and On-board Camera Video below:</p>
<p><video style="margin-top: -10px; style="width:100% !important; height:auto !important;" poster="http://www.isro.gov.in/sites/default/files/videos/thumbnails/12142/c37-onboard.jpg" preload="auto" controls="controls"><source src="http://bhuvan3.nrsc.gov.in/2dresources/videos/pslv_c37.mp4" type="video/mp4" />Your browser does not support the video tag. Please update your browser to view the video.</video></p>
<p>This record was previously held by Russian Space Agency which launched 37 satellites in June 2014. Earlier in the same year America&#8217;s Orbital Sciences Corporation had launched 34 satellites in a single mission. In June 2016 ISRO had lauched 20 satellites in a single flight with its PSLV-C34.</p>
<p>The launched satellites include 714kg Cartosat-2 Series Satellite (which will be used for remote sensing) along with 103 co-passenger satellites. The pool of 103 co-passenger Sats on the PSLV-C37 has:<br />
1) ISRO Nano Satellite-1 (INS-1) &amp; INS-2 are from India which are technology demonstration satellites.<br />
2) 96 satellites from USA.<br />
3) One satellites each from The Netherlands, Switzerland, Israel, Kazakhstan and UAE.</p>
<p><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/news/pslv_c37.jpg" alt="pslv c37 launch" width="480" height="524" /></p>
<p>In 16 minutes 48 seconds the satellites achieved a polar Sun Synchronous Orbit of 506 km inclined at an angle of 97.46 degree to the equator and in the next 12 minutes, all the 104 satellites were successfully separated from the PSLV fourth stage in a predetermined sequence beginning with Cartosat-2 series satellite, followed by INS-1 and INS-2. In its offical post isro said:</p>
<blockquote><p>After separation, the two solar arrays of Cartosat-2 series satellite were deployed automatically and ISRO&#8217;s Telemetry, Tracking and Command Network (ISTRAC) at Bangalore took over the control of the satellite. In the coming days, the satellite will be brought to its final operational configuration following which it will begin to provide remote sensing services using its panchromatic (black and white) and multispectral (colour) cameras.</p></blockquote>
<p>Mayilsamy Annadurai (Director, Isro Satellite Centre) said:</p>
<blockquote><p>We can also hit centuries like our cricketers. In another two months, the number of satellites built by Isro will reach 100. Besides GSLV missions, we have get Chandrayan &#8211; 2 ready for launch next year.</p></blockquote>
<p>You can watch the complete lanuch video below:</p>
<div class="video_wrap"><iframe loading="lazy" width="600" height="400" src="http://www.youtube.com/embed/fujsQ5teHJI"></iframe></div>
<p class="spaced">
Sources: <a href="http://www.isro.gov.in/update/15-feb-2017/pslv-c37-successfully-launches-104-satellites-single-flight">ISRO</a> , <a href="http://timesofindia.indiatimes.com/india/isro-sets-history-launches-104-satellites-in-one-go/articleshow/57159734.cms">TOI</a> Image Source: ISRO</p>
<p>The post <a href="https://www.ocfreaks.com/isro-launches-104-satellites/">ISRO creates history by launching 104 satellites in one go!</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/isro-launches-104-satellites/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		<enclosure url="http://bhuvan3.nrsc.gov.in/2dresources/videos/pslv_c37.mp4" length="20724407" type="video/mp4" />

		<post-id xmlns="com-wordpress:feed-additions:1">2636</post-id>	</item>
		<item>
		<title>AMD Ryzen CPUs listed for online pre-order</title>
		<link>https://www.ocfreaks.com/amd-ryzen-cpu-listed-online-pre-order/</link>
					<comments>https://www.ocfreaks.com/amd-ryzen-cpu-listed-online-pre-order/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Saby D'silva]]></dc:creator>
		<pubDate>Wed, 15 Feb 2017 12:27:45 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[AMD]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[news]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2622</guid>

					<description><![CDATA[<p>AMD Ryzen CPUs have been seen listed for pre-order on multiple online stores with prices! </p>
<p>The post <a href="https://www.ocfreaks.com/amd-ryzen-cpu-listed-online-pre-order/">AMD Ryzen CPUs listed for online pre-order</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" src="https://www.ocfreaks.com/imgs/common_title/amd_ryzen.jpg" width="375px" height="291px" class="aligncenter" /></p>
<p><strong>New Update on AMD Ryzen:</strong> <a href="https://www.ocfreaks.com/amd-ryzen-official-release-pre-order/">Official release, Benchmarks and pre-order list</a></p>
<p>With the launch of AMD&#8217;s new Ryzen CPUs inching closer, more and more information is surfacing about them online. Not even two days past the leak about the the full lineup and pricing, Ryzen CPUs have been seen listed for pre-order on multiple online stores, with a Thai retailer revealing the legit box-art. Have a look.</p>
<p><img decoding="async" src="https://www.ocfreaks.com/imgs/news/ryzen_thai_prices_boxart.jpg" width="600px" height="754px" class="aligncenter" /></p>
<p style="text-align:right; font-size:13px;">Source: <a href="http://wccftech.com/amd-ryzen-processor-box-pre-order/">Wccftech</a> </p>
<p>AMD has chosen to go with a &#8220;less is more&#8221; approach for their box art, consisting of a black background with the Ryzen logo in the middle. A small AMD logo can be seen right below the Ryzen logo, and on the top-right corner of the package. The left side of the box contains a short passage giving the features of the processor. Judging from the thickness of the package, it is fair to say that the CPU cooler will be bundled along with the processor. The coolers look amazing, complete with RGB lighting (apparently the biggest innovation of the year 2016 😀 ) From all the praise the new AMD stock coolers (Wraith) have been getting, this is a good move by AMD, as it could allow the XFR enabled processors to reach higher clock speeds.</p>
<p><img decoding="async" src="https://www.ocfreaks.com/imgs/news/ryzen_coolers.jpg" width="600px" height="754px" class="aligncenter" /></p>
<p>The prices listed here are a bit on the higher side. The final pricing is expected to be lower than this(according to the leaks, anyway). A Belgian retailer (<a href="http://www.centralpoint.be">Centralpoint.be</a>) also has listed Ryzen 7 CPUs as available for pre-order. Heres the list:</p>
<table class="aligncenter compact">
<tbody>
<tr style="border-top:1px solid #999;">
<th style="border-right:1px solid #999;border-left:1px solid #999;">Model SKU</th>
<th style="border-right:1px solid #999;">Price exc. VAT(in €)</th>
<th style="border-right:1px solid #999;">Price inc. VAT(in €)</th>
</tr>
<tr>
<td style="text-align: center">AMD: Ryzen 7 1700 3.7GHZ 8 CORE 65W<br />(Product Id: YD1700BBM88AE)</td>
<td style="text-align: center;">319</td>
<td style="text-align: center;">386</td>
</tr>
<tr>
<td style="text-align: center">AMD: Ryzen 7 1700 3.7GHZ 8 CORE 65W<br />(Product Id: YD1700BBAEMPK)</td>
<td style="text-align: center;">319</td>
<td style="text-align: center;">386</td>
</tr>
<tr>
<td style="text-align: center">AMD: Ryzen 7 1700X 3.8GHz 8 CORE<br />(Product Id: YD170XBCM88AE)</td>
<td style="text-align: center;">389</td>
<td style="text-align: center;">471</td>
</tr>
<tr>
<td style="text-align: center">AMD: Ryzen 7 1700X 3.8GHz 8 CORE<br />(Product Id: YD170XBCAEMPK)</td>
<td style="text-align: center;">409</td>
<td style="text-align: center;">495</td>
</tr>
<tr>
<td style="text-align: center">AMD: Ryzen 7 1800x 4.0GHZ 8 CORE<br />(Product Id: YD180XBCM88AE)</td>
<td style="text-align: center;">499</td>
<td style="text-align: center;">604</td>
</tr>
<tr>
<td style="text-align: center">AMD: Ryzen 7 1800x 4.0GHZ 8 CORE<br />(Product Id: YD180XBCAEMPK)</td>
<td style="text-align: center;">519</td>
<td style="text-align: center;">628</td>
</tr>
</tbody>
</table>
<p style="text-align:right; font-size:13px;">Source: <a href="http://www.centralpoint.be">Centralpoint.be</a> via <a href="http://wccftech.com/amd-ryzen-7-1800x-1700x-1700/">Wccftech</a> </p>
<p>What intrigues me here is that they have two SKU listings for each part, with a €20 price difference between the two SKUs (for the same product), except for the R7 1700, whose two SKUs are priced the same too. Maybe they&#8217;ve messed up on the naming.The pricing given here is closer to what the leaked pricing suggests.</p>
<p>The Ryzen CPUs are expected to be released at Feb 28th 2017 &#8211; the same date AMD will host its &#8216;Capsaicin &#038; Cream'(GDC) 2017 press event.</p>
<p>Source(s): <a href="http://wccftech.com/amd-ryzen-7-1800x-1700x-1700/">Wccftech(1)</a> <a href="http://wccftech.com/amd-ryzen-processor-box-pre-order/">Wccftech(2)</a></p>
<p>The post <a href="https://www.ocfreaks.com/amd-ryzen-cpu-listed-online-pre-order/">AMD Ryzen CPUs listed for online pre-order</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/amd-ryzen-cpu-listed-online-pre-order/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2622</post-id>	</item>
		<item>
		<title>AMD&#8217;s Ryzen CPU lineup specs and other details out prior release</title>
		<link>https://www.ocfreaks.com/amd-ryzen-cpu-lineup-specs-details/</link>
					<comments>https://www.ocfreaks.com/amd-ryzen-cpu-lineup-specs-details/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Saby D'silva]]></dc:creator>
		<pubDate>Mon, 13 Feb 2017 14:10:39 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[AMD]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[news]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2609</guid>

					<description><![CDATA[<p>Details emerged about AMD new "Ryzen" series of processors out prior to its official release. The price to performance ratio seems promising. Fingers crossed!</p>
<p>The post <a href="https://www.ocfreaks.com/amd-ryzen-cpu-lineup-specs-details/">AMD&#8217;s Ryzen CPU lineup specs and other details out prior release</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" src="https://www.ocfreaks.com/imgs/common_title/amd_ryzen.jpg" width="375px" height="291px" class="aligncenter" /></p>
<p><strong>New Update on AMD Ryzen:</strong> <a href="https://www.ocfreaks.com/amd-ryzen-official-release-pre-order/">Official release, Benchmarks and pre-order list</a></p>
<p>Some new details have emerged about AMD&#8217;s new &#8220;Ryzen&#8221; series of processors, and it is astounding to say the least. This new information is leaked from the internal product listing of a Chinese retailer. Without further ado, here are the  details:</p>
<p><img decoding="async" src="https://www.ocfreaks.com/imgs/news/ryzen_specs_leak.jpg" class="aligncenter" /></p>
<p style="text-align:right; font-size:13px;">Source: <a href="http://tieba.baidu.com/p/4975965039">Baidu</a> </p>
<p>Here&#8217;s a table translated to English and with prices normalised for USD:</p>
<table class="aligncenter compact">
<thead style="border-top:1px solid #999;">
<tr>
<th style="border-right:1px solid #999;border-left:1px solid #999;">AMD Ryzen CPU</th>
<th style="border-right:1px solid #999;">Cores/Threads</th>
<th style="border-right:1px solid #999;">L3</th>
<th style="border-right:1px solid #999;">TDP</th>
<th style="border-right:1px solid #999;">Base</th>
<th style="border-right:1px solid #999;">Turbo</th>
<th style="border-right:1px solid #999;">XFR</th>
<th style="border-right:1px solid #999;">Overclocking<br />Unlocked</th>
<th style="border-right:1px solid #999;">Price</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:center;">AMD Ryzen 7 1800X</td>
<td style="text-align:center;">8/16</td>
<td style="text-align:center;">16MB</td>
<td style="text-align:center;">95W</td>
<td style="text-align:center;">3.6GHz</td>
<td style="text-align:center;">4.0GHz</td>
<td style="text-align:center;">4.0GHz+</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$499</td>
</tr>
<tr>
<td style="text-align:center;">AMD Ryzen 7 1700X</td>
<td style="text-align:center;">8/16</td>
<td style="text-align:center;">16MB</td>
<td style="text-align:center;">95W</td>
<td style="text-align:center;">3.4GHz</td>
<td style="text-align:center;">3.8GHz</td>
<td style="text-align:center;">3.8GHz+</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$389</td>
</tr>
<tr>
<td style="text-align:center;">AMD Ryzen 7 1700</td>
<td style="text-align:center;">8/16</td>
<td style="text-align:center;">16MB</td>
<td style="text-align:center;">65W</td>
<td style="text-align:center;">3.0GHz</td>
<td style="text-align:center;">3.7GHz</td>
<td style="text-align:center;">N/A</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$319</td>
</tr>
<tr>
<td style="text-align:center;">AMD Ryzen 5 1600X</td>
<td style="text-align:center;">6/12</td>
<td style="text-align:center;">16MB</td>
<td style="text-align:center;">95W</td>
<td style="text-align:center;">3.3GHz</td>
<td style="text-align:center;">3.7GHz</td>
<td style="text-align:center;">3.7GHz+</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$259</td>
</tr>
<tr>
<td style="text-align:center;">AMD Ryzen 5 1500</td>
<td style="text-align:center;">6/12</td>
<td style="text-align:center;">16MB</td>
<td style="text-align:center;">65W</td>
<td style="text-align:center;">3.2GHz</td>
<td style="text-align:center;">3.5GHz</td>
<td style="text-align:center;">N/A</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$229</td>
</tr>
<tr>
<td style="text-align:center;">AMD Ryzen 5 1400X</td>
<td style="text-align:center;">4/8</td>
<td style="text-align:center;">8MB</td>
<td style="text-align:center;">65W</td>
<td style="text-align:center;">3.5GHz</td>
<td style="text-align:center;">3.9GHz</td>
<td style="text-align:center;">3.9GHz+</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$199</td>
</tr>
<tr>
<td style="text-align:center;">AMD Ryzen 5 1300</td>
<td style="text-align:center;">4/8</td>
<td style="text-align:center;">8MB</td>
<td style="text-align:center;">65W</td>
<td style="text-align:center;">3.2GHz</td>
<td style="text-align:center;">3.5GHz</td>
<td style="text-align:center;">N/A</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$175</td>
</tr>
<tr>
<td style="text-align:center;">AMD Ryzen 3&nbsp;1200X</td>
<td style="text-align:center;">4/4</td>
<td style="text-align:center;">8MB</td>
<td style="text-align:center;">65W</td>
<td style="text-align:center;">3.4GHz</td>
<td style="text-align:center;">3.8GHz</td>
<td style="text-align:center;">3.8GHz+</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$149</td>
</tr>
<tr>
<td style="text-align:center;">AMD Ryzen 3&nbsp;1100</td>
<td style="text-align:center;">4/4</td>
<td style="text-align:center;">8MB</td>
<td style="text-align:center;">65W</td>
<td style="text-align:center;">3.2GHz</td>
<td style="text-align:center;">3.5GHz</td>
<td style="text-align:center;">N/A</td>
<td style="text-align:center;">Yes</td>
<td style="text-align:center;">$129</td>
</tr>
</tbody>
</table>
<p style="text-align:right; font-size:13px;">Source: <a href="http://wccftech.com/amd-ryzen-full-lineup-pricing-clock-speeds-leaked/">Wccftech</a> </p>
<p>Okay, now let&#8217;s analyze the details in the table. According to the leaks, AMD would be releasing Ryzen in 4C/4T(R3), 4C/8T(R5), 6C/12T(R5) and 8C/16T(R7) variants. All of these configs are further subdivided into Normal edition and &#8220;X&#8221;(Whatever cheesy name AMD comes up with) edition chips that are clocked higher, have a higher TDP and have XFR enabled. XFR is AMD&#8217;s version of Enhanced Auto Overclocking (to be introduced with Ryzen), that allows the chip to be clocked at frequencies higher than the Turbo boost speed, should your cooling solution be able to handle it. The whole process is automated and does not require any user intervention. </p>
<p>At the top of the chart are the R7 variants (Enthusiast and Professional Grade). Among these, the 1800X and 1700X are 8C/16T CPUs with 16 MB L3 cache and a TDP of 95 W. The only difference between these (apparently) is that the 1800X has a higher Stock Clock and Turbo Boost by a margin of 200MHz, for which it carries 110$ higher price than the latter. <a href="http://wccftech.com/amd-ryzen-7-1700x-389-8-core-cpu-benchmarks-leaked/">Previously leaked benchmarks</a> have shown the 8C/16T Ryzen variants literally obliterating the i7 7700k (Kaby Lake); which is a 350$ chip. Also, AMD themselves have demoed benchmarks (in their new horizon event) showing the same chip (clocked at 3.4 GHz w. Turbo disabled, ie, SLOWER than the released chips) going toe-to-toe against the 1100$ 6900k (Broadwell-E). So, it&#8217;s really surprising to see the top of the line Ryzen CPU priced at less than half the price of it&#8217;s direct competitor. A price that is in fact closer to the 4C/8T Intel Chip (7700K). At this price point, AMD need not even compete on performance to the Intel counterpart. Any person with a slim budget could sense the much better deal that AMD is offering. But if it does in fact compete, well, it would be a huge icing on the cake for consumers and a big blow to Intel. Below this is the R7 1700 which has a lower Stock Clock of 3 GHz without XFR, and with a lower TDP of 65W. </p>
<p>Moving lower, the R5 variants are mid range CPUs that are either 4C/8T or 6C/12T, with both  having &#8220;X&#8221; edition and Normal chips. These are priced between 175 &#8211; 260$. 259$ for the 6C/12T variant with XFR(R5 1600X) and 175$ for the 4C/8T variant without XFR(R5 1300). These would be going against the Core i5 CPUs of Intel, whose top performer is priced closer to the 1600X.</p>
<p>All 8C/16T and 6C/12T CPUs will have 16MB of L3 Cache. Below this, all CPUs will have 8MB of L3 Cache</p>
<p>At the lower end of the spectrum are the R3 variants, that are 4C/4T with and without XFR. The R3 1200X(hope you understand the naming convention. I won&#8217;t be going through it again!!!) is priced at 149$ and the R3 1100 is priced at 129$. These would be going against the i3 CPUs.</p>
<p>All the Ryzen CPUs will have unlocked multipliers. Whether or not a system built around Ryzen is OCable will depend on the Motherboard chipset (Motherboards with X370 and B350 chipsets support Overclocking. Those with X320 and X/B/A300 chipsets dont).</p>
<p>One thing I don&#8217;t get is why AMD is abandoning (OK, strong word, but you get the point) the sub 100$ market. That could&#8217;ve been a huge get for AMD, if it would have released a Dual Core Variant to compete with Intel&#8217;s Pentiums. After all, who needs a premium range CPU for office work? I hope for their own sake they do come up with something for this segment.</p>
<p>Coming back to the point of the post, let me say that if AMD does price their CPUs close to what this leak suggests and does compete in performance, Intel would have to seriously up their game (or increase their marketing budget, whatever works for them :-)) to stay relevant in the market.</p>
<p>P.S., how very refreshing it is to see AMD CPUs have a TDP close to that of the Intel CPUs?!?!</p>
<p>Source(s): <a href="http://wccftech.com/amd-ryzen-full-lineup-pricing-clock-speeds-leaked/">Wccftech</a> and <a href="http://tieba.baidu.com/p/4975965039">Baidu</a></p>
<p>The post <a href="https://www.ocfreaks.com/amd-ryzen-cpu-lineup-specs-details/">AMD&#8217;s Ryzen CPU lineup specs and other details out prior release</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/amd-ryzen-cpu-lineup-specs-details/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2609</post-id>	</item>
		<item>
		<title>SoundMagic ES18S Earphone Review</title>
		<link>https://www.ocfreaks.com/soundmagic-es18s-earphone-review/</link>
					<comments>https://www.ocfreaks.com/soundmagic-es18s-earphone-review/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Saby D'silva]]></dc:creator>
		<pubDate>Sat, 04 Feb 2017 12:37:10 +0000</pubDate>
				<category><![CDATA[Reviews]]></category>
		<category><![CDATA[audio]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[Review]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2593</guid>

					<description><![CDATA[<p>A review of Soundmagic's entry level earphone - the ES18S.</p>
<p>The post <a href="https://www.ocfreaks.com/soundmagic-es18s-earphone-review/">SoundMagic ES18S Earphone Review</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p class="compact" style="padding-top: 10px;">The low to mid range segment is  the most crowded segment in the earphone category. Unfortunately,  it has also for a long time been the most lacking in terms of performance. This particular segment accounts for a large portion of the earphone market, and just because a pair of earphones are cheap doesn&#8217;t mean it needs to sound so!!! Though some might consider it illogical on my part, but hey,  that&#8217;s just me&#8230;</p>
<p class="compact">The past few years has seen a drift in this scenario, with a few OEMs consistently pushing out high performance earphones that also won&#8217;t put much of a burden on your wallets. Soundmagic is one of these brands.  It&#8217;s E10S has repeatedly been awarded best budget earphone awards from multiple highly reputed sources. This, however,  is a review of Soundmagic&#8217;s cheapest offering,  the ES18S.</p>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Specifications:</h2>
<table style="width: 400px; height: 350px">
<tr>
<td style="vertical-align: middle";><b>Wearing Style</b></td>
<td style="vertical-align: middle";>Intraaural (in the ear)</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Driver Type</b></td>
<td style="vertical-align: middle";>Dynamic, Neodymium</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Driver Size</b></td>
<td style="vertical-align: middle";>10mm</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Frequency range</b></td>
<td style="vertical-align: middle";>15Hz &#8211; 22kHz</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Impedance</b></td>
<td style="vertical-align: middle";>16Ohms</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Sensitivity</b></td>
<td style="vertical-align: middle";>100dB</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Cable length</b></td>
<td style="vertical-align: middle";>1.2m</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Connector</b></td>
<td style="vertical-align: middle";>Gold-plated 3.5mm straight plug</td>
</tr>
<tr>
<td style="vertical-align: middle";><b>Weight</b></td>
<td style="vertical-align: middle";>11g</td>
</tr>
</table>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Packing and Accessories:</h2>
<p class="compact">ES18S comes in a thermoformed plastic clamshell package within a printed cardboard cover. With the earphones we get 3 pairs of silicone earbuds, a rather nice black pouch and a clip. Nothing more to say here.</p>
<div class="compact image" style="display:inline-block; float:left;">
<a href="https://www.ocfreaks.com/imgs/review/es18s/packing_front.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/es18s/packing_front.jpg" alt="Packing_Front"  width="320px"></a>
</div>
<div class="compact image" style="display:inline-block; float:right;">
<a href="https://www.ocfreaks.com/imgs/review/es18s/packing_back.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/es18s/packing_back.jpg" alt="Packing_Back"  width="320px"></a>
</div>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/review/es18s/packing_inside.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/es18s/packing_inside.jpg" alt="Packing_Inside" height="800px" width="600px"></a>
</div>
<p style="text-align: center;"><i>Packing</i></p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/review/es18s/accessories.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/es18s/accessories.jpg" alt="Accessories" height="485px" width="600px"></a><i>Accessories</i>
</div>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Build Quality:</h2>
<p class="compact">The ES18S has an inline mic and a single button remote for call accept/end and play/pause. A unique feature in these earphones is a CTIA-OMTP(read more about about 3.5mm audio jack <a href="https://www.ocfreaks.com/3-5mm-earphone-connector-compatibility-issue/">here</a>) switch,  which ensures that this earphone would be compatible with all phones sporting a 3.5 mm jack. Although a pretty noble feature, I do have one issue with this. The switch doesn&#8217;t really appear to be of that great a quality,  and if it gets damaged,  it could possibly render the earphone useless. So I&#8217;d suggest you to stick with a position, and not to over(ab)use this switch. If you do want to use this earphone in both modes, a better solution would be to use an adapter. This way, the solution would be independent of the earphones,  and you could use it with other earphones as well. The drivers used in the ES18s are housed in a Plastic Casing, with small L and R markings. The cable, although silicone, does have a fair bit of memory. I suggest wrapping the cables over under to avoid the cable getting mangled up(I actually suggest doing this with every cable. But in cables with memory,  this is especially a must).</h2>
<div class="spaced image" style="display: inline-block;">
<a href="https://www.ocfreaks.com/imgs/review/es18s/3.5mm_trrs_jack.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/es18s/3.5mm_trrs_jack.jpg" alt="3.5mm TRRS Jack" height="296px" width="222px"></a><i>3.5mm TRRS Jack</i>
</div>
<div class="spaced image" style="display: inline-block;">
<a href="https://www.ocfreaks.com/imgs/review/es18s/inline_mic_w_remote.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/es18s/inline_mic_w_remote.jpg" alt="Mic with Single Button Remote" height="296px" width="222px"></a><i>Mic with Single Button Remote</i>
</div>
<div class="spaced image" style="display: inline-block;">
<a href="https://www.ocfreaks.com/imgs/review/es18s/ctia-omtp_switch.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/review/es18s/ctia-omtp_switch.jpg" alt="CTIA-OMTP Switch" height="296px" width="222px"></a><i>CTIA-OMTP Switch</i>
</div>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Performance:</h2>
<p class="compact">The performance of this earphone impressed me in a lot of ways. But it does have its own quirks. The bass response is too good,  and much better than what other earphones (that I&#8217;m aware of) offer at this price range. The mids and highs, however, are a slight letdown. It&#8217;s not that the ES18S has poor mid frequency and treble performance. The mids are OK, ie,  they are not muddied or anything, but they aren&#8217;t that impressive as well. The treble response, on the other hand, is actually really good. Just the right amount without being harsh on the ears. So, why did I say it&#8217;s a slight letdown?</h2>
<p class="compact">Well, the bass response is slightly (mind you,  REALLY SLIGHTLY) overpowering, and covers the mids and highs in some places. But believe me, unless you&#8217;re a treblehead and prefer your highs a little on the harsher side, it&#8217;s highly unlikely you&#8217;ll ever notice it. With most earphones at this price offering Pathetic (and I do mean Pathetic, with a capital P!) treble response to say the least, I guess I cant really complain much. I suppose SoundMagic took the easy way out here to overcome sibilance.</p>
<p class="compact">The Soundstage on these earphones are a bit on the narrower side, but we cant really have everything now, can we?!?! Besides, I really dont think you should be looking for a low end IEM if you really are concerned about the soundstage performance.</p>
<p class="compact">The inline Mic in these earphone are average. They provide more than adequate performance for a phone call, which is the primary reason they are included anyways.</p>
<h2 class="shead" style="padding-top: 15px; margin-bottom: 20px;">Conclusion:</h2>
<p class="compact">All things said, the ES18S does offer exceptional value for money. Would I recommend these as a High Performance Primary earphone? Depends on what your budget is. Would I recommend these as a cheap on the go earphone? In a Heartbeat.</p>
<div class="highlight spaced">
<div style="width: 295px; display: inline-block; vertical-align:top; padding-right: 15px; border-right: dotted #777 1px;">
<h3>Pros:</h3>
<ul style="padding-left:20px">
<li>Great Bass Response</li>
<li>Comes with an inline Mic</li>
<li>Pouch included</li>
<li>Excellent Value for Money</li>
</ul>
</div>
<div style="width: 295px; display: inline-block; vertical-align:top; padding-left: 15px; padding-right: 15px;">
<h3>Cons:</h3>
<ul style="padding-left:20px">
<li>Underwhelming mid frequency response</li>
<li>Slightly overpowering Bass</li>
<li>Average Build quality.</li>
</ul>
</div>
<p style="clear: both; padding-top:15px; margin-bottom:10px"><strong>Rating: 4.5/5<br />
Highly recommended as a Budget Earphone!</strong></p>
</div>
<p>The post <a href="https://www.ocfreaks.com/soundmagic-es18s-earphone-review/">SoundMagic ES18S Earphone Review</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/soundmagic-es18s-earphone-review/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2593</post-id>	</item>
		<item>
		<title>Handbrake Tutorial Part 2: x264 Advanced Encoding &#038; Compression Settings Guide</title>
		<link>https://www.ocfreaks.com/handbrake-tutorial-part-2-x264-advanced-encoding-compression-settings-guide/</link>
					<comments>https://www.ocfreaks.com/handbrake-tutorial-part-2-x264-advanced-encoding-compression-settings-guide/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Saby D'silva]]></dc:creator>
		<pubDate>Thu, 02 Feb 2017 08:09:27 +0000</pubDate>
				<category><![CDATA[Guides & Tutorials]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[guide]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[video]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2586</guid>

					<description><![CDATA[<p>An in-depth Guide/Tutorial explaining all the x264 intricacies and advanced settings offered in handbrake advanced tab. The settings in this tab are for those who like to tweak and fine tune the encoder's settings for the video.</p>
<p>The post <a href="https://www.ocfreaks.com/handbrake-tutorial-part-2-x264-advanced-encoding-compression-settings-guide/">Handbrake Tutorial Part 2: x264 Advanced Encoding &#038; Compression Settings Guide</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="spaced tocpostimage">
<img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/hbx264.jpg" alt="x264 in Handbrake" height="256px" width="256px">
</div>
<p class="compact" style="clear: left; float:left">Some of you might find it odd that I made a separate post to talk about the settings in the Advanced tab of Handbrake. But rest assured, there’s a damn good reason why I chose to do so. The first tutorial was targeted at beginners. In essence, I’d say that the first tutorial was 80% handbrake and 20% some general info about videos and encoding. This tutorial would be about 20% Handbrake and 80% x264 video encoding and compression, as you need to know a fair bit about how x264 encodes video to completely understand the options in this tab.</p>
<div class="toc_container"><span class="toc_title">Table of Contents</span></p>
<div class="toc">
<ol class="toc_list">
<li class="toc_text"><a href="#x264_Video_Encoding" title="x264 Video Encoding"><span>1. </span><span>x264 Video Encoding</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Eliminating_Redundancies" title="Eliminating Redundancies"><span>1.1. </span><span>Eliminating Redundancies</span></a></li>
<li class="toc_text"><a href="#Rate_Factor_vs_Quantization_Parameter" title="Rate Factor vs Quantization Parameter"><span>1.2. </span><span>Rate Factor vs Quantization Parameter</span></a></li>
</ol>
<li class="toc_text"><a href="#Advanced_Tab" title="Advanced Tab"><span>2. </span><span>Advanced Tab</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Encoding" title="Encoding"><span>2.1. </span><span>Encoding</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Reference_Frames" title="Reference Frames"><span>2.1.1. </span><span>Reference Frames</span></a></li>
<li class="toc_text"><a href="#Maximum_B_Frames" title="Maximum B Frames"><span>2.1.2. </span><span>Maximum B Frames</span></a></li>
<li class="toc_text"><a href="#Pyramidal_B_Frames" title="Pyramidal B Frames"><span>2.1.3. </span><span>Pyramidal B Frames</span></a></li>
<li class="toc_text"><a href="#Weighted_P_Frames" title="Weighted P Frames"><span>2.1.4. </span><span>Weighted P Frames</span></a></li>
<li class="toc_text"><a href="#8x8_Transform" title="8x8 Transform"><span>2.1.5. </span><span>8&#215;8 Transform</span></a></li>
<li class="toc_text"><a href="#CABAC" title="CABAC"><span>2.1.6. </span><span>CABAC</span></a></li>
</ol>
<li class="toc_text"><a href="#Analysis" title="Analysis"><span>2.2. </span><span>Analysis</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Adaptive_B_Frames" title="Adaptive B Frames"><span>2.2.1. </span><span>Adaptive B Frames</span></a></li>
<li class="toc_text"><a href="#Adaptive_Direct_Mode" title="Adaptive Direct Mode"><span>2.2.2. </span><span>Adaptive Direct Mode</span></a></li>
<li class="toc_text"><a href="#Subpixel_Motion_Est(subme)" title="Subpixel Motion Est(subme)"><span>2.2.3. </span><span>Subpixel Motion Est(subme)</span></a></li>
<li class="toc_text"><a href="#Motion_Est_Method" title="Motion Est Method"><span>2.2.4. </span><span>Motion Est Method</span></a></li>
<li class="toc_text"><a href="#Motion_Est_Range(merange)" title="Motion Est Range(merange)"><span>2.2.5. </span><span>Motion Est Range(merange)</span></a></li>
<li class="toc_text"><a href="#Partition_Type" title="Partition Type"><span>2.2.6. </span><span>Partition Type</span></a></li>
<li class="toc_text"><a href="#Trellis" title="Trellis"><span>2.2.7. </span><span>Trellis</span></a></li>
</ol>
<li class="toc_text"><a href="#Psychovisual" title="Psychovisual"><span>2.3. </span><span>Psychovisual</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#No_DCT_Decimate" title="No DCT Decimate"><span>2.3.1. </span><span>No DCT Decimate</span></a></li>
<li class="toc_text"><a href="#Adaptive_Quant_Strength" title="Adaptive Quant Strength"><span>2.3.2. </span><span>Adaptive Quant Strength</span></a></li>
<li class="toc_text"><a href="#Psychovisual_Rate_Distortion" title="Psychovisual Rate Distortion"><span>2.3.3. </span><span>Psychovisual Rate Distortion</span></a></li>
<li class="toc_text"><a href="#Psychovisual_Trellis" title="Psychovisual Trellis"><span>2.3.4. </span><span>Psychovisual Trellis</span></a></li>
<li class="toc_text"><a href="#Deblocking" title="Deblocking"><span>2.3.5. </span><span>Deblocking</span></a></li>
</ol>
</ol>
<li class="toc_text"><a href="#Closing_Notes" title="Closing Notes"><span>3. </span><span>Closing Notes</span></a></li>
</ol>
</div>
</div>
<p class="compact">Before going any further, let me make this clear; most users won’t need to mess around with these settings. The settings in this tab are just for those few users who like to tweak and fine tune the encoder&#8217;s settings for the video. You can get a decent output without using this tab.</p>
<div class="special sp_blue notestar spaced">
<strong>Note:</strong> I highly recommend you to go through my article on<a href="https://www.ocfreaks.com/beginners-guide-tutorial-video-redundancies/" target="_blank"> Video Redundancies </a>. I&#8217;ve written it as a precursor to this tutorial.
</div>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="x264_Video_Encoding">x264 Video Encoding</span></h2>
<p class="compact">x264 is, as of now, the most popular and widely regarded as the best video encoder out there. No other encoder comes close to it in terms of quality at a given bitrate, and it is compatible with most devices too. Let us see now what it is that makes this codec so good.</p>
<h3 class="msize" style="padding-top: 5px; text-decoration: underline"><span id="Eliminating_Redundancies">Eliminating Redundancies</span></h3>
<p class="compact">To those who dont know the various redundancies that exist in a video and why eliminating them is important, check out: <a href="https://www.ocfreaks.com/beginners-guide-tutorial-video-redundancies/" target="_blank"> Video Redundancies </a>.</p>
<p class="compact">To eliminate spatial and temporal redundancies, each <a href="https://www.ocfreaks.com/handbrake-complete-tutorial-part-1-transcode-compress-videos/#Modulus" target="_blank"><strong>macroblock</strong></a> in a frame is scanned first to identify the redundant information. These redundant information are then predicted by using various algorithms and are replaced by the <strong>&#8220;predicted</strong>&#8221; blocks, which ultimately results in a much smaller file size. Two kinds of prediction are used by x264 to predict the macroblocks in a frame:</p>
<div class="highlight spaced">
<ol class="emplist">
<li class="spaced"><b>Intra Frame Prediction:</b> Macroblocks are predicted by using previously encoded data in the <strong>current frame</strong>. This is used for eliminating <strong>spatial redundancies</strong>. A prediction for the current block is formed from the previously encoded neighbouring blocks.
</li>
<li>
<p class="nl"><b>Inter Frame Prediction:</b> Macroblocks are predicted by using previously encoded data in the <strong>neighbouring frames</strong>. This is used for eliminating <strong>temporal redundancies</strong>. It is also known as <strong>Motion Estimation</strong>. This prediction is done by scanning the corresponding block that is already encoded in the neighbouring frames. The similar blocks are considered to be the <strong>static</strong> part of the scene(the &#8220;background&#8221;), while the differing blocks are collectively considered to be the <strong>active</strong>(&#8220;moving&#8221;) part in the scene. The output is then, a video that is comprised of <strong>reference frames</strong>, which contains the static and active parts, and <strong>predicted frames</strong> which consists of the moving parts overlaid on the background to recreate the scene, frame by frame.</p>
<p class="compact">So basically, what happens here is that the static parts in the scene are copied as it is from the reference frame to the predicted frame. And for the active parts, a <strong>motion vector</strong> is calculated to change their position from that of the reference frame to that of the predicted frame. This process is called <strong>Motion Compensation</strong>. So, the predicted frame, in this sense, directly or indirectly depends on the reference frame, and would take up much less space than what it would if the entire frame was stored.</p>
</li>
</ol>
</div>
<p class="compact">H.264 standard defines 3 types of frames that can be used by the codec. These are:</p>
<div class="highlight spaced">
<ol class="emplist">
<li class="spaced"><b>I Frame:</b> I frame (Intra Frame) is nothing but the frame copied as it is from the source. It is completely independent of other frames in the video stream, and can be decoded without reference from the other frames. The frame is encoded by using only <strong>Intra Frame Prediction</strong>. The more the number of I frames in the video, the better the quality, but the lower the compression. I frames are used in H.264 in the start of the video file or in a rapid scene change.</li>
<li class="spaced"><b>P Frame:</b> P Frames(Predicted Frames) are frames that are dependent on previous I or P frames. These frames only hold the information about the moving part in the scene, by using <strong>Inter Frame Prediction</strong>. On an average, it can be said to contain about 50% the information contained on an I frame.</li>
<li><b>B Frame:</b> B Frames(Bidirectional Predicted Frames) are frames that are dependent on both previous as well as future I and P frames. These frames, similar to P frames, only hold the information about the moving part in the scene. On an average, it can be said to contain about 50% the information contained on a P frame.</li>
</ol>
</div>
<p class="compact">The way the encoder arranges these frames together is called <strong>GOP(Group Of Pictures)</strong>, starting with the I frame at the beginning. This, in turn is made up of <strong>mini GOPs</strong> beginning with a P/B frame.  Now, consider an I frame to be of size x, a P frame 0.5x, and B frame 0.25x. For the following GOPs:</p>
<p class="compact">IIII: Size=4x<br />
IPPP: Size=2.5x<br />
IBBP: Size=2x</p>
<p class="compact">The advantages of using predicted frames are quite evident from the above example.</p>
<div class="special sp_blue notestar spaced">
<b>Note:</b> As B frames need both previous and future frames as reference, the order of encoding for the third GOP in the above example would actually be: IPBB. After the I and P frames are encoded, the B frames would be encoded and put in between them. It should also be noted that many devices have a limitation on the maximum number of B frames that can be used(since decoding of B frames require a lot of computational power). Regardless of all these, the beginning of a GOP will always be signalled by an I frame.
</div>
<p class="compact">Once the predicted frames are formed (by either Intra or Inter prediction), each block in it is subtracted from the ones in the actual frame to form the <strong>residual block</strong>. These residual blocks are then transformed using either order 4 or order 8 <strong>integer transform</strong> to output a stream of coefficients for each block. The <strong>transformed coefficients</strong> are then <strong>quantized</strong>, ie, scaled by a value obtained from the <strong>Quantization Parameter</strong>(QP). The basic idea is to reduce the value of the coefficient as much as possible. The QP defines by what extent each block is to be compressed. Higher QP values mean more compression but lower quality, and lower values mean less compression but higher quality. The quantized blocks are then <strong>entropy coded</strong> to finally obtain the output video file. This is a form of lossless compression method that is done at the end, to eliminate the coding redundancies.</p>
<h3 class="msize" style="padding-top: 5px; text-decoration: underline"><span id="Rate_Factor_vs_Quantization_Parameter">Rate Factor vs Quantization Parameter</span></h3>
<p class="compact">One difference that you can observe when encoding videos (in Handbrake) using x264 in Constant Quality mode is that; while all other codecs will offer you a<strong> QP (Quantization Parameter)</strong> Slider, x264(and x265) will offer you an <strong>RF (Rate Factor)</strong> Slider. There is quite an inherent difference between the two.</p>
<p class="compact">Constant Quality encoding can be achieved by two ways:</p>
<div class="highlight spaced">
<ol class="emplist">
<li class="spaced">
<p class="nl"><b>Constant Quantization Parameter (CQP):</b> In this method, constant quality is achieved by compressing every frame of the same type by the same amount, ie, a constant QP is maintained for the entire video. So, if the QP slider is kept at 24, it will remain 24 for the entire video.</p>
<p class="compact">The QP slider scale is linear, and the output filesize would change linearly with the QP value.</p>
</li>
<li class="spaced">
<p class="nl"><b>Constant Rate Factor (CRF):</b> In this method, the QP is not kept constant throughout the video, but will be variable. Thus, different frames are compressed by different amounts, depending on the amount of detail and motion on the frame. CRF takes advantage of the simple fact that the eye perceives more detail in stationary objects than in moving objects. So, it applies more compression for fast motion scenes, and less compression for still scenes. Due to this, the output video will appear to be much more detailed. So, if the RF slider is kept at 24, then the QP might range from around 26-18.</p>
<p class="compact">The RF slider scale is <strong>logarithmic</strong>, and the output filesize would change <strong>exponentially</strong> with deviation of the RF value.</p>
</li>
</ol>
</div>
<p class="compact">So, which of these is better? Obviously CRF, as it can distribute bits in a much more efficient way than CQP.</p>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Advanced_Tab">Advanced Tab</span></h2>
<p class="compact">The settings within this tab are unlocked by checking the <strong><em>&#8220;Use Advanced Tab instead&#8221;</em></strong> option in the Video tab. These settings allow you to fine tune your video by adjusting the various conversion parameters of the x264 codec. This tab is further subdivided into three sections: <strong><em>Encoding</em></strong>, <strong><em>Analysis</em></strong>, and <strong><em>Psychovisual</em></strong>.</p>
<div class="spaced image">
<img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/handbrake_advanced_tab.jpg" alt="Handbrake Advanced Tab" /><br />
<i>Handbrake Advanced Tab</i>
</div>
<h3 class="msize" style="padding-top: 5px; text-decoration: underline"><span id="Encoding">Encoding</span></h3>
<p class="compact">The <strong><em>Encoding</em></strong> section deals with <strong>video compression</strong>. It offers various ways by which your video bitrate could be further reduced.</p>
<h4 class="psize il"><span id="Reference_Frames">Reference Frames: </span></h4>
<p class="il np">This setting specifies the maximum number of frames each P frame can use as a reference. The higher this value, the better the compression. But it must be noted that many devices have limitations on the maximum number of reference frames that can be used. So, unless your sure what this value is, keep it at default(3).</p>
<div class="vspacer_25px"></div>
<h4 class="psize il"><span id="Maximum_B_Frames">Maximum B frames: </span></h4>
<p class="il np">This setting allows you to set the maximum number of successive B frames that can be encoded, after which an I or P frame has to follow for reference.</p>
<div class="vspacer_25px"></div>
<h4 class="psize il"><span id="Pyramidal_B_Frames">Pyramidal B frames: </span></h4>
<p class="il nl">Enabling this setting allows the B frames to be used as reference for other B frames wherever possible, thereby increasing compression. Options of None, Normal and Strict are provided. </p>
<ul class="np">
<li><em>None</em>: B frames are not used as reference.</li>
<li><em>Strict</em>: One B frame per mini GOP can be used as reference</li>
<li><em>Normal</em>: Numerous B frames per mini GOP can be used as reference.</li>
</ul>
<h4 class="psize il"><span id="Weighted_P_Frames">Weighted P Frames: </span></h4>
<p class="il np">Enabling this option allows the encoder to detect fades in reference frames, and assign it a particular weight. If this is OFF, the encoder will be unable to see the similarity between frames in cases where a frame is simply lighter or darker from the previous frame, as the entire frame is changing. Turning this ON can improve compression in such cases.</p>
<div class="vspacer_25px"></div>
<h4 class="psize il"><span id="8x8_Transform">8&#215;8 Transform: </span></h4>
<p class="il np">Enabling this option allows the use of 8&#215;8 blocks, rather than the normal 16&#215;16 blocks, for prediction. This can improve compression by quite a lot(at least 5%).</p>
<div class="vspacer_25px"></div>
<h4 class="psize il"><span id="CABAC">CABAC: </span></h4>
<p class="il nl">After quantization, the data stream has to be encoded. x264 offers two methods to achieve this: <strong>CABAC(Context Adaptive Binary Arithmetic Coding)</strong> and <strong>CAVLC(Context Adaptive Variable Length Coding)</strong>. CABAC offers better compression, but requires more processing power to encode and decode than CAVLC. CAVLC, on the other hand, offers inferior compression, but requires less processing power to encode and decode than CABAC.</p>
<p class="np">To turn ON CABAC encoding, tick the &#8220;CABAC&#8221; checkbox. Unchecking it will use CAVLC encoding, by default.</p>
<div class="vspacer_25px"></div>
<h3 class="msize" style="padding-top: 5px; text-decoration: underline"><span id="Analysis">Analysis</span></h3>
<p class="compact">This section contains settings using which you can control how x264 analyzes the source video.</p>
<h4 class="psize il"><span id="Adaptive_B_Frames">Adaptive B frames: </span></h4>
<p class="il nl">Using the options in this setting, you can control how x264 makes the decision to use a B frame.</p>
<ul class="np">
<li><em>OFF</em>: B frames will be placed in a fixed pattern.</li>
<li><em>Fast</em>: x264 can decide how many B frames to use depending on the complexity of the scene, but the decisions made are suboptimal.</li>
<li><em>Optimal</em>: x264 makes an optimal decision on when B frames are to be used. When using a higher number of Maximum B frames with Pyramidal B Frames, it is recommended to use this setting.</li>
</ul>
<h4 class="psize il"><span id="Adaptive_Direct_Mode">Adaptive Direct Mode: </span></h4>
<p class="il nl">This setting specifies how motion vectors are calculated for each block. Calculating motion vectors for every block is a CPU intensive and time consuming process. x264 has a few tricks up it&#8217;s sleeve for this.</p>
<ul class="np">
<li><em>None</em>: Adaptive Direct Mode is disabled. Motion Vectors have to be calculated for each block.</li>
<li><em>Spatial</em>: Motion vectors from the neighbouring blocks are used for the current block. This can significantly reduce the encoding time.</li>
<li><em>Temporal</em>: The current block is compared with the matched block in a P frame within the GOP. Using this, the motion vector is estimated rather than calculating it for each block.</li>
<li><em>Automatic</em>: x264 automatically chooses whether to use Spatial or Temporal for each block.</li>
</ul>
<h4 class="psize il"><span id="Subpixel_Motion_Est(subme)">Subpixel Motion Est(subme): </span></h4>
<p class="il nl">One of the things that make x264 far superior to other codecs is it&#8217;s amazing Motion Compensation capabilities. x264 even supports estimating the motion of a block by a non integer number of pixels, which is called Subpixel Motion Estimation. The advantages that this offers are quite obvious.</p>
<ul class="np">
<li><em>SAD(Sum of Absolute Differences)</em>: In this, the absolute differences between the pixels in the current block and the corresponding pixels in the block to be compared are taken, and are then added to obtain an SAD value. The block which gives the lowest SAD value will be the considered to be the block using which the motion vector will be calculated. This method can be used either with no Subpixel Motion Estimation(<strong><em>subme 0</em></strong>), or with one iteration of Quarter Pixel precision(<strong><em>subme 1</em></strong>).</li>
<li><em>SATD (Sum of Absolute Transformed Differences)</em>:Similar to SAD, with the only difference being that the differences of each pixel is frequency transformed before being added. Although this is much slower than SAD, it gives a much better prediction. This method can be used with two iterations of Quarter Pixel precision(<strong><em>subme 2</em></strong>), one iteration of Half Pixel precision interpolated to give quarter pixel precision(<strong><em>subme 3</em></strong>), always with Quarter Pixel precision(<strong><em>subme 4</em></strong>) and with Quarter Pixel precision + Bidirectional Motion Estimation(<strong><em>subme 5</em></strong>).</li>
<li><em>RD(Rate Distortion)</em>: The disadvantage of using SAD/SATD is that, many a time, the number of bits used for representing a sample would be more than what is actually needed. This could drastically increase the output file size, especially when using Quarter Pixel Precision.<br />
RD rectifies this issue by measuring the distortion D and the the number of bits R required for each decision, and comparing these with a cost function to make the mode decision. This can be used in either I/P frames(<strong><em>subme 6</em></strong>) or in all frames(<strong><em>subme 7</em></strong>).</li>
<li><em>RD Refine</em>: In this setting, RD is used to refine both motion vectors and mode decisions. This again, can be used in either I/P frames(<strong><em>subme 8</em></strong>) or in all frames(<strong><em>subme 9</em></strong>). This  is slower than normal RD, but more efficient.</li>
<li><em>QPRD(Quarter Pixel Rate Distortion)</em>: This setting does an RD optimization on some quarter pixels using a hexagonal search(<strong><em>subme 10</em></strong>). First, the SATD is checked. If this is found to be above the  threshold value, then the RD process is skipped. If the SATD is below the threshold value, then RD is used. This process much slower, and requires <strong><em>trellis</em></strong> to be set at 2 and <strong><em>Adaptive Quant Strength</em></strong> > 0.</li>
</ul>
<h4 class="psize il"><span id="Motion_Est_Method">Motion Est Method: </span></h4>
<p class="il nl">x264 has a variety of search patterns for estimating how each block of pixels have moved in successive frames.</p>
<div class="highlight np">
<p class="nl">Key:</p>
<p><a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/key.png" target="_blank"><img decoding="async" class="compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/key.png" alt="Key" height="90px" width="566px"></a></p>
<ul class="emplist">
<li>
<p class="nl"><em>Diamond</em>:<br />Pattern:</p>
<div><a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/diamond.png" target="_blank"><img decoding="async" style="margin-bottom: 5px; margin-left: 20px" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/diamond.png" alt="Diamond Pattern" height="90px" width="90px"></a></div>
<p class="compact">Searches similar pixels in a Diamond pattern. This is the fastest method, however the results obtained are the most inferior.</p>
</li>
<li>
<p class="nl"><em>Hexagon</em>:<br />Pattern:</p>
<div><a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/hexagon.png" target="_blank"><img decoding="async" style="margin-bottom: 5px; margin-left: 20px" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/hexagon.png" alt="Hexagon Pattern" height="150px" width="150px"></a></div>
<p class="compact">Searches similar pixels in a Hexagon pattern. Slower than Diamond search, but produces much better results.</p>
</li>
<li>
<p class="nl"><em>Exhaustive</em>:<br />Pattern:</p>
<div><a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/exhaustive.png" target="_blank"><img decoding="async" style="margin-bottom: 5px; margin-left: 20px" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/exhaustive.png" alt="Exhaustive Pattern" height="150px" width="150px"></a></div>
<p class="compact">Searches similar pixels in a wide area(directly given by the Motion Est Range) surrounding the current pixel. This is an extremely slow pattern, and in most cases, the compression gain offered by this is just not worth it.</p>
</li>
<li>
<p class="compact"><em>Transformed Exhaustive</em>: It is similar to exhaustive, but is slightly better and slower.</p>
</li>
<li>
<p class="compact"><em>Uneven Multi Hexagon</em>: This makes use of five different search patterns; Unsymmetrical cross search, Small rectangular full search, Uneven Multi Hexagon grid search, Extended Hexagon based search and Diamond search. Based on the complexity of the scene, x264 will choose one or multiple of these patterns to estimate motion. Like exhaustive, the range of this search is directly controlled by the Motion Est Range. This is slower than Hexagon search(faster than Exhaustive), but gives much better results in scenes with complex motion.</p>
</li>
</ul>
</div>
<h4 class="psize il"><span id="Motion_Est_Range(merange)">Motion Est Range(merange): </span></h4>
<p class="il np">This value specifies the maximum range in pixels that the encoder searches for a match. For Diamond and Hexagon pattern, this value ranges from 4-16. For Uneven Multi Hexagon and Exhaustive, this value can be extended beyond 16, which can be particularly useful for high motion scenes.</p>
<div class="vspacer_25px"></div>
<h4 class="psize il"><span id="Partition_Type">Partition Type: </span></h4>
<p class="il nl">Each macroblock is broken down to form prediction blocks by the x264 encoder. There are 6 possible ways by which this can be done;</p>
<ul class="nl">
<li>Intra Macroblock: 16&#215;16, 8&#215;8</li>
<li>Inter Macroblock: 16&#215;16, 16&#215;8, 8&#215;16, 8&#215;8</li>
<li>The 8&#215;8 blocks can further be broken down into even smaller blocks.</li>
</ul>
<p class="nl">Each of these partitions are then represented using separate motion vectors. This partitioning is called mode.</p>
<p class="nl">A macroblock with less partitions would require lesser motion vectors to represent its motion. However, these motion vectors might not accurately represent the motion, resulting in a large error and hence encoding the error would require more bits. Similarly, more partitions would require more motion vectors to represent the motion information and fewer bits to encode the residual error.</p>
<p class="nl">The mode selection for each macroblock is one of the steps which contributes to x264s ability to give a great quality output at a low bitrate, but it is a time consuming process, especially if more macroblocks are partitioned.</p>
<p class="np">By using the options in this setting, you can control how many macroblocks the encoder will partition. Options of <strong><em>Most</em></strong>, <strong><em>None</em></strong> ,<strong><em>Some</em></strong> and <strong><em>All</em></strong> are provided.</p>
<h4 class="psize il"><span id="Trellis">Trellis: </span></h4>
<p class="il np">Enabling this setting allows x264 to use trellis quantization algorithm for rounding off the transformed coefficients, which can improve compression by a bit. CABAC must be enabled to use this. You can choose to use this either for encoding only or always(for both analysis and encoding). Choosing always can hit your encoding speed.</p>
<div class="vspacer_25px"></div>
<h3 class="msize" style="padding-top: 5px; text-decoration: underline"><span id="Psychovisual">Psychovisual</span></h3>
<p class="compact">Using the settings in this section, you can control the extent to which the encoder will remove psychovisual redundancies.</p>
<h4 class="psize il"><span id="No_DCT_Decimate">No DCT Decimate: </span></h4>
<p class="il np">DCT Decimation allows the x264 encoder to skip encoding any of the blocks which it views as redundant information. These blocks are the not written to the output file, effectively reducing the bitrate. Checking this option will prevent x264 from skipping such blocks. This is useful if you want to preserve the grain in your videos, which are otherwise removed by DCT decimation.</p>
<div class="vspacer_25px"></div>
<h4 class="psize il"><span id="Adaptive_Quant_Strength">Adaptive Quant Strength: </span></h4>
<p class="il nl">Adaptive Quantization is the process of using a different value quantizer for each block. As x264 uses CRF for constant quality(in Handbrake), this setting can be used to control how x264 distributes bits between the flat areas and the complex areas in the frames.</p>
<p class="np">Higher values(>1) means more bits are allocated to the flats than to the complex areas in a frame, effectively reducing the banding artifacts, but causing some ringing artifacts. Lower Values(<1) means more bits are allocated to the edges in a frame, effectively reducing the ringing artifacts, but causing some banding artifacts.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/ringing_and_banding.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part2_x264/ringing_and_banding.jpg" alt="Ringing and Banding Artifacts" height="674px" width="674px"></a><i>Ringing Artifacts: In the edges of the circle.<br />
Banding Artifacts: Discontinuities in the Gradient inside the circle and in the background.</i>
</div>
<h4 class="psize il"><span id="Psychovisual_Rate_Distortion">Psychovisual Rate Distortion: </span></h4>
<p class="il np">This setting adjusts the tradeoff between detail retention and actual video quality(the way the computer sees it). Higher values tend to retain the finer details(grain) at the expense of some loss in quality(undesirable blocking artifacts). The encoded video will thus, appear sharper and more detailed as compared to what it would have been if this was set to 0. To use this, subme should be 6 or higher.</p>
<div class="vspacer_25px"></div>
<h4 class="psize il"><span id="Psychovisual_Trellis">Psychovisual Trellis: </span></h4>
<p class="il np">This setting can be used to improve the sharpness and retain details by varying the strength function of the trellis quantization algorithm. The slider works similar to the Rate Distortion Slider. Higher values bias the finer details over the quality.</p>
<div class="vspacer_25px"></div>
<h4 class="psize il"><span id="Deblocking">Deblocking: </span></h4>
<p class="il np">Does the same thing as the Deblocking Filter in the &#8220;Filters&#8221; tab, but in a much better way. There are two parameters that you could give as input to x264&#8217;s deblocking filter: Alpha and Beta. Alpha value control the amount of deblocking to be applied; higher values would give a softer image. Beta value is the threshold value with which the block is first compared before it is deblocked.</p>
<div class="vspacer_25px"></div>
<div class="special sp_blue notestar spaced">
<b>Note:</b> The Preset and Tune values in the &#8220;Video&#8221; tab work by altering the Advanced x264 settings, and could be used as an alternative if you are intimidated by these settings.
</div>
<h2 style="padding-top: 30px; margin-bottom: 20px;"><span id="Closing_Notes">Closing Notes</span></h2>
<p class="compact">Well, thats all there is to encoding videos using Handbrake. Always make it a practise to encode a preview first and try playing it on your intended device. Video encoding does take a lot of time, and you wouldn&#8217;t want to be that fool who spends hours encoding the entire video just to find that it doesn&#8217;t work on your device.</p>
<p class="compact">Apart from that, have fun encoding! Hope you found this tutorial helpful.</p>
<p>The post <a href="https://www.ocfreaks.com/handbrake-tutorial-part-2-x264-advanced-encoding-compression-settings-guide/">Handbrake Tutorial Part 2: x264 Advanced Encoding &#038; Compression Settings Guide</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/handbrake-tutorial-part-2-x264-advanced-encoding-compression-settings-guide/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2586</post-id>	</item>
		<item>
		<title>Handbrake Complete Tutorial Part 1: How to Transcode &#038; Compress Videos</title>
		<link>https://www.ocfreaks.com/handbrake-complete-tutorial-part-1-transcode-compress-videos/</link>
					<comments>https://www.ocfreaks.com/handbrake-complete-tutorial-part-1-transcode-compress-videos/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Saby D'silva]]></dc:creator>
		<pubDate>Fri, 09 Sep 2016 14:53:53 +0000</pubDate>
				<category><![CDATA[Guides & Tutorials]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[tutorial]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2559</guid>

					<description><![CDATA[<p>An in-depth guide cum tutorial showing how to properly transcode videos using handbrake, with all the settings explained in as simple and concise a manner as possible, without sacrificing the finer details.</p>
<p>The post <a href="https://www.ocfreaks.com/handbrake-complete-tutorial-part-1-transcode-compress-videos/">Handbrake Complete Tutorial Part 1: How to Transcode &#038; Compress Videos</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="spaced tocpostimage">
<img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbico.jpg" width="256" height="256" alt="Handbrake" />
</div>
<p class="compact" style="clear: left; float:left">In this tutorial, I will show you how to properly transcode videos using Handbrake. I&#8217;ve gone over all the settings in as simple and concise a manner as possible, without sacrificing the finer details (no pun intended 😉 ). Hope you find it useful.</p>
<div class="toc_container">
<span class="toc_title">Table of Contents</span></p>
<div class="toc">
<ol class="toc_list">
<li class="toc_text"><a href="#General_Info_about_Handbrake_and_Videos" title="General Info about Handbrake and Videos"><span>1. </span><span>General Info about Handbrake and Videos</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Why_Transcode_Videos?" title="Why Transcode Videos?"><span>1.1. </span><span>Why Transcode Videos?</span></a></li>
<li class="toc_text"><a href="#JFYI" title="JFYI"><span>1.2. </span><span>JFYI</span></a></li>
</ol>
<li class="toc_text"><a href="#Picture_Tab" title="Picture Tab"><span>2. </span><span>Picture Tab</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Anamorphic" title="Anamorphic"><span>2.1. </span><span>Anamorphic</span></a></li>
<li class="toc_text"><a href="#Modulus" title="Modulus"><span>2.2. </span><span>Modulus</span></a></li>
<li class="toc_text"><a href="#Cropping" title="Cropping"><span>2.3. </span><span>Cropping</span></a></li>
</ol>
<li class="toc_text"><a href="#Filters_Tab" title="Filters Tab"><span>3. </span><span>Filters Tab</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Detelecine_Deinterlace_and_Decomb" title="Deinterlace, Detelecine and Decomb"><span>3.1. </span><span>Detelecine, Deinterlace and Decomb</span></a></li>
<li class="toc_text"><a href="#Denoise" title="Denoise"><span>3.2. </span><span>Denoise</span></a></li>
<li class="toc_text"><a href="#Deblock" title="Deblock"><span>3.3. </span><span>Deblock</span></a></li>
</ol>
<li class="toc_text"><a href="#Video_Tab" title="Video Tab"><span>4. </span><span>Video Tab</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Video_Codec" title="Video Codec"><span>4.1. </span><span>Video Codec</span></a></li>
<li class="toc_text"><a href="#Framerate" title="Framerate"><span>4.2. </span><span>Framerate</span></a></li>
<li class="toc_text"><a href="#x264_Exclusive_Settings" title="x264 Exclusive Settings"><span>4.3. </span><span>x264 Exclusive Settings</span></a></li>
</ol>
<li class="toc_text"><a href="#Audio_Tab" title="Audio Tab"><span>5. </span><span>Audio Tab</span></a></li>
<ol class="toc_list">
<li class="toc_text"><a href="#Audio_Codec" title="Audio Codec"><span>5.1. </span><span>Audio Codec</span></a></li>
<li class="toc_text"><a href="#Mixdown" title="Mixdown"><span>5.2. </span><span>Mixdown</span></a></li>
<li class="toc_text"><a href="#Sample_Rate" title="Sample Rate"><span>5.3. </span><span>Sample Rate</span></a></li>
<li class="toc_text"><a href="#DRC" title="DRC"><span>5.4. </span><span>DRC</span></a></li>
<li class="toc_text"><a href="#Gain" title="Gain"><span>5.5. </span><span>Gain</span></a></li>
</ol>
<li class="toc_text"><a href="#Subtitles_Tab" title="Subtitles Tab"><span>6. </span><span>Subtitles Tab</span></a></li>
<li class="toc_text"><a href="#Chapters_Tab" title="Chapters Tab"><span>7. </span><span>Chapters Tab</span></a></li>
<li class="toc_text"><a href="#Presets" title="Presets"><span>8. </span><span>Presets</span></a></li>
<li class="toc_text"><a href="#Recommended_Settings" title="Recommended Settings"><span>9. </span><span>Recommended Settings</span></a></li>
<li class="toc_text"><a href="#Anamorphic_Revisited" title="Anamorphic Revisited"><span>10. </span><span>Anamorphic Revisited</span></a></li>
<li class="toc_text"><a href="#Closing_Notes" title="Closing Notes"></span>11. </span><span>Closing Notes</span></a></li>
</ol>
</div>
</div>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="General_Info_about_Handbrake_and_Videos">General Info about Handbrake and Videos</span></h2>
<h3 class="msize" style="padding-top: 5px;"><span id="Why_Transcode_Videos?">Why Transcode Videos?:<span></h3>
<p class="compact">Well, there could be many different reasons for this. Few that come to mind, off the top, are:</p>
<ol>
<li>Incompatibility of the video codec with your device.</li>
<li>Uploading a video with a low bandwidth connection.</li>
<li>Reducing file size to save your device memory.</li>
</ol>
<h3 class="msize" style="padding-top: 5px;"><span id="JFYI">JFYI:<span></h3>
<p class="compact">In the words of its developer:</p>
<blockquote><p>&#8220;HandBrake is a GPL-licensed, multiplatform, multithreaded video transcoder.&#8221;</p></blockquote>
<p class="compact">What needs to be noted here is that Handbrake is a <strong>video transcoder</strong>. It wasn&#8217;t, isn&#8217;t and quite probably never will be a <em>&#8220;Video Converter&#8221;</em>. I have heard the terms <strong>container and codec, converter and encoder (or transcoder)</strong> misunderstood and used interchangeably countless times. So, I feel it would be best if I clear that up first.</p>
<div class="highlight spaced">
<ul class="emplist">
<li class="spaced"><b>Container:</b> This is your actual video file format. If your file name is xxx.yyy, then yyy is the container. For example, mp4, avi, mkv, 3gp, flv are all container formats, and in no way signifies the codec used.</li>
<li class="spaced"><b>Codec:</b> A video file basically comprises of two things. The audio that you hear, and the video that you see. Codec (COder-DECoder), simply put, is the program using which data streams are encoded for storage on a device, and decoded for playback. The video and audio streams are encoded using different codecs and are held together in the container format. For example; aac, mp3, wma are audio codecs; and x264, xvid, VP8 are video codecs.</li>
<li class="spaced"><b>Transcoding:</b> Encode using a different codec from the one with which the video is currently encoded.</li>
<li><b>Converting:</b> Changing the container format of the video file, with or without transcoding.</li>
</ol>
</div>
<p class="compact">So, from this it is evident that most video converters are transcoders as well (though in most cases, devoid of many of the features offered by standalone video transcoders like Handbrake), while video transcoders may or may not offer conversion.</p>
<p class="compact">Handbrake currently supports two output container formats: MKV and MP4. So, it wouldn&#8217;t be right classifying it as a video converter per se, but it most certainly is a video transcoder. And quite a good one at that.</p>
<div class="special sp_blue notestar spaced">
<strong>Note:</strong> Encoding videos on Handbrake is a <em>CPU intensive task</em>. Handbrake (in its latest release) does offer support for <em>GPU acceleration</em>. But I strongly suggest that you leave it off. The time gained by enabling this is not much, and a significant loss in quality can be observed in the output. Handbrake also supports Intel&#8217;s <em>Quick Sync encoder</em> for <strong>H.264</strong> (for 2nd Gen or greater i-Core CPUs, with iGPU enabled). I can&#8217;t comment on how effective this is as I haven&#8217;t had any real experience with it. But if the words on internet are anything to go by, I&#8217;d suggest not using this as well, at least for now.
</div>
<p class="compact">Now enough of all this blabbering! Let&#8217;s jump right on to using Handbrake.</p>
<p class="compact">First, let&#8217;s have a look at the window:</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hb1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hb1.jpg" width="674" height="460" alt="Handbrake Window" /></a><i>Handbrake Window</i>
</div>
<p class="compact">To add a file to transcode, simply drag and drop it to the window. Or, you can click on <strong><em>&#8220;Source&#8221;</em></strong> and browse to the file location to add it. Then set the destination and the output file name. If Batch transcoding (transcoding more than 1 file) is what you&#8217;re after, then after you&#8217;ve set all the required parameters for transcoding, click <strong><em>&#8220;Add to Queue&#8221;</em></strong> and add another file. Click <strong><em>&#8220;Show Queue&#8221;</em></strong> to view all the files in queue to be encoded.</p>
<p class="compact">Click on <strong><em>&#8220;Preview&#8221;</em></strong> to view a 10 second(can be changed) preview of how your output would look like.</p>
<p class="compact">Choose either MP4 or MKV container according to your requirements. Tick the <strong><em>&#8220;Web Optimized&#8221;</em></strong> check box if you want to upload the video to a website.</p>
<p class="np">Now we&#8217;ll see the various settings offered by handbrake.</p>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Picture_Tab">Picture Tab</span></h2>
<p>This tab contains all the settings that you&#8217;ll need to modify the <strong>Resolution</strong> and <strong>Aspect Ratio</strong> (Width / Height) of your video.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbpic1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbpic1.jpg" width="674" height="345" alt="Handbrake Picture Tab" /></a><i>Handbrake Picture Tab</i>
</div>
<h3 class="psize il"><span id="Anamorphic">Anamorphic: </span></h3>
<p class="il nl">Anamorphic is the property of scaling the width of a video by a factor in order to correct its Aspect Ratio.This setting is a bit complicated to explain. So, I feel it&#8217;s best if I explain it in a later part. For now, just understand this;</p>
<p class="nl">If your video doesn&#8217;t appear squished on your device, and you want to keep its resolution as it is, keep this option to <strong><em>Strict</em></strong> and let Handbrake handle the rest.</p>
<p class="np">If your video doesn&#8217;t appear squished on your device, and you want to reduce its resolution, keep this option to <strong><em>loose</em></strong> and reduce the resolution. Keeping it to none with <em>&#8220;Keep Aspect Ratio&#8221;</em> enabled will work too. But if the video source itself is anamorphic, then that property will be lost.</p>
<h3 class="psize il"><span id="Modulus">Modulus: </span></h3>
<p class="il np">Most video encoders divide each video frame into <strong>macroblocks</strong>, which can be said to be an array of pixels. A macroblock generally consists of 16&#215;16 pixels. This means that both the width and the height of the video would have to be divisible by 16. The downside here is that you&#8217;d almost never get a perfect resolution and aspect ratio. For example, imagine a video that has an aspect ratio of 1.84 and is 640 pixels wide. The standard resolution for such a video would be 640&#215;348 (approximately). But since the height and width both must be divisible by 16, the resolution would be reduced to 640&#215;336, thereby creating an effective aspect ratio of 1.9. By using the Modulus option, you get to decide the multiplying factor for the resolution, at the expense of some overhead. By setting the value of modulus to 2, you would be able to preserve the aspect ratio of the 640&#215;348 video as it is, as the height and width now just needs to be divisible by 2. But to achieve this, 4 additional horizontal pixels would be padded and encoded (348 is not divisible by 16. Next closest number divisible by 16 is 352. 352-348=4). But these would get cropped off during playback, and in most cases won&#8217;t be visible.</p>
<div class="vspacer_25px"></div>
<h3 class="psize il"><span id="Cropping">Cropping: </span></h3>
<p class="il np">You can use this setting to crop off a part of your video file. Just set this to <strong><em>Custom</em></strong>, with all settings 0, if you don&#8217;t want to do so. You can also leave it to <strong><em>Automatic</em></strong>. But in some very rare cases, Handbrake will crop off a portion of your video file even when not needed, or it may miss a portion to be cropped. So, as the saying goes, Better be safe than sorry! </p>
<div class="vspacer_25px"></div>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Filters_Tab">Filters Tab</span></h2>
<p class="compact">This tab contains settings that you&#8217;ll need if you are dealing with a noisy and/or distorted source file. Before encoding the video, Handbrake would run it through these filters to rectify the source.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbfil1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbfil1.jpg" width="674" height="345" alt="Handbrake Filters Tab" /></a><i>Handbrake Filters Tab</i>
</div>
<h3 class="psize il"><span id="Detelecine_Deinterlace_and_Decomb">Detelecine, Deinterlace and Decomb: </span></h3>
<p class="il nl">Only worry about these settings if your source is a broadcast content(analog broadcast content, to be precise).</p>
<p class="nl"><strong>Interlacing</strong> is the process of dividing each frame into two fields, with each field containing alternate horizontal lines of the frame, making it suitable for broadcast (<i>For more info, see: <a href="http://en.wikipedia.org/wiki/Interlaced_video"  target="_blank">Interlaced Video</a></i>). By this, the content can be broadcasted at twice the frame rate as that of <strong>progressively</strong> scanned video (<i>For more info, see: <a href="http://en.wikipedia.org/wiki/Progressive_scan" target="_blank">Progressive Video</a></i>), without any additional bandwidth. The downside to this is, you&#8217;ll get <strong>combing artefacts</strong> if you try viewing this on your computer monitor.</p>
<p class="nl">So, in order to rectify this, you&#8217;ll need to enable either the <strong><em>&#8220;Deinterlacing&#8221;</em></strong> or the <strong><em>&#8220;Decomb&#8221;</em></strong> Option. The difference between these two is that while Deinterlacing would deinterlace each and every frame of the video, Decomb would check which parts of the video have combing artefacts and would fix just those frames. I recommend using the <strong><em>Decomb</em></strong> option in <strong><em>default</em></strong> mode, as Deinterlacing could reduce the video quality in case the frame isn&#8217;t entirely interlaced. But if your video seems to be interlaced entirely (rarely does this happen), using <strong><em>Deinterlacing</em></strong> at <strong><em>Fast</em></strong> setting can save time on your encode. It&#8217;s always better to keep these settings off if your video isn&#8217;t interlaced.</p>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/decomb-1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/decomb-1.jpg" width="674" height="530" alt="Original Interlaced Frame" /></a><i>(a). Original Interlaced Frame<br />
Notice how the frame is Divided into two fields, one containing the odd lines and the other containing the even lines. In scenes with fast motion or in which the camera position is changed quickly, both the odd and even fields can be seen separately, which is called Combing Effect. This effect can be seen clearly in the above frame.</i>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/decomb-2.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/decomb-2.jpg" width="674" height="530" alt="Decombed Frame" /></a><i>(b). Decombed Frame(Default Preset)<br />
The combing artefacts are removed, while keeping quality loss to a minimum.</i>
</div>
<p class="nl"><strong>Telecining</strong> is the process of converting a video shot in one frame rate into a frame rate that is suitable for <strong>broadcasting</strong>. Extra frames need to be added to such videos. There are two ways by which this could be achieved.</p>
<ol class=nl>
<li>Duplicating certain (not all) fields (interlaced frames), called <strong>Hard Telecine</strong>.</li>
<li>Showing those fields a bit longer than usual by repeating them during playback, called <strong>Soft Telecine</strong>.</li>
</ol>
<p class="nl">Hard telecined video needs to be <strong>Detelecined</strong> before viewing it on a computer. You can tell if a video is hard telecined or not by analysing it frame by frame. If you obtain a pattern of frames with combing artefacts and then some without it, I&#8217;d say you&#8217;ve got a Hard Telecined Video. For example, one pattern, commonly observed in NTSC content, is 2 interlaced frames and 3 normal frames (or 2 duplicated fields in 8 fields). For PAL content, in very rare cases, this pattern is 2 interlaced frames and 23 normal frames (or 2 duplicated fields in 48 fields).</p>
<p class="nl">Just leave this filter on <strong><em>default</em></strong> for such videos. Else keep it off.</p>
<div class="special sp_blue notestar np"><strong>Note:</strong> <strong>Never EVER</strong> keep <em>Detelecine and Deinterlace</em> both ON at the same time. This can seriously reduce your video quality. There is no issue in leaving Detelecine and Decomb ON however.</div>
<h3 class="psize il"><span id="Denoise">Denoise: </span></h3>
<p class="il nl">If you&#8217;ve got excess grain or blur in your video, you can use this option to reduce it, but at the expense of loss of finer details. Handbrake version 0.10 and above has added support for <strong><em>NLmeans denoising filter</em></strong>, which although takes more time in encoding, gives better results than <strong><em>hqn3d filter</em></strong>(the one used in pre 0.10 versions). If you don&#8217;t mind the extra time, use this in <strong><em>ultralight</em></strong> (or <strong><em>light</em></strong> if your video is too grainy) preset. Otherwise, use <strong><em>hqn3d</em></strong> in <strong><em>weak</em></strong> preset. Keep this option off if you if you feel your video is fine as it is.</p>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/denoise-1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/denoise-1.jpg" width="674" height="505" alt="Original Grainy Frame" /></a><i>(a). Original Grainy Frame<br />
The frame is a bit grainy.</i>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/denoise-2.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/denoise-2.jpg" width="674" height="505" alt="Denoised Frame" /></a><i>(b). Denoised Frame(hqn3d; medium)<br />
The grain is reduced, but there is a noticeable loss of detail(for instance, the wrinkles).</i>
</div>
<h3 class="psize il"><span id="Deblock">Deblock: </span></h3>
<p class="il nl">This filter can be used to remove visible sharp edges between adjacent macroblocks. Only use this option as a last resort. Even the smallest changes in this can affect the quality drastically. For all intents and purposes, I recommend you to steer clear off this option. There is only so much one can do to rectify a bad source. But in case you really need to use this option, don&#8217;t exceed the setting of 5.</p>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/deblock-1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/deblock-1.jpg" width="674" height="505" alt="Original blocky Frame" /></a><i>(a). Original Blocky Frame<br />
The sharp edges between macroblocks are clearly visible in this frame. These are called blocky artefacts.</i>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/deblock-2.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/deblock-2.jpg" width="674" height="505" alt="Deblocked Frame" /></a><i>(b). Deblocked Frame(Setting:5)<br />
The blocky artefacts are removed, but so are the details. Overall, the whole image looks softened.</i>
</div>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Video_Tab">Video Tab</span></h2>
<p class="compact">This tab contains settings related to your Video encoder.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbvid1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbvid1.jpg" width="674" height="345" alt="Handbrake Video Tab" /></a><i>Handbrake Video Tab</i>
</div>
<h3 class="psize nl"><span id="Video_Codec">Video Codec:</span></h3>
<p class="nl">For MP4:</p>
<ul class="compact">
<li><em>x264(H.264/AVC Standard)</em>: Always choose this if your device supports it. It offers the best quality for the size.</li>
<li><em>MPEG 4 Part 2(H.263 Standard)</em>: Faster encoding and better support for old devices than x264. But the quality will be lower.</li>
<li><em>MPEG 2 Part 2(H.262 Standard)</em>: Faster encoding than MPEG 4. But the output file will be much larger and of inferior quality. Only use this if your device doesn&#8217;t support even MPEG 4.</li>
<li><em>x265 (H.265/HEVC Standard)</em>: This is a relatively new encoder. It uses the H.265 standard, which is an improvement over the H.264 standard. x265 offers the same quality as x264 at much lower bitrates, i.e., the output file size will be much lower. But support for this encoder is quite minimal, especially in mobile devices. VLC(for Windows PC, that is) currently offers support for this codec, but I have seen playback issues with some x265 videos on mobile devices. So, I recommend you to check if your device supports this codec, before making the decision to use this.</li>
</ul>
<p class="nl">For MKV:</p>
<ul class="np">
<li><em>x264, MPEG4, MPEG2 and x265</em>: Same as MP4.</li>
<li><em>Theora(VP3)</em>: VP3 is a relatively old codec that was intended to compete with MPEG 4. Theora was evolved from this codec and it offers various improvements over its predecessor, On2&#8217;s VP3. However, it doesn&#8217;t compare to x264 in terms of quality at a given bit rate. But where Theora really triumphs is that it is truly open source and not subject to any patents. This in itself makes it a favourable choice to those who want to distribute content, as they aren&#8217;t required to pay any royalty fee. x264, though open source, is still subject to the patents held by MPEG consortium for the H.264 standard. And distributors of H.264 encoded content are, by law, required to pay a licensing fee.</li>
<li><em>libvpx(VP8)</em>: libvpx can be said to be an improvement over the somewhat dated Theora encoder. It offers much better quality, and like Theora, is completely free. It still doesn&#8217;t offer the amazing quality of x264, but it has become successful in closing that gap. And I mean BY A LOT. So, it&#8217;s a great alternative if you want to distribute content.</li>
</ul>
<h3 class="psize il"><span id="Framerate">Framerate: </span></h3>
<p class="il np">Framerate is the number of frames displayed per second (fps). Keep this option to same as source unless, for some reason, you need to change it.</p>
<div class="vspacer_25px"></div>
<h3 class="psize nl"><span id="x264_Exclusive_Settings">x264 Exclusive Settings:</span></h3>
<p class="nl"><b>x264 Preset:</b> By using this slider you can adjust the level of tradeoff between encoding speed and filesize and/or quality. The extreme left setting will finish encoding quicker but the filesize will be larger for the quality. The extreme right setting will take much longer to encode, but it will offer the lowest filesize for the quality.</p>
<p class="nl"><b>x264 Tune:</b> Options of None, Film, Animation, Grain, Still Image, PSNR, SSIM, Fast Decode are provided. Choose any one of these options according to your requirements. (For example, Film if your source is a movie, Grain if you want to retain grain, etc. PSNR and SSIM will offer you maximum quality the way a computer will see it, and is not generally recommended to use.)</p>
<p class="nl"><b>H.264 Profile:</b> Four profile options are provided: Main, Baseline, High, Auto.</p>
<ul class="nl">
<li><em>Main</em>: Less CPU intensive, Fast Encode, Fast Decode (Playback), Large Filesize.</li>
<li><em>Baseline</em>: More CPU Intensive, Slower Encode, Slower Decode (Playback), Lower Filesize.</li>
<li><em>High</em>: Most CPU Intensive, Slowest Encode, Slowest Decode (Playback), Lowest Filesize.</li>
<li><em>Auto</em>: Selects the Profile most suited for your settings automatically.</li>
</ul>
<p class="np"><b>H.264 Level:</b> Each H.264 level provides a set of constraints like max bit rate, frame size, etc for encoding. For the full list of constraints for each level, see: <a href="http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels" target="_blank">H.264 Levels</a></p>
<p class="nl">Handbrake offers two methods for Encoding Video: Constant Quality and Average Bitrate.</p>
<p class="nl"><b>Constant Quality:</b> In this method, you have no control over the output file size. For most cases, this is the better option of the two. The output file is most likely to be of better quality and lower size using this method. In this method you can control the quality of the video by using the quality slider. The extreme right value (lowest number) represents the highest possible quality (lossless, output will be bigger than the source if the source itself is lossy), while the extreme left value(highest number) represents the lowest quality (extremely lossy).</p>
<p class="nl"><b>Average Bitrate:</b> Unless you REALLY know what you&#8217;re doing, don&#8217;t use this option. This option gives you control over the file size, but at the expense of quality. All you need to do is take what your estimate is of the output file size (in kb), divide it by the duration of the video(in seconds), and enter it in the box labelled <strong><em>&#8220;Avg bitrate(kbps)&#8221;</em></strong>. However, the problem here is that, more often than not your estimated file size will be either too large or too low.</p>
<p class="nl">If you use this setting, do remember to check the <strong><em>2-pass Encoding</em></strong> and <strong><em>Turbo First Pass</em></strong> check boxes. The reason for this is not every portion of the video has the same bitrate (thus, the term &#8220;Average&#8221;). Some portions require higher bitrate (fast action scenes), while some appear fine at lower bitrates (scenes with less motion). So, if <strong><em>2-Pass encoding</em></strong> is turned on, Handbrake will encode the video a second time, allocating bits to different parts of the video in a much better way than the first time.</p>
<p class="nl">But obviously, this will require much more time than a single pass encode. This is rectified by turning on <strong><em>Turbo First Pass</em></strong>, which will encode the first time much quicker and less efficiently (since the actual output will be that of the second pass, the first encode can be thought of as redundant). It still requires more time than a single pass encode, but the overall time will be much lesser than what it would be if this option is kept off.</p>
<div class="special sp_blue notestar np">
<strong>Note:</strong> Settings for the other codecs can be self deduced once you understand x264&#8217;s settings. So, for the sake of brevity, I wont be going over those.
</div>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Audio_Tab">Audio Tab</span></h2>
<p class="compact">This tab contains settings related to your audio encoder.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbaud1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbaud1.jpg" width="674" height="345" alt="Handbrake Audio Tab" /></a><i>Handbrake Audio Tab</i>
</div>
<h3 class="psize nl"><span id="Audio_Codec">Audio Codec: </span></h3>
<p class="nl">For MP4:</p>
<ul class="compact">
<li><em>libav AAC</em>: Encodes your audio to AAC using ffmpeg&#8217;s libav codec library.</li>
<li><em>FDK AAC/AAC-LC</em>: Encodes your audio to AAC-LC using the FDK Encoder. Generally much better results are obtained using FDK than by using libav.</li>
<li><em>FDK HE-AAC</em>: Encodes your audio to HE-AAC using the FDK encoder. More suited for lower bitrate audio files (&lt;80kbps) for streaming.</li>
<li><em>LAME MP3</em>: Encodes your audio to the extremely popular MP3 format using the LAME encoder. Higher bitrates are needed for achieving the same quality as AAC-LC.</li>
<li><em>libav AC3</em>: Encodes your audio to AC3 using ffmpeg&#8217;s libav codec library.</li>
<li><em>Passthru(AAC, MP3, AC3, DTS, DTS- HD)</em>: These would pass through the source audio settings as it is to the output file.</li>
<li><em>Passthru(Auto)</em>: This setting will sense your source format, and pass through your source audio settings as it is to the output file. Use this option if you don&#8217;t want to transcode your audio.</li>
</ul>
<p class="nl">For MKV:</p>
<ul class="np">
<li><em>Libav AAC , FDK AAC/AAC-LC, FDK HE-AAC, LAME MP3, libav AC3, Passthru(All)</em>: Same as MP4.</li>
<li><em>Vorbis</em>: Vorbis can be said to be the audio equivalent of Theora. It is a free and open source codec that isn&#8217;t subject to any patents. Audio encoded in Vorbis is almost identical to AAC, and can be used as a viable alternative to AAC to distribute content.</li>
<li><em>libav FLAC</em>: 16 bit and 24 bit FLAC options are available by using ffmpeg&#8217;s libav codec library. These options are lossless, so the filesize will increase by a lot.</li>
</ul>
<h3 class="psize il"><span id="Mixdown">Mixdown: </span></h3>
<p class="il np">Options of Dolby ProLogic II, Dolby Surround, Mono, Stereo, 5.1ch, 6.1ch, 7.1ch, None and Automatic are provided. Choose any one of these options according to your requirements.</p>
<div class="vspacer_25px"></div>
<h3 class="psize il"><span id="Sample_Rate">Sample Rate: </span></h3>
<p class="il np">Number of Audio samples per second. Keep this setting at auto for best results.</p>
<div class="vspacer_25px"></div>
<h3 class="psize il"><span id="DRC">DRC: </span></h3>
<p class="il np">Dynamic Range Compression. This setting is used to alter the difference between the lowest and loudest sounds in the audio file. Use this setting at greater than 0 if you feel the lower volume parts in the audio file are too low in volume, while the louder parts are too loud. Generally, a value between 1 and 2 is sufficient for most files. At default, this value is kept at 0 (DRC OFF).</p>
<div class="vspacer_25px"></div>
<h3 class="psize il"><span id="Gain">Gain: </span></h3>
<p class="il nl">This setting is used to increase the volume of the entire audio file. The value should be in dB. Never keep this setting at more than 10 dB. It will distort your audio at the really loud places. To calculate this value: Suppose you need 2 times the volume of your source file in your output. Then:</p>
<div class="highlight np">
V2 / V1 = 2, Gain = 20 log (V2 / V1) = 6.02dB.
</div>
<p class="compact">You can also add an additional audio track by using the <strong><em>&#8220;Add Track&#8221;</em></strong> option. This is particularly useful if you have an audio track in your preferred language, and would like to add it to your video.</p>
<p class="np">Similarly, you can also delete existing tracks that you don&#8217;t need.</p>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Subtitles_Tab">Subtitles Tab</span></h2>
<p class="compact">You can add Subtitle tracks to your video file by clicking on <strong><em>&#8220;Import SRT&#8221;</em></strong>. Your subtitle needs to be in SRT format for this to work.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbsub1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbsub1.jpg" width="674" height="345" alt="Handbrake Subtitles Tab" /></a><i>Handbrake Subtitles Tab</i>
</div>
<p class="compact">Handbrake can <strong>softcode</strong>(mux) or <strong>hardcode</strong>(embed) the Subtitle track to your Video, according to your wish. Softcode means that the subtitle file won&#8217;t be &#8220;written&#8221; to your video, whereas in hardcode, it is. The advantage of softcode is that you can turn the subtitles OFF whenever it is not required, or switch to another subtitle track in a different language. The disadvantage is, it won&#8217;t be displayed if the device does not support the subtitle format.</p>
<p class="compact">You can also adjust the <strong>offset time</strong> for the subtitle, which would delay or advance the start time of the subtitle track, according to your requirement.</p>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Chapters_Tab">Chapters Tab</span></h2>
<p class="compact">You can use the options provided in this tab to edit existing chapter markers in your source file, import existing chapters from a csv file to your output file, or export the chapters in your source file to a csv file.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbchap1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbchap1.jpg" width="674" height="345" alt="Handbrake Chapters Tab" /></a><i>Handbrake Chapters Tab</i>
</div>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Presets">Presets</span></h2>
<p class="compact">Handbrake has numerous built in presets which you could use to simplify your encoding task. You can also create your own custom preset by clicking the <strong><em>&#8220;Add&#8221;</em></strong> button, or remove existing presets by clicking &#8220;Remove&#8221;.</p>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbpre1.jpg" target="_blank"><img loading="lazy" decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/hbpre1.jpg" width="257" height="547" alt="Handbrake Presets" /></a><i>Handbrake Presets</i>
</div>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Recommended_Settings">Recommended Settings:</span></h2>
<p class="compact">I&#8217;ll only provide the recommended settings for Constant Quality method, as it&#8217;s just not possible to provide the average bitrate without having a look at the video. The average bitrate differs a lot from video to video, and I don&#8217;t think it is right to give you a &#8220;safe&#8221; bitrate, which could leave you with a file that is much larger than required.</p>
<p class="compact"><b>For Mobile Devices:</b></p>
<div class="highlight spaced">
<ul class="emplist">
<li class="spaced">Container: MP4; Resolution: Height: 640 (Keep AR);</li>
<li class="spaced">Video Codec: x264; Preset: Very Fast; Tune: Film; Profile: Auto; RF: &gt;=24;</li>
<li>Audio Codec: AAC; Audio Bitrate: =&lt;160.</li>
</ul>
</div>
<p class="compact"><b>For HDTVs (Or Monitors):</b></p>
<div class="highlight spaced">
<ul class="emplist">
<li class="spaced">Container: MP4; Resolution: Height: 720 (&gt;27&#8243; screens) 1080 (27&#8243; and above screens) (Keep AR);</li>
<li class="spaced">Video Codec: x264; Preset: Fast; Tune: Film; Profile: Auto; RF: Between 18 and 20;</li>
<li>Audio Codec: AAC; Audio Bitrate: &gt;=160.</li>
</ul>
</div>
<p class="compact"><b>For Web:</b></p>
<div class="highlight spaced">
<p class="compact">HTML 5 supports embedding video and audio onto an html page using &lt;video&gt; and &lt;audio&gt; tags. The advantage of this is that you don&#8217;t need a plugin (like flash) to play video on your browser. This means the video will load much quicker, and will use less system resources.</p>
<p class="compact">The formats supported till now by HTML5 are:</p>
<ul class="emplist">
<li class="spaced">H.264 video and AAC audio in MP4 container, licensing fee needs to be paid for content distribution, fully supported by Handbrake.</li>
<li class="spaced">VP3 video with vorbis audio in Ogg container, no licensing fee, Ogg container not supported by Handbrake.</li>
<li>VP8 Video with Vorbis audio in webm container, no licensing fee, webm container not supported by Handbrake.</li>
</ul>
<p class="compact">I&#8217;ve only provided the formats at least partially supported by Handbrake. For the full list, see: <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats" target="_blank">HTML5 Supported Media Formats</a></p>
<p class="compact">Your best bet to legally distribute paid content on your webpage would be to transcode your file to VP8 video and vorbis audio in Matroska(MKV) container, and to convert it to webm format using a 3rd party converter.</p>
</div>
<p class="compact">Take note that these settings that I&#8217;ve given are not foolproof. It is quite possible ymmv. It all depends on your source file. It is always a good practice to see what happens when you encode using a slightly different setting.</p>
<p class="compact">That&#8217;s the reason I&#8217;ve given you these settings. So that you have a starting point, from where on you could tweak the settings according to your requirements.</p>
<h2 class="shead" style="padding-top: 30px; margin-bottom: 20px;"><span id="Anamorphic_Revisited">Anamorphic Revisited:</span></h2>
<p class="compact">If you haven&#8217;t dozed off till now, well, good job! Now it&#8217;s time to reap your metaphorical reward (remember, I told you I&#8217;d explain Anamorphic in detail in a later part. This is the &#8220;later part&#8221;!).</p>
<p class="compact">Things could get a bit complicated here, but I&#8217;ll try to keep it as simple as possible.</p>
<p class="compact">Quite a few times, you may come across a video file that will be displayed in a squished or stretched form in your computer. You check the resolution and the Aspect Ratio of the video, but that seems correct. So, what is the problem?</p>
<p class="compact">In order to fully understand this, you need to know about <strong>Display Aspect Ratio (DAR)</strong>, <strong>Storage/Frame Aspect Ratio (SAR/FAR)</strong> and <strong>Pixel Aspect Ratio (PAR)</strong>. So, here goes:</p>
<div class="highlight spaced">
<ul class="emplist">
<li class="spaced"><b>Display Aspect Ratio (DAR):</b> This is a flag in the video file that tells the display device what Aspect Ratio to display the Video at. Most commonly this value is either 4:3 (for SD content) or 16:9(for HD or Widescreen content).</li>
<li class="spaced"><b>Storage/Frame Aspect Ratio (SAR/FAR):</b> This is the actual Aspect Ratio of your video file, not taking into consideration the PAR. This is the value that you&#8217;ll get when you divide the width and height data of your video file obtained from the Media Info in your video Player.</li>
<li><b>Pixel Aspect Ratio (PAR):</b> Pixel, or picture element, is the smallest element in an image. But the harsh truth is, this element is not always a square. For computer graphics, it is a square, but for analog broadcast content, it needs to be rectangular. Pixel Aspect Ratio is a ratio that defines the shape of each pixel.</li>
</ul>
<p class="compact">The math between these three values is:</p>
<p class="compact"><b>DAR = SAR x PAR</b></p>
</div>
<div class="special sp_blue notestar spaced">
<strong>Note:</strong> Please keep in mind that the terms resolution, PAR, actually have nothing to do with analog video. In an analog video, vertical resolution is nothing but the number of scanning lines and horizontal resolution depends on either the system bandwidth(for broadcast content) or the sampling rate. PAR in essence, is actually a pretty clever hack that allows us to view the converted analog content properly.
</div>
<p class="compact">Most analog broadcast content are not in 4:3(Standard Definition) or 16:9(Widescreen) aspect ratio. The resolution of NTSC content is 720&#215;480(AR=1.5) and that of PAL content is 720&#215;576(AR=1.25).</p>
<p class="compact">Now, imagine what would happen if PAL or NTSC content is viewed on a computer monitor (or any digital display, for that matter). As monitors generally have an aspect ratio of 4:3 or 16:9 these images would look distorted horizontally.</p>
<p class="compact">In order to compensate for this, NTSC contents are scaled horizontally by a factor of about 0.9(or 1.2 for widescreen) to obtain a resolution of approximately 640&#215;480(854&#215;480 for widescreen), while PAL contents are scaled horizontally by a factor of 1.07(or 1.45 for widescreen) to obtain a resolution of approximately 768&#215;576(or 1024&#215;576 for widescreen). This factor is known as Pixel Aspect Ratio (PAR), as it can be said that each pixel is scaled by this factor to fit the display screen.</p>
<p class="compact"><strong>Anamorphic</strong> is the property of scaling the width of a video by a factor (PAR) in order to correct its Aspect Ratio.</p>
<p class="compact">To apply anamorphic property to a video:</p>
<ol>
<li>Set the <strong><em>Anamorphic</em></strong> Option to <strong><em>Custom</em></strong>.</li>
<li>Then you&#8217;ll be able to tweak the PAR, Source Resolution and the display width values.</li>
<li>The resolution shown in the Width and Height boxes will be the actual resolution of your output. The Aspect Ratio that you get from this resolution is the SAR. The resolution that you get by scaling the width by the PAR value is the Resolution at which the video file will be displayed on your screen. The Aspect Ratio that you get from this resolution is the DAR.</li>
<li>Keep changing the PAR and viewing the preview, till you obtain an output preview that is satisfactory.</li>
</ol>
<p class="compact">Anamorphic is also widely used to preserve the resolution of widescreen movies in DVDs. This is what the tag &#8220;Enhanced for Widescreen&#8221; means in a DVD. Films used to be shot at an aspect ratio of 4:3 or 1.33. From there, this value underwent a series of changes, from 1.66, 2.59, 2.35, 1.85, 2.20, 2.76, etc. Even today, there is no standard Aspect ratio at which films are supposed to be shot, and much of it depends on the choice of the director. There are three ways to accommodate such films on a standard display:</p>
<ol>
<li>Stretch the video to fit on the screen, while preserving the Aspect Ratio. So, for wider Aspect Ratios the sides of the picture gets cropped off, while for taller Aspect ratios the top and bottom of the picture gets cropped off. This method is called <strong>Pan and Scan</strong>.</li>
<li>For wider aspect ratios, movies are encoded with black bars on the top and bottom of the frame. This is called <strong>letterboxing</strong>. And for taller Aspect Ratios, black bars are added to the sides of the frame. This is called <strong>Pillarboxing</strong>. This method was popular before anamorphic. It isn&#8217;t required now as modern displays and DVD players add black spaces by itself to fix the Aspect Ratio.</li>
</ol>
<p class="compact">Both these methods are rendered useless now with the advent of Anamorphic.</p>
<ol start="3">
<li>By using <strong>anamorphic</strong> property, the PAR of the movie is adjusted to view it in both 4:3 as well as 16:9 displays. This method is the one that is most widely used now. Pan and scan crops off a part of the frame, while Letterboxing/Pillarboxing reduces the effective resolution, as part of the resolution is comprised of just black lines. So, anamorphic in this sense, offers the best of both worlds. It preserves the Resolution and the Aspect Ratio while keeping the video frame intact.</li>
</ol>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/anamorphic-1.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/anamorphic-1.jpg" alt="Original Frame" /></a><i>(a). Original Frame</i><br />
2.35 Aspect Ratio; PAR=1
</div>
<div class="compact image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/anamorphic-2.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/anamorphic-2.jpg" alt="SAR Output Frame" /></a><i>(b). The Frame as it would be stored on an Anamorphic Disk<br />
The SAR Output. The frame appears squished.</i>
</div>
<div class="spaced image">
<a href="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/anamorphic-3.jpg" target="_blank"><img decoding="async" class="aligncenter compact" src="https://www.ocfreaks.com/imgs/guide_tutorial/handbrake_part1/anamorphic-3.jpg" alt="16:9 Anamorphic Frame" /></a><i>(c). The Frame as it would be displayed on a 16:9 Display<br />
Black bars are added to the top and bottom of the frame while playback, to compensate for the wider Aspect Ratio of 2.35(letterboxing).</i>
</div>
<p class="compact">You&#8217;ll need to crop off the bars if you want to convert a pillarboxed/letterboxed source to anamorphic.</p>
<h2 style="padding-top: 30px; margin-bottom: 20px;"><span id="Closing_Notes">Closing Notes</span></h2>
<p style="margin-bottom: 5px;">I&#8217;ll be ending this tutorial here.</p>
</p>
<p>For the <strong><em>&#8220;Advanced&#8221;</em></strong> tab, I&#8217;ll be making a separate post. Part 2 Coming soon!</p>
<p>The post <a href="https://www.ocfreaks.com/handbrake-complete-tutorial-part-1-transcode-compress-videos/">Handbrake Complete Tutorial Part 1: How to Transcode &#038; Compress Videos</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/handbrake-complete-tutorial-part-1-transcode-compress-videos/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2559</post-id>	</item>
		<item>
		<title>Net Neutrality and what you can do to save it in India</title>
		<link>https://www.ocfreaks.com/net-neutrality-and-what-you-can-do-to-save-it-in-india/</link>
					<comments>https://www.ocfreaks.com/net-neutrality-and-what-you-can-do-to-save-it-in-india/?noamp=mobile#respond</comments>
		
		<dc:creator><![CDATA[Saby D'silva]]></dc:creator>
		<pubDate>Wed, 15 Apr 2015 15:00:45 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[featured]]></category>
		<category><![CDATA[news]]></category>
		<guid isPermaLink="false">http://www.ocfreaks.com/?p=2540</guid>

					<description><![CDATA[<p>When Sir Tim Berners Lee invented the World Wide Web, he wanted it to be open and neutral. This was the way he dreamt it to be, and it most definitely is the way it&#8217;s supposed to be. Come today, and this idea is being threatened by a bunch of selfish money grubbing nitwits. Net [&#8230;]</p>
<p>The post <a href="https://www.ocfreaks.com/net-neutrality-and-what-you-can-do-to-save-it-in-india/">Net Neutrality and what you can do to save it in India</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img decoding="async" class="aligncenter" src="https://www.ocfreaks.com/imgs/netneutrality.png" /></p>
<p>When Sir Tim Berners Lee invented the World Wide Web, he wanted it to be open and neutral. This was the way he dreamt it to be, and it most definitely is the way it&#8217;s supposed to be. Come today, and this idea is being threatened by a bunch of selfish money grubbing nitwits.</p>
<p>Net neutrality is the simple idea that all internet traffic should be treated equally by the ISPs, with no preferential treatment given on any basis. The idea is to keep the internet open and free to all. The threat looming over this is due to the greediness of a few network providers, who leap at any opportunity they get to make some extra cash.</p>
<p>In India, it all started back in December 2014, when Airtel decided that it was fair game to exclude VoIP from it&#8217;s standard data plans, and offered separate packs for it. As expected, Airtel drew flack from all four corners for this act, and they were forced to roll it back.</p>
<p>Later in February 2015, Facebook with Reliance Communication, launched Internet.org in India, a platform that aimed to provide free net connectivity to users via an app. The catch? You could only access the websites which they have partnered up with.</p>
<p>And now, Airtel announced it&#8217;s Airtel Zero Plan, by which App and Web developers could pay a fee to make their app or site toll free for the end users. Sounds great, right? Airtel is calling it a win-win solution, which benefits the users as well as the developers, and they wouldn&#8217;t be wrong in thinking so.</p>
<p>But I urge you to see the bigger picture. The Internet wouldn&#8217;t be place it is now if it weren&#8217;t for the existence of many websites that have made a significant mark. But most of these sites had humble origins. Even the mighty Google had its origins in a garage. So, it really isn&#8217;t right to assume that all new startups will have the sufficient means to consistently pay for the plan.  And as end users, we would naturally be inclined to use the free alternative. So, such biasing would eliminate competition as we know it completely. And this is not all. Now, Airtel has announced this plan. If this goes on track, then it&#8217;s safe to assume that other providers will follow suit with similar plans of their own as well. So, to level the playing field with the bigwigs, the startups will have to pay the tariff to all the network providers,  which is next to impossible. So, we&#8217;ll have apps that will be toll free in one network, and carry a hefty toll on others. And whats to stop the network providers from throttling the websites not on the platform in the future?</p>
<p>Right now, the final say in whether to pass this plan or not rests in the hands of TRAI. But that is not the only issue. Internet.org has already been passed and has an Android app. And trust me, newer threats will emerge. So, in light of all this, I urge all the fellow netizens to respond to TRAI of this here: <a href="http://www.savetheinternet.in/">Save the Internet</a>. All it takes are a few clicks, and it gives you the satisfaction of knowing that whatever the outcome, at least you did your part.</p>
<p>Here ends the rant!</p>
<p>Link to TRAI&#8217;s consultation paper on OTT : <a href="http://www.trai.gov.in/WriteReaddata/ConsultationPaper/Document/OTT-CP-27032015.pdf">Consultation Paper on Regulatory Framework for Over-the-top (OTT) services</a></p>
<p>Also, read this worderful article by Sir Tim Berners Lee on Net neutrality: <a href="http://ec.europa.eu/commission/2014-2019/ansip/blog/guest-blog-sir-tim-berners-lee-founding-director-world-wide-web-foundation_en">Net Neutrality is critical for Europe&#8217;s Future.</a></p>
<p>The post <a href="https://www.ocfreaks.com/net-neutrality-and-what-you-can-do-to-save-it-in-india/">Net Neutrality and what you can do to save it in India</a> appeared first on <a href="https://www.ocfreaks.com">OCFreaks!</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.ocfreaks.com/net-neutrality-and-what-you-can-do-to-save-it-in-india/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2540</post-id>	</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Page Caching using Disk: Enhanced 

Served from: www.ocfreaks.com @ 2026-03-05 18:31:03 by W3 Total Cache
-->