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.

Blocking in H.265 Export
#1
Hello

Really hoping for some assistance with the results I'm getting from a H.265 export.  The export sequence works fine - no problem at all.  The issue is the H.265 export generating blocking in a part of a clip that is blue sky and wispy cloud.  The blocking is very noticeable. 

Any first response would suggest compression artefact.  I too believe this to be the case.  That said I am certain it is at the H.265 export point.  The original clip is a time-lapse generated from Raw stills and exported in Prores 4444 6K. Then in Resolve using the appropriate color space a Mystery box clip is applied (taking the clip to HDR) and then re exported in H.265.  Prior to the H.265 export point the only compression has been from Raw to Prores 4444.  Hardly a compression process that will result in blocking.  Further I have checked this clip in STANDARD DYNAMIC RANGE UHD using H.264 compression and the result is perfectly fine - no blocking.  I have also checked the  HDR Prores 4444 export and it too seems to be clean (this check is not completely fool proof as I have only checked on a standard dynamic range monitor so the picture appears over exposed.  None the less no blocking is evident)

So to me the problem lies in the H.265 export.  All of the settings I am using on the Hybrid H.265 export are as per recommendation of Mystery Box.  These can be seen here . . . https://www.mysterybox.us/blog/2016/10/2...vering-hdr

As a basic summary I am using average bitrate 1 pass, 18000 bitrate, sampling i420 and 10 bit bit depth, Level 5.1 / Main10 / Main.  I have tried doubling the bitrate - blocking problem exists.  My knowledge on this compression process is almost non existent.  I have exhausted my understanding of all the possible causes - but as yet I still have not resolved the blocking.  I would have thought given the color space I am working in as well as the 10 bit bit rate there should be no such problems as this.  

Really hoping someone can suggest a solution.

Thanks in advance
CraigPlease, read the 'Infos needed to fix&reproduce bugs,..'-sticky before you post about a problem.
Reply
#2
My first suggestion when reading your post is:
Rate control in 'average bitrate (1-pass)' isn't that good.
Do not use 'average bitrate (1-pass)', better use 'constant rate factor (1-pass)'.

That said, the blog entry mentions:
Quote:...
Encoding Mode: Average Bitrate (1-Pass)
Target Bitrate: 18,000 - 50,000 kbps
...
while handling, 4k content, so keeping that in mind while using 6k instead of 4k it seems to be obvious, that the lowest bit rate encouraged to use for 4k might be to low for 6k.
-> If you want to stick with 'average bitrate (1-pass)' (against my advice), you will have to use a higher bit rate.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
Much appreciated.  Suggestion led to resolution.
Thanks
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)