ICBF Fader Release

When I use a master list with fader as master and a second list with fader as ICBF crossfade I got a strange
issue. The master list is running but I moved the fader at zero for a blackout. Starting the second ICBF works also when I increase the fader. But when I decrease the fader suddenly the dimmer releases right away while all other attributes be faded out. This doesn't make any sense in my eyes. Why dimmers should be released while all other attributes be fading.
Is there a setting I have missed?
Got this on a RoadHog4 consoles and on Hog PC.


  • MLorenzMLorenz Registered User, Hog Beta
    Very old issue I had reported very often. Thought it was solved. But seems not.
    This is only happening when the the IPCB list ist not fully stomping other cuelists, correct?
  • Go_ButtonGo_Button Registered User
    Yes you are right. I'm running 2.5.0 actually but will try this with the new update. It's a bit frustrating. I thought I'm doing something fundamental wrong.
  • MLorenzMLorenz Registered User, Hog Beta
    You are not doing anything wrong... It is there since a very very long time and had been reported several times...
    I thought it had been figuered out and fixed. Some releases ago when a lot of IPCB bugs had been fixed.
    Will try it tomorrow with 2.6.0
  • dreanolivaresdreanolivares Registered User, HES Alumni
    Can you give us an example of the programming that you have in each cuelist? We will try and recreate the problem here.
  • Go_ButtonGo_Button Registered User
    I normally use a master cuelist for my shows. All attributes are recorded in it to make sure all cues do look exactly the way I want it. The fader is a normal intensity master and "Persist On Override" is active.
    Everything is working as it should. For a blackout I decrease the master to zero but the cuelist is still running. Now I have started a second fader. It's an IPCB crossfader with only one cue in it. The cue uses some lamps of the master cuelist and some attributes, like dimmer, position and color. Increasing the fader works like a crossfader should work. But when I decrease the crossfader the dimmer is not fading back to zero, like all other attributes, it gets switched off right away. But color and position are fading back to their values recorded in the master cuelist.
  • Go_ButtonGo_Button Registered User
    It's much simpler than expected. Use a single dimmer at 100% and record a list. Run the list on a master and move the fader to zero but let the list active. Run a second list with dimmer at 100% but this time as IPCB crossfade. The fader is fading to full but if you decrease it , it is not fading back! I'm a bit surprised that a simple operation like this is not working on Hog4 although it was reported many times.
  • ejberendsenejberendsen Registered User, Hog Beta
    This is not only the case with ICFB faders. When the master of your mainlist is at zero (but still active) and you run an other list on top of that one the release time of the second master will be ignored. So when you release the second list the intensity will drop in 0 sec.

  • Go_ButtonGo_Button Registered User
    Have tried this but with two lists and intensity master release time is working and will not be ignored.
    But with ICFB crossfader it's not working.
  • ejberendsenejberendsen Registered User, Hog Beta
    I am sure it is not working. The list should be active in the background. When you touch for example vl2500 washes and store this in cue 1 on master 1. Play this cue and put the master at zero. Then put the vl's at full and store them on an other master. Play the second master with fader at full. When you release the second master the intensity will snap out.
    I had this on a show last weekend.
  • Go_ButtonGo_Button Registered User
    But do you think this is a normal behavior of hog software or a bug? I have worked with some other desks in the past years and I'd never had something like this before.
  • ejberendsenejberendsen Registered User, Hog Beta
    As marc said there are issues with the ICFB fader. The one I had last weekend is a bug. I thinks it is since version 2.6.0.
  • Go_ButtonGo_Button Registered User
    Thanks. I hope this will get fixed.
  • MLorenzMLorenz Registered User, Hog Beta
    The IPCB Fader stuff you mentioned is a bug!!!!
    HAve to try version by version, because I guess it was gone in one release.
  • cmuenchowcmuenchow Registered User, Administrator, HES Staff
    I found a defect in our backlog that seems to match this problem... and its a nasty one to solve but something we will need to tackle eventually I agree..

    Defect D-01748
    Problems releasing IPCB lists/scenes with other intensity scaled playback sources in background

    Hog 4 OS v2.2.0
    IPCB faders do not release their intensity values properly to other LTP playbacks when the LTP playback's intensity scaler is set below 100%. Instead of crossfading to the LTP playback's intensity level using the movement of the IPCB fader the IPCB cuelist fades to the LTP playback's full potential intensity and then snaps off when the IPCB fader reaches 0%.

    100% Repro:
    -Select any fixture
    -Make Cuelist #1 with some color, position, gobo and intensity at full in it. (normal playback)
    -Clear Programmer
    -Select the same fixture
    -Make Cuelist #2 with another color, position and intensity at full in it, but no gobo information (set to IPCB Fader)
    -Start List #1, Fader up
    -Fade IPCB List #2 to 100%
    -Bring Fader of List #1 down to zero or any other value
    -Lower IPCB Fader of List #2, all parameters follow the fader like the should, but intensity stays at 100% until you get to 0 and then the intensity bumps direct to the set value of fader #1.

    So to recap, the intensity during an IPCB release is not releasing to the fader output state of the other LTP playback. The Hog OS has never accounted for this.
    Regression Info:

    Occurs in all versions of Hog 3 and Hog 4 OS but has morphed over time.
    This defect reflect the behavior in v2.2.0 software.
  • Go_ButtonGo_Button Registered User
    Thanks for that information. It's good to know you're working on it. =D>
Sign In or Register to comment.