Problem with "old" interfaces (Box/Ssa/Cable) [fixed]

[Pink LD]

V7 on 2 different Win7 64bit machines, 2 different Win 8.1 machines, and tried on 2 different XFactor boxes.
I readdressed 15 of my 6 and 7 channel LED fixtures down to 1-100. And 3 of the fixtures went buggy.
Long story short after bringing them home and testing them against my programming on multiple machines, and using the blank default show of the software here is what I know:
Anything addressed between 15 and about 40 interact with each other. I put up a dimmer on the fixture addressed to 22 and the Ch15 fixture reacts in odd ways. If I play around with the faders between 22 and 29 I can override chs 15-21. There are more in this range but I haven't mapped them all out.
My global dimmers on scene and a selection of strobe scenes for all these fixtures make the fixtures addressed at 15, 22, 29, and 36 act unexpectedly.
It is not a patch input or output issue, I used the default lightshow with no fixtures put into Editor and did not patch anything.
It is not a fixture setting. I used fixtures that can do 3, 6, or 7ch modes; or 7ch only.
And yet the DMX bargraph does not show this error data.
I can get a video to you of the behaviour probably by Wednesday.

[support]

We had a very similar problem with an old bugged libray file ("efk_hardware.dll" for Windows / "efk_hardware.dylib" for MacOS).

Can you please confirm that the "modification date" of this library, in your software folder, is 13 of June ?

[Pink LD]

I will in about 2 hours.

[Pink LD]

Yes, they are 13.6.2014 for Windows. I don't use Mac

[support]

We found a problem with other interfaces than D512/Remote/Rack.
This file should fix the problem: http://download.thelightingcontroller.c ... re.dll.zip

[Pink LD]

Shop tests appear that this problem is fixed. However I will give it all a field test on Friday and report back to you.

[Pink LD]

Everything worked fine in the field this weekend. I use the fix file, I did not have time to update to 7.1.5 proper. But at this point I consider this fixed.