Report Bug:

To report a bug that you have discovered in a personality file,
find the file in the database and click on the picture of a bug.
You will then be required to input your details and information
about the bug.

Please ensure that you are using the most recent version of the personality file before reporting a bug.

Current Bug Reports:

Fixture Details Desk Type Bug Info Status Report Date

Clay Paky
A.leda B-EYE K20
Clay Paky_A.leda B-EYE K20.d4

 Diamond 4 (.d4)

 Capture model: (Probably) lens feature modelling obscuring LED cluster. From default values, after selecting the fixture and raising intensity the internal visualiser shows only one quadrant of the LED cluster being visible. Adjust the index value of the lens rotation control covers and uncovers more or less of the cluster but only for one half. This was seen with the fixtures patched in extended and extended RGBW modes, I did not check other modes.

 Requested

 10/06/2019 10:42:15

American DJ3
Vizi CMY300
ADJCMY3B.R20

 Pearl 2000/2004 (.R20)

 GOBO ROTATION CHANNEL ON ALL DMX MODES : Incorrect DMX values, new values are : ROTATING GOBO INDEXING & GOBO ROTATION 0 - 127 GOBO INDEXING 0 - 360 128 - 190 CLOCKWISE ROTATION FAST - SLOW 191 - 192 STOP 193 - 255 COUNTER-CLOCKWISE ROTATION SLOW - FAST

 Requested

 15/05/2019 11:18:43

Microh
Halo Beam 150
MMHBM150.R20

 Pearl 2000/2004 (.R20)

 the shutter/iris values is not correct when locate is used, the shutter doesn't open, it need to be over 8% when locate is used

 Requested

 09/03/2019 18:02:59

Chauvet3
Maverick MK2 Spot
CHMVV2SB.R20

 Pearl 2000/2004 (.R20)

 in 24 ch mode when (locate is used) the virtual dimmer is oscilating, the initial value is off

 Requested

 09/03/2019 17:59:34

High End
Cyberlight 2.0
High End_Cyberlight 2.0.d4

 Diamond 4 (.d4)

 see http://forum.avolites.com/viewtopic.php?f=7&t=6017 It occurs that the CMY channels are inverted in capture - you need to invert them in Titan, in order to get output when pressing locate. Unfortunately the manual doesn't give away how these channels are supposed to work, but I have reason to assume these channels need to be un-inverted in capture/AtlaBase. Don't know if you have a fixture to test this - and then, please have AtlaBase correct this

 Requested

 17/02/2019 03:30:53