There may be a timestamping problem, or this computer is too slow.

[Marco Ballesio]

On Tue, Sep 13, 2011 at 1:15 PM, Thabelo Mmbengeni <thabelo at gmail.com> wrote:
> Cool thanks, that solved the problem syncing xvimagesink to false.

I'm glad it helped, but note that this approach makes the sink never
drop a buffer. It might be slightly better to set an appropriate value
for "max-lateness".

The best would be, indeed, to find which element is declaring a wrong
latency and fix its reported value.

Regards

>
> On Tue, Sep 13, 2011 at 12:53 PM, Marco Ballesio <gibrovacco at gmail.com>
> wrote:
>>
>> On Tue, Sep 13, 2011 at 10:40 AM, Thabelo Mmbengeni <thabelo at gmail.com>
>> wrote:
>> > Gstreamer is using at most +-15% of my cpu but. And resource usage in
>> > total
>> > is 70% cpu usage RAM remains at 1.2G of 3G.
>>
>> so maybe you have enough juice in your system for that pipeline (is it
>> only user space CPU?).
>>
>> It's possible that buffers are dropped from the sink because of too
>> high a latency in the system. What if you add the option sync=false on
>> the xvimagesink? What if you reduce the frame resolution?
>>
>> Regards
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
>
> --
> Regards
>
> Thabelo Mmbengeni (TMT Services Cape Town HO, Engineering dep)
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>