[gst-devel] Re: XVID plugin and one question

[Gianluca Insolvibile]

Doh! I was totally missing the point with threads and queues! I tried running
gst-launch as you (and Ronald) told me, and now it works perfectly. I will start
working on frame rate and resolution negotiation... you will hear from me soon! ;-)

Regards and thanks,
	Gianluca

Wim Taymans wrote:

 > yo,
 >
 >
 >>You will find the code for the xviddec plugin at
 >>
 > http://mdf.sourceforge.net, together with the debug log and a > small
 > m4v video contents (this works when fed to xviddec). For a DivX5
 > contents to be played through > avidemux please refer to
 > http://www.divx.org.
 >
 > very nice.
 >
 >
 >>gst-launch --gst-mask=-1 filesrc location=xXx_DivX.divx ! avidemux
 >>
 > video_00! xviddec ! disksink location=test
 >
 > looking at the log, you should put the xviddec and disksink into a
 > thread. The problem with runing the above pipeline is that avidemux does
 > not have a video_00 path when you create and run this pipeline. They
 > will become available after N iterations. The problem is then that
 > xviddec has an unconnected sinkpad, causing a failure.
 >
 > if you run like:
 >
 > gst-launch --gst-mask=-1 filesrc location=xXx_DivX.divx ! avidemux
 > video_00! { queue ! xviddec ! disksink location=test }
 >
 > things should work better as the thread (with the {}) will not go into
 > the playing state right away (since queue is not connected) but will do
 > so if the video_00 pad becomes available at runtime.
 >
 > You can alternatively create an app that handles this better or enhance
 > gst-launch.
 >
 >
 >>Regards,
 >>Gianluca
 >>
 >
 > regards,
 >
 > Wim
 >
 >