Thread: [Mlt-devel] Westley geometry question
Brought to you by:
ddennedy,
lilo_booter
From: Jonathan T. <jon...@gm...> - 2009-03-22 20:30:21
|
I'm attempting to use the "Composite" transition, but I can't seem to make the B track geometry grow to cover up the entire A track. The B track seems to max out around 85% to 90% the size of the video, regardless of what X,Y,HxW I try. Here is a snippet from the Westley XML: Any suggestions? <transition in="120" out="210"> <property name="mlt_service">composite</property> <property name="a_track">0</property> <property name="b_track">1</property> <property name="start">50%,50%:5%x5%:0</property> <property name="end">0%,0%:100%x100%:100</property> <property name="halign">centre</property> <property name="valign">centre</property> </transition> Also, I read in the documentation (i.e. http://www.mltframework.org/twiki/bin/view/MLT/Services), that the "start" and "end" properties have been depreciated. Are there any examples using the "geometry" property to set the start, keys, and end properties? Thanks! -Jonathan http://www.OpenShotVideo.com |
From: Dan D. <da...@de...> - 2009-03-23 17:05:34
|
2009/3/22 Jonathan Thomas <jon...@gm...>: > I'm attempting to use the "Composite" transition, but I can't seem to make > the B track geometry grow to cover up the entire A track. The B track seems > to max out around 85% to 90% the size of the video, regardless of what > X,Y,HxW I try. Here is a snippet from the Westley XML: Any suggestions? There are a few factors. First, are the aspect ratios and resolution of the clips in A and B the same? I suggest you first try with DV files with matching aspect ratio and the appropriate corresponding dv_... mlt profile. Secondly, the geometry, by default, defines a bounding box, and the transition scales the B clip down to fit inside the bounding box but does not scale the B clip over 100% of its resolution. You can set fill=1 to make it scale up as well. Also, it normalizes differences in aspect ratio to keep everything looking correct, but you can set distort=1 to make it ignore aspect and arbitrarily stretch the B video to the rectangle. > <transition in="120" out="210"> > <property name="mlt_service">composite</property> > <property name="a_track">0</property> > <property name="b_track">1</property> > <property name="start">50%,50%:5%x5%:0</property> > <property name="end">0%,0%:100%x100%:100</property> > <property name="halign">centre</property> > <property name="valign">centre</property> > </transition> > > Also, I read in the documentation (i.e. > http://www.mltframework.org/twiki/bin/view/MLT/Services), that the "start" > and "end" properties have been depreciated. Are there any examples using > the "geometry" property to set the start, keys, and end properties? >From your settings above: geometry="0=50%,50%:5%x5%:0;-1=0%,0%:100%x100%:100" It is a semicolon-delimited list of frame#=value where negative frame # starts from the end of the transition. The maximum number of key frames is the number of frames in the duration of the effect (no sub-frame keyframes). -- +-DRD-+ |
From: Jonathan T. <jon...@gm...> - 2009-03-24 02:37:58
|
Thanks! I added distort=1 to the composite transition, and it works great. What's strange is the video clips were all acquired via the same miniDV camera, and thus both have the same aspect ratio, 720 x 480. I suppose my geometry rectangle must have had a different aspect ratio than the clips? Thanks, -Jonathan On Mon, Mar 23, 2009 at 11:05 AM, Dan Dennedy <da...@de...> wrote: > 2009/3/22 Jonathan Thomas <jon...@gm...>: > > I'm attempting to use the "Composite" transition, but I can't seem to > make > > the B track geometry grow to cover up the entire A track. The B track > seems > > to max out around 85% to 90% the size of the video, regardless of what > > X,Y,HxW I try. Here is a snippet from the Westley XML: Any suggestions? > > There are a few factors. First, are the aspect ratios and resolution > of the clips in A and B the same? I suggest you first try with DV > files with matching aspect ratio and the appropriate corresponding > dv_... mlt profile. Secondly, the geometry, by default, defines a > bounding box, and the transition scales the B clip down to fit inside > the bounding box but does not scale the B clip over 100% of its > resolution. You can set fill=1 to make it scale up as well. Also, it > normalizes differences in aspect ratio to keep everything looking > correct, but you can set distort=1 to make it ignore aspect and > arbitrarily stretch the B video to the rectangle. > > > <transition in="120" out="210"> > > <property name="mlt_service">composite</property> > > <property name="a_track">0</property> > > <property name="b_track">1</property> > > <property name="start">50%,50%:5%x5%:0</property> > > <property name="end">0%,0%:100%x100%:100</property> > > <property name="halign">centre</property> > > <property name="valign">centre</property> > > </transition> > > > > Also, I read in the documentation (i.e. > > http://www.mltframework.org/twiki/bin/view/MLT/Services), that the > "start" > > and "end" properties have been depreciated. Are there any examples using > > the "geometry" property to set the start, keys, and end properties? > > From your settings above: > geometry="0=50%,50%:5%x5%:0;-1=0%,0%:100%x100%:100" > > It is a semicolon-delimited list of frame#=value where negative frame > # starts from the end of the transition. The maximum number of key > frames is the number of frames in the duration of the effect (no > sub-frame keyframes). > > -- > +-DRD-+ > |
From: Dan D. <da...@de...> - 2009-03-24 02:55:49
|
On Mon, Mar 23, 2009 at 7:37 PM, Jonathan Thomas <jon...@gm...> wrote: > Thanks! I added distort=1 to the composite transition, and it works great. > What's strange is the video clips were all acquired via the same miniDV > camera, and thus both have the same aspect ratio, 720 x 480. I suppose my > geometry rectangle must have had a different aspect ratio than the clips? In that case, it should not have been necessary to use distort=1. Usage of distort is generally not a good thing because it generally means users will not get a good result when using clips with differing properties. The name "distort" was chosen to indicate that it is somewhat dangerous. How are you testing this? Are you making a westley file that you run with inigo to prototype the effect, prototyping with inigo option syntax, or doing this all in your code? Did you make sure to set the MLT profile correctly? If you have a simple westley file or inigo command, please share it so I can take a look. > Thanks, > -Jonathan > > On Mon, Mar 23, 2009 at 11:05 AM, Dan Dennedy <da...@de...> wrote: >> >> 2009/3/22 Jonathan Thomas <jon...@gm...>: >> > I'm attempting to use the "Composite" transition, but I can't seem to >> > make >> > the B track geometry grow to cover up the entire A track. The B track >> > seems >> > to max out around 85% to 90% the size of the video, regardless of what >> > X,Y,HxW I try. Here is a snippet from the Westley XML: Any >> > suggestions? >> >> There are a few factors. First, are the aspect ratios and resolution >> of the clips in A and B the same? I suggest you first try with DV >> files with matching aspect ratio and the appropriate corresponding >> dv_... mlt profile. Secondly, the geometry, by default, defines a >> bounding box, and the transition scales the B clip down to fit inside >> the bounding box but does not scale the B clip over 100% of its >> resolution. You can set fill=1 to make it scale up as well. Also, it >> normalizes differences in aspect ratio to keep everything looking >> correct, but you can set distort=1 to make it ignore aspect and >> arbitrarily stretch the B video to the rectangle. >> >> > <transition in="120" out="210"> >> > <property name="mlt_service">composite</property> >> > <property name="a_track">0</property> >> > <property name="b_track">1</property> >> > <property name="start">50%,50%:5%x5%:0</property> >> > <property name="end">0%,0%:100%x100%:100</property> >> > <property name="halign">centre</property> >> > <property name="valign">centre</property> >> > </transition> >> > >> > Also, I read in the documentation (i.e. >> > http://www.mltframework.org/twiki/bin/view/MLT/Services), that the >> > "start" >> > and "end" properties have been depreciated. Are there any examples >> > using >> > the "geometry" property to set the start, keys, and end properties? >> >> From your settings above: >> geometry="0=50%,50%:5%x5%:0;-1=0%,0%:100%x100%:100" >> >> It is a semicolon-delimited list of frame#=value where negative frame >> # starts from the end of the transition. The maximum number of key >> frames is the number of frames in the duration of the effect (no >> sub-frame keyframes). >> >> -- >> +-DRD-+ > > -- +-DRD-+ |
From: Jonathan T. <jon...@gm...> - 2009-03-30 03:10:57
|
I think my problem was related to the default profile not matching my 2 video clips aspect ratio. Once I selected the correct profile, my video clips resized correctly. FYI: I am testing this using the Python swig bindings inside OpenShot... not inigo. Thanks! -Jonathan On Mon, Mar 23, 2009 at 8:55 PM, Dan Dennedy <da...@de...> wrote: > On Mon, Mar 23, 2009 at 7:37 PM, Jonathan Thomas > <jon...@gm...> wrote: > > Thanks! I added distort=1 to the composite transition, and it works > great. > > What's strange is the video clips were all acquired via the same miniDV > > camera, and thus both have the same aspect ratio, 720 x 480. I suppose > my > > geometry rectangle must have had a different aspect ratio than the clips? > > In that case, it should not have been necessary to use distort=1. > Usage of distort is generally not a good thing because it generally > means users will not get a good result when using clips with differing > properties. The name "distort" was chosen to indicate that it is > somewhat dangerous. > > How are you testing this? Are you making a westley file that you run > with inigo to prototype the effect, prototyping with inigo option > syntax, or doing this all in your code? Did you make sure to set the > MLT profile correctly? If you have a simple westley file or inigo > command, please share it so I can take a look. > > > > Thanks, > > -Jonathan > > > > On Mon, Mar 23, 2009 at 11:05 AM, Dan Dennedy <da...@de...> wrote: > >> > >> 2009/3/22 Jonathan Thomas <jon...@gm...>: > >> > I'm attempting to use the "Composite" transition, but I can't seem to > >> > make > >> > the B track geometry grow to cover up the entire A track. The B track > >> > seems > >> > to max out around 85% to 90% the size of the video, regardless of what > >> > X,Y,HxW I try. Here is a snippet from the Westley XML: Any > >> > suggestions? > >> > >> There are a few factors. First, are the aspect ratios and resolution > >> of the clips in A and B the same? I suggest you first try with DV > >> files with matching aspect ratio and the appropriate corresponding > >> dv_... mlt profile. Secondly, the geometry, by default, defines a > >> bounding box, and the transition scales the B clip down to fit inside > >> the bounding box but does not scale the B clip over 100% of its > >> resolution. You can set fill=1 to make it scale up as well. Also, it > >> normalizes differences in aspect ratio to keep everything looking > >> correct, but you can set distort=1 to make it ignore aspect and > >> arbitrarily stretch the B video to the rectangle. > >> > >> > <transition in="120" out="210"> > >> > <property name="mlt_service">composite</property> > >> > <property name="a_track">0</property> > >> > <property name="b_track">1</property> > >> > <property name="start">50%,50%:5%x5%:0</property> > >> > <property name="end">0%,0%:100%x100%:100</property> > >> > <property name="halign">centre</property> > >> > <property name="valign">centre</property> > >> > </transition> > >> > > >> > Also, I read in the documentation (i.e. > >> > http://www.mltframework.org/twiki/bin/view/MLT/Services), that the > >> > "start" > >> > and "end" properties have been depreciated. Are there any examples > >> > using > >> > the "geometry" property to set the start, keys, and end properties? > >> > >> From your settings above: > >> geometry="0=50%,50%:5%x5%:0;-1=0%,0%:100%x100%:100" > >> > >> It is a semicolon-delimited list of frame#=value where negative frame > >> # starts from the end of the transition. The maximum number of key > >> frames is the number of frames in the duration of the effect (no > >> sub-frame keyframes). > >> > >> -- > >> +-DRD-+ > > > > > > > > -- > +-DRD-+ > |