Still stuck

[Gary Thomas]

On 2013-03-07 11:42, pfarmer wrote:
> Gary Thomas wrote
>> On 2013-03-07 11:34, pfarmer wrote:
>>> Gary Thomas wrote
>>>> Why does this pipeline work:
>>>>      gst-launch -e -vvv shmsrc socket-path=/tmp/shm-stream.sock \
>>>>        ! "application/x-rtp, sampling=(string)YCbCr-4:2:2,
>>>> width=(string)720, height=(string)480, payload=(int)96" \
>>>>        ! rtpvrawdepay \
>>>>        ! fakesink
>>>>
>>>> and this one does not?
>>>>      gst-launch -e -vvv shmsrc socket-path=/tmp/shm-stream.sock \
>>>>        ! "application/x-rtp, sampling=(string)YCbCr-4:2:2,
>>>> width=(string)720, height=(string)480, payload=(int)96" \
>>>>        ! rtpvrawdepay \
>>>>        ! ffenc_mpeg4 \
>>>>        ! fakesink
>>>
>>> That is an excellent question. I also don't see why it should not work.
>>> Anyway do you know that there are more debug outputs available as the -v
>>> switch? It is like Chuk Crisler-2 said: add the --gst-debug switches. So
>>> for
>>> example:
>>>
>>>      gst-launch shmsrc socket-path=/tmp/shm-stream.sock \
>>>        ! "application/x-rtp, sampling=(string)YCbCr-4:2:2,
>>> width=(string)720,
>>> height=(string)480, payload=(int)96" \
>>>        ! rtpvrawdepay \
>>>        ! ffenc_mpeg4 \
>>>        ! fakesink
>>> --gst-debug=shmsrc:5,rtpvrawdepay:5,ffenc_mpeg4:5,fakesink:5
>>>
>>> If you tried those already, what do they say?
>>> btw: I would like a qualified answer of this issue also :)
>>
>> See my replies already on the list.  Feel free to look through the debug
>> logs.
>
> Well I saw them, but as far as I can see, those are only the verbose outputs
> of gst-launch.

I was referring to the debug logs, generated at '*:9', on my website:
   http://www.mlbassoc.com/misc/log.fakesink
   http://www.mlbassoc.com/misc/log.fakesink+ffenc

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------