<?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/"
	>

<channel>
	<title>nikon &#8211; Huahua&#8217;s Tech Road</title>
	<atom:link href="https://zxi.mytechroad.com/blog/tag/nikon/feed/" rel="self" type="application/rss+xml" />
	<link>https://zxi.mytechroad.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 05 May 2025 06:16:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.2</generator>

<image>
	<url>https://zxi.mytechroad.com/blog/wp-content/uploads/2017/09/cropped-photo-32x32.jpg</url>
	<title>nikon &#8211; Huahua&#8217;s Tech Road</title>
	<link>https://zxi.mytechroad.com/blog</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Nikon Z8/Z9 HLG Deepdive &#124; HLG 详解 VS N-LOG</title>
		<link>https://zxi.mytechroad.com/blog/photography/nikon-z8-z9-hlg-deepdive-hlg-%e8%af%a6%e8%a7%a3-vs-n-log/</link>
					<comments>https://zxi.mytechroad.com/blog/photography/nikon-z8-z9-hlg-deepdive-hlg-%e8%af%a6%e8%a7%a3-vs-n-log/#respond</comments>
		
		<dc:creator><![CDATA[zxi]]></dc:creator>
		<pubDate>Sun, 04 May 2025 04:45:51 +0000</pubDate>
				<category><![CDATA[Photography]]></category>
		<category><![CDATA[HDR]]></category>
		<category><![CDATA[hlg]]></category>
		<category><![CDATA[n-log]]></category>
		<category><![CDATA[nikon]]></category>
		<category><![CDATA[photography]]></category>
		<guid isPermaLink="false">https://zxi.mytechroad.com/blog/?p=10405</guid>

					<description><![CDATA[网上关于HLG的资料相对来说还是比较匮乏的，更别说是针对Nikon Z系列了。之前做过一期简单的HLG直出视频，但是没人感兴趣&#8230; 首先HLG是一条用于交付的Gamma曲线，向下兼容SDR内容，这也就注定了它的上限比较低，这也是为什么大部分人对它不感兴趣的原因(另一个原因是它是HDR）。HLG的动态范围(尤其高光)比不过N-LOG，更别说Slog3了。暗部表现则比其他LOG曲线要好一些。它最大的优点就是所见即所得，不需要LUT还原，也(基本)不需要向右曝光，特别适合HDR直出。不过如果你只做SDR的话，还是选N-LOG吧。只是2025年了，拍N-LOG/NRAW获得12+档动态范围，然后再压缩到8档，我只能说历史的包袱太沉重了。可以参见：再谈苹果XDR显示器与HDR之殇 响应曲线 我在Z8上实测响应曲线，测试方法：调整曝光，记录不同曝光值下中灰的IRE，并和理论值做对比。为了统一起见，我将中灰(Stop 0)都曝光到36%。Note: HLG中灰的理论值应该是38%，不过差别不大，大概0.2档左右。结果实测N-LOG的时候，同样用了95 (37.2%)的斑马线，最后得到的曝光是38%，不管了，差不多就行了。 Z8 HLG实测曲线和理论曲线在[-7, +3]的范围内贴合的非常不错。实测的HLG底噪大约是3%,。两者在高光部分差别比较大，HLG中灰以上一档就开始变成对数曲线，和Stops应该是线性关系，但实测下来，Nikon对+3档以上的高光做了一些保护，曲线非常平滑，因此也比理论多了1档的高光，中灰以上5.3档才会完全过曝。 但比起N-LOG还是差了一档多。另外HLG模式下，IRE最大值不是100，而是97左右，斑马线需要设置在245才会有效果。 N-LOG的曲线大致上贴合的还是不错的。noise floor，13%左右。-7档开始就贴着了。只有在+1档到+2档的附近有点波动。高光部分的斜率还是太大了，竟然比理论值还大一些。中灰以上6档就过曝了。只比HLG好了不到1档。 名义ISO 众所周知，N-LOG的基础ISO是800，第二档则是ISO 4000。HLG的基础ISO是400，第二档是ISO 2000。无论是N-LOG还是HLG，它们的ISO都是名义ISO，或者说等效ISO。在相同照度下，我使用相同的参数(1/400s F/4 ISO800)拍摄灰卡，N-LOG和HLG的IRE是36%左右，SDR则为52%。三者还原之后中灰的亮度大体上相同（SDR稍微亮了一点），证实了&#8221;名义&#8221;ISO。但实际上传感器使用的ISO是多少呢？其实都是ISO 100左右，如何证明呢？拍摄同样的白卡，记录刚刚过曝时的曝光参数。N-LOG: 1/30s F/4 ISO 800HLG:&#8230;]]></description>
										<content:encoded><![CDATA[
<p>网上关于HLG的资料相对来说还是比较匮乏的，更别说是针对Nikon Z系列了。之前做过一期简单的HLG直出视频，但是没人感兴趣&#8230;</p>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe title="为什么没人用？HLG HDR直出初体验含新手教程 Ft. Nikon Z8" width="500" height="281" src="https://www.youtube.com/embed/7WcQtb5We6E?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<p>首先HLG是一条用于<strong>交付</strong>的Gamma曲线，向下兼容SDR内容，这也就注定了它的上限比较低，这也是为什么大部分人对它不感兴趣的原因(另一个原因是它是HDR）。HLG的动态范围(尤其高光)比不过N-LOG，更别说Slog3了。暗部表现则比其他LOG曲线要好一些。它最大的优点就是所见即所得，不需要LUT还原，也(基本)不需要向右曝光，特别适合HDR直出。不过如果你只做SDR的话，还是选N-LOG吧。只是2025年了，拍N-LOG/NRAW获得12+档动态范围，然后再压缩到8档，我只能说历史的包袱太沉重了。可以参见：<a href="https://zxi.mytechroad.com/blog/hdr/%e5%86%8d%e8%b0%88%e8%8b%b9%e6%9e%9cxdr%e6%98%be%e7%a4%ba%e5%99%a8%e4%b8%8ehdr%e4%b9%8b%e6%ae%87/" data-type="post" data-id="10387">再谈苹果XDR显示器与HDR之殇</a></p>



<h2 class="wp-block-heading">响应曲线</h2>



<p>我在Z8上实测响应曲线，测试方法：调整曝光，记录不同曝光值下中灰的IRE，并和理论值做对比。为了统一起见，我将中灰(Stop 0)都曝光到36%。Note: HLG中灰的理论值应该是38%，不过差别不大，大概0.2档左右。结果实测N-LOG的时候，同样用了95 (37.2%)的斑马线，最后得到的曝光是38%，不管了，差不多就行了。</p>



<figure class="wp-block-image size-large"><a href="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/hlg-vs-nlog.png"><img fetchpriority="high" decoding="async" width="1024" height="688" src="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/hlg-vs-nlog-1024x688.png" alt="" class="wp-image-10423" srcset="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/hlg-vs-nlog-1024x688.png 1024w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/hlg-vs-nlog-300x202.png 300w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/hlg-vs-nlog-768x516.png 768w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/hlg-vs-nlog-1536x1032.png 1536w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/hlg-vs-nlog.png 1584w" sizes="(max-width: 1024px) 100vw, 1024px" /></a></figure>



<p>Z8 HLG实测曲线和理论曲线在[-7, +3]的范围内贴合的非常不错。实测的HLG底噪大约是3%,。两者在高光部分差别比较大，HLG中灰以上一档就开始变成对数曲线，和Stops应该是线性关系，但实测下来，Nikon对+3档以上的高光做了一些保护，曲线非常平滑，因此也比理论多了1档的高光，中灰以上5.3档才会完全过曝。 但比起N-LOG还是差了一档多。另外HLG模式下，IRE最大值不是100，而是97左右，斑马线需要设置在245才会有效果。</p>



<p>N-LOG的曲线大致上贴合的还是不错的。noise floor，13%左右。-7档开始就贴着了。只有在+1档到+2档的附近有点波动。高光部分的斜率还是太大了，竟然比理论值还大一些。中灰以上6档就过曝了。只比HLG好了不到1档。</p>



<h2 class="wp-block-heading">名义ISO</h2>



<p>众所周知，N-LOG的基础ISO是800，第二档则是ISO 4000。HLG的基础ISO是400，第二档是ISO 2000。无论是N-LOG还是HLG，它们的ISO都是名义ISO，或者说等效ISO。在相同照度下，我使用相同的参数(1/400s F/4 ISO800)拍摄灰卡，N-LOG和HLG的IRE是36%左右，SDR则为52%。三者还原之后中灰的亮度大体上相同（SDR稍微亮了一点），证实了&#8221;名义&#8221;ISO。但实际上传感器使用的ISO是多少呢？其实都是ISO 100左右，如何证明呢？拍摄同样的白卡，记录刚刚过曝时的曝光参数。<br>N-LOG: 1/30s F/4 ISO 800<br>HLG: 1/30s F/4 ISO 400<br>SDR: 1/30s F/4 ISO 80 (NL profile, Active D-lighting off)<br>进光量相同，传感器同时过曝了，表明实际ISO是相同的。<br>等效ISO也可以这么理解：<br>N-LOG拍摄时欠曝3档，后期还原时把中灰提亮3档，以起到保护高光的目的。<br>HLG拍摄时欠曝2档，后期还原时把中灰提亮2档，以起到保护高光的目的。<br>这也就是为什么按照标准曝光（将中灰曝到36% IRE)，N-LOG暗部噪点爆炸，需要使用向右曝光的原因之一。<br>HLG则相当于找了一个平衡点，欠曝2档，等效于使用ISO 400拍视频，对于全画幅来说勉强可以接受吧。<br></p>



<h2 class="wp-block-heading">HLG quality 设置</h2>



<p>由于是面向直出的交付曲线，只有H.265编码支持HLG。虽然Nikon贴心的提供了HLG质量选项，但这里有个坑，在默认的设置下，相机是会对HLG的画面进行锐化的，导致使用超级锐的Z卡扣镜头时会产生过度锐化的情况。需要将Quick Sharp设置成-1才能获得未锐化的画面。有需要的话，也可以将对比度和饱和度也降低一些，推荐-1。</p>



<figure class="wp-block-image size-large"><a href="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.33.50 PM.jpg"><img decoding="async" width="1024" height="685" src="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.33.50 PM-1024x685.jpg" alt="" class="wp-image-10407" srcset="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.33.50 PM-1024x685.jpg 1024w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.33.50 PM-300x201.jpg 300w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.33.50 PM-768x514.jpg 768w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.33.50 PM-1536x1028.jpg 1536w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.33.50 PM.jpg 1856w" sizes="(max-width: 1024px) 100vw, 1024px" /></a></figure>



<p class="has-text-align-center"></p>



<figure class="wp-block-image size-large"><a href="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.40.11 PM-scaled.jpg"><img loading="lazy" decoding="async" width="1024" height="513" src="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.40.11 PM-1024x513.jpg" alt="" class="wp-image-10409" srcset="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.40.11 PM-1024x513.jpg 1024w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.40.11 PM-300x150.jpg 300w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.40.11 PM-768x385.jpg 768w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.40.11 PM-1536x769.jpg 1536w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/Screenshot-2025-05-03-at-9.40.11 PM-2048x1026.jpg 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>



<p class="has-text-align-center">不同Quick Sharp模式下的波形图</p>



<figure class="wp-block-image size-large"><a href="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/contrast-scaled.jpg"><img loading="lazy" decoding="async" width="1024" height="576" src="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/contrast-1024x576.jpg" alt="" class="wp-image-10413" srcset="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/contrast-1024x576.jpg 1024w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/contrast-300x169.jpg 300w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/contrast-768x432.jpg 768w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/contrast-1536x864.jpg 1536w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/contrast-2048x1152.jpg 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>



<p class="has-text-align-center">调整对比度</p>



<figure class="wp-block-image size-large"><a href="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/saturation-scaled.jpg"><img loading="lazy" decoding="async" width="1024" height="576" src="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/saturation-1024x576.jpg" alt="" class="wp-image-10414" srcset="https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/saturation-1024x576.jpg 1024w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/saturation-300x169.jpg 300w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/saturation-768x432.jpg 768w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/saturation-1536x864.jpg 1536w, https://zxi.mytechroad.com/blog/wp-content/uploads/2025/05/saturation-2048x1152.jpg 2048w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>



<p class="has-text-align-center">调整饱和度</p>
]]></content:encoded>
					
					<wfw:commentRss>https://zxi.mytechroad.com/blog/photography/nikon-z8-z9-hlg-deepdive-hlg-%e8%af%a6%e8%a7%a3-vs-n-log/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Nikon Z8 HLG / N-Log Stops vs IRE</title>
		<link>https://zxi.mytechroad.com/blog/photography/nikon-z8-hlg-nlog-stops-vs-ire/</link>
					<comments>https://zxi.mytechroad.com/blog/photography/nikon-z8-hlg-nlog-stops-vs-ire/#respond</comments>
		
		<dc:creator><![CDATA[zxi]]></dc:creator>
		<pubDate>Tue, 09 Jul 2024 05:02:45 +0000</pubDate>
				<category><![CDATA[Photography]]></category>
		<category><![CDATA[expousre]]></category>
		<category><![CDATA[hlg]]></category>
		<category><![CDATA[nikon]]></category>
		<category><![CDATA[nlog]]></category>
		<category><![CDATA[nraw]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[z8]]></category>
		<guid isPermaLink="false">https://zxi.mytechroad.com/blog/?p=10133</guid>

					<description><![CDATA[Recently I switched from N-RAW to H.265 / HLG for quicker HDR workflow in Final Cut Pro, basically just drop the clips in a HLG&#8230;]]></description>
										<content:encoded><![CDATA[
<p>Recently I switched from N-RAW to H.265 / HLG for quicker HDR workflow in Final Cut Pro, basically just drop the clips in a HLG timeline and that&#8217;s it, just like the iPhone&#8217;s Dolby Vision (HLG HDR) footage.</p>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="85mm 手动镜头打鸟 | 鸽子求偶 | 加拿大鹅 | Nikon Z8 | 4K HDR" width="500" height="281" src="https://www.youtube.com/embed/CAySu64so1g?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<p>I did some test about IRE vs stops in HLG mode and compared that to the <a href="https://download.nikonimglib.com/archive3/hDCmK00m9JDI03RPruD74xpoU905/N-Log_Specification_(En)01.pdf">theoretical N-Log curve</a>.</p>



<p>Setup: I expouse the 18% midgray to 36% IRE in HLG mode to match that with N-Log. Adjust the exposure time first then aperture, ISO to over and under expose the midgray for IRE readings.</p>



<p>Note: Techincally, you should expose midgray to <strong>38% IRE</strong> in HLG mode (<a href="https://xtremestuff.net/recording-editing-with-hybrid-log-gamma-part-1/">ref</a>), diffuse white will be around <strong>75% IRE</strong>, 75%+ is for specular highlights (0~3 stops over diffuse white).</p>



<h2 class="wp-block-heading">Stops vs IRE</h2>



<figure class="wp-block-image size-large"><a href="https://zxi.mytechroad.com/blog/wp-content/uploads/2024/07/Nikon-Z8-_-Stops-vs-IRE-huahua-1.png"><img loading="lazy" decoding="async" width="1024" height="681" src="https://zxi.mytechroad.com/blog/wp-content/uploads/2024/07/Nikon-Z8-_-Stops-vs-IRE-huahua-1-1024x681.png" alt="" class="wp-image-10136" srcset="https://zxi.mytechroad.com/blog/wp-content/uploads/2024/07/Nikon-Z8-_-Stops-vs-IRE-huahua-1-1024x681.png 1024w, https://zxi.mytechroad.com/blog/wp-content/uploads/2024/07/Nikon-Z8-_-Stops-vs-IRE-huahua-1-300x200.png 300w, https://zxi.mytechroad.com/blog/wp-content/uploads/2024/07/Nikon-Z8-_-Stops-vs-IRE-huahua-1-768x511.png 768w, https://zxi.mytechroad.com/blog/wp-content/uploads/2024/07/Nikon-Z8-_-Stops-vs-IRE-huahua-1.png 1212w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>



<p>First of all, we can see that HLG curve is more contrastive than N-Log. Highlights will be clipped after <strong>5 stops over midgray</strong> which I think is OK for a lot of scences. N-Log retains more infornation in the highlights (if not over-exposed) up to 6.3 stops at the cost of noiser shadows. HLG has more detials in the shadow area, <strong>noise floor is about 2%</strong> at ISO 400 (12.5% for N-Log).</p>



<p>Another thing intresting is that the HLG curve is very steep from -1 to +3 stops but quickly saturated afterwards (non-linear anymore), highlights are compressed and will clipped around <strong>96% IRE</strong>, making sure to set the <strong>high zebra to 245</strong> when shooting HLG.</p>



<h2 class="wp-block-heading">Base ISO for HLG and N-Log</h2>



<p>Nikon Z8&#8217;s HLG has a &#8220;nominal&#8221; base ISO 400. Under the hood, the sensor is working at ISO 100, shadows will be boosted by <strong>2 stops</strong> while highlights will be intact, bascially you are shooting at ISO 100 with 2 stops under to protect highlights.</p>



<p>N-Log has a &#8220;nominal&#8221; base ISO 800. Same as HLG, the sensor is working at ISO 100, shadows will be boosted by <strong>3 stops</strong> while highlights will be intact, bascially you are shooting at ISO 100 with 3 stops under to protect highlights. However, you will see a lot of noise in shadow area due to insufficient light and 1.3 ~ 1.7 stops &#8220;over-exposure&#8221; is usually needed to compensate that to get clean image. </p>



<h2 class="wp-block-heading">Consolution</h2>



<p>HLG has a pretty good balance between highlights and shadows, very user friendly for HDR workflow. Unlike N-Log, there is no need to over-expose (even 1 stop under looks good to me), no camera LUT needed for restoration, zero or minimum color grading needed. Another advantage of HLG over N-Log is monitoring, most of the time you can rely on the screen/viewfinder (with zebra on) to adjust the exposure and only open the waveform if needed. </p>
]]></content:encoded>
					
					<wfw:commentRss>https://zxi.mytechroad.com/blog/photography/nikon-z8-hlg-nlog-stops-vs-ire/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Nikon Z8/Z9 Video Format / Bitrate / Compression ratio &#124; NRAW &#124; ProRes &#124; ProRes RAW &#124; H.265</title>
		<link>https://zxi.mytechroad.com/blog/photography/nikon-z8-prores-prores-raw-bitrate-and-compression-ratio/</link>
					<comments>https://zxi.mytechroad.com/blog/photography/nikon-z8-prores-prores-raw-bitrate-and-compression-ratio/#respond</comments>
		
		<dc:creator><![CDATA[zxi]]></dc:creator>
		<pubDate>Sat, 15 Jun 2024 17:26:28 +0000</pubDate>
				<category><![CDATA[Photography]]></category>
		<category><![CDATA[bitrate]]></category>
		<category><![CDATA[codec]]></category>
		<category><![CDATA[compression]]></category>
		<category><![CDATA[nikon]]></category>
		<category><![CDATA[nraw]]></category>
		<category><![CDATA[prores]]></category>
		<category><![CDATA[prores raw]]></category>
		<category><![CDATA[z8]]></category>
		<guid isPermaLink="false">https://zxi.mytechroad.com/blog/?p=10121</guid>

					<description><![CDATA[The Nikon official site didn&#8217;t provide the birate for ProRes / ProRes RAW, I did some test my self, here&#8217;re the results. I only tested&#8230;]]></description>
										<content:encoded><![CDATA[
<p>The <a href="https://onlinemanual.nikonimglib.com/z8/en/video_frame_size_and_rate_options_41.html">Nikon official site</a> didn&#8217;t provide the birate for ProRes / ProRes RAW, I did some test my self, here&#8217;re the results. I only tested fullframe (FX) in ~4K resolution. </p>



<h2 class="wp-block-heading">ProRes Raw 12Bit</h2>



<style type="text/css">
	table.tableizer-table {
		font-size: 14px;
		border: 1px solid #CCC; 
		font-family: Arial, Helvetica, sans-serif;
	} 
	.tableizer-table td {
		padding: 4px;
		margin: 3px;
		border: 1px solid #CCC;
	}
	.tableizer-table th {
		background-color: #104E8B; 
		color: #FFF;
		font-weight: bold;
	}
</style>
<table class="tableizer-table">
<thead><tr class="tableizer-firstrow"><th>Resolution / FPS</th><th>Bitrate (Mbps)</th><th>Compression Ratio</th></tr></thead><tbody>
 <tr><td>4140 x 2330 60p</td><td>3350</td><td>1.977</td></tr>
 <tr><td>4140 x 2330 50p</td><td>2810</td><td>1.964</td></tr>
 <tr><td>4140 x 2330 30p</td><td>1620</td><td>2.044</td></tr>
 <tr><td>4140 x 2330 25p</td><td>1360</td><td>2.029</td></tr>
 <tr><td>4140 x 2330 24p</td><td>1280</td><td>2.070</td></tr>
</tbody></table>



<p>ProRes Raw has a very low compression ratio of 2, which suggests that it might be lossless compressed, which takes more spaces than Nikon&#8217;s lossy N-RAW, 2.5x of the high quality and 4.5x of the normal quality!</p>



<h2 class="wp-block-heading">ProRes HQ 422 10Bit</h2>



<style type="text/css">
	table.tableizer-table {
		font-size: 14px;
		border: 1px solid #CCC; 
		font-family: Arial, Helvetica, sans-serif;
	} 
	.tableizer-table td {
		padding: 4px;
		margin: 3px;
		border: 1px solid #CCC;
	}
	.tableizer-table th {
		background-color: #104E8B; 
		color: #FFF;
		font-weight: bold;
	}
</style>
<table class="tableizer-table">
<thead><tr class="tableizer-firstrow"><th>Resolution / FPS</th><th>Bitrate (Mbps)</th><th>Compression Ratio</th></tr></thead><tbody>
 <tr><td>3840 x 2160 60p</td><td>1800</td><td>5.273</td></tr>
 <tr><td>3840 x 2160 50p</td><td>1500</td><td>5.273</td></tr>
 <tr><td>3840 x 2160 30p</td><td>910</td><td>5.215</td></tr>
 <tr><td>3840 x 2160 25p</td><td>760</td><td>5.204</td></tr>
 <tr><td>3840 x 2160 24p</td><td>730</td><td>5.201</td></tr>
</tbody></table>



<p>With compression ratio of 5.2, ProRes is still 2x the size of the normal quality n-raw!  Though the former one has 1.5x number of pixels to deal with (YUV422 vs Bayer). </p>



<p>I hope Nikon could provide more options for ProRes via firmware updates. A 10x~12x compression ratio version (ProRes LT 422) will be very useful to balance between quality and disk space.</p>



<h2 class="wp-block-heading">H.265 420 10 bit</h2>



<style type="text/css">
	table.tableizer-table {
		font-size: 14px;
		border: 1px solid #CCC; 
		font-family: Arial, Helvetica, sans-serif;
	} 
	.tableizer-table td {
		padding: 4px;
		margin: 3px;
		border: 1px solid #CCC;
	}
	.tableizer-table th {
		background-color: #104E8B; 
		color: #FFF;
		font-weight: bold;
	}
</style>
<table class="tableizer-table">
<thead><tr class="tableizer-firstrow"><th>Resolution / FPS</th><th>Bitrate (Mbps)</th><th>Compression Ratio</th></tr></thead><tbody>
 <tr><td>7680 x 4320 30p</td><td>400</td><td>47.461</td></tr>
 <tr><td>7680 x 4320 25p</td><td>400</td><td>39.551</td></tr>
 <tr><td>7680 x 4320 24p</td><td>400</td><td>37.969</td></tr>
 <tr><td>3840 x 2160 120p</td><td>400</td><td>47.461</td></tr>
 <tr><td>3840 x 2160 100p</td><td>400</td><td>39.551</td></tr>
 <tr><td>3840 x 2160 60p</td><td>340</td><td>27.918</td></tr>
 <tr><td>3840 x 2160 50p</td><td>340</td><td>23.265</td></tr>
 <tr><td>3840 x 2160 30p</td><td>190</td><td>24.979</td></tr>
 <tr><td>3840 x 2160 25p</td><td>190</td><td>20.816</td></tr>
 <tr><td>3840 x 2160 24p</td><td>190</td><td>19.984</td></tr>
</tbody></table>



<p>For H.265, there is no option for all-intra, and only in 420. Compression ratio is much higher given long GOP. One thing to note, that bitrate is variable depend on the content, i.e. very dark scene will have a much lower bitrate (&lt;100Mbps for 4K60).</p>



<h2 class="wp-block-heading">NRAW High Quality 12 bit</h2>



<style type="text/css">
	table.tableizer-table {
		font-size: 14px;
		border: 1px solid #CCC; 
		font-family: Arial, Helvetica, sans-serif;
	} 
	.tableizer-table td {
		padding: 4px;
		margin: 3px;
		border: 1px solid #CCC;
	}
	.tableizer-table th {
		background-color: #104E8B; 
		color: #FFF;
		font-weight: bold;
	}
</style>
<table class="tableizer-table">
<thead><tr class="tableizer-firstrow"><th>Resolution / FPS</th><th>Bitrate (Mbps)</th><th>Compression Ratio</th></tr></thead><tbody>
 <tr><td>8256 x 4644 60p</td><td>5780</td><td>4.555</td></tr>
 <tr><td>8256 x 4644 50p</td><td>4810</td><td>4.561</td></tr>
 <tr><td>8256 x 4644 30p</td><td>2890</td><td>4.555</td></tr>
 <tr><td>8256 x 4644 25p</td><td>2410</td><td>4.552</td></tr>
 <tr><td>8256 x 4644 24p</td><td>2310</td><td>4.559</td></tr>
 <tr><td>4128 x 2322 120p</td><td>3840</td><td>3.428</td></tr>
 <tr><td>4128 x 2322 100p</td><td>2900</td><td>3.783</td></tr>
 <tr><td>4128 x 2322 60p</td><td>1740</td><td>3.783</td></tr>
 <tr><td>4128 x 2322 50p</td><td>1450</td><td>3.783</td></tr>
 <tr><td>4128 x 2322 30p</td><td>870</td><td>3.783</td></tr>
 <tr><td>4128 x 2322 25p</td><td>730</td><td>3.757</td></tr>
 <tr><td>4128 x 2322 24p</td><td>700</td><td>3.761</td></tr>
</tbody></table>



<p>First of all, given 4.5 compression ratio, NRAW is definitely a lossy codec. Interesting thing is that 8K&#8217;s compression ratio is higher than 4K&#8217;s. 4.5 vs 3.7.</p>



<h2 class="wp-block-heading">NRAW Normal Quality 12 bit</h2>



<style type="text/css">
	table.tableizer-table {
		font-size: 14px;
		border: 1px solid #CCC; 
		font-family: Arial, Helvetica, sans-serif;
	} 
	.tableizer-table td {
		padding: 4px;
		margin: 3px;
		border: 1px solid #CCC;
	}
	.tableizer-table th {
		background-color: #104E8B; 
		color: #FFF;
		font-weight: bold;
	}
</style>
<table class="tableizer-table">
<thead><tr class="tableizer-firstrow"><th>Resolution / FPS</th><th>Bitrate (Mbps)</th><th>Compression Ratio</th></tr></thead><tbody>
 <tr><td>8256 x 4644 60p</td><td>3470</td><td>7.587</td></tr>
 <tr><td>8256 x 4644 50p</td><td>2890</td><td>7.591</td></tr>
 <tr><td>8256 x 4644 30p</td><td>1740</td><td>7.565</td></tr>
 <tr><td>8256 x 4644 25p</td><td>1450</td><td>7.565</td></tr>
 <tr><td>8256 x 4644 24p</td><td>1390</td><td>7.576</td></tr>
 <tr><td>4128 x 2322 120p</td><td>1750</td><td>7.522</td></tr>
 <tr><td>4128 x 2322 100p</td><td>1460</td><td>7.513</td></tr>
 <tr><td>4128 x 2322 60p</td><td>880</td><td>7.479</td></tr>
 <tr><td>4128 x 2322 50p</td><td>730</td><td>7.513</td></tr>
 <tr><td>4128 x 2322 30p</td><td>440</td><td>7.479</td></tr>
 <tr><td>4128 x 2322 25p</td><td>370</td><td>7.412</td></tr>
 <tr><td>4128 x 2322 24p</td><td>350</td><td>7.522</td></tr>
</tbody></table>



<p>For normal quality, the compression ratio is even higher, reaching 7.5:1 which is not bad for all-intra. </p>
]]></content:encoded>
					
					<wfw:commentRss>https://zxi.mytechroad.com/blog/photography/nikon-z8-prores-prores-raw-bitrate-and-compression-ratio/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
