<div class="gmail_quote">On Mon, Nov 30, 2009 at 8:50 AM, Sameer Naik <<a href="mailto:sameer.subscriptions@damagehead.com">sameer.subscriptions@damagehead.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi, I have developed an audio decoder plugin for gstreamer that uses TI's dsp decoders that decode the audio frames on the dsp. An overview of the plugin architecture: In the plugin i am parsing the audio stream (if the stream is not packetized) so as to feed entire audio frames to the dsp decoder. Due to the parsing code i store some of the input data to parse with the next input buffer. in the stream once i have sync'd to an audioframe, i calculate the encoded framelength and start copying the data into an internal buffer that is designated as the dsp decoders input buffer. Only after the entire frame has been copying, the DSP algorithm is fired up to decode the encoded audio frame. Regarding seeking i have a few questions. Firstly, on an seek event i will need to clear the data in the decoders input buffer as well as the data that i store for parsing with the next input buffer. I want to know whether 1] the plugin could receive a buffer (_chain process) and an event (_event_handler) at the same time. What i mean to say is if the _chain function is called, could the pad _event handler be called while the _chain function is still processing the input buffer. 2] Or does this happen in an orderly fashion, where if the _chain function is currently processing data, then the pad _event handler will not be called until the _chain has finished its processing. Currently i have specified locks on the dsp decoders input buffers, which is required if case 1 true, while it is absolutely unnecessary if case 2 is true. </blockquote><div> This might help you Sameer: <pre><code>"The actual seek is performed in the application thread so that success or failure can be reported as a return value of the seek event. It is therefore important that before executing the seek, the element acquires the STREAM_LOCK so that the streaming thread and the seek get serialized." </code></pre> <a href="http://cgit.freedesktop.org/gstreamer/gstreamer/tree/docs/design/part-events.txt">http://cgit.freedesktop.org/gstreamer/gstreamer/tree/docs/design/part-events.txt</a> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Secondly, as mentioned above i clear the decoders input buffer and the other buffers on a seek event. Should i do this buffer cleanup on a seek event or should i handle this in a new segment event or both. </blockquote><div> The documentation of the events should help you with the newsegment too. </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Currently seeking is working most of the time. however it does fail sometimes. Your response will help me in narrowing things down. Please comment ~Sameer </blockquote><div> <pre><code>best regards, Katcipis</code></pre> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_blank">http://p.sf.net/sfu/bobj-july</a> _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.sourceforge.net">gstreamer-devel@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a> </blockquote></div>