19:23 <pftbest> Hello! I am looking at video_timings table in video.py and I see that 1920x1080@30Hz format says pix_clk: 89.01e6. Shouldn't this be 74.25 as defined in SMPTE standard?

20:23 <uis[m]> <pftbest> "Hello! I am looking at video_tim..." <- https://tomverbeure.github.io/video_timings_calculator

20:23 <tpb> Title: Video Timings Calculator (at tomverbeure.github.io)

20:31 <pftbest> uis[m]: There is no 30 fps format on that website) But if I choose 1080p60 and then change to 30 it suggests me this clock values [79.75,68.25,65.76,74.25]

20:31 <pftbest> There is no 89.01

20:34 <pftbest> I'm not sure where this weird clock is from. But the SMPTE timings for 1080p30 are the same as 1080p60, so you can just set timings to 1080p60 and use 74.25 clock to get 30 fps

21:08 <uis[m]> <pftbest> "There is no 89.01" <- Play with H Blank and V Blank on custom. 280 and 270 got me 89.1

21:43 <pftbest> I agree it's possible to make such a format if you really try, the question is why such a weird format is in litex source code :)

21:44 <pftbest> Why not just use the standard one which uses much lower clock frequency and can be rounded up to 75 mhz without any issues