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.

[HELP] why i set x264 reference frame is 3, but encoded file is 4?
#1
why i set x264 reference frame is 3, but encoded file is 4? how to solve?

[Image: eqaM6xLrpyk8j3G.jpg]
Reply
#2
I can reproduce this, but to me this does not look like a Hybrid bug, but a problem of MediaInfo (or x264?), since:
a. Hybrid does call x264 properly with --ref 3
b. x264s SEI data (MediaInfo reports this as 'Encoding settings' also reports 'ref=3'
might be related to: https://sourceforge.net/p/mediainfo/bugs/485/
Seems like it's related to whether b-frame pyramid is used or not.
All in all it does not look like something that could be changed in Hybrid.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
according to the intro,

[Image: 7NBAgOq5YdbC8wy.jpg]


so if have time, is it always good to use max reference frame 4, b-frame 16, and preset placebo, to get the best encode quality? thanks
Reply
#4
Yes, maxing out ref-frames and b-frames and using placebo should improve compressibility.
Best encoding quality can only be archived through lossless encoding.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
Ah, I think I just encountered this, too; perhaps in a different perspective/setting.

Expected output
: Slow, Ref 5
Output: Slow, Ref 4

As far as I can tell, "--ref 5" was not called because "--preset slow" supposedly has it already, according to the help popup in the presets. Is it possible that Slow has ref 4 instead? Tried manually adding the command line --ref 5, but it just eats that input, too.
Sample debug of my tinkering attached.
[attachment=1356]
Reply
#6
This depends on whether b-pyramid is used or not.
-> Not a bug in Hybrid, inconsistency between x264 and MediaInfo, nothing for me to do.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)