Hi all,
i found out something strange today on both quartz and tiger touch 2 running V10.0
what i did was this:
- created new showfile
- in dmx settings assigned an artnet universe to line 1
- patched 4 dimmers on line 1
- recorded all 4 dimmers @ 100 % under fader 1 record mode channel
- created a dimmer saw shape spread 4 under fader 2 also record mode channel
- created a group master for the group of the 4 dimmers under fader 3
i had the dmx workspace open to view my output and i had "ArtNetominator" software running to see the actual artnet output too.
when i set the group master on fader 3 to lets say 50 % i can see that when i move my fader 1 (the one with 4 dimmers @ 100) that the values don't go above 128 so all normal.
when i run the shape on fader 2 while fader 1 is back down (@0) the values also don't go above 128 so still doing fine.
but when i then set fader 1 @ 100 while the shape is still running the values of the shape go to 255 while my group master is still @ 50 %
is there a reason why the desk acts like this or did i stumble upon a bug.
10.0 new bug ?
Moderator: Moderators
Re: 10.0 new bug ?
This is correct behaviour for a scale master and dimmer shape with size at full.
The dimmer saw shape will modify the dimmer control from -255 to +255 relative to its origin. When the scale master is set to 50% the origin becomes 128 and the modifier becomes -128/+128 so it will still be able to reach 255.
The dimmer saw shape will modify the dimmer control from -255 to +255 relative to its origin. When the scale master is set to 50% the origin becomes 128 and the modifier becomes -128/+128 so it will still be able to reach 255.
Re: 10.0 new bug ?
i used a group master, not scale master.
the bug only occurs when the fader with the dimmers @ 100 is fired
the bug only occurs when the fader with the dimmers @ 100 is fired
Re: 10.0 new bug ?
This is not a bug. 'Scale' is the default type assigned to group master.
Re: 10.0 new bug ?
Didnt know that, its strange that that is the standard mode for a master.
My bad
My bad
Re: 10.0 new bug ?
Another strange thing running V10 simulator,
when you save macro's to lets say the position pallets window, the macro works fine, when you save and reload the show the macro becomes unasigned.
Am i missing something ?
when you save macro's to lets say the position pallets window, the macro works fine, when you save and reload the show the macro becomes unasigned.
Am i missing something ?
Re: 10.0 new bug ?
yyy898 wrote:Another strange thing running V10 simulator,
when you save macro's to lets say the position pallets window, the macro works fine, when you save and reload the show the macro becomes unasigned.
Am i missing something ?
All being well this should be fixed in the next version.
Who is online
Users browsing this forum: No registered users and 25 guests