• Date
    ahendin
  • Date
  • Replies 5 replies
  • Subscribers 184 subscribers
  • Views 3179 views
  • Users 0 members are here

BUG: Chauvet Strike 324 goes to FL on Goto Cue, Out!

Hello, ETC. Profile fix needed, or possibly help debugging if a software programming corruption. I've just installed the latest fixture library, 10.2.x, build 50, and the problem remains. Running 2.2 (build 96, release version), and about to go into tech week for a middle school musical. There is a partial workaround, but with a student running the lights for the show I'd much rather resolve the issue.

I patched a Chauvet Strike 324 in 5ch mode to DMX 2/501-505 on ch 79. 

1) Double-clicking the (unlabeled) Intensity box and setting to 0 does that.

2) Pressing [Out] sends the fixture to FL. Reset to 0. This is a seriously bright fixture; pretty jarring!

3) Pressing [Goto Cue] [1] [Enter] (channel not listed as active in Blind) sends fixture to FL.

4) Pressing [Goto Cue] [Out] [Enter] sends fixture to FL.

5) I can assign the channel 0 Intensity in every cue (working in Cue only mode currently), or create a macro to do this, but this does not solve the [Goto Cue] [Out] problem, and I use that a lot. Would love a fix ASAP. Timeframe?

I also ended up in a state where console commands were not reaching the rack (no response to faders or direct channel commands; blackout not activated, grandmaster at FL). Restarting the software did not resolve this. I had to reboot the console.

Note also that the beam control names do not match those printed in the Chauvet manual:

a) Chauvet 5-Ch "Flash Intensity" is ETC "Intens", OK.

b) "Flash Duration" is ETC "Strobe Duration".

c) "Flash Rate" is ETC "Shutter Strobe".

d) "Special Effects" is ETC "Strobe Mode".

e) "Pixel Control Macros" is ETC "Effect Macros".

It all ends up being pretty obvious, but is there a good reason why the labels don't match up?

Please advise timeframe for library update, or how else I should approach this. Thanks,

Abe Hendin
The Abraham Joshua Heschel School

  • Not familiar with this fixture, but seems the intensity channel works other way round, ie a "0" from the desk sets it at full and vice versa. Not at a desk right now, but am pretty sure you can invert it in patch.
  • in reply to johannes
    Other possibility: default value is wrong on that channel.
  • in reply to johannes
    don't know the fixture either, but the problem, or probably rather the first layer of the problem is that the home value for Intens is set to 255. either create a home preset where you change this, or go to patch, fixtures, arrow down to the personality, copy, edit and in the intens row go to the home column where it says 255, click there and type 0 enter. click return until your back in regular patch. now don't forget to re-patch your fixtures to the new type.

  • Hello, Abe!

    I think the profile is wrong at this time, and we will work to fix it.  What is wrong is simply that the intensity is homed to full when it should be homed at 0.  This can be changed for your ease of use now by copying to profile, editing the home value to 0, and then patching as the copy and not the original.  This will help until a fix can be made in a profile library update.

    I believe this issue occurred due to some fuzziness in the manual for the fixture.  At first glance it appears that strobe intensity could be set so that at full the fixture was on and not strobing- thus leading us to home the intensity at full.  This is a mistake since DMX 1 is not strobe but rather intensity.

    As for the naming- we have our own naming conventions for parameters, and this is tied into how we calculate changes within the program.  We choose the appropriate name in our library to correspond with the behavior of the device, not to match the name as assigned by the original manufacturer.\

    I hope this helps clarify things.

    Thank you,

  • in reply to saranow

    Thanks, Johannes and Ueli, and Sasha for clarifying naming and confirming the issue. I've copied the fixture profile and corrected a couple of things. Home value for Intensity was indeed set to 255. The manual states that in 5ch mode, 000-005 has no function, 006-255 = 0-100%. The range was not correctly set to match this. But the manual is incorrect: setting the minimum value to 6, which should = Intensity 0, puts it at the minimum brightness. If I set value to 5-255 (user 0-100), 0 shows no intensity. But I still have to set it to 3% to turn it on. Minor issue, as conventionals pretty much behave this way, but seems odd with an LED. Anyhow, delighted to have correct home value for correct Out behavior. Makes my day, and I'll now know what to do next time. Thanks, all, for being here.

Related

www.etcconnect.com