From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 5C413E008CA; Tue, 18 Nov 2014 23:36:17 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mailext0.televes.com (mailext0.televes.com [212.163.42.140]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 11C55E0087D for ; Tue, 18 Nov 2014 23:36:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailext0.televes.com (Postfix) with ESMTP id 62A549A3F7B; Wed, 19 Nov 2014 08:36:03 +0100 (CET) X-Virus-Scanned: by amavisd-new at mailext0.televes.com Received: from mailext0.televes.com ([127.0.0.1]) by localhost (mailext0.televes.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id garFeORdtwAZ; Wed, 19 Nov 2014 08:36:03 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mailext0.televes.com (Postfix) with ESMTP id 873FC9A402D; Wed, 19 Nov 2014 08:36:02 +0100 (CET) Received: from tves0.televes.com (tvesbackup0 [212.163.42.137]) by mailext0.televes.com (Postfix) with ESMTP id 73AFE9A3F7B; Wed, 19 Nov 2014 08:36:02 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by tves0.televes.com (Postfix) with ESMTP id 204C4F024971A; Wed, 19 Nov 2014 08:36:02 +0100 (CET) Received: from arantia1.arantia.com (ARANTIA0.televes.com [192.168.178.2]) by tves0.televes.com (Postfix) with ESMTP id 1B74EF0249700; Wed, 19 Nov 2014 08:36:02 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by arantia1.arantia.com (Postfix) with ESMTP id EB1071621479; Wed, 19 Nov 2014 08:36:01 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by arantia1.arantia.com (Postfix) with ESMTP id C5649161A0A0; Wed, 19 Nov 2014 08:36:01 +0100 (CET) Received: from arantia1.arantia.com ([127.0.0.1]) by localhost (arantia0 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05553-01; Wed, 19 Nov 2014 08:36:00 +0100 (CET) Received: from [192.168.178.108] (unknown [192.168.178.108]) by arantia1.arantia.com (Postfix) with ESMTP id 4C26E1621479; Wed, 19 Nov 2014 08:36:00 +0100 (CET) Message-ID: <546C4860.2040605@arantia.com> Date: Wed, 19 Nov 2014 08:36:00 +0100 From: Marco Trillo User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Nikolay Dimitrov References: <54664E1A.50009@mail.bg> <5467DB7F.1000604@mail.bg> <546B2700.2020300@arantia.com> <546B6071.9060409@mail.bg> In-Reply-To: <546B6071.9060409@mail.bg> Cc: "meta-freescale@yoctoproject.org" Subject: Re: [dizzy] Choppy gstreamer video (MPEG TS over UDP) X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2014 07:36:17 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: Kind regards, Marco