Pearl Expert Titan problem

[icatech]

Hi there,

we had our Pearl Expert upgraded to Titan a few weeks ago and on the whole are very happy with it.

However, we have an intermittent problem with dimmer attributes being dropped at random, which causes pain during the focus and programming. This happens on movers, LEDs and conventional (dimmer-only) fixtures alike, and we can't find a pattern to it.

Is this a known issue or does anyone else suffer from it?

All help appreciated.

Thanks,

Lee

[niclights]

I have never seen any such problem.

It might help to explain a little more to understand.

Do you mean intensity is disappearing from programming on playbacks or just from raised presets?

For programming what mode do you record in (ie. channel/fixture/stage)? If using 'by channel', are you certain the information was in the programmer when recorded?

Any other details you can think of?


Sorry if this sounds obvious but I think it is always important to cover the basics first.

[icatech]

To be clear, the information is just disappearing from the programmer. It's not disappearing out of playbacks once recorded.

So for example, I have a bunch of Color Blocks. I raise the dimmer to 100% on the wheel, then switch attribute control to colours and start mixing. For no apparent reason the dimmer resets to 0%. Nobody hit clear, or any other key for that matter.

We've had the same problem with the dimmer attribute on Martin Mac250 Kryptons, and even with dimmer-only channels for conventional fixtures, which seems particularly weird.

[niclights]

Strange. I must admit I mostly use the faders for intensity rather than the wheel. Do you know if this happens with faders too?

My instincts tell me this could be a hardware issue with phantom fader values of zero being sent to the software.
Currently the faders do not level match for intensity values that are already in the programmer by other means. ie. if you set intensity by wheel then raise the associated fixture fader, the values represented by fader level immediately override, rather than waiting for the fader to reach the existing level before taking control. Therefore faulty hardware (including worn faders) or simply nudging a fader could cause this?

It could also happen even if the values originally entered via the fader, with the fader still in the raised position, although perhaps slightly less likely that it is just a faulty fader.

You can observe fader readings by opening usb expert. Maybe try just wiggling some of the fixture handles side to side while at zero or full and see if it any values are sent?