>>>> a) The affine composite quality is roughly the same as Qt's
> (look at >>>> 'S' and 's'). >>>> b) The composite transition appears to have an off-by-one error >>>> between the image and the alpha channel. I do not yet know if it > is >>>> really off or if it is just side-effect of the simple > implementation. >>>> c) There is a lot of aliasing even within the Qt composited area > as a >>>> result of low resolution. >>> >>> The previous two images were generated by rendering to H.264 and then >>> converting the first frame to PNG. Here are two new ones that render >>> straight from the project to PNG. >> >> Based on those results, is there any reason the watermark filter > shouldn't use the affine transition by defaut? > > There are subtle differences between composite and affine's simple > compositing use cases and not so subtle differences in performance > (composite is faster). So, I do not want to suddenly change behavior > of watermark for people who are already happily using it. I would like > to see if composite can be improved/fixed, however. But I do think you > should consider to change dynamictext to not use watermark and instead > use affine through either filter_transition or code copied from > watermark. Also, you could write a Qt backend to dynamictext that > writes directly on frame instead of using an external composite. > qimage/transition_vqm shows how to do that. Great ideas. I'll look into it. ~BM ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
