Hi.
Just a guess: Are you possibly reusing a 1st-pass statistics file from a
different encode, or did you change parameters between 1st and 2nd pass
which affect the GOP size limits or scene detection sensitivity?
Just to exclude the most obvious first, before digging deeper if there
was a known GOP type bug for this version specifically.
Posting the whole command lines for both passes would certainly be helpful.
Zero Un schrieb am 17.03.2019 um 13:17:
Hello i have this mistake many times on a encode
x265 [warning]: specified frame type (5) at 77330 is not compatible with
keyframe interval
x265 [error]: slice=I but 2pass stats say B
_______________________________________________
x265-devel mailing list
x265-devel@videolan.org
https://mailman.videolan.org/listinfo/x265-devel
--
Fun and success!
Mario *LigH* Rohkrämer
maito:cont...@ligh.de
_______________________________________________
x265-devel mailing list
x265-devel@videolan.org
https://mailman.videolan.org/listinfo/x265-devel
