Jump to content

edrex

Members
  • Posts

    2
  • Joined

  • Last visited

  1. Without it I get a deadlock at around 21s: [h264_v4l2m2m @ 0x2be3250] All capture buffers returned to userspace. Increase num_capture_buffers to prevent device deadlock or dropped packets/frames. and heuristically 32 seems to work. Curious that you haven't seen that. I'm on Armbian bullseye, so maybe it's something new in userland? same kernel I assume.. I left the default quality (`-cbf 12` like regular h.264 encoding?) for testing. I'm wanting to add configurable encoding to filestash's on-demand transcoding settings. Expecting a deep dive into ffmpeg lore to get all those stream-oriented settings working with hardware encoding
  2. Hi @JMCC, I happened upon this thread as I was experimenting with HW encoding for one of my two HC1s, so I was very happy to read your posts and test out your custom ffmpeg build. I'm seeing a modestsubstantial speed boost (1.8x vs 0.9x) compared to the Armbian build. My encode params are `-vcodec h264_v4l2m2m -num_capture_buffers 32 -pix_fmt nv21`. Any additional suggestions? Thanks
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines