Production Switchers

I have two questions about using Effects Dissolve on the Carbonite.

1> I figured out how to use the Dashboard to create a custom control that uses Effects Dissolve, but I can only do 9 frames or less on the transition. If I do anything above that it jumps partway through the move to the end. Is this a bug?

2> Is there a way to hold the sources in the DVE keys to something other than what was recorded on the effect for a certain memory, or move (maybe in the Dashboard on a custom control)? I don't want to change the store or recall memory modes so that the keys never change to what was stored, but there are certain fly effects I want to do that the sources could always be changing. On the GVG Krystal DVE years ago there was a Hold Input button. Is there anything like that on the Carbonite?

Thanks!

When your Inserting the State Event you have to set the Store Attributes at that time. In DashBoard this is why the Attributes also show up under the Custom Control section. So you define all of the elements that you want to have recalled -- basically the State is "switcher" wide and you have to mark the items you want included or set them to off for those that you don't want included. This is for the Whole switcher so do it for all the MEs and MiniMEs.
#Carbonite

So, I'm not sure I'm understanding. If I click on State Attributes, and then ME 1, it defaults to having TransArea, NextTrans, PGMBus, PSTBus, SharedPattern, and all the keyer buttons lit up. I would think unchecking Key1Bus, Key2Bus, Key3Bus, and Key4Bus would mean that those sources would no longer change based on what what was saved on the memory. But that doesn't seem to be the case. If I uncheck those and save the state I get a "State PGM Mode" line in my CC, but if I change the source of the keyer and run the CC it still changes it back to the source that was saved with it.

I figured out how to have it change the source to something else, but I can't figure out how to make it stay on what I select before running the CC.

Does it matter what order you do the State in? I mean, does it matter if you do a State that has the Effects Dissolve before you do the State that has the store attribute? Or do I just have the wrong store attribute for not changing the source?

I may need to call into Tech Support and have someone TeamViewer in to see what I'm doing on the DashBoard to see if I'm doing things correctly.

#Carbonite

The Issue is actually probably with the fact that your "Recall Attributes" are probably not set to Memory but rather always Recall. This would be over Riding your individual Store Attributes.
#Carbonite

What is the difference between the two modes? If it's on Memory, it will recall what was saved, correct? What does Always Recall do?

Honestly, this was not explained very well when we had training 5 years ago, and the switcher has been working the way it was set up, so we didn't change it.
#Carbonite

If it is on Memory it will recall how each individual Stored memory is defined when stored. In Always recall mode it will OVERRIDE the definitions of the individual Store Attributes and force it to recall what was there when the memory was stored.

Imagine you had a show and you had 60 memories where Key 3 was always off but now you had to do a special event sponsor for this week or what ever. Your going to put a graphic in Key 3 and leave it on air. Well instead of going back and editing all 60 memories you would use the Recall Attributes to change that to say Never Recall -- Now you don't have to go back and change the Bus sources, Keytype, Active settings in all 60 memories. Even Better since next week your back to normal all you have to do is flip those attributes back to Memory Mode.
#Carbonite

I just checked and the Memory Recall ME1K1 - ME1K4 are all set to Memory, as are most of the other settings. The Recall Mode Attrib is also set to Memory Value. On the Store side, Recall Mode Attrib is set to PGM Value. I'll call Tech Support when I can, without seeing it I imagine this is extremely difficult. Thanks!
#Carbonite

Then you will need to edit the CC -- Run the single Event. Make sure to go to the Store Attribute and check that you set the buttons correctly -- they need to be OFF not LIT to make sure that they ignore the Source (BUS) and not recall it. Then store your State again (you can do a replace or delete and insert). Then go to your next State and run that event and do the same to all the parameters.


#Carbonite

OK, riddle me this: I do a State command that does the Effect Dissolve at 9 frames (again, anything higher and it jumps), AND all the keyer information turned off. When I run that event they stay off. But when I run the next event, a Memory Recall of the effect, they all get turned back on. I thought the point of doing the State command was to override the Memory. Can you do a State command and the Memory recall on the same command?

While I'm on that subject, can I even do the Effect Dissolve and turn the keyer information off on the same command, or do they need to be separate? Initially I thought they had to be separate, but now I'm not so sure.
#Carbonite

A STATE entry in a Custom Control is essentially a MEMORY RECAL. However your not wasting Memory Registers thus having near unlimited States. If I were to build a BOX move in 3 Memories and run them using effects dissolve I could essentially just make a Custom Control that Recalls these 3 memories. However now those memories if changed would break my custom control. So instead we allow you to STORE (state) this information directly inside of the Custom Control.

So what you're essentially doing is recalling this information then recalling a memory (which has it's own Attributes).


#Carbonite