> > 3- Question: The internal (empty) keyframes that form, what are they? > How are they used? > The "bump" is a kind of FloatAuto, an element in an automation list that is one of the 12 automation types of keyframe lists: mute, cam_x,y,z, proj_x,y,z fade, pan, mode, mask, and speed lists which are part of the "Track". A FloatAuto is one of 4 auto "value" types that are stored in the auto at the keyframe "position", float, mask, int, pan. A FloatAuto stores a floating value for the automation at a position on the track. When a FloatAuto get_value is invoked at a track position, the position is used to access a previous and next auto list element values based on the "current" position. The returned value is generated using one of 5 modes of curve interpolation, smooth, linear, tangent, free, bump. smooth: bezier interpolation which are flat at the endpts linear: piecewise linear curve. tangent: bezier interpolation with collinear endpts in a specified line. free: piecewise bezier, if there is such a thing. bump: has 2 values, one viewed from the left/right, discontinuous. When a FloatAuto is created, it gets a list default value. This varies by auto type speed=0, fade=100, ..., and at position 0., but this is almost always immediately changed to a value specified for the current position, a value/mode you specify in the sliders and drag values of the GUI updates.
5- Question: Acting on the slider to make changes, everything works > fine. But by dragging the keyframe with the mouse to change it, you > only change the keyframe itself and the next (empty) one to which it > is tied; but not the others. Am I wrong? > You are right. When you are dragging, the "span" and "edge" are not specified, and the defaults are not spanning, and the right edge. 6- Question: Is it indifferent to enable/disable the "Allow keyframe > spanning" button? > Yes, the keyframe spanning button in the MenuBar applies to plugin keyframes. The update is done by first creating a textual "diff" on the xml values of the plugin keyframes, then applying that diff to all of the keyframes selected in the "span". The bump FloatAuto bump_update subtracts the old and new values to create a "diff" that is added to all of the values in the right_edge ... auto values ... left_edge region created by bump autos and media endpts. Thank you so much for all of the testing and documentation. This is all very much appreciated. Phyllis and I try to keep it all up to date, but this is just too much for two old people and a dog. gg On Mon, Aug 24, 2020 at 5:20 AM Andrea paz via Cin < [email protected]> wrote: > Thanks. I did some first tests of Bump Keyframes. My > considerations/questions: > > 1- The best way to create bump keyframes is in the Phyllis example: > select the region and then > Keyframes --> Create curve type --> bump > Keyframes --> Create keyframes --> speed (or other) > > 2- However, you can also create them by clicking or double-clicking then > RMB --> bump > RMB --> speed (or other) > > 3- Question: The internal (empty) keyframes that form, what are they? > How are they used? > > 4- Make sure that the keyframes at the edges are bump type and that > the left edge is set to the right and the right edge is set to the > left. This way the changes will only affect keyframes within the > range. > > 5- Question: Acting on the slider to make changes, everything works > fine. But by dragging the keyframe with the mouse to change it, you > only change the keyframe itself and the next (empty) one to which it > is tied; but not the others. Am I wrong? > > 6- Question: Is it indifferent to enable/disable the "Allow keyframe > spanning" button? > > 7- With the sliders using, only the keyframes of the track are > changed. A workaround to edit all armed tracks of all types at the > same time is as follows (always applies, not only to bump keyframes): > a- disable "Master track" of all tracks except the first one, on which > we will work. > b- switch to "gang media" mode. Now only the Master track is visible, > but every change made on its keyframes is also applied to the other > tracks. (great innovation; more I examine the latest features > introduced and more I understand how powerful, comfortable and > functional they are. Thanks!) > > If I can understand these points; combining the GG explanation, I can > try to write the section for the manual, which you (phyllis) can then > check. If you want, of course. > > > [PS: I take this opportunity to ask another thing. > I changed the video card, going back to AMD Navi 10. It is now stable > and working (So I no longer have Nvidia and Cuda). I also formatted > and reinstalled everything. I have these warnings on terminal: > > file:/home/paz/video_editing/prova/1080/0005.3gp > err: Invalid data found when processing input > FFStream::decode: failed > HW device init failed, using SW decode. > file:/home/paz/video_editing/prova/1080/0005.3gp > err: Invalid data found when processing input > mesa: for the --simplifycfg-sink-common option: may only occur zero or > one times! > mesa: for the --global-isel-abort option: may only occur zero or one times! > mesa: for the --amdgpu-atomic-optimizations option: may only occur > zero or one times! > > Apparently the .3gp format (with h264 and aac codecs) is not supported > by vaapi. It's not a problem, but I don't understand the meaning of > the three lines starting with "mesa: ...".] > -- > Cin mailing list > [email protected] > https://lists.cinelerra-gg.org/mailman/listinfo/cin >
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
