master vs. 1.5.1 - changing video-size on compositor input

Tim Müller tim at centricular.com
Wed Aug 26 12:25:43 PDT 2015


On Wed, 2015-08-26 at 20:47 +0200, Peter Körner wrote:

Hi Peter,

> I have a project built with 1.5.1 as a base. It contains a compositor
> within a pipeline similar to this:
> 
> > compositor name=mix !
> >
> video/x-raw,format=I420,width=1920,height=1080,framerate=25/1,pixel-aspect-ratio=1/1
> !
> > identity name=sig !
> > queue !
> > intervideosink channel=video_mix_out
> >
> > intervideosrc channel=video_cam1_mixer !
> >
> video/x-raw,format=I420,width=1920,height=1080,framerate=25/1,pixel-aspect-ratio=1/1
> !
> > videoscale !
> > capsfilter name=caps_0 !
> > mix.
> >
> > intervideosrc channel=video_cam2_mixer !
> >
> video/x-raw,format=I420,width=1920,height=1080,framerate=25/1,pixel-aspect-ratio=1/1
> !
> > videoscale !
> > capsfilter name=caps_1 !
> > mix.
> 
> during operation I change the x/y settings on the compositor but also
> the caps on the capsfilter to something like:
> 
> > Reconfiguring Mixerpad 0 to x/y=0/273, alpha=1.00, zorder=1
> > Reconfiguring Capsfilter 0 to video/x-raw, width=(int)950, height=(int)534
> >
> > Reconfiguring Mixerpad 1 to x/y=970/273, alpha=1.00, zorder=2
> > Reconfiguring Capsfilter 1 to video/x-raw, width=(int)950, height=(int)534
> 
> which will, for example, produce a side-by-side view of the two inputs.
> In gstreamer 1.5.1 this works pretty well. With the current master, I
> get errors from videoaggregator (see attached log). I'm unsure if I
> missed something in my application or if this is a regression somewhere
> between 1.5.1 and master.
> 
> I also tested the very same code with 1.5.90 and there I additionally
> get those errors:
> 
> ** (python3:12647): CRITICAL **: gst_video_frame_map_id: assertion
> 'info->width <= meta->width' failed
> 0:00:03.599031061 12647      0x28720f0 WARN              compositor
> compositor.c:513:gst_compositor_pad_prepare_frame:<mix> Could not map
> input buffer

Any chance you could perhaps make a small example app that reproduces
the problem and file a bug in bugzilla and attach it there? That would
make it easier to debug and fix.

 Cheers
  -Tim

-- 
Tim Müller, Centricular Ltd - http://www.centricular.com

Join us at the GStreamer Conference: 8-9 October 2015 in Dublin, Ireland




More information about the gstreamer-devel mailing list