Hello Editsuite.com friends,

Due to tons of abuse, we now require that you request user access by sending us your Login, Name, Email Address, Phone Number, and Profession by submitting that info HERE.  I'll review your request and try to get back to you within the week.  You can't imagine how many folk want to trash forums with bogas advertising. 

Also, please help us gain enough Facebook "Likes" to have a custom Facebook URL!  

--Gary Lieberman

Kalypso and modifying timeline keyframe duration

1 reply [Last post]
Wed, 01/25/2006 - 12:34
apollo1980
User offline. Last seen 14 years 25 weeks ago. Offline
Joined: 10 Oct 2005

Hey gang.

Why is it when I tell the timeline that I want a duration of a given keyframe to be X that it doesn't change, or changes to something oddball?

Back in the days of when I used the good old kalydoscope DVE (still my favorite), it was simple. Now, I can't get it to take on the Kalypso.

What am I doing wrong?

Thanks in advance.

p.s. why did Grass Valley get away from the 0 keyframe duration option and I have to put in 0.01 instead? (used for inserting a dummy keyframe to change sources or move axis points, etc.)

Top
Wed, 01/25/2006 - 20:06
#1
Bob Ennis
User offline. Last seen 4 years 37 weeks ago. Offline
Joined: 24 Aug 2005
The "something odball" is a known bug, and has to do with the Kalypso re-interpreting your original duration & not transposing it properly in sec / frames / fields. It's annoying, but is usually harmless. As you why your keyframe isn't taking the entered time - the only reason SHOULD be because you have to press the MOD button for the entry to take. MOD MOD would change all keyframes. With the new EFF DUR now working in the latest versions, you don't have to use MOD...just press EFF DUR, enter your total value & you're done. But with keyframes, you have to select Keyframe Duration, enter a time, & press MOD (or MOD MOD). If you're doing this & it STILL isn't taking times, 1st make sure that Edit Enable is ON - otherwise it won't accept ANY changes...if all this is still correct & it isn't taking times, try a reboot of the system - the processor may have gotten confused.

Bob Ennis

Top