Weird move FX behaviour in stand alone
Posted: Thu Dec 14, 2023 4:53 pm
I have a DVC4 Gold interface and I'm using the most recent version of Daslight 5 (released 29th november 2023).
In Daslight 5, I created a single scene containing all the needed attributes for a specific scene: two LED fresnels and four moving heads.
Two of those moving heads have a static position with a rotating gobo, the other two have a move FX applied to them.
This looks and works perfectly fine in Daslight 5, using the DVC 4 gold interface.
We want to run this on stand alone, so I wrote this scene (and another with only the static positions) to the DVC 4 Gold interface and set it to 'stand alone mode' using the hardware tool.
The scene with just the static positions work fine.
The scene with the FX is doing weird stuff.
One static MH is correct, the other ones are going haywire, moving all over the place and strobing, with the wrong gobo.
As if the DMX patch in the interface is incorrect, which seems very illogical.
I tried to write the scene again to be sure, the problem persists.
The scene still works fine when using the interface with Daslight 5
Is this a known issue or does anyone have any ideas?
In Daslight 5, I created a single scene containing all the needed attributes for a specific scene: two LED fresnels and four moving heads.
Two of those moving heads have a static position with a rotating gobo, the other two have a move FX applied to them.
This looks and works perfectly fine in Daslight 5, using the DVC 4 gold interface.
We want to run this on stand alone, so I wrote this scene (and another with only the static positions) to the DVC 4 Gold interface and set it to 'stand alone mode' using the hardware tool.
The scene with just the static positions work fine.
The scene with the FX is doing weird stuff.
One static MH is correct, the other ones are going haywire, moving all over the place and strobing, with the wrong gobo.
As if the DMX patch in the interface is incorrect, which seems very illogical.
I tried to write the scene again to be sure, the problem persists.
The scene still works fine when using the interface with Daslight 5
Is this a known issue or does anyone have any ideas?