Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Henrik Bodenhoff via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Cc: Michael Henrik Bodenhoff <MIBO@milestone.dk>
Subject: [FFmpeg-devel] Flushing while decoding , but need already decoded frames
Date: Fri, 24 May 2024 09:35:22 +0000
Message-ID: <AM9PR02MB6850EAFBA235B3A0781E3A23BCF52@AM9PR02MB6850.eurprd02.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2344 bytes --]

Hi ,

my team recently had to abandon switching to using FFmpeg from specific decoder implementations (NvDEC, Intel Media SDK , IPP and quite a few codec specific decoders) because of big performance issues because of the way FFmpeg works….. or at least we think it is (we’re FFmpeg noobs 😃  )

It's actually an issue we also had with Intel Media SDK,  leading us to pay Intel to extend Media SDK to do what we needed.

Our product is a video surveillance system, and that means we have to decode a LOT of video streams simultaneously.

For motion detection we want to only decode keyframes, and skip P and B frames , and that works fine with FFmpeg most of the time, except for when the video stream contains B frames.
Without B-Frames it’s really simple (simplified pseudocode) :

while(true)
{
  receiveStreamCompleteFrame();
  If(KeyFrame)
  {
    avcodec_send_packet();
    if(avcodec_receive_frame()==0)
    {
       // do motion detection
    }
  }
}

But! with B Frames FFmpeg doesn’t return keyframes when they are decoded, they are kept, and we can’t seem to flush them out. avcodec_flush_buffers allow us to continue to next keyframe, but it doesn’t seem to give us the keyframe we just gave to FFmpeg with avcodec_send_packet.

while(true)
{
  receiveStreamCompleteFrame();
  If(KeyFrame)
  {
    avcodec_send_packet();
    if(avcodec_receive_frame()==0)
    {
       // do motion detection
    }
    Else
    {
      avcodec_flush_buffers();
      if(avcodec_receive_frame()==0)
      {
         // do motion detection
      }
    }
  }
}

Calling avcodec_receive_frame after calling avcodec_flush_buffer results in -11 and no frame

is there anyway around this ? And if not, could FFmpeg be made to have this functionality ?

I tried contacting one of the FFmpeg consultants from https://ffmpeg.org/consulting.html but never got a response

Michael Bodenhoff
Principal Software Engineer
FT01
Email: mibo@milestone.dk

[Linkedin Logo]<https://linkedin.com/company/milestone-systems>[Twitter Logo]<https://twitter.com/milestonesys>[Youtube Logo]<https://www.youtube.com/user/Milestonesys>[Facebook Logo]<https://www.facebook.com/milestonesys/>[Instagram Logo]<https://www.instagram.com/milestonesystems/>

[Milestone Logo]<https://www.milestonesys.com/>


[-- Attachment #1.2: image001.png --]
[-- Type: image/png, Size: 183 bytes --]

[-- Attachment #1.3: image002.png --]
[-- Type: image/png, Size: 3730 bytes --]

[-- Attachment #1.4: image003.png --]
[-- Type: image/png, Size: 6222 bytes --]

[-- Attachment #1.5: image004.png --]
[-- Type: image/png, Size: 4532 bytes --]

[-- Attachment #1.6: image005.png --]
[-- Type: image/png, Size: 2547 bytes --]

[-- Attachment #1.7: image006.png --]
[-- Type: image/png, Size: 12009 bytes --]

[-- Attachment #1.8: image007.png --]
[-- Type: image/png, Size: 8722 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

             reply	other threads:[~2024-05-24  9:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  9:35 Michael Henrik Bodenhoff via ffmpeg-devel [this message]
2024-05-24 10:02 ` Andreas Rheinhardt
2024-05-24 11:39   ` Andrey Turkin
2024-05-24 12:20     ` Ronald S. Bultje
2024-05-24 12:52     ` Anton Khirnov
2024-05-24 13:16     ` Michael Henrik Bodenhoff via ffmpeg-devel
2024-05-24 13:35       ` Andreas Rheinhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM9PR02MB6850EAFBA235B3A0781E3A23BCF52@AM9PR02MB6850.eurprd02.prod.outlook.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=MIBO@milestone.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git