hi!
i do: gst-launch filesrc location=my.264 ! h264parse ! myh264decoder ! ffmpegcolorspace ! fbdevsink the filesrc passes buffers of 4096 byte to h264parse. h264parse passes a 23 byte buffer to myh264decoder where i decode to get stream configuration - works. But next buffer is 8 byte and i cant push the decoded buffer to downstream. 0:00:01.265381034 1526 0x7b388 DEBUG h264parse gsth264parse.c:956:gst_h264_parse_sink_event:<h264parse0> Pushing newseg rate 1, applied rate 1, format 2, start 0, stop 3041866, pos 0 0:00:01.268311470 1526 0x7b388 DEBUG h264parse gsth264parse.c:897:gst_h264_parse_chain:<h264parse0> received buffer of size 4096 0:00:01.269130929 1526 0x7b388 DEBUG h264parse gsth264parse.c:499:gst_h264_parse_chain_forward:<h264parse0> NAL type: 7, ref_idc: 1 0:00:01.269879079 1526 0x7b388 DEBUG h264parse gsth264parse.c:540:gst_h264_parse_chain_forward:<h264parse0> we have a SPS or PPS NAL 0:00:01.270759876 1526 0x7b388 DEBUG h264parse gsth264parse.c:553:gst_h264_parse_chain_forward:<h264parse0> pushing buffer 0x432c0, size 23, ts 0:00:00.000000000 |
> 0:00:01.269130929 1526 0x7b388 DEBUG h264parse
> gsth264parse.c:499:gst_h264_parse_chain_forward:<h264parse0> NAL type: 7, > ref_idc: 1 > 0:00:01.269879079 1526 0x7b388 DEBUG h264parse > gsth264parse.c:540:gst_h264_parse_chain_forward:<h264parse0> we have a SPS > or PPS NAL Come to think of it; wouldn't it make more sense to move the send-config and config-interval options from rtpmpv4pay and rtph264pay to mpeg4videparse and h264parse respectively? This way; streaming back on the network would be supported for any encapsulation (es, ts, rtp) instead of just rtp ATM. -- greetz, marc Anyone who imagines that all fruits ripen at the same time as the strawberries, knows nothing about grapes. -- Philippus Paracelsus crichton 2.6.26 #1 PREEMPT Tue Jul 29 21:17:59 CDT 2008 GNU/Linux ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel signature.asc (196 bytes) Download Attachment |
In reply to this post by ericcardmanNo3
you mean the buffer pushed by filesrc is 8 bytes ?
As IMHO h264parse pushes one NALU for every buffer, so there might be an issue with your decoder ? -kapil On Tue, Mar 30, 2010 at 9:20 PM, ericcardmanNo3 <[hidden email]> wrote:
-- http://www.linkedin.com/in/kapilagrawal ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
In reply to this post by ericcardmanNo3
Hi,
On Tue, Mar 30, 2010 at 6:50 PM, ericcardmanNo3 <[hidden email]> wrote: > > hi! > > i do: > gst-launch filesrc location=my.264 ! h264parse ! myh264decoder ! > ffmpegcolorspace ! fbdevsink > > the filesrc passes buffers of 4096 byte to h264parse. > h264parse passes a 23 byte buffer to myh264decoder where i decode to get > stream configuration - works. > But next buffer is 8 byte and i cant push the decoded buffer to downstream. > > 0:00:01.265381034 1526 0x7b388 DEBUG h264parse > gsth264parse.c:956:gst_h264_parse_sink_event:<h264parse0> Pushing newseg > rate 1, applied rate 1, format 2, start 0, stop 3041866, pos 0 > 0:00:01.268311470 1526 0x7b388 DEBUG h264parse > gsth264parse.c:897:gst_h264_parse_chain:<h264parse0> received buffer of size > 4096 > 0:00:01.269130929 1526 0x7b388 DEBUG h264parse > gsth264parse.c:499:gst_h264_parse_chain_forward:<h264parse0> NAL type: 7, > ref_idc: 1 I think the problem here is that the parser returns ONLY an SPS and your decoder is emitting a buffer after it.. as SPS/PPS contain only metadata no meaningful (render-able) information can be emitted from the decoder, so I'd rather ignore the output buffer which is indeed to small to be rendered (unless you have a 3x2 pixels image). >From my pov the parser is kind of misleading in many cases. You may check on gst-dsp about how to avoid it. Regards, Marco > 0:00:01.269879079 1526 0x7b388 DEBUG h264parse > gsth264parse.c:540:gst_h264_parse_chain_forward:<h264parse0> we have a SPS > or PPS NAL > 0:00:01.270759876 1526 0x7b388 DEBUG h264parse > gsth264parse.c:553:gst_h264_parse_chain_forward:<h264parse0> pushing buffer > 0x432c0, size 23, ts 0:00:00.000000000 > > -- > View this message in context: http://n4.nabble.com/h264parse-srcpad-buffers-NAL-SPS-PPS-experts-needed-tp1745406p1745406.html > Sent from the GStreamer-devel mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/gstreamer-devel > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Free forum by Nabble | Edit this page |