Just realized a few days ago (Cap Sensors!!)

Buzz313thBuzz313th Registered User
In the diagnostics menu, when you do a hardware test on the front panel... I had no idea what the button, "Disable/Enable Cap Sensors" was refering to... I just noticed that the "Fader Caps" are touch sensitive. Fantastic!!

I can only assume this is a hardware feature being held for version 2.0 of H4? I take it we will have the cap sensors associated to some cool features, like what we find on another desk? Care to give us some teasers of what else you guys have up your sleeves?



  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    edited July 2013
    Cap Sense is currently working.
    If you have a Fade Master Macro running and you touch the fader, the fader will stop moving and NOT fight you. Remove your hand and the fader will jump to its position.

    We do have plans to show that a fader is touched.
  • Buzz313thBuzz313th Registered User
    edited July 2013
    Sweet!!! Can you guys consider setting fader options to the cap sense? Being able to assert would be great, not to mention showing the "sensed" fader on the playback bar.

    Since we are on the topic of macro triggered faders. I was looking for a method to set a fade time while fading a master via a comment macro. It defaults to a snap fade. How can the user set a fade time to a comment macro that is triggering a master to fade?

    EDIT.... Nevermind.. I found the "T" Command. Had to look on the online manual as I couldn't find it in the one on the desk...

    Sorry... My mistake.
  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    edited July 2013
    Showing that a fader is touched on the playback bar is something we have planned.


    FM1='s Fade Master 1

    /0 ='s Fader Value you wish the fader to move to

    t5 ='s the Time you want the fader to take moving to the new value (I just put in 5 for a number)
  • Buzz313thBuzz313th Registered User
    edited July 2013
    Thanks Michael
  • stgtechstgtech Registered User
    edited July 2013
    In my particular instance I use comment macros on my main cue stack to control a separate fader with a house light scene. I used to have cues setup in 10% intervals and use gm#/cue syntax. The nice thing about this is that if I had to override it I could simply by hitting pause. Now with the single scene and the fm#/%t time syntax I don't need all the cues and can have individual control over percentage and time. BUT there is no way to stop it once that macro fires. With the cap sense I would like to see it be able to see me grab the fader and stop the fade macro.

Sign In or Register to comment.