The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.3.12-nmm1 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



Selur's Little Message Board
[HELP] rife - encoding freezes - Printable Version

+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html)
+--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html)
+--- Thread: [HELP] rife - encoding freezes (/thread-3859.html)

Pages: 1 2

RE: rife - encoding freezes - Selur - 28.09.2024

Guessing by your emphasizations, you don't understand why Bwdif is loaded and why I chose 120fps:
QTGMC can use Bwdif (depending on the settings, which is why the plugin is loaded).
I used 120fps as an example of a frame rate above 59.94fps which QTGMC created from the interlaced 29.97fps source I used.

Cu Selur

RE: rife - encoding freezes - humanoid86 - 28.09.2024

https://drive.google.com/file/d/1XlzHHr9_CvWHFKMaGPxhzYQKTCZJuEyn/view?usp=sharing

от 23,97(24)фпс до 60фпс

ужасные прыжки пропали при переходе микро-сцен

RE: rife - encoding freezes - Selur - 28.09.2024

For "field-blended" input, a field matcher (TFM, VFM) will be used, not a deinterlacer.

Cu Selur

RE: rife - encoding freezes - humanoid86 - 29.09.2024

https://drive.google.com/file/d/1VlFGWF7RUs06fiAPbl9Ejsx5_3ZmjUU9/view?usp=sharing

What is this indicator for??? 0.150 is indicated

Huh

RE: rife - encoding freezes - Selur - 29.09.2024

Will adjust the tool-tip for the next version to:
Quote:Scene change:
Change the scene change threshold, so scene changes are properly detected. When properly detected, instead of interpolating across scene changed, the last frame before a scene change will be repeated to avoid artifacts.
For SD content, using 0.1 to 0.15 seems to work fine.
For HD content, instead of using 0.15 using 0.5 seems to work better.
hope that clears things up.

Cu Selur

RE: rife - encoding freezes - humanoid86 - 29.09.2024

(29.09.2024, 08:00)Selur Wrote: Will adjust the tool-tip for the next version to:
Quote:Scene change:
Change the scene change threshold, so scene changes are properly detected. When properly detected, instead of interpolating across scene changed, the last frame before a scene change will be repeated to avoid artifacts.
For SD content, using 0.1 to 0.15 seems to work fine.
For HD content, instead of using 0.15 using 0.5 seems to work better.
hope that clears things up.

Cu Selur

choose/guess then pray what helped - not Big Grin

It’s better to choose field-blended with bob (ultra-fast) Cool

RE: rife - encoding freezes - Selur - 29.09.2024

Quote:choose/guess then pray what helped - not
That is what Vapoursynth Preview is for; seeing what setting xy does.

Quote:It’s better to choose field-blended with bob (ultra-fast)
If blended frames are what you are into, I'm happy you found something that works for you.

Cu Selur

RE: rife - encoding freezes - humanoid86 - 29.09.2024

(29.09.2024, 08:32)Selur Wrote:
Quote:choose/guess then pray what helped - not
That is what Vapoursynth Preview is for; seeing what setting xy does.

That's what I meant - wasting time

run Preview and analysis - many times

Big Grin

RE: rife - encoding freezes - Selur - 29.09.2024

If adjusting values is a waste of time for you, you should not use Hybrid, since that is the main reason, I can think of, to use Hybrid. There are other tools that can do similar things. (StaxRip, MeGui, enhancr, flowframes, rife-app,...)

Hybrid at first is meant for advanced users that want and understand how to tweak stuff. Smile
¯\_(ツ)_/¯

Cu Selur

RE: rife - encoding freezes - humanoid86 - 29.09.2024

OK Big Grin