MiB functions

[artppro]

hi,
I can't found nothing about MiB ( move in black) in the chimp manual.
Can somebody create a cuelist to show diferent options of early,late,specific cue.......functions ?
Thanks,!

[Harald]

I try to explain to you.
1) Step 1: program a start position for one or more fixtures.
2) !! Program in step 2 dimmer off !! (Dimmer 0%)
3) In step 3 you program the new gobo position and/or color, and Dimmer 100%
In step 3 you scroll to the right option MIB, and push SET--> select EARLY.
That's it.....

[Clearlighter]

Hi Forum Members,
I am new to the Chimp and currently in the process of learning the console. I have been used to working with ETC consoles and I’m just struggling with a few things which you may be able to help with. I have tried following the manual and looking for some on-line tutorials, but so far, I have not been able to solve my issue.

I am running (in real life, not pre-vis) a small rig with a small cue list simulating a theatrical performance that has some nice slow fades and looks utilizing both conventional and intelligent fixtures on a Chimp 100 with Banana Wing running Software Version 1.11 (20/12/19).

The intelligent fixtures are Infinity TS260C7 Profiles, TS260C7 Fresnels and Furion S401 Spots. I have checked the fixture library and all fixtures have “Mark” engaged in the relevant attributes. Some attributes have “Mark Zero”, but all my movement, color, gobo, etc. are set to “Mark”. These are the default fixture profiles contained within the fixture library.

In the default timings screen, MIB default time is 2 seconds and MIB delay is 0.25 seconds. When I ran the cue list through, nothing pre-marked or Moved in Black. I assumed that MIB would be automatic with values set in the default times. Can anyone verify this?

Second attempt at running the cue list, I manually put MIB information into the Cue Timings, but still no MIB or pre marking happened.
The following is what I was trying to do:
Q1 – Preset. Conventionals at low level. LED Fresnel at 20% in Congo Blue.
Q2 – Blackout. All fade to black over 5 seconds.

I wait an extra 5 seconds before executing Q3 just to make sure I am not interfering with MIB.

Q3 – LED Fresnel intensity up from 0 to 60%. My intention was for it to have already MIB and should be white when the intensity starts to come in however it begins its color in Congo Blue and fades to White during the fade up. I had a MIB command set to “Early” in this cue, but color still fades from Congo Blue to White.

I wait an extra 5 seconds before executing Q4 just to make sure I am not interfering with MIB.

Q4 – Furion Spots fade in. This is the first time they have been utilized in the cue list. However, they fade into position from their home position instead of MIB prior to the cue. Once again, I manually put an MIB command set to “Early” within this cue and tried to run it again. But once again none of my fixtures performed any MIB or pre marking to positions.

I have also tried to set specific mark cues to see if that would work, but so far no matter what I have tried, I have not been able to get anything to MIB.

Can anyone let me know if I am working this the wrong way or maybe suggest some console setting I may need to turn on or adjust that I may have missed. I believe the cue list settings were set to Tracking when I recorded these cues.

Any help or suggestions will be greatly appreciated.
Cheers, Michael.

[denishessberger]

The first cue of your Cuelist needs to have 0% intensity stored for the fixtures you want to MiB.

If a Fixture never has a defined 0% Intensity Value in your cuelist the Output Engine ignores MiB set in the Cuelist. This is to give you consistent Playback results and not being dependant on other Playbacks for MiB Calculation.

Also, is your Cuelist set to Tracking or Non-Tracking?

Best,
Denis

[Clearlighter]

The first cue of your Cuelist needs to have 0% intensity stored for the fixtures you want to MiB.

If a Fixture never has a defined 0% Intensity Value in your cuelist the Output Engine ignores MiB set in the Cuelist. This is to give you consistent Playback results and not being dependant on other Playbacks for MiB Calculation.

Also, is your Cuelist set to Tracking or Non-Tracking?

Best,
Denis

I was missing an active 0% recorded in a previous cue. Once I put that in, it worked as expected. Thank you Denis. 

[denishessberger]

Glad it worked

Denis