Beta 10 - My bugs list

[PolDavril]

(87)
BUG. When the option "Open Show mode in full screen" is selected, the active page in the Show window is always the last one at startup.
It should be "Page 1" for more convenience.
(reported in viewtopic.php?f=19&t=2357).

[PolDavril]

(88)
BUG. There are probably some issues with the UNDO function. I noticed some oddities but I have to look deeper.

[PolDavril]

(89)
BUG/REGRESSION. Check the fixtures in the attached show file (remove dummy ".zip").
The first one (led-par64) has 1 RGB beam.
The second (led-rainbow) has 6 RGB beams.
The third (led-taurus) has 28 single color beams.
In CURVE effect for fixture #1, the 3 RGB channels are present in the channels list.
However, no color channels are listed for fixtures #2 and #3 in CURVE (but they were listed in a previous beta).

[Jp]

Hi

Now i'm back, let's begin

72: It's perfectly normal right now. I handle two names for the Easy Remote (ER) controls. By default they use the automatic mode: the name depends on the association it uses: If you linked a scene to an ER button, it will use the scene's name... In the ER control configuration, the check box is unchecked and the name is grayed out when used in automatic. You can define your own by checking the checkbox and entering your own name. I didn't change the default name, I knew that I'll have to add a multi command system like in DVC3 i'll have to chnage this system anyway (after the official )
73: We'll see what we can do after the official, ther's not much space to do so...
76: Again, we'll see what we can do after the official, there's a lot of things possible to enhance this view
80: It's a big feature with big changes and we know a lot of you want it but it's a lot of work so we will certainly do something about it in the next big version
84: We added this option because people asked for it since it's highly doable and (should be) easy, we'll se what we can do after the official
86: We may do samothing about it after the official (need to speak about it with the rest of the team)

75/79/87: It's already internally fixed, wait for the next version

74/78/81/82/88/89: We are currently looking into it

As always, thanks for the feedback

[PolDavril]

Hi Jp,

Thanks for the answers.
One more oddity below.

(90)
BUG. At the very start, in Scene properties, the values for fade in/out are not correctly initialized and show "-1m-1s00" instead of "00m00s00".

[PolDavril]

(91)
BUG. When the option "Enable fader animation" is off in Preferences, the color remains when a reset button is pressed (All/Family/Select) although all faders go back to zero.
If a fader is moved up or down and set to zero again, the color goes on glowing a little bit.
This issue occurs when a RGB fader is moved manually while a scene is running (LTP mode).
It seems to be the same issue with single color channels too.

[PolDavril]

(92)
QUESTION. When adding a fixture in PATCH, is there a way to choose which channels are initialized to ON (or not) for Fade and Dimmer ? Are these flags initialized by default with an internal logic ? Is it part of parameters in ssl2 ?
Check the fixtures in the attached show file (remove the dummy ".zip"), they still contain the default parameters.
In my opinion, there are some oddities.
- led-dynaspot : "Pan"/"Tilt" channels are set to FADE=ON ; I don't think it's useful to fade the coordinates of a moving head by default.
- led-rainbow : "Red x", "Green x" and "Blue x" channels are set to FADE=ON but not to DIMMER=ON. However, one may want to use all channels with the general dimmer also.
OK, it's always possible to change these settings after a new patch has been done but it takes time, especially when there are a lot of channels and/or fixtures to modify.
Could you clarify this ? Of course, you can.

[PolDavril]

(93)
BUG. In PATCH, when a fixture is duplicated or copied/pasted, all current parameters should be copied too but they are not (Invert Pan, Invert Tilt, Swap Pan/Tilt, Fade and Dimmer). They are always reinitialized by default and they must be changed manually again.

[PolDavril]

(94)
BUG (CRASH). Try the following actions.
- In PATCH, add a fixture
- Right click on this fixture and select "Copy"
- Click "File" -> "New" to start a new project
- The "Paste" button is still active. Click on it and... crassshhh...
I suppose that the internal data are cleared when "New" is done and the "Paste" function should be disabled after "New".
Same issue when another file is loaded.

(95)
BUG ? In PATCH, the "Copy" button is always inactive in "List view" although it's possible to paste.
Is this intentional ?

(96)
BUG ? In PATCH "Grid view", a right click triggers a contextual menu (and it's possible to paste a fixture starting from the address that has been clicked). However, in "List view", the right click does not trigger any contextual menu.
Is it intentional ?

[PolDavril]

(97)
BUG. In PATCH, when a fixture is duplicated, the new fixture does not show up immediately but it remains hidden until a zoom button is clicked.
Same issue with Copy/Paste.
In fact, the duplicated (and pasted) fixtures do not "make their entrance" as the other ones.
When several fixtures are pasted at once, when they appear, they are stacked on each other.

[PolDavril]

(98)
BUG. See the attached zip archive with several files : dvc, xep and jpg screen copies.
Load the show file. Select the "led-taurus" tab.
Load the effect xep file. It contains 4 effects stacked. For each effect, all RGB channels are selected, however it was not intended so !
The effects has been created as follows: the first curve on all "Red x" channels, the second on all "Green x", the third on all "Blue x" and the fourth on all "White x". At design time, the preview is correct and the generated scene is correct also.
However, when this effect is saved and loaded again, all channels become selected in all four effects.
There is a bug, either when the effect is saved or when it is loaded.
Note that this issue can be reproduced with a beta May 3, the latest beta has another bug preventing to select individual color beams (my bug #89).

Daslight44-CurveEffectTaurusIssue.jpg (76.96 KiB) Viewed 15603 times

[PolDavril]

(99)
BUG/MEMORY ISSUES. Check the attached dvc file created in DVC3 and the screen copies (in the true zip file attached).
In DVC3, this show file uses about 53 MB of memory.
In Daslight, this same show file uses 1700 MB !!! And the loading is very slow.
When this show file is loaded in Daslight4, all dialog windows become black (usually the sign of a bad memory usage) and the "DMX Levels" tool crashes with a message like "No more memory".
On the EDIT page, there is no default group and scene.
I'm really afraid of this issue for bigger shows, as well as the general stability of the application.
There are surely things to fix about the memory usage.
(I'm running Windows 8.1 64bits - Screen resolution 1366x768 32 bit color).

Daslight46-MemoryIssue2.jpg (71.68 KiB) Viewed 15601 times

[PolDavril]

(100)
BUG/INCONVENIENCE. In Effects generator, the checkboxes "Include set levels" (for EDIT) and "Include live levels" (for LIVE) do not update the effect preview. Whatever the state of the checkboxes (selected or not), the set/live levels are always used for the fixture preview.
It would be more convenient if the preview was the same as the generated effect, taking the set/live levels into account.

[PolDavril]

(101)
BUG ? INCONVENIENCE/LIMITATION. In SHOW, maximum 7 x 12 (= 84) scenes buttons can be added. When a 85th button is added, it replaces the last one without prior notice.
Why this limitation ? Is it possible to push the limits ?
Also, the buttons in SHOW are added by 7 rows in a column before skipping to the next column, even if the SHOW window is undocked and set to fullscreen.
***edit***: Actually, the 85th button is stacked over the previous one and hides it, and so are the 86th, 87th, etc.
Obviously, there is a bug in the buttons positioning when the button count exceeds 84.
The same issue when other controls are added (fader, pan/tilt, RGB) : they are stacked over the 84th button.

[PolDavril]

(102)
SUGGESTION. The "Remote" options in SHOW should be saved within the show file.