Intensity Fade Time Bug

GordoGordo Registered User, Hog Beta
I've encountered a bug with two separate showfiles on both Hog4PC/Windows10 and a Hog4 running 3.3.0
Some fixtures are snapping on rather than fading in with their allocated fade times
When one of these same showfiles was loaded onto a Hog 4 running 3.2.1 the problem did not manifest

Comments

  • MitchMitch Registered User, HES Staff
    edited January 2016
    Hi, is all of the same type(s) doing this? What fixture types are they?
    Would some of the fixture type be observing the time, and others of the same type not?
    Was it consistent which were and were not observing the fade time?
    Any chance the ones not observing are all on the same universe and the ones working correctly all on a different universe?
    Can you give any more details?
    Do you know what software version the showfile was created with? Was it originally a Hog 3 show?

    Thanks
  • GordoGordo Registered User, Hog Beta
    Hi Mitch
    It's not restricted to one fixture type, in the current showfile I'm looking at there are Auras, Vipers and B-eye K10's which are all displaying the same behaviour but not necessarily in the same cues
    All the same fixture types display this behaviour in the same cues
    It does not seem to be consistent as in the same fixtures will always snap on. But it does seem that the same fixtures display this behaviour in the same cues even after a reboot
    The fixtures are on different universes
    Both files were created on Hog 4, the first on 3.2.??? and I'm fairly certain I created the current file (different show) on 3.3.0

    It looks as though the fixtures all fade out at their correct time

    I don't know if this helps at all, but a cue originally recorded with Aura's at full, then updated (or merge record, I don't remember) to Auras at 0, plays back as follows.
    Cue 2 Aura@ no intensity programmed
    Cue 3 Auras programmed @ 0 (updated cue) fade time 2sec globally - Aura's snap to full then fade to 0

    Let me know if I can provide you with any further info

    Gordo
  • GordoGordo Registered User, Hog Beta
    Probably related, I've discovered a IFCB fader with an intensity chase as the only cue snap's to a base intensity of full when fading up from 0
    Looks like it uses the correct 0% intensity base at around 70% fader, also fades out correctly with the fader
  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    edited January 2016
    Hello Gordo,

    Please send me your show file as I am not seeing this with a new show. I started a new show on 3.3.0 b1175 and patch an Aura standard, record a cue with the intensity at full and played back the cue. The intensity correctly faded from 0 to 100.

    I also quickly tested this on on 3.2.1 and again the intensity correctly faded using the fade time.

    (mgraham@barco.com)
  • cmuenchowcmuenchow Registered User, Administrator, HES Staff
    I am suspicious this might be a bug related to marking. Are any of the effected cues marked or right before a marked cue?
  • GordoGordo Registered User, Hog Beta
    Hi Chris

    I don't make use of any Mark Cues, but do hard program in all my movements in black
  • GordoGordo Registered User, Hog Beta
    Michael,
    I've emailed you the showfile I'm currently working on, listing some of the cues where this behaviour can be spotted

    Thanks

    Gordo
  • nijst001nijst001 Registered User
    Hi, I have this problem when I mark a cue...
  • GordoGordo Registered User, Hog Beta
    From Michael:

    " I am able to see the problem in your show and can recreate it in a new show.

    The problem is uninitialized Intensity values are applying the incorrect fade time when initialized in a tracking list for the first time.

    I have logged this as D-2784.



    This will only occur if the fixture(s) has a CMY value tracking and then intensity is added to the list in a later cue.

    A temporary work around is to add a 0% intensity value for the fixture(s) so they have a initialized value and will not jump."



  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    This will be addressed in the upcoming 3.3.1 patch release.
    At this time I do not have a release but we are working to get this patch out ASAP.
  • nijst001nijst001 Registered User
    The fixture I have this problem with does not have CMY (Showtec Indigo 4500)
  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    edited January 2016
    Send me your show file along with what list / cue and fixtures giving you trouble.
    We have also fixed a few other cases that could cause this problem.
  • jxgriffijxgriffi Registered User, DL Beta, Hog Beta
    Michael,

    I'm having some of these issues with DIMMERS also. I like to do a "video" list which is IPCB fader with everything going to 0 and a light blue on any color mixing fixtures. If the dimmers in question are not active from a cue list (or are already at 0 in an active cuelist), when the fader runs up, they POP to full and then fade down.

  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    Thanks Jon, will make sure to test this case.
    we are taking a little longer on this patch as we want to cover all cases.
    We hope to be in beta by the end of the week.
  • Firewood1Firewood1 Registered User, Hog Beta
    Hi Michael, there's lots of talk of this with IPCB faders, and cues with CMY values etc, but can I just check that this has been caught in the most basic possible situation?

    Fixture 1 @ Full
    Record to Master 1

    Fixture 1 @ Full
    Record to Master 2
    Clear Programmer

    Play Master 1, with fader at 0
    Push Master 2 fader to full, press play. Fixture snaps to full ignoring time.

    Really basic, i'm sure you have it logged, but wanted to check
  • webbo04webbo04 Registered User
    I experienced this last week with a show. The only way I got around it was to go into the cue previous and record my fixtures at 0%.

    Definitely a bug!
  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    Hello Everyone,

    We have fixed this and are currently in beta.
  • cormacjackcormacjack Registered User, DL Beta
    Hi Michael,
    Would it be possible to give an idea of when you might release a patch for this ? Would it be in march or possibly later than that?
    Starting some small summer projects and ideally would start on a recent version of the S/W.
    Currently on v3.2.1

    Thank you.
  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    Hello Cormacjack,

    3.3.1 was released on Monday.
Sign In or Register to comment.