x264 t_mod: I get 600 fps instead 25

[blob2500]

:confused:

Hi,
I try x264 t_mod 164 r3106 (x64), from:
https://github.com/jpsdr/x264/releases

but I get huge fps in file output if output is avi.

Example:

script avisynth:

c:\x264t2\x264_x64 --muxer avi --fps 25/1 --crf 22.0 --output "x264r3106tMod_.avi" "inputfile.avs"

"--fps" is ignored, anyone value I put.

ouput file:

General
Complete name : D:\_A_TESTMPG\x264r3106tMod_.avi
Format : AVI
Format/Info : Audio Video Interleave
File size : 4.67 MiB
Duration : 1 s 583 ms
Overall bit rate : 24.8 Mb/s
Writing application : Lavf58.76.100

Video
ID : 0
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L3
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : H264
Duration : 1 s 583 ms
Bit rate : 24.6 Mb/s
Width : 704 pixels
Height : 400 pixels
Display aspect ratio : 16:9
Frame rate : 600.000 FPS
Original frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.146
Stream size : 4.65 MiB (99%)
Writing library : x264 core 164 r3106+55M 24adf88 t_mod_New [(8 & 10)-bit@all X86_64]
Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / fade_compensate=0.00 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=3 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / fgo=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=22.0000 / qcomp=0.60 / qpmin=0:0:0 / qpmax=69:69:69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00 / aq-sensitivity=10.00 / aq-factor=1.00:1.00:1.00 / aq2=0 / aq3=0


It's a bug? Or do I have to set something in x264.exe to get right fps?

Thanks in advance.

(I tried others version, r2969 it's the last one that works.)

[benwaggoner]

Sure sounds like a regression to me!

But why are you trying to make an .avi in 2023?

[jpsdr]

It seems that 2969 is the last version before using the merged code and i redo all the integration of the mods... It's not impossible that unfortunately i broke something, but i'm only building x264, none of the mods are updated, there is, unfortunately, nothing i can do, i don't have the knowledge to work on the mods.
Edit: a long time ago, someone had an issue with avi, tried a modification (pure guess !), but never had a feedback, neither the possibility to give him a test version.
PM me an email address i can send you a test version, no idea if it will work or what it will realy do...

[blob2500]

Thanks for your posts.

But why are you trying to make an .avi in 2023?

Because my old sat-receiver/pvr/player (model: mVision HD 300 Net) supports h.264/HD in AVI container only (or Xvid but SD, not HD). I think it supports playng of .ts too (how recording format), but I don't like this container; I prefer AVI or MKV (that I know them better) for video to archive.

I prefer MKV, however AVI is about common denominator for all my H/W players (but without AAC audio). An other my pvr (Humax 6400s) prefer MKV; AVI doesn't play fine on this, with h264 if start/end code between h.264 NALU in stream has 4 byte (jerky playback), instead 3 byte (smooth playback). But I think "normal"/common Annex B format is with 4 byte (too Avinaptic reports error in stream with 3 bytes).

@ jpsdr

I sent PM to you. Thanks

[blob2500]

What good old version do you recommend that produces avi?

2851 kMod/tMod?

(I know... I could use a recent x264 build and remuxing .264 into .avi via ffmpeg, but I prefer .avi directly).

Thanks.

[jpsdr]

If the last working version in my mod is the 2969, use it instead of tMod, as it will be more up to date than the tMod.
I don't know about kMod.

I took a look at the original tMod code and current, didn't see anything wrong... My actual guess, issue is the big ffmpeg bump : 2 -> 4, and maybe the initialisation part must now be done differently than before, but i have absolutely no knowledge on ffmpeg, so i have no idea how it can be fixed.
It seems it was a MasterNobody patch, maybe he would know what to do to fix...

[blob2500]

If the last working version in my mod is the 2969, use it instead of tMod, as it will be more up to date than the tMod.
I don't know about kMod.
I omitted the 2969 because, if I understood correctly, it has compatibility problems with some TV/hardware players (I remember some Samsung or LG tv)

->

https://code.videolan.org/BugMaster/x264/-/issues/1

https://code.videolan.org/videolan/x264/-/commit/92d36908cbafd2a6edf7e61d69f341027b57f6f8

https://code.videolan.org/videolan/x264/-/commit/f9af2a0f71d0fca7c1cafa7657f03a302da0ca1c


Even the old "Gspot" doesn't identify files made with 2969 as "H264", I think for the same reason.
if I change those SPS headers in the stream with a hex editor(0x00000001676408 -> 0x00000001676400 in my case) it will identify as H264.
Same issue there is in Avidemux 2.8.x encoding (vsWin64 version has r2969 bundled).

original file made r2969

https://i.postimg.cc/Jn5vrg6X/2969orig.jpg

modified with hex editor

https://i.postimg.cc/xC2BSYRY/2969mod.jpg



I took a look at the original tMod code and current, didn't see anything wrong... My actual guess, issue is the big ffmpeg bump : 2 -> 4, and maybe the initialisation part must now be done differently than before, but i have absolutely no knowledge on ffmpeg, so i have no idea how it can be fixed.
It seems it was a MasterNobody patch, maybe he would know what to do to fix...
thank you for your interest. :)

[jpsdr]

Ah... This story of compatibility issue indeed remind me of a very old something, so maybe indeed the r2969 has it...