All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Bara - SKIDATA <Benjamin.Bara@skidata.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Richard Leitner - SKIDATA <Richard.Leitner@skidata.com>,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Ezequiel Garcia <ezequiel@collabora.com>
Subject: RE: [PATCH] media: coda: avoid starvation on well-compressed data
Date: Tue, 6 Oct 2020 14:56:09 +0000	[thread overview]
Message-ID: <AM6PR01MB55747704D5C56A44F5E08414E20D0@AM6PR01MB5574.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CAAEAJfDnC5=iomoNivrwKt5th866qMKPY0Tw9i_PfKqsFTm69Q@mail.gmail.com>

> -----Original Message-----
> From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> Sent: Montag, 28. September 2020 22:06

> If you have some (public) bitstream that are known to timeout, and that you could
> share with me, that would be nice, so I could have a more complete set of samples.

Thanks for the response! We only have MPEG4 and H.264 encoded videos in use
and the described problem occurs only with MPEG4.
I analyzed the video streams with ffprobe [1] and found out that the problem occurs
when the video contains a couple of small P frames between key frames.

For my test bitstreams, I basically did the same as your colleague Nicolas,
but additionally I did some variations with ffmpeg [1].
To get really small P frames, only little changes between frames are allowed.
Therefore, a "single color video" seems to be the best choice.
Since the problem seemed to be related to the size of a frame, I varied:
width, height, bitrate and GoP (amount of P frames between key frames).
This should also be possible with your gstreamer pipeline [2, 3].

These things also lead to my "simplistic approach" to solve the issue.
I saw your patch series and will try it as soon as possible.

Regards
Benjamin

[1] https://ffmpeg.org/
[2] https://gstreamer.freedesktop.org/documentation/libav/avenc_mpeg2video.html?gi-language=c#avenc_mpeg2video:gop-size
[3] https://gstreamer.freedesktop.org/documentation/libav/avenc_mpeg2video.html?gi-language=c#avenc_mpeg2video:maxrate

*Get "packet sizes" of video stream:*
ffprobe -hide_banner -select_streams v -show_entries packet=flags,size -of compact video.avi


      reply	other threads:[~2020-10-06 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 11:58 [PATCH] media: coda: avoid starvation on well-compressed data Benjamin Bara - SKIDATA
2020-08-21 11:59 ` Benjamin Bara - SKIDATA
2020-09-18  8:35   ` Benjamin Bara - SKIDATA
2020-09-28 20:06     ` Ezequiel Garcia
2020-10-06 14:56       ` Benjamin Bara - SKIDATA [this message]

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=AM6PR01MB55747704D5C56A44F5E08414E20D0@AM6PR01MB5574.eurprd01.prod.exchangelabs.com \
    --to=benjamin.bara@skidata.com \
    --cc=Richard.Leitner@skidata.com \
    --cc=ezequiel@collabora.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.