![]() Resultant file: very poor framerate, blurryĮncoding speed – solid 10 fps, c. Hardware: Raspberry Pi 3, overclocked to 1350mhz ![]() The resultant file is massively compressed, and always 1MB regardless of which switches I pass (constant rate factor, scaling, audio codec etc)Ī discussion on github suggests that it's very early days for the hardware h264 encoder, but I wondered if anyone else has had better results?įor the record, encoding a 30 second audio video file of an Atari ST demo screen: Unfortunately the results when transcoding video are somewhat underwhelming. ![]() I’ve used Technoid’s valuable instructions to rebuild my custom ffmpeg, incorporating hardware h264 encoding.Īfter commenting out line 1956 in libavcodec/utils.c, I'm able to run ffmpeg with the new encoder.
0 Comments
Leave a Reply. |