Beta 11 - My bugs list

[PolDavril]

Hi,

Here are some more things (cont'd from viewtopic.php?f=19&t=2352).

(105)
SUGGESTION/INCONVENIENCE. In PATCH, the "ScanLibrary" frame should be resizable horizontally for longer fixture names can be displayed in full without the 3 dots at the end.

[PolDavril]

(106a)
BUG/INCONVENIENCE. When doing UNDO after an effect is generated in EDIT mode in a scene, the list of steps is not automatically updated. The scene must be unselected (or another scene clicked) and selected again for the updated list appears in the steps frame.

(106b)
BUG. Effect in EDIT mode. The UNDO does not restore the previous steps correctly. The step on which the effect has been generated (with the parameter "On current step"), I mean the first step of the undone effect, remains as is. See the attached show file (remove dummy ".zip").

[PolDavril]

(107)
BUG ? With Daslight4 Beta 11, Easy View 2 is back to version 0.6 build 6288 2nd February 2016. The language is set by default and cannot be changed (I don't see any options to do it).
Daslight4 Beta 9 contained a newer version (0.6 build 6817 28th April 2016) with more options.
Are there issues with the Beta10/Beta11 packages ?

[Jp]

Hey

I'll add the resizable patch grid in our ideas list and I'll check the bugs with the effect generation

Regarding the 3D, I'll just say that we used the version from February because there was a lot of problems with the newer version... BUT we prepare a new version, with a new lot of remade things, and it will be AWESOME just wait for it

[PolDavril]

Hi Jp,

Thanks for the reply.
One more oddity found tonight in our beloved software.

(108)
BUG. In SHOW, I select the 64 scenes (see the attached file, remove dummy "zip").
When I move the block of scenes, scenes do not keep together, blank spaces are inserted and whole lines do swap. It seems to be at random, depending how the whole block of buttons is moved around on the window.

[PolDavril]

(109)
SUGGESTION. In SHOW. An option to duplicate a button would be convenient. The idea behind this : a custom default button is created (button size, colors, text, icon, ...) and then duplicated. This avoids to edit the same properties for each new button. The association to the scene can be made manually afterwards.

(110)
SUGGESTION. In SHOW. Either be able to edit the page label ("Page 1", "Page 2", ...) and set another text title, or the possibility to add a free text on each page of the SHOW. For example, each song of a concert can have its own page in Show and the song title could be written.

[PolDavril]

(111)
BUG/INCONVENIENCE. In SHOW, each time a page is clicked (with edit mode = on), the Remote option is reset to on. It should keep its current state.

[PolDavril]

(112)
BUG/INCONVENIENCE. In SHOW, the Control Editor window should keep the latest position when called. When working with the SHOW window on a second screen, the dialog is displayed on the first screen each time.
Note: keep the windows sizes and positions (at least during the session), should be a general rule for Daslight.

[PolDavril]

(113)
BUG. In relation to the post viewtopic.php?f=19&t=2363 .
In MIDI in Mapping, in the Outputs, the Maximum Value allowed must not exceed 127, as it is a MIDI data. At present, the maximum can be set up to 255. That's not logical.
These minimum and maximum values control the virtual length of the slider track of the MIDI control. For example, if the minimum is set to 50 and the maximum to 100, the corresponding DMX values will be 0 for MIDI data between 0 and 50, and 255 for MIDI data between 100 and 127. All intermediate values are automatically converted.

[PolDavril]

(114)
VERY USEFUL SUGGESTION. For LIVE, There should be shortcuts with DMX/MIDI/Port/Keyboard mappings for "Reset All", "Reset Family" and "Reset Select". When an external MIDI controller is used (e.g. Akai APC mini), as the external faders can be used to control channels of running scenes in LTP mode, it would be extremely useful to assign a button on the controller for any "Reset", and thus clear LTP on channels without having to rush to the mouse.

[PolDavril]

(115)
BUG. When a scene button is clicked in SHOW, the data is not sent to MIDI out, like it does in LIVE. That means that the external controller is not updated.

[Jp]

Hi

I just fixed the bug 115, 114/110/111 were done this morning

The fixes will come in the next beta

We'll check the other things later...

[PolDavril]

Thanks
Another annoying issue.

(116)
BUG/INCONVENIENCE. For MIDI Preferences, the MIDI input is saved and correctly selected at startup. However, all the MIDI outputs are always selected at startup, whatever the output that has been chosen before. Either these preferences are not saved or not loaded when Daslight4 starts.
It's really disturbing, as MIDI notes are sent to other MIDI devices and produce unwanted sounds...

[PolDavril]

(117)
BUG/INCONVENIENCE. Try this. In LIVE, I've got 3 groups already. I create an effect on some fixtures. When I generate the effect, I never know in which group the effect will be created. For example, even if "Group 2" is selected, the effect is sometimes generated in "Group 1" or "Group 3". The generated scene has to be moved manually.
It would be more convenient if the effect was generated in the highlighted (current selected) group.

[PolDavril]

(118)
SUGGESTION/INCONVENIENCE. In Jump Dialog, it would be easier to select/unselect the scenes if the name of the scene itself was clickable. For now, we have to aim at the little checkbox.
In a general rule, all checkboxes should allow a click on their label also.