Effects problems

LXConsole support and feedback
Post Reply
Poplinski
Posts: 40
Joined: Mon Mar 25, 2013 3:55 pm
Location: Malm�, Sweden

Effects problems

Post by Poplinski »

I have discovered a problem with effects...
In a show I am running a chase on top of a few other cues meaning that the effect fades in linked to a cue and fades out linked to another cue.
During the fades or rather when the fades are about to finish I experienced
several channels that have nothing to do with the channels being used in the chase to flash on very briefly (looks so fast that it couldn`t even be done on purpose I think). Even though it`s very fast , still very disturbing in a very subtle and dark lighting design.
I have tried to do the effect manually, but with the same result. It seems to happen randomly, not always with the same channels.
I cannot see anything happen in the live window, so my guess is that it is a bug that sends a message via dmx.
And , I`m afraid you can`t see it unless you have everything rigged.
I can send the show file to someone (admin?) if that can help to find a solution.
/
Uli Ruchlinski
admin
Site Admin
Posts: 1643
Joined: Mon Nov 05, 2007 1:26 am
Contact:

Post by admin »

e-mail the file to lx @ claudeheintzdesign.com

Be sure to include the operating system and LXConsole version numbers as well as the output interface (DMX USB, Art-Net, etc.).
admin
Site Admin
Posts: 1643
Joined: Mon Nov 05, 2007 1:26 am
Contact:

Post by admin »

The file tested OK using the latest build of LXConsole and Art-Net output. 3.0.7 is a fairly old version.

According to the change history:
3.1.9 (6623A) solves multi-thread related issues with output buffers including one that could cause a crash and another that shut down DMX USB Pro output when an effect was played by an action attached to a cue. Adds support for OSC remote inclusion of a group in a cue.

This old bug may account for your problem. I'd try your file using the latest build or even the last release. That may solve the problem.

The only DMX Pro mk2 I have access to is a pre-release version with a bad USB connector. I will attempt to check your file with that soon. (Provided I can clamp it to get a stable USB connection)
Post Reply