Daslight Forum

Follow up to the above. I have since discoverd that this procedure only works for single channels if multiple channels, such as the master dimmer for four moving head ligts (w+x+y+z), mapping cannot be performed on any universe above 1. This is an almost complete failure.

I have found a major bug in the DMX mapping utility. If any universe other than 1 is the DMX mapping target, you MUST use the DMX universe number not Auto and you must enter the actual fader DMX address rather than letting the utility select the channel. For example to map Input 1 channel 10 to Univ...

I am unable to map DMX input triggers for any sliders beyond the first device in the patch. all subsequent devices have a mapping result of 353+369+385+401 and cannot be triggered from an external control. I cannot sellect the universe or the appropriate trigger channel and the device does not respo...

There appears to be fairly major bug in the new release. When configuring device preferences it is no longer possible to assign the same ArtNET universe to different devices. For example we have one Elation eNode and one instance of Madrix3 running on a local PC. Previous revisions would allow both ...

Testing using iOS and Android platforms. Using the Beta 2017-08-16 residing in a Lenovo M900 mini core 7 PC hard wired to the LAN Buttons and controls consistently do not load or load incorrectly when using EasyRemote and iOS devices There are virtually no dropped graphics or buttons when using an A...

Follow up. There has been a recent "update" to the Android app and now these problems are occuring on Android devices as well.
Is there a specific graphic type that needs to be used for buttons? Png, jpeg, bmp?

We have discovered these bugs on all tested iOs devices: Buttons feedback sometimes flips with a scene operating but the iOs button indicating off. Same with multiple scenes from the same group. Scene buttons from a group are set as Play/Stop. This requires re-selecting the scene which will stop it ...

Not only does it lag, but we have discovered, now that we are attempting to operate the systems simultaneously, that all Daslight4 instances interfere with each other. The lag was occuring when more than two instances were open and running on their respective PC's but only one was actively being use...

We have discovered that running more than two Daslight DVC4 (DVC Gold) instances on two different computers (with no common fixtures or universes) will cause Daslight to lag, slow and freeze when sending ArtNET commands rapidly. For example We can turn a Martin MH-5 on and off or change color or gob...

In Daslight 4 (Stable, 5/17) new hardware add can not be set for any ArtNET universe above 1 (ArtNET 0x0). In Daslight 4 (Beta, 6/17) new hardware add can add any or all ArtNET universes defined in edit. Hardware devices will NOT save the tickmarks for "Use broadcast" or any of the "A...