couldn't find associated picture parameter set with id: 0

[Dylan Broome]

Hi Tim, is the above data enough to determine what is going on with the PPS?

Regards,
Dylan


On Wed, Jun 11, 2014 at 2:33 PM, Dylan Broome <dylan at blackmoth.com.au>
wrote:

> Hello Tim and Nicolas,
>
> Thank you both very much for the replies.
>
> Nicolas, I will endeavour to try 1.2.4, bitbake and gi make building
> gstreamer targets a bit tricky :)
>
> Tim, its using avc. The codec_data is :
> 0142401fffe1000a6742401fa680ec19640001000668ce30a48000
>
> From:
>
> /GstPipeline:pipeline0/GstRtpH264Depay:depay.GstPad:src: caps =
> video/x-h264, stream-format=(string)avc, alignment=(string)au,
> codec_data=(buffer)0142401fffe1000a6742401fa680ec19640001000668ce30a48000
>
> Thank you for your time,
> Dylan
>
>
> On Mon, Jun 9, 2014 at 11:08 PM, Tim Müller <tim at centricular.com> wrote:
>
>> On Fri, 2014-06-06 at 12:02 +1000, Dylan Broome wrote:
>>
>> Hi Dylan,
>>
>> as Nicolas said, please try the latest 1.2.x or even git master if you
>> can, just to make sure it's not a bug that's already been fixed.
>>
>> >         Then on the client system we display the stream with the
>> >         following pipeline:
>> >
>> >         rtspsrc name=videosrc buffer-mode=1 protocols=tcp ! queue
>> >         name=videoqueue ! rtph264depay name=depay ! h264parse !
>> >         imxvpudec name=decode ! imxipuvideotransform ! imxipusink
>> >         name=sink sync=false
>> >
>> >
>> >         First we get this once :
>> >         0:00:02.786696666  2811 0x37d02030 WARN
>> >         codecparsers_h264 gsth264parser.c:1736:gst_h264_parse_pps:
>> >         failed to read SE
>> >         0:00:02.786785666  2811 0x37d02030 WARN
>> >         codecparsers_h264 gsth264parser.c:1743:gst_h264_parse_pps:
>> >         error parsing "Picture parameter set"
>> >         0:00:02.786826333  2811 0x37d02030 WARN
>> >         h264parse
>> >         gsth264parse.c:510:gst_h264_parse_process_nal:<h264parse2>
>> >         failed to parse PPS:
>> >
>> >         Thereafter we get this from what looks like every frame:
>> >
>> >         0:00:13.371507669  2793 0x37c02030 WARN
>> >         codecparsers_h264
>> >         gsth264parser.c:1814:gst_h264_parser_parse_slice_hdr: couldn't
>> >         find associated picture parameter set with id: 0
>>
>> Well, it would be good to know what the data of the PPS is or why it
>> fails to parse it.
>>
>> You also don't really need h264parse in the pipeline here, rtph264depay
>> *should* be able to output both bytestream format or avc format, so if
>> the decoder advertises correctly what it needs it should just work. Of
>> course it should work with h264parse too.
>>
>> Pass -v to gst-launch-1.0 to check what output caps the rtph264depay
>> negotiates to.
>>
>> If it's video/x-h264,stream-format=avc, then show us the codec_data
>> field of the caps.
>>
>> If it's video/x-h264,stream-format=byte-stream, then add an .. !
>> identity dump=true ! .. between the rtph264depay and h264parse and show
>> us the output (in an attachment please) of the first few seconds/buffers
>> (until you see the pps parsing error for the first time).
>>
>> Cheers
>>  -Tim
>>
>> --
>> Tim Müller, Centricular Ltd - http://www.centricular.com
>>
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140616/9d76917d/attachment.html>