Beta 8 - My bugs list

[PolDavril]

Hi Jp and thanks for the good work.

(19 cont'd) OK. No problem for me.

(20) BUG (reminder for us - topic is taken from previous discussions).
The FADER icon is grayed at startup in General tab (but it's OK in all fixture tabs).

(21) QUESTION. What is the following option in Preferences ?
- Send feedback when loading a show

[PolDavril]

(22) IMPROVEMENT in the lower part of the main window.
Whatever the section currently selected (FADER/PALETTE/EFFECT), when any fixture or General tab is clicked, it comes back to FADER.
It would be more convenient to stay on the current section. If possible, of course.

[Jp]

- Send feedback when loading a show

It allows the software to send midi release commands when loading a show, it was asked here:
http://forum.daslight.com/viewtopic.php?f=19&t=2246

22) I though that was fixed, i'll check it tomorrow

[PolDavril]

(22 cont'd) Yes, you're right, it had been fixed at a moment, but the previous behavior has come back in newer releases.

(23) QUESTION. The Pixel and Matrix effects do not work with Extra Color beams but I assume that's normal, as those effects need true RGB channels ? Anyway, no problem about that, in my opinion.

[PolDavril]

(24)
BUG. When importing scenes, the Fade parameter in scene Properties is not imported and always set to On. Attachment : source show file for importing scenes (a scene with Fade=On, a scene with Fade=Off).

[PolDavril]

(25)
BUG. In the 2D view, when selecting fixtures. In my opinion, it may cause incorrect order of fixtures with automatic positionning, because of duplicate order numbers. Some issues found below.

(25a)
In the example attached, I select odd fixtures. 1st is number "1", 3rd is number "2".
I invert selection. 2nd is number "2" but 4th is number "2" also
Again, and 1st is number "3", 3rd is number "3" also.

(25b)
I select 1st and 2nd fixtures. 1st is number "1", 2nd is number "2".
I move down selection. Same issue as before.

(25c)
I select 1st (number "1"), 2nd (number "2") and 3rd (number "3").
I unselect the 2nd and select the 4th (number "3" also).

(25d)
Move up/down selections seem to work in a strange way when 2 or more fixtures are selected. I will try tomorrow again.

[PolDavril]

(25 cont'd)
I can't understand the logic of the "Move up selection" and "Move down selection" buttons. There is surely one. Please give me some more info about that before I go on testing the positioning features.

(26)
BUG (in my opinion). When one or more fixture group buttons have been clicked, all selected fixtures are unselected by clicking anywhere on the panel around the fixtures. In that case, all fixture group buttons should be reset to Off but they are not. The drawback is that any active fixture group button has to be clicked twice to make a new selection.

(26a)
IMPROVEMENT. A deeper logic is to check if all fixtures of a group become unselected, when clicks are done, and set the corresponding fixture group button to Off in that case.
OR simply set a fixture group button to Off when at least one of its fixtures becomes unselected (better, in my point of view).

[Jp]

Hi

We'll look into the fixture index bugs (it's purely graphical though don't worry )

Regarding the fixture groups, we'll enhance it, originally it was never planned to be able to unselect them...

Regarding the 23) yes, extra colors are not used I think, but neither are the color presets. It's a known limitation that we plan on improve in the future

[PolDavril]

(27)
BUG. In LIVE, while Scene 1 runs, select 1 of the 8 beams. For that beam, click "Beam off".
Now start Scene 2. The selected beam is automatically On again. Click "Beam off"' once more : the beam goes on running.
In my opinion, that's not logical and 2 different enhancements are possible.
- Either the "off" beam should not be reset to On when a new scene is run (I prefer this one)
- Or the beam should be set to off whenever "Beam off" is clicked

[PolDavril]

(2 cont'd)
BUG about the interaction Color wheel / Master dimmer.
Now the values changed with the master dimmer are sent to the color wheel.
However, the opposite does not work : the changes made on the color wheel are not sent to the master fader. When the master fader is not at its maximum, the color wheel "blinks" and the color settings are hard to do.

[Jp]

Well the opposite is not supposed to work...
When you set a value in the color wheel in live, the color is applied to the ltp values which don't care about the master fader (which is applied later, at the end of the dmx computing)
So the value is always set without the "master dimmer" information right now...

one idea would be to store the value correct for the current master dimmer, but then I have to store a color that is not the one you set (it would be brighter than it)

[PolDavril]

Thanks Jp.

(28)
BUG. When the ScanLibrary Editor is run by the tool menu and still running when I close Daslight4, it crashes (without the crash report form).

(28a)
BUG. When the "DMX levels" window is opened, the main "Close" button remains active. When I click on it to close Daslight, it crashes (with the crash report form).

(28b)
BUG. When "DMX recording" window is opened, a single click on the main "Close" button does nothing but a double click closes Daslight (no crash).
Same for "Stand Alone" window.

[PolDavril]

(29)
BUG with "Map to DMX in". Load this file. When "File" -> "New" is done, the first 3 DMX in indicators remain lit although the DMX in is no more mapped.
According to my tests, it happens when a DMX in is mapped to multiple DMX out's.

[Jp]

28) Will be fixed
29) Nice one will also be fixed

[PolDavril]

(30)
BUG ? In SHOW, I created some custom faders.
Move the "Red 1", "Green 1" and "Blue 1".
The selected values on the custom faders are sent to the main faders but they "flash" between zero and the current value when they are moved.
When the color is changed by the main faders, the custom faders in SHOW are not updated.
However, all other custom controls work in pair with their "mirror" fader.