The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 198 - File: inc/plugins/google_seo.php PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 135 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once



This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Preserving 4:1:1 colorspace from DV video source
#1
Hey Selur,

I have some DV video that I'm deinterlacing and encoding, and I want to make sure I don't lose color information by using the wrong colorspace.  I read elsewhere that 4:1:1 and 4:2:0 are basically storing the same information in different ways.  Is that your understanding?

If using 4:2:0 is inappropriate for 4:1:1 source video, I'd appreciate any guidance.  I'm encoding in x265.

Thank you in advance!
Reply
#2
In the case of 4:1:1, for every 4 luma samples horizontally, there is only one chroma sample (either U or V), and for every luma sample vertically, there is one chroma sample. In contrast, in 4:2:0, for every 4 luma samples horizontally, there are two chroma samples, and for every 2 luma samples vertically, there are two chroma samples.
=> they are not storing the same information.
4:2:0 has more chroma information compared to 4:1:1, where as 4:1:1 has more luma information.
That said, usually the difference it not visibly noticeable.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
Would 4:2:2 capture the extra 4:1:1 information without altering the video in a negative way, or would some undesirable conversion process happen?  I understand filesize might be a bit larger, but if 4:2:2 will retain the information I'd lose by going to 4:2:0, then I'd rather go with 4:2:2.
Reply
#4
Yes, you could use 4:2:2 and enable 'Convert to target color space after source filter' and if all of the filters you use support that color space you could lessen potential losses.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
I and my family videos thank you Smile
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)