From: Marco Trillo <martri@arantia.com>
To: Nikolay Dimitrov <picmaster@mail.bg>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [dizzy] Choppy gstreamer video (MPEG TS over UDP)
Date: Wed, 19 Nov 2014 08:36:00 +0100 [thread overview]
Message-ID: <546C4860.2040605@arantia.com> (raw)
In-Reply-To: <546B6071.9060409@mail.bg>
Hi,
On 11/18/2014 04:06 PM, Nikolay Dimitrov wrote:
>> That way you can configure your elements individually. In particular, we
>> found that setting the `low-latency' property to true in `vpudec' and
>> the `qos' property to false in `aiurdemux' provided better results.
>
> "low-latency" definitely lowers the time to display 1st frame (< 1s),
> but need to test whether it affects long-term stability. Hope to be
> able to test soon "qos" property.
One small correction: the `qos' property belongs to the video sink (we
are using `mfw_v4lsink'), not to `aiurdemux' as I said in my first e-mail...
Regarding the time-to-first-frame you mention, we are also running in a
big show-stopper issue with `aiurdemux': depending on the number of PIDs
present in the program table -- for example if the program contains
subtitles or multiple audio streams --, the demuxer takes a long, long
time to provide the pads. Only in relatively simple programs (one audio
and one video PID) the demuxer seems to behave right.
It is quite possible this is not an issue for you if you control the
source stream. In any case, more information is available at:
<https://community.freescale.com/thread/324048>
Kind regards,
Marco
next prev parent reply other threads:[~2014-11-19 7:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 18:46 [dizzy] Choppy gstreamer video (MPEG TS over UDP) Nikolay Dimitrov
2014-11-14 20:25 ` Daiane Angolini
2014-11-15 23:02 ` Nikolay Dimitrov
2014-11-16 18:29 ` Daiane Angolini
2014-11-18 11:01 ` Marco Trillo
2014-11-18 15:06 ` Nikolay Dimitrov
2014-11-19 7:36 ` Marco Trillo [this message]
2014-11-19 21:45 ` Nikolay Dimitrov
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=546C4860.2040605@arantia.com \
--to=martri@arantia.com \
--cc=meta-freescale@yoctoproject.org \
--cc=picmaster@mail.bg \
/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.