Beam Time for gobo change on Mac2k

I think it may be the way that the library is made... Have you tried fading between the two values over say 5 seconds or does it stay idle for 2 secs, move over one (Snap) and then have 2 secs after the move?

When the cue is fired the gobo snaps at the beginning of the cue no matter how we recorded it.

What about a delay time for the gobo and everything else snap..? Or record the Gobo info into a scene and apply your timing in the scene. Then use a comment macro to fire the scene from the cue (and make sure you cue has no gobo info in)

Regards,

The problem is just getting the gobo to not snap in the cue. It's not about -when- the gobo snaps to the next slot. We just want it to slowly change from one gobo to another over the course of 5 seconds.

What would recording it all in a scene do differently from putting it into a cue? I will still go try this, I just don't know what the overall goal of the test is.

I am really looking for the correct syntax/method (that is known to work in other instances) on changing the gobo slowly at a given rate. A Mac2k profile has an effects time channel to control the gobo time - how do I properly use this in a Hog3 environment.

Using a Road Hog Full Boar - build 2440.

did you use index or spin in the gobo-field??

I think that if you use slot it will snap from 1 to 1, if you use spin it should slow rotate

The gobos are already set to spin mode by a previous cue. I also tried going back to index mode - then tried just making a cue with only the gobo change in it - same thing - gobo snaps to next gobo when the cue is fired.

I really think it is about the proper way to tell the gobo to change over a given time. I truly believe I am not using proper syntax to get it to do the right thing. I am missing something either easy or buried in a keystroke that I don't know.

I'm having the same problems with VL2500 spots, I cannot get them to roll from one static gobo to another no matter what timings/settings I try.

You need to change the path of your fade. Most gobo parameters default to "Start" which means the entire transition happens at the beginning of the crossfade. Change it to linear if you want smooth transitions.

You can set a path for each parameter on each fixture independantly. To change the default path for a parameter, go into the Edit Fixtures window under Patch.

I am missing something either easy or buried in a keystroke that I don't know.

You need to change the path of your fade. Most gobo parameters default to "Start" which means the entire transition happens at the beginning of the crossfade. Change it to linear if you want smooth transitions.

You can set a path for each parameter on each fixture independantly. To change the default path for a parameter, go into the Edit Fixtures window under Patch.

And missing something easy is what is going on I believe. I will look at this tomorrow. Thanks Eric.

[QUOTE=Andris;35724]I'm having the same problems with VL2500 spots, I cannot get them to roll from one static gobo to another no matter what timings/settings I try.

For VL2500s (or ANY VL for that matter)...set your cue beam parameter time to 0. Then, under the BEAM selections, navigate your encoders to "BEAM TIME." Select USER and dial the encoder to around 20 seconds (the time does not correspond to the CORRECT time...just an FYI). This will give you about a 3 second roll.

This also applies to COLOR slots and use "COLOR TIME."

Tried different paths, nothing will make the gobo channel do anything but snap.

Talked to someone else about it here at our shop and they stated the M2K software won't let me do that, but even when I am viewing the DMX from the console the DMX for the gobo channel will still snap to the next value.

Changing the path makes the gobo snap at a different place in time while the cue is firing - but it still snaps...

Is the personality for the light written in a way that will not allow this?

:confused:

[QUOTE=ericthegeek;35730]You need to change the path of your fade. Most gobo parameters default to "Start" which means the entire transition happens at the beginning of the crossfade. .

You might want to check on that statement, Eric. I just looked at several fixture profiles, and all paths are LINEAR by default.

I have tried all the same procedures that Ryan did and I still can't get a fade on a VL gobo either.

Can someone try this in their rig so I can make sure I'm not crazy??

Andris,

I can't speak for Macs, but I have a rig of VL2K's and VL1K's. The method I mentioned works PERFECTLY for getting them to slow roll between gobos...same with colors. You have to dial up the "beam user time" to around 20seconds or so. The time on the encoders is not "REAL" time. I found for about a 3-4 second roll, the "beam time" encoder should be dialed up between 20-25 seconds. The cue "beam" time should be set to 0.

And I have to agree with Andris, the default paths for the gobo channels were set to linear and not start - but only in the spin mode, the slots mode they -are- set to start.

Also in the conversation about M2K's I discovered the Mac III Profile will not slow fade from one gobo to another as Martin has made it impossible to do this, as it will cause problems with the gears in the gobo wheel from heat if the gobo's are left split for a while,

They have rewritten M2K fixture software in the past to accommodate a slow roll from one gobo to another, however, I need to talk to someone at Martin to figure out if it will do it now.

[QUOTE=ryanB;35804]the default paths for the gobo channels were set to linear and not start - but only in the spin mode, the slots mode they -are- set to start.


When I look at a VL profile in Edit Fixtures, there is no way to change anything in slot mode, it is all hatched out. Only in spin mode can I change a path. I also patched a M2K profile and it does the same thing. How are you able to see the path of slot mode?