08:17 <fairway> everybody, can you pass the 60fps vs 30fps video test ?

08:18 <fairway> 'by video test" i mean. there are 2 random videos (one is 30fps, the other is 60fps) can you identify which one is which'

08:44 <noobaroo> fairway It's coincidental that you mention this because lately I've been wondering if pixels are even real at all.

08:50 <fairway> noobaroo i have no idea what you just said

17:06 <nikomo> Hey, I think I found an issue with av1_nvenc, but I can't figure out enough of the issue to write a usable bug report. Anyone got ideas? Running "ffmpeg.exe -y -i test_input.mkv -c:v av1_nvenc debug.mkv" produces a file that plays audio but no video in VLC, and plays video but no audio in Windows's Media Player. h264_nvenc, hevc_nvenc, and libsvtav1 all produce working files. But doing -t 5 with av1_nvenc produces a file that plays both

17:06 <nikomo> video and audio in Media Player. ffmpeg version N-118106-g350ebef112-20241222

17:12 <nikomo> Confirmed on N-118197-gbb85423142-20241231 now too

17:13 <nikomo> I can only assume it's the specific input file being funny, because other samples don't cause it, but I would have imagined telling ffmpeg to re-encode the video stream would take care of any funny business

17:16 <JEEB> not necessarily with stuff like timestamps etc

17:16 <JEEB> you can see timestamps from various points of the flow with `-v verbose -debug_ts`

17:16 <JEEB> (it will print a lot, but sudden jumps should show up)

17:39 <nikomo> Doing an encode with -report now, then I'll do an SVT one and try and look for differences

17:39 <nikomo> I couldn't at a glance see any funny business with timestamps

17:50 <nikomo> There is maybe something interesting about the sample file

17:50 <nikomo> Stream #0:0(jpn), 6, 1/1000: Video: h264 (High), 1 reference frame, yuv420p(progressive, left), 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn (default)

17:50 <nikomo> 1 reference frame?

17:53 <JEEB> that just means that in the checking process it noticed that the stream seems to utilize 1 reference (not sure how far it checks that). nothing unusual, just means it can refer to one other frame. should not affect timestamps

18:02 <nikomo> I see a lot of [vf#0:0 @ 000001400e59e480] Clipping frame in rate conversion by 0.003990, but that also happens on SVT

18:08 <nikomo> I'm fine with software encode, but it is a bit annoying not being able to report this

23:01 <xx> fairway: I can't even tell the difference between 720p and 4k

23:01 <xx> "human eyes can't even see more than 24 fps"