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

DVE PBus/Timeline Jumping

3 replies [Last post]
Wed, 12/13/2006 - 22:03
AJR
User offline. Last seen 10 years 27 weeks ago. Offline
Joined: 10 Feb 2006

All,

I'm working on an effect for one of the shows where I work and I've run into a bit of a problem. I have a 5 keyframe effect in the DVEous with a pause on the 3rd keyframe. I have a timeline in the switcher (A GV 4k) with a PBus command to run the DVE forward. It runs to the third keyframe and pauses like I want. When I hit the PBus run forward trigger again, the DVE timeline jumps back to the first keyframe and runs up to the third keyframe and stops again. What I'm trying to do is when I hit the run forward trigger the second time, have it resume from the third keyframe and play to the 5th. I know I could get this to probably work with CPL but I can't use it due to flexibility issues. I've also heard funky things happen when you use CPL and PBus to control the DVE at the same time. Any ideas how to get the DVE timeline (using PBus) to play from the first keyframe to the third, pause, then send a second run forward command and then resume from the 3rd keyframe and play through the 5th? Any help would be greatly appreciated.

Thanks,

Allan

P.S. Sorry in advance for being confusing :-)

Top
Thu, 12/14/2006 - 22:46
#1
Jeremy W
User offline. Last seen 11 years 5 weeks ago. Offline
Joined: 7 Oct 2005
One question: Are you changing Emem's when the DVE effect pauses? In other words, are you recalling and running Emem 1, then recalling the Emem again? If so, you could split the DVE move at the pause into 2 effects, making 2 Emems to run it? Don't know if this is feasible to do.
Top
Thu, 12/14/2006 - 16:56
#2
Bill D
User offline. Last seen 10 years 32 weeks ago. Offline
Joined: 18 Aug 2005
[quote="AJR"]All, I'm working on an effect for one of the shows where I work and I've run into a bit of a problem. I have a 5 keyframe effect in the DVEous with a pause on the 3rd keyframe. I have a timeline in the switcher (A GV 4k) with a PBus command to run the DVE forward. It runs to the third keyframe and pauses like I want. When I hit the PBus run forward trigger again, the DVE timeline jumps back to the first keyframe and runs up to the third keyframe and stops again. What I'm trying to do is when I hit the run forward trigger the second time, have it resume from the third keyframe and play to the 5th. I know I could get this to probably work with CPL but I can't use it due to flexibility issues. I've also heard funky things happen when you use CPL and PBus to control the DVE at the same time. Any ideas how to get the DVE timeline (using PBus) to play from the first keyframe to the third, pause, then send a second run forward command and then resume from the 3rd keyframe and play through the 5th? Any help would be greatly appreciated. Thanks, Allan P.S. Sorry in advance for being confusing :-)[/quote] Allan, If you are trying to use CPl to recall the effect and P-bus to run it, that is the problem. I have gotten this to work sometimes in the past.. But it is hit or miss... One way it may work is to put start time of DPM 1 (cpl) at end of timeline (so the timeline never actually see its).. Then run p-bus as normal.. I am pretty certain though the pause is gonna mess it up either way... Either Recall through P-bus as well, or run dve manually.. later
Top
Thu, 12/14/2006 - 03:13
#3
Mike Cumbo
User offline. Last seen 3 years 23 weeks ago. Offline
Joined: 18 Aug 2005
Allan, describe the timeline and what triggers you are using. Might be easier to diagnose that way. BTW, I have built timelines like you describe many times with no problems, perhaps you have an incorrect trigger somewhere.
Top