>
> On Tue, 2008-02-12 at 01:39 -0500, Aaron Lindsey wrote:
>> I've written an rtp sender and receiver based on the test3v example for
>> streaming mpeg4 video.  When I set them both up to run, they would each
>> show output indicating that everything was running fine.  The pipeline
>> was linked and playing, etc, etc.  However, no video would be displayed
>> (videotestsrc on the sender and xvimagesink on the receiver).  The only
>> way I've been able to get video to show up, is by grabbing the pipeline
>> from the stream on the receiver and setting the "send-config" attribute
>> on the payloader.  Like this:
>>
>> pipeline = farsight_stream_get_pipeline( videoStream );
>> pay = gst_bin_get_by_name( GST_BIN( pipeline ), "rtpmp4vpay0" );
>> g_object_set( G_OBJECT( pay ), "send-config", TRUE, NULL );
>>
>> If I do that, it works.  Is it standard to do this?  It feels like
>> something that I'm messing up elsewhere and then duct taping here.  The
>> test programs definitely don't do this anywhere.  Also, this is with
>> farsight 0.1.25.  Thanks.
>
> What you are doing is right. The MPEG-4 codec requires configuration
> information to be sent to initialise the decoder before playback can
> start. But the current send-config is not ideal, since we are streaming
> over UDP and it could get lost. The payloaders for mpeg4 (but also some
> other codecs like Theora, etc), should be modified to be able to resend
> the config information regularly in case the first one is lost. The
> other way to do it is to read it from the caps and send it in the sdp
> (but that's very annoying to do with codec negotiation, because that
> means you'd have to initialise every encoder before doing the offer).
>
> --
> Olivier Crête
> [EMAIL PROTECTED]
> Collabora Ltd

Thanks for the explanation.  That helps a lot.

Aaron

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Farsight-devel mailing list
Farsight-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/farsight-devel

Reply via email to