[CinCV TNG] Cinelerra Merging from 4.0 - testing report
beccatoria at hotmail.com
Fri Apr 3 04:00:12 CEST 2015
Yes, I see. Could this be because each mask keyframe MUST have a value for mask points, feathering and value, all at once? You cannot set just one of them, and if you don't actively set the others, they will default to the "current" setting. Where "current" actually means the setting of the previous keyframe?
The notion of "current" meaning the previous keyframe can also be observed in the histograms (camera, projector, fade, etc.) If you are working with Camera Z, for instance? And you set Keyframe A to 1.0, then a second later you set Keyframe B to 1.8? Now, when you select a point between Keyframes A and B and check the Camera settings, it will show 1.0 not whatever interpolated value that is actually being displayed.
It sounds like similar behaviour is occurring in the masks - i.e. defaulting to the previous keyframe (the one to the left). But complicated by the fact that each mask keyframe must have three attributes - mask points, feathering and value - and these are being created if not specified by the user?
I hope I have explained that in a way that makes sense. It is also only a guess at what's going on based on user experience.
Also, if I have to choose between no interpolation and interpolation that requires careful planning/does not always work perfectly, I would choose the imperfect interpolation.
> Date: Thu, 2 Apr 2015 22:00:33 +0200
> From: j6t at kdbg.org
> To: cinelerra at lists.cinelerra-cv.org
> Subject: Re: [CinCV TNG] Cinelerra Merging from 4.0 - testing report
> Am 02.04.2015 um 00:20 schrieb Rebecca ⠀:
> > 4) Mask keyframes - as also noted by others. Interpolation of value and
> > feathering has been fixed (YAYYYY!). I do not believe that
> > interpolation of mode is possible - it's a binary state. However, a
> > keyframe /image /will only appear on the track if a mask point is
> > moved. If only the feathering or value is changed, then a keyframe /is
> > /created (because interpolation up to that point works), but the little
> > green icon we know and love fails to appear. If you select an earlier
> > point and press play and let it play over the place where the keyframe
> > /should /be, the keyframe image suddenly appears.
> It is even worse than that: Say, you have two keyframes with widley
> different values and/or feather values. When you click somewhere between
> the the keyframes, you get interpolated mask shapes, value and feather
> Now, when you change the mask shape, the value and feather value jump
> back to the value of the keyframe to the left, although the shape
> retains the interpolation (plus the modification that was just made, of
> I don't know what the intent of this new behavior is.
> The code does have the old behavior: just comment out the line
> #define USE_KEYFRAME_SPANNING
> in mwindow.inc. I haven't tested this, yet.
> -- Hannes
> Cinelerra mailing list
> Cinelerra at lists.cinelerra-cv.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cinelerra