{"id":551,"date":"2014-11-14T17:36:00","date_gmt":"2014-11-14T17:36:00","guid":{"rendered":"http:\/\/endcrawl.com\/blog\/?p=551"},"modified":"2022-05-25T17:56:38","modified_gmt":"2022-05-25T17:56:38","slug":"2048x1152-is-a-total-crock","status":"publish","type":"post","link":"http:\/\/endcrawl.com\/blog\/2048x1152-is-a-total-crock\/","title":{"rendered":"2k is not 2048&#215;1152"},"content":{"rendered":"<p>If you are doing your final post finishing in&nbsp;2048&#215;1152, you are actually hurting your picture, and you should stop at once. Here&#8217;s why.<\/p>\n<p><!--more--><\/p>\n<p>Juggling your post finishing rasters has always been a mild pain. To wit:<\/p>\n<ul>\n<li>HD masters are 1920x<strong>1080<\/strong><\/li>\n<li>DCI &#8220;Scope&#8221; is 2048&#215;858<\/li>\n<li>DCI &#8220;Flat&#8221; is 1998x<strong>1080<\/strong><\/li>\n<li>DCI &#8220;Full Container&#8221; is 2048x<strong>1080<\/strong><\/li>\n<\/ul>\n<p>Did you notice anything there?<\/p>\n<h3>Deliverables are 1080 lines or less. (Always.)<\/h3>\n<p>Yep: none of those&nbsp;containers have&nbsp;more than 1080 lines of resolution. As far as DCI, SMPTE, your SDI cables, and Digital&nbsp;Cinema&nbsp;projectors are all concerned, &#8220;2k&#8221;&nbsp;still means 1080 lines of resolution <em>or less<\/em>. This turns out to be pretty important.<\/p>\n<p>If you are finishing in a 16&#215;9 aspect ratio, and you&#8217;re finishing in &#8220;2k&#8221;, you&#8217;re actually going to deliver &#8230; 1920&#215;1080. Which is HD.<\/p>\n<p>Likewise, if you&#8217;re finishing in 1.85 and &#8220;2k&#8221;, your actual deliverable is 1998&#215;1080. Again, 1080 lines. Not 1152.<\/p>\n<p>But wait, it gets worse. Putting&nbsp;that extra 14% of spatial resolution into your DI&nbsp;<strong>can actually damage the picture that your audience sees<\/strong>. Why? Because your fancy, non-standard 1152 lines of resolution will have to be&nbsp;scaled down to 1080 lines of resolution. But that&#8217;s not a&nbsp;big deal, right? You just press the magic resize button, and there&#8217;s no penalty, right?<\/p>\n<h3>2048&gt;1920 is not enough Oversampling<\/h3>\n<p>It&#8217;s become conventional wisdom that oversampling is a good thing. Shoot 4k or 5k, finish in 2k or HD. No problem. I happen to agree with that, and Charles Poynton made an eloquent, <a href=\"http:\/\/hollywoodpostalliance.org\/?page_id=7539\" target=\"_blank\" rel=\"noopener noreferrer\">5-hour long argument<\/a> to that effect at a recent talk at the&nbsp;HPA retreat.<\/p>\n<p>But in this case we&#8217;re oversampling not by&nbsp;200% or 300%. We&#8217;re oversampling&nbsp;by a lousy 14%.&nbsp;To <a href=\"http:\/\/www.nattressplugins.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">quote one guy<\/a> on the topic:<\/p>\n<p style=\"padding-left: 30px;\"><em>&#8220;Resampling an image works well for large factors. A small factor like 2048\/1920 is difficult to achieve as you basically need a very very large filter kernel to effectively remove just the frequencies you don&#8217;t want. In other words, the reject band (1920&gt;2048) is very narrow as compared to the size of the image. That doesn&#8217;t give much room for any filtering to work in.&#8221;<\/em><\/p>\n<p>In plain English: a small resize factor will only serve to soften your image. You&#8217;re stepping on your image. You&#8217;re making it&nbsp;worse.<\/p>\n<p>You (or your client) may have thought that you were finishing in &#8220;better resolution&#8221; by &#8220;going 2k&#8221;.&nbsp;But since you have to down-res all&nbsp;deliverables\u2014you know, the thing that your audience will actually see\u2014that higher resolution is not only thrown away, but contributes to&nbsp;an&nbsp;inferior final picture.<\/p>\n<p>[UPDATE: Graeme Nattress writes, &#8220;what will happen is necessarily softening, but aliasing because the downsampling filter, if inadequate, will let through aliasing artifacts.&#8221; Thanks Graeme.]<\/p>\n<p>This is true for finishing in 1.78 (16&#215;9) or&nbsp;1.85. It&#8217;s not true for finishing in 2.39. If you&#8217;re finishing 2.39, stick with 2k, since you&#8217;re only at 858 lines of res anyway.<\/p>\n<h3>Canary In the Coal Mine<\/h3>\n<p>Scrolling&nbsp;credits turn out to be the canary in the coal mine here, because they can look really, really bad when you resize them by a small factor. They are&nbsp;very unforgiving. Our slate tries to point this out as politely as possible:<\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"aligncenter size-full wp-image-994\" src=\"http:\/\/endcrawl.com\/blog\/wp-content\/uploads\/2014\/11\/Screen-Shot-2016-04-14-at-08.23.27.png\" alt=\"Endcrawl slate about resizing\" width=\"758\" height=\"410\" srcset=\"http:\/\/endcrawl.com\/blog\/wp-content\/uploads\/2014\/11\/Screen-Shot-2016-04-14-at-08.23.27.png 758w, http:\/\/endcrawl.com\/blog\/wp-content\/uploads\/2014\/11\/Screen-Shot-2016-04-14-at-08.23.27-200x108.png 200w, http:\/\/endcrawl.com\/blog\/wp-content\/uploads\/2014\/11\/Screen-Shot-2016-04-14-at-08.23.27-300x162.png 300w, http:\/\/endcrawl.com\/blog\/wp-content\/uploads\/2014\/11\/Screen-Shot-2016-04-14-at-08.23.27-680x368.png 680w, http:\/\/endcrawl.com\/blog\/wp-content\/uploads\/2014\/11\/Screen-Shot-2016-04-14-at-08.23.27-400x216.png 400w, http:\/\/endcrawl.com\/blog\/wp-content\/uploads\/2014\/11\/Screen-Shot-2016-04-14-at-08.23.27-50x27.png 50w\" sizes=\"(max-width: 758px) 100vw, 758px\" \/><\/p>\n<p>(<a href=\"http:\/\/endcrawl.com\">Endcrawl<\/a> solves the problem&nbsp;by giving you unlimited renders in all aspect ratios, so you can kick out&nbsp;a native, shimmer-free version for each individual deliverable.)<\/p>\n<p>(Of course, that doesn&#8217;t help if someone is <em>still resizing your render after the fact<\/em>.)<\/p>\n<p>But janky-looking end credits actually just illuminate a deeper problem in your overall post workflow: it makes exactly zero sense to finish in 2048&#215;1152.<\/p>\n<h3>A Better Workflow<\/h3>\n<p>If you shot in 2048&#215;1152, there&nbsp;may not much you can do there. Sorry.<\/p>\n<p>But if you&nbsp;acquired your picture at 2.4k or higher, and your DI is not&nbsp;native RAW, then you should be working from&nbsp;RGB frames that are in&nbsp;the actual raster of your Original Aspect Ratio (OAR). Meaning&nbsp;either&nbsp;2048&#215;858, 1998&#215;1080, or good old 1920&#215;1080. Again, nothing wrong with HD. It&#8217;s great.<\/p>\n<p>For UHD\/4k, just double all of those numbers.<\/p>\n<p>But don&#8217;t finish in 2048&#215;1152. It yields no&nbsp;benefit and can only serve to&nbsp;step on&nbsp;your final picture.<\/p>\n<p>Unfortunately,&nbsp;this bad trend actually&nbsp;looks&nbsp;to be on uptick. It doesn&#8217;t help that ARRI <a href=\"http:\/\/www.arri.com\/news.html?article=1059&amp;cHash=8e74cc354907ef6e67ff2c9e4767e805\" target=\"_blank\" rel=\"noopener noreferrer\">recently introduced<\/a> a 2048&#215;1152 ProRes recording mode on their Alexa camera. Don&#8217;t blame ARRI though. There are legitimate reasons&nbsp;for <em>shooting<\/em> 2048&#215;1152, but those legit reasons all have to do with cropping your final output. (E.g. it&#8217;s good kung fu&nbsp;to shoot ARRI ProRes 2048&#215;1152&nbsp;and crop for a 2048&#215;858 finish.)<\/p>\n<p>In summary:<\/p>\n<ul>\n<li>There are no 2k display or delivery standards above 1080 lines of res.<\/li>\n<li>The difference between HD and 2k is actually minimal and you shouldn&#8217;t care. HD looks great, even on large screens.<\/li>\n<li>If you&#8217;re finishing in 1.78 or 1.85, <em>you should not<\/em> be working at 1152&nbsp;lines of resolution. This is very bad kung fu.<\/li>\n<li>Tell your post house, and if they are annoyed, just blame it all Pliny.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Dear post houses: we need to talk. You&#8217;re stepping on my picture. 1152p is not a thing.<\/p>\n","protected":false},"author":1,"featured_media":997,"comment_status":"closed","ping_status":"closed","sticky":true,"template":"","format":"standard","meta":[],"categories":[9,13,16],"tags":[],"_links":{"self":[{"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/posts\/551"}],"collection":[{"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/comments?post=551"}],"version-history":[{"count":9,"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/posts\/551\/revisions"}],"predecessor-version":[{"id":3260,"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/posts\/551\/revisions\/3260"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/media\/997"}],"wp:attachment":[{"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/media?parent=551"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/categories?post=551"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/endcrawl.com\/blog\/wp-json\/wp\/v2\/tags?post=551"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}