On mercredi, 3 mars 2021 07.28:51 h CET Dan Dennedy wrote: Hi Dan, all
Thanks for sharing that with us ! > Brian has been working on time effects (i.e. keyframes for speed and > direction) for a good while now, and a couple of months ago I realized it > requires breaking the API. So, if we are going to break the API I want to > make some other changes we can live with for a little while. However, > considering how long he has worked on this, I do not want it to take too > long or be too adventurous. Mostly, we are talking about removing > deprecated and legacy things, and a little renaming. Our goal is to make > the first release by the end of April. There will be a 6.26.0 release > before it, soon. For the 6.26.0 I would really like to fix the OpenCV compilation issue [1]. I was hoping the root of the issue would be fixed sooner in OpenCV but still waiting for a fix... will try to come up with a solution to at least unbreak compilation for OpenCV >= 4.5.1 by the end of next week if ok for you. Otherwise, I am excited to test Brian's work on time remap! [1] https://github.com/mltframework/mlt/issues/636[1] > The branch in git is named "v7". > > The plans are on the Road Map page (that also includes things beyond the > first 7.0 release): > https://mltframework.org/changes/todo/ > > I started working on a migration guide for app developers: > https://mltframework.org/docs/v7migration/ > > And here is a GitHub for tracking our tasks: > https://github.com/mltframework/mlt/issues/655 Thanks, these resources will be helpful. > My changes in mlt_events and a LADSPA-only build option for the jackrack > module were motivated by my port to macOS on Apple M1 silicon (still in > progress). > > In particular, I want you to see the proposed removal of the motion_est > module with its autotrack_rectangle filter, and the region filters in the > core module. > > I think the autotrack_rectangle is sub-par compared to opencv.tracker, but > I do not have much experience with either. In any case, the only other > interesting thing in motion_est is slowmotion, which is unsatisfactory. And > I would rather not bother to port this module's usage of mlt_geoemtry to > mlt_rect. Yes, the autotrack_rectangle filter is really bad at following objects. It is still used by some users but I agree we should get rid of it in favor of the opencv tracker. Same for slowmotion. > Removal of the region filter and transition is due to its usage of the > mlt_frame.get_alpha_mask function pointer I want to remove to simplify > handling of alpha channel. Besides, we now have mask_start and mask_apply > which are more flexible in some ways; you can see how they are used in > Shotcut. You can use any filter in conjunction with mask_start but > typically something that affects alpha. Then, any number of other filters > including additional alpha-affecting ones before mask_apply, which > composites the result onto the snapshot made by mask_start. (These are not > new to v7.) Not yet implemented is multiple instances of mask_start and > mask_apply on the same producer. Fine for me, the region filter was not implemented in recent versions of Kdenlive anyways, I was not aware of the mask_start / apply stuff, will have a look, thanks. > Please let me know about any show-stoppers or objections with these plans.
_______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
