Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trim HDR 4K source #1234

Closed
madey83 opened this issue Feb 14, 2024 · 7 comments
Closed

Trim HDR 4K source #1234

madey83 opened this issue Feb 14, 2024 · 7 comments

Comments

@madey83
Copy link

madey83 commented Feb 14, 2024

when i have tried cut/trim 4k HDR source i have got this:

Frame Mismatch (v2.35.113)

Target file has 81927 frames, but should have 82047 frames!

StaxRip.ErrorAbortException: Target file has 81927 frames, but should have 82047 frames!
at StaxRip.GlobalClass.ProcessJob(String jobPath)

log.txt

@Dendraspis
Copy link
Collaborator

Dendraspis commented Feb 14, 2024

And I guess you have cut out those exact 120 frames?

EDIT: Ah, ok, I see what the problem is ... have to investigate it.

@madey83
Copy link
Author

madey83 commented Feb 14, 2024

i've tried cut exactly 716 frames...

@Dendraspis
Copy link
Collaborator

716 frames at the beginning, got it.
Might take a while, but I will come to it when I have more information....

@Dendraspis
Copy link
Collaborator

Dendraspis commented Feb 14, 2024

Ok, had to check it now... 😅

The warning is because there is a frame mismatch and the frame mismatch is because of the fact, that those non-re-encoded cuts are only possible when cut at key frames. So if you want to have those exact 716 frames cut out, you have to re-encode.

For now you can disable the warning in Options » Misc. In one of the next versions the Frame Mismatch check will ignore the Copy/Mux runs.

EDIT:
Should also check what happens with the metadata....

@madey83
Copy link
Author

madey83 commented Feb 15, 2024

image

on the left hand side you have key frame found by this command
.\ffprobe.exe -select_streams v -show_entries packet=pts_time,flags -of compact -read_intervals 700%800 E:\HDR.mkv | findstr K

on the right hand side you have shown information how many frames were selected. Cutted was in this approach 715 frames.

in this log you can find information that i was able to trim/cut on 716 frame... All my DoVi sources were cutted without problem.

DoVi_staxrip.log

this is how key frames look like for DoVi source

image

@madey83
Copy link
Author

madey83 commented Feb 15, 2024

Avidemux was able to cut some frames and left only 24... which i could not cut further...

this is how avidemux show frame 716
image

@Dendraspis
Copy link
Collaborator

Will be fixed with v2.37....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants