The Avolites Discussion Forum

Hi all,

I'm having a strange problem when hooking up either a Pearl Expert or a Tiger Touch (both Titan 3.1) to a PC running Lightconverse by ACDI. Essentially I am using Lightconverse Avo Demo, thus connecting universes 1~4 to ACDI.

Basically I can patch and control any fixture in that setup. But every now and then some or all fixtures go crazy: loosing color, position, whatever. This sometimes happens even at 'Locate Fixture': some do locate, some don't.

In the LC DMX view it seems like ACDI sometimes omits some DMX channels - if I do the same thing by ArtNet (and use a tool to log ArtNet), everything is fine. Furthermore, if I toggle the desk to Classic mode, and patch ackordingly, everything is fine with ACDI, too! It's only with ACDI and Titan.

Anyone has had this issue before, or has a hint or a solution? Many thanks.

S.

Hey,

You shouldn't need ACDI when using Titan. You setup your IPs on both console and LC machine, then connect the two via a network cable. Then go into the tools menu on the console, go to switch task and chose the titan window. From here, select tools -> setup dmx outputs and assign the LC from the artnet drop down menu onto a dmx line on the console and set the universe. You need to make sure LC is running before the console will see it over artnet.

Just to add I have seen the problem before using Vision and the solution was to use Artnet.

Hey there,

thanks for the replies, however: simply suggesting not to use ACDI is not exactly a solution. That's what ACDI is designed for, isn't it? But much more, I'm craving for a solution I could suggest to clients for training and demos. There is an LC AVO demo version available for free which runs ACDI only, so the only thing to purchase is the ACDI thing. This would be perfect -- if it'd run okay...

Sebastian
________________________
Trendco
Training & Services

Do you have the desk connected to Light Converse via a crossover cable or through a switch. I have seen this problem in the past and inserting a switch often solves the issue. It could also be a faulty network cable.

Just in case someone else is interested:

seems this is solved in version 4 - with the upgrade, ACDI works like a charm


Maybe one of the Avo guys could confirm this.