search

Chen-tao / webm

Automatically exported from code.google.com/p/webm
0 stars 0 forks source link

vpxenc fps status #537

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
When encode higher resolutions, fps is between 0.00 and 0.02, but usually 0.01.
Could you provide a 3rd digit?

repro
vpxenc encode a video of 4k or 8k

Original issue reported on code.google.com by fbarch...@chromium.org on 26 Jan 2013 at 8:07

GoogleCodeExporter commented 9 years ago 
e.g. on 1080p

Pass 2/2 frame 4993/4993 38912258B   62346b/f 1494830b/s 73715301 ms (0.07 
fps)←[K6.406 63.371 61.595      55F
Stream 0 PSNR (Overall/Avg/Y/U/V) 43.705 46.253 45.722 50.361 50.520

Shows (0.07 fps)
Could you make it 0.
4993/73715301 is 0.06773 fps.  Could you show 3 decimal points? e.g. (0.068 fps)

Original comment by fbarch...@chromium.org on 26 Jan 2013 at 9:47

GoogleCodeExporter commented 9 years ago 
As performance has improved this may be unnecessary.
Its mainly a problem on 4k videos that reports 0.01 fps.
Also theres an ETA now

Original comment by fbarch...@chromium.org on 27 Feb 2013 at 12:47

GoogleCodeExporter commented 9 years ago 
fps status has been changed to ms/f for < 1 fps and fps >= 1
Prefer a consistent format - one or the other, so that output can be put into 
spreadsheets for multiple movies with the same values.

Original comment by fbarch...@chromium.org on 7 Mar 2013 at 9:35

GoogleCodeExporter commented 9 years ago

Original comment by fgalli...@google.com on 14 Mar 2013 at 10:12

GoogleCodeExporter commented 9 years ago 
At the moment, builds being slow, ms/f is more accurate.
I'm noticing on this very long encode that ETA is not coming down as fast as it 
should, while frames are going up... because ms/f is going up.
Pass 2/2 frame 101923/101898 1052410303B 950209320 ms 9322.82 ms/f [ETA 
200:19:28] 45.
ms/f started around 6000 ms/f, and goes up by about 100 ms/f each day.

Original comment by fbarch...@chromium.org on 14 Mar 2013 at 10:22