Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; view has a deprecated constructor in /home2/edit/public_html/sites/all/modules/views/includes/view.inc on line 19

Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; views_display has a deprecated constructor in /home2/edit/public_html/sites/all/modules/views/includes/view.inc on line 1910

Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; views_many_to_one_helper has a deprecated constructor in /home2/edit/public_html/sites/all/modules/views/includes/handlers.inc on line 616
macro "escape" | Editsuite.com

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 "escape"

5 replies [Last post]
Sat, 11/04/2006 - 10:47
jbs
User offline. Last seen 14 years 16 weeks ago. Offline
Joined: 1 Jul 2006

Hi everyone. I've been playing with the 8000 for about a month now, but it won't go online until after training in December and we get some more conversion equipment in. Its pretty much all the same concepts as our Grass 3000 (just have to look for the menus) - with the addition of more robust machine control and MACROS! So I have questions that I hope you guys can help me out with.

I've built a few undercut effects using macros instead of timelines so that an effect on the same M/E doesn't prevent me from transitioning with keys. I feel lazy though since it was so ridiculously easy... am I too lazy? Should I be using timelines instead like on the Grass? Anyway, I'm cueing clips and stepping through an Aprisa VCS playlist using VTR control which works acceptably well - better than GPI or DNF/p-bus anyway.

My question: Is there a way to escape out of a macro IN PROGRESS? One macro I've built steps through a playlist by FF-ing the Aprisa (cue next) on the first press followed by an infinite pause - the pause is there to provide time for the VCS to cue. Then the effect plays out after hitting take. What if an operator "accidentally" chooses the wrong effect and can't get out of the macro on the pause? (I know... just don't "accidentally" do it!) I've tried to get out of a macro as its paused but it won't let me.

At first I created the effect to play from the start and then cue the next item at the end - making it ready for the next effect. That would be a one-punch deal preventing my problem, but for a couple good reasons I won't go into right now I decided to do it the other way... which gets me locked into a macro because of the pause.

EDITED***I think I just found the answer to my question - just took some reading. I remember trying this but I didn't think it worked. Can anyone confirm it? From the manual:

"During macro execution, recalling the same register again stops the macro being executed. Therefore, pressing twice a button for which a macro attachment is set stops the macro being executed."

Of course I'm using the flex-key pad to run the macro.

Another question - can you put a macro in a timeline??? (told you I have questions)

Top
Thu, 11/16/2006 - 13:16
#1
jbs
User offline. Last seen 14 years 16 weeks ago. Offline
Joined: 1 Jul 2006
After playing around with it I don't think I can get a cut with path turned off on transition. With path turned on I'm locked into a specific transition and can't select keys. I guess I'll stick to macros or do it the old-fashioned way - a gpi loopback. I was hoping to get away from that though.
Top
Sun, 11/05/2006 - 20:18
#2
Bill D
User offline. Last seen 10 years 3 weeks ago. Offline
Joined: 18 Aug 2005
[quote="Bob Ennis"]Path On/Off can be set for pretty much any parameter within an M/E - Keyers, Crosspoint Selection, Transition, etc.[/quote] Cool thanks Bob
Top
Sun, 11/05/2006 - 17:01
#3
Bob Ennis
User offline. Last seen 4 years 36 weeks ago. Offline
Joined: 24 Aug 2005
Path On/Off can be set for pretty much any parameter within an M/E - Keyers, Crosspoint Selection, Transition, etc.

Bob Ennis

Top
Sun, 11/05/2006 - 16:21
#4
Bill D
User offline. Last seen 10 years 3 weeks ago. Offline
Joined: 18 Aug 2005
[quote="Bob Ennis"]Unlike the Kalypso, you don't HAVE to use macros in order to not affect keyer states. In the 8000's timeline/Path/M/E menu is a choice for OFF. This causes the selected area to ignore any and all timeline-oriented commands. This flag can be set for the whole effect, or on a keyframe-by-keyframe basis. So a keyer whose path has been set to OFF will remain on if it's currently on & off if it's currently off. Because of this flexibility, you may find it easier to build traditional timelines to accomplish what you want than to feel like you HAVE to use macros. Macros on the 8000 are panel-oriented. They cannot affect menu functions, and they currently cannot be triggered by timeline functions.[/quote] If you use the path off, will it also not care about your next transition module? I assume path on/off can be a per keyer basis? Bill
Top
Sat, 11/04/2006 - 16:42
#5
Bob Ennis
User offline. Last seen 4 years 36 weeks ago. Offline
Joined: 24 Aug 2005
Unlike the Kalypso, you don't HAVE to use macros in order to not affect keyer states. In the 8000's timeline/Path/M/E menu is a choice for OFF. This causes the selected area to ignore any and all timeline-oriented commands. This flag can be set for the whole effect, or on a keyframe-by-keyframe basis. So a keyer whose path has been set to OFF will remain on if it's currently on & off if it's currently off. Because of this flexibility, you may find it easier to build traditional timelines to accomplish what you want than to feel like you HAVE to use macros. Macros on the 8000 are panel-oriented. They cannot affect menu functions, and they currently cannot be triggered by timeline functions.

Bob Ennis

Top