Page 1 of 1
ColorKinetics Color Blast 12 / Mac500
Posted: 11 Oct 2006, 17:35
by centralchristianchurch
Anyone know why when using ColorKinetics Colorblast12, I save the looks into the playback page. They look fine. When I include it in the theatre stack, any lights that are just 255 on the Blue, don't show up. If I move the playback up it works fine. Also, if I add 1 on red or green, it then works properly. Weird.
Any ideas? or should I just do what works by adding another color into it?
Also, how to I get to the Lamp On setting on the Mac500m4 from the board, so I don't have to do it manually from the light?
Thanks!
Posted: 12 Oct 2006, 00:12
by niclights
Hmmm. This is the second time someone has mentioned this. I am 99% sure this is an obscure bug that I discovered a while back whereby that particular attribute, even though it shows in the LCD as in the programmer, does not store correctly if it has been 'included'.
/edit: Ok. I just tested in the simulator and yes it is (or at least was) a problem. Specifically it only occurs when that particular attribute (normally magenta) is defined as HTP.
The workaround for the moment is to 'nudge' this attribute by wheel to re-affirm it's value. It should then store correctly. Annoying, but at least it is not a showstopper!
It is possible that this was fixed in a later version. Can you pls confirm your software version?
I don't have an answer re Mac 500 lamp on. This should be detailed in the fixture manual.
--------------------
(This bit for Avo if not already fixed)
To repeat:
Patch fixture with HTP channel defined on lower bank 10 (eg. ChromoFix HTP)
Adjust blue attribute and store.
[clear]
[include] the memory. Value will show correctly in the programmer.
Store the memory. Memory will be empty.
Stranger still, if another attribute from the same fixture (possibly in the same focus mask?) is included then all the values are stored correctly.
-------------------
Version
Posted: 12 Oct 2006, 16:43
by centralchristianchurch
I have ver 1.2
Posted: 12 Oct 2006, 18:19
by Olie
This is a bug and it is fixed in the next release of software.
Update
Posted: 13 Oct 2006, 05:45
by centralchristianchurch
Where is that update at? I couldn't find anything higher than 1.2
Kris
Posted: 18 Oct 2006, 10:26
by Olie
I am afraid you will have to wait. The current release of software does not contain the fix.