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

Scene change detection is very different to av-scenechange result #885

Open
L4cache opened this issue Oct 10, 2024 · 4 comments
Open

Scene change detection is very different to av-scenechange result #885

L4cache opened this issue Oct 10, 2024 · 4 comments

Comments

@L4cache
Copy link

L4cache commented Oct 10, 2024

sc.json
an.json

It looks like some offset is introduced and get progressively worse:
120-119=1
217-215=2
354-351=3
...

Source is 24000/1001 fps YUV420P10 HEVC in MKV

@L4cache
Copy link
Author

L4cache commented Oct 10, 2024

With FFmpeg 7.1 dlls. 7.0.2 dlls works fine.

@shssoichiro
Copy link
Collaborator

Do you know which one is correct?

@L4cache
Copy link
Author

L4cache commented Oct 11, 2024

av-scenechange one is correct.
I think this could be silimilar to HomeOfAviSynthPlusEvolution/L-SMASH-Works#73
Because:

  1. This problem happens with FFmpeg 7.1 dlls, but 7.0.2 dlls works fine.
  2. I did more test with H.264 file and didn't saw this problem.

@shssoichiro
Copy link
Collaborator

I suspected something similar as well. A fix would be very important. In the meantime, there are a couple of workarounds:

  • Use --chunk-method bestsource, this has a slow indexing time when it first loads the input, but it is guaranteed to be frame accurate
  • Alternatively, transcode to H.264 lossless before encoding to the final format with av1an.

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

No branches or pull requests

2 participants