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
#26
Quote:Btw, is there any way to do chunked encoding without frame detection?
Not in the way it is usually done.
What you is usually done for chunked encoding is:
  • detect the GOPs in the source (navigation to key frames is usually fast, and cutting on key frames is lossless)
  • split the source into chunks (containing xy GOPs)
  • encode each of these chunk separately
  • merge chunks
(here it is assumed that key frames are mainly where it makes sense, so that a chunk ideally contain a whole scene)
Problems occur if your source has damaged/buggy in the time codes or the contained data.
vfr can be tricky if audio&video are processed at the same time.
If your video is cfr, contains 'proper' (= in meaningful places) key frames, you process audio and video separately and your source is not damaged, there should be no sync issues.

Downside of chunking, especially when using small chunks is that rate control can't be as good and you additionally may end up with 'pumping' effects (= quality jumps between junks).

Quote:For example, I want to encode 3h file with QTGMC in 3 parts (so I don't lose speed)?
lose speed? Compared to what? How?

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)