Writing to myself. Problem resolved. Wrong timebase.
Thanks.
W dniu 13.02.2018 o 13:56, Marcin Woźniak pisze:
I am using HiSilicon 3516A board, there is no V4L device but other
approach using /dev/venc ioctl calls and MPP API.
I am able to open the encoder, read raw H264 packets but no go, looks
I am using HiSilicon 3516A board, there is no V4L device but other approach
using /dev/venc ioctl calls and MPP API.
I am able to open the encoder, read raw H264 packets but no go, looks like
read_packet is called about 10 times slower than it should.
If i move the code to outside of ffmpeg and
Finnaly i was able to set up timing data in h264 stream.
Trying to save this as -f test.h264 produces good file, trying to mux it
drops FPS to tenth of original (25 fps becomes 2.5 fps and bitrate from
1024 kb/s to little more than 100 kbs).
PTS of every NAL unit is different exactly by 4 (
Hello,
I try to implement an HiSilicon H264 encoder direct input as ffmpeg
libavdevice source (someking like V4L linux for cameras with H264 source
driver).
I successfully recieve H264 packets with NAL units and set correct PTS
according to source packet.
I am stuck at the moment where timing d