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

Macro build

9 replies [Last post]
sonyman
sonyman's picture
User offline. Last seen 14 years 44 weeks ago. Offline
Joined: 9 Feb 2009

Good Evening:
I recently built a macro recalling an Effect for Device 5. Device 5 is a DDR. I then had the switcher cut to that cross point and then run the DDR as a Cue with a 4 frame pause then run. The Effect for device 5 was built with the cue and play section in the device menu. I entered both a start and stop time code in the device menu using the VTR control module. When I ran the macro it all went well until the DDR did not stop at the time code stop point. It just continued. The DDR was running as a VTR not VDCP. The clip on the DDR was 1:30 in duration. Shouldn?t the effect run based on the effect information so it knows the start and stop parameters.
Thanks for any assistance.
Macro:
Effect 41 recall
Cross point 17 cut PRG/PST
Cue device 5
Pause 4 frames
Play device 5
I also tried using the timeline run instead of cue and play and it did run the clip, but did not stop it either.

Bill D
User offline. Last seen 10 years 34 weeks ago. Offline
Joined: 18 Aug 2005
Seems like that maybe if you are on lets say device effect 1 before you do a clear and load, then that effect will have the corrupt rewind action until you reload it. If you are on effect 2, when you clear/load that will be the problem, and effect 1 will be fine., etc.
Bill D
User offline. Last seen 10 years 34 weeks ago. Offline
Joined: 18 Aug 2005
Obviously a bug, that is atleast 2 years old and would be nice if sony addressed! Curt you have a ton of rewind actions if they all starting not working correctly could ruin a show. I found reloading the effect usually fixes it. But trick is to get off of that effect before you reload, can't reload a new effect while that effect is the current one recalled. I have been re-loading my open effect the last week. Few more times I may just move it to fix it. Should work for another 6 months maybe. Today I deleted from the hard disk and re-saved. See what happens tomorrow. My only rewind effect so I have time to play. rest are macro recalls.
Curt
Curt's picture
User offline. Last seen 11 years 34 weeks ago. Offline
Joined: 30 Sep 2005
So it is almost like it corrupts this one register..interesting. Bill I know you have mentioned issues in the past as well. Have either of you ever found a way to get this reg back, or do i have to remember to never use this effect a device recall etc? Now that I think about it, I had this same problem I mentioned about 2 months ago..w/ I think the same register...but an entirely different show load... Might be time to move that effect!! This most recent time for me, I was able to just reset the CUEUP and resave...it seems to be ok for now atleast. Does a panel all-clear or anything seem to help? Related to this, I have also seen/heard ( w/ other TD's) it happen a handful of times in the past month where I will load a show, and one effect will cue up the wrong clip. So...first show I have Clip A at SB 42, another show load I have Clip B at SB 42. ( Both using DEV1 and the same physical chn of EVS via VDCP) Do an all clear and all load of the second show,, and SB 42 is still calling up Clip A from the previous load. Then I just reload that effect only, and it works. ( tells me it is ok on the HD) Almost like that part of the effect didn't load w/ the all-load. Even weirder part...it shouldn't work at all because I did an all-clear...so it is like the all-clear isn't working correctly. In theory, if the all -clear worked, there wouldn't be anything at 42. So not only is the all clear not working, but the reload isn't either. Almost like the effect is locked out or something. Just thinking..wonder when I am loading if I am sitting on that SB ( effect) and for some reason it is getting wacky. Shouldn't matter I would think since I am doing an all clear/load...but maybe...hmm..have to pay more attention to that. thanks Curt
Bob Ennis
User offline. Last seen 5 years 16 weeks ago. Offline
Joined: 24 Aug 2005
[quote="Curt"]Speaking of device control issues/bug, I had it today where for some reason I lost the Cueup information in the rewind action for one of two devices in an effect. Had to go back in and reset the cueup. Prior to this did some moving around/resaving of other device effects, but not this one. Wonder if something got confused along the way. Curt[/quote] I get this all the time on a select few effects that come up corrupted regardless of me re-laerning & re-saving them...they consistently come back up missing cueup & rewind information. My solution has been to duplicate the effect onto another timeline register & then fix it on the new register, and then modify my shotbox & re-save all of this.

Bob Ennis

Bill D
User offline. Last seen 10 years 34 weeks ago. Offline
Joined: 18 Aug 2005
[quote="Curt"]Speaking of device control issues/bug, I had it today where for some reason I lost the Cueup information in the rewind action for one of two devices in an effect. Had to go back in and reset the cueup. Prior to this did some moving around/resaving of other device effects, but not this one. Wonder if something got confused along the way. Curt[/quote] This has been a bug for about 2 years. If you get off the effect and load it may work ok. tends to keeep getting 'corrupt' day after day. Keep an eye on that effect, it may continue to do this. If you have contacts at Sony maybe report it, there have been some mentions of it in the past on here. But has not been addressed. Is there a # to call sony to report bugs. I always knew how to report them to GVG
Curt
Curt's picture
User offline. Last seen 11 years 34 weeks ago. Offline
Joined: 30 Sep 2005
Speaking of device control issues/bug, I had it today where for some reason I lost the Cueup information in the rewind action for one of two devices in an effect. Had to go back in and reset the cueup. Prior to this did some moving around/resaving of other device effects, but not this one. Wonder if something got confused along the way. Curt
Bill D
User offline. Last seen 10 years 34 weeks ago. Offline
Joined: 18 Aug 2005
Actually the stop function does work without using a extra keyframe which also will work. Rewind action should be cue and timecode cue up and play should have a start and stop time. Timeline should be 1 keyframe, start. Once you get it working (try rebuilding in another effect maybe, there has been bugs with device control rewind actions and such). I would build macro to be Timeline recall device 5 #xx crosspoint XX pause 6 frames or whatever to allow machine to cue timeline run device 5 The cue is not needed since timeline is cueing, and if you do a device play it will not stop since you are not running the timeline.
Joe Kern
User offline. Last seen 15 years 3 weeks ago. Offline
Joined: 27 Oct 2006
I am not sure about using cue and play mode, but in timeline mode you don't use the timecode to stop a DDR. You add an additional keyframe on your device effect and just program stop. Then make your first keyframe duration 1:30 or the length of your clip. We operate in this mode, so we would have 2/3 keyframes. KF0(rewind) would be a cue to the specific timecode on your DDR KF1 would be "START" with a duration of 1:30 KF2 would be "STOP" this should work for you. Joe
AJR
User offline. Last seen 10 years 29 weeks ago. Offline
Joined: 10 Feb 2006
Just out of curiosity, does the device cue when you recall the effect? Do you need the cue as part of the macro? I'm not that experienced with VDCP or VTR control but the only thing I can think of is that since you're not running the device 5 effect, that could be why the clip is not stopping. So have the macro recall the effect, throw the source online, run the effect timeline (which would have the timecode information and would play the clip and stop it at the outpoint). Maybe that could work?