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.

[BUG] Incorrect range signalling
#28
Ahhh,... different 'chunked encoding'.
Hmmm,...
First thought: one could abuse 'my' 'chunked encoding' by giving it a huge minimum chunk size and thus causing the tool to split into X huge chunks and encode them in parallel. (this probably is not supported in most tools, isn't in Hybrid; + the in parallel probably will cause problems)
Second thought: one could probably write some script or tool to do the whole thing. (split, encode, merge)
Third thought: maybe trying to figure out why the frame rate drops would be the better approach.
If you have a cpu with 'performance' and 'efficiency' cores, maybe looking into forcing the load on the performance or disabling the efficiency cores is the solution.
Could also be some network problem if the source, target or temp lies on a network drive.
Might also be a threading / memory handling issue.

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


Messages In This Thread
Incorrect range signalling - by r3dfx - 23.01.2025, 13:01
RE: Incorrect range signalling - by Selur - 23.01.2025, 16:15
RE: Incorrect range signalling - by r3dfx - 23.01.2025, 16:30
RE: Incorrect range signalling - by Selur - 23.01.2025, 16:44
RE: Incorrect range signalling - by Selur - 23.01.2025, 18:17
RE: Incorrect range signalling - by r3dfx - 23.01.2025, 18:40
RE: Incorrect range signalling - by Selur - 23.01.2025, 18:42
RE: Incorrect range signalling - by r3dfx - 23.01.2025, 20:08
RE: Incorrect range signalling - by r3dfx - 10.02.2025, 20:55
RE: Incorrect range signalling - by Selur - 10.02.2025, 21:01
RE: Incorrect range signalling - by r3dfx - 10.02.2025, 23:49
RE: Incorrect range signalling - by Selur - 11.02.2025, 04:26
RE: Incorrect range signalling - by r3dfx - 11.02.2025, 12:28
RE: Incorrect range signalling - by Selur - 11.02.2025, 19:04
RE: Incorrect range signalling - by r3dfx - 05.03.2025, 18:01
RE: Incorrect range signalling - by Selur - 05.03.2025, 18:09
RE: Incorrect range signalling - by Selur - 05.03.2025, 18:10
RE: Incorrect range signalling - by Selur - 05.03.2025, 18:46
RE: Incorrect range signalling - by r3dfx - 05.03.2025, 19:52
RE: Incorrect range signalling - by Selur - 05.03.2025, 21:09
RE: Incorrect range signalling - by r3dfx - 05.03.2025, 21:44
RE: Incorrect range signalling - by Selur - 05.03.2025, 22:08
RE: Incorrect range signalling - by r3dfx - 11.03.2025, 23:05
RE: Incorrect range signalling - by Selur - 12.03.2025, 06:10
RE: Incorrect range signalling - by r3dfx - Yesterday, 17:11
RE: Incorrect range signalling - by Selur - Yesterday, 18:30
RE: Incorrect range signalling - by r3dfx - Yesterday, 19:04
RE: Incorrect range signalling - by Selur - Yesterday, 19:19
RE: Incorrect range signalling - by r3dfx - Yesterday, 19:53
RE: Incorrect range signalling - by Selur - Yesterday, 20:01
RE: Incorrect range signalling - by r3dfx - Yesterday, 20:44
RE: Incorrect range signalling - by Selur - Yesterday, 21:38
RE: Incorrect range signalling - by r3dfx - Yesterday, 22:10

Forum Jump:


Users browsing this thread: 2 Guest(s)