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.

RIFE Manual Scene Cut
#1
As you may have seen, another user of RIFE proposed to specify a list of frames corresponding to scene changes instead of relying on automatic scene detection. Is there a way to inject these frame numbers using Hybrid? The automatic scene cut is not particularly reliable over a long show.

https://forum.doom9.org/showthread.php?t=185379
Reply
#2
For me, personally, using 0.10 usually works fine, and I prefer adjusting the scene change detection than having to manually search for all key frames.
I could write code for it, but it seems like an awful lot of trouble. (Hybrid would basically use the code that was posted in the thread.)
Got an example where adjusting the threshold doesn't work?

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#3
I've attached a clip with glitches at the following timecodes
00:00:14:02
00:00:19:02
00:00:27:03

https://we.tl/t-bWGEuIfvkK
Reply
#4
Will look at it after work. (I assume that is a source that will create glitches even with adjusted scene threshold and not some already messed up content.)

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#5
Ah, I see the problem you have.
You are not cropping your source and you have large black bars and additionally large portions of the image do not change, thus most of the image stays unchanged. Smile
You would have to lower the scene threshold way more.
0.08 works fine here for all but the last scene change, the one would require 0.04. (without cropping)
=> will added a new option Smile

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#6
Uploaded a new dev version, which should support instead of using misc.SCDetect specifying the scene changes manually.

Cu Selur
Reply
#7
Thank you for this, I hope to test this soon and let you know how I get on!
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)