Beta 9 - My bugs list

[PolDavril]

Hi,

Here are some bugs and other thoughts.

(32)
BUG. The "Release at end" option does not work for the scenes. When this option is deselected, the scene is set to pause mode but DMX data is still sent to the fixture. It releases the channels and it must not. This is important when using moving spots, where the beam must stay lit after a movement, until the scene is unpaused.
(example attached - just remove the dummy ".zip" extension).

(33)
BUG. The strobe effect should display in 2D view for all values. This had been reported before with a sample file. A solution would be to begin to simulate the strobe at a lower rate, so that greater values are still visible. Or by using a non-linear scale.

(34)
IMPROVEMENT (important). In some cases where precision is needed, it's very convenient to increment or decrement DMX values by 1 with the keyboard arrow keys. A classical example is to align a very narrow beam to a distant target with pan/tilt at 16-bit resolution.
But there is no way (as far as I know) to select a channel fader without clicking on it or on the fader track. Doing this, the value is automatically changed, depending on where it has been clicked, and the current value is lost.
The idea is that any channel can be selected by a left-click on its icon at the top and/or on its number at the bottom, so that the arrow keys can make it move.

(35)
IMPROVEMENT. It would be more convenient if the keyboard arrow keys were set to repeat mode without having to hold the Alt key. This would be handy for scrolling through the channel faders and for setting DMX values on the faders, quickly and easily.
**edit May 9, 2016** : in my opinion, no longer needed (with the arrow keys above the faders and below the faders, it's enough).

(36)
IMPROVEMENT (minor). When right-clicking on a fader icon, presets are displayed in a pop-up. If a channel has no preset (e.g. RGB color, pan, tilt, ...), the pop-up should maybe not display the "Map to DMX in / Map to MIDI in) menu. It's not that important but simply better that way, in my opinion.

[PolDavril]

(37)
BUG. The "Invert Pan", "Invert Tilt" and "Swap Pan/Tilt" options do not work (ssl2 file attached - just remove the dummy zip extension).
In DVC3, the fixture changes its initial pan/tilt position in realtime when the options are set in Patch and all DMX commands are inverted according to the parameters.
Nothing in Daslight4.

[Jp]

Hi

32) is normal I think. The release at end option allows a scene to keep it's last state until the user completely stops it.
33) I'll see what I can do
34) if you click on the text displaying the level, it might work (you can edit the value as well )
35) i'll see what I can do as well
37) I'll speak to the concerned dev

[PolDavril]

Hi Jp,

Thanks.

(32 cont'd) Yes, I agree that the "Release at end", when deselected, allows the scene to keep its latest state but, actually, it does not work. Obviously, all DMX parameters are reset before the scene button gets into pause mode. The scene must be set to pause mode before sending the "zero" values (just as if the scene was paused manually).

(34 cont'd) Yes, the fader position can be changed by clicking on its text value but it does not set the focus to the fader. That means that, after a new value has been entered with digits, the keyboard arrow keys do not operate.

[PolDavril]

(38)
IMPROVEMENT. When no fixture is selected, the preset pop-up above the fader should not be displayed when right-clicking. Whatever the preset selected, it won't be taken into account, as the faders are inactive...

[PolDavril]

(32 cont'd)
BUG. About the "Release at end" option. See the attached show file (just remove the dummy ".zip" extension).
Additional issue : when SCENE1 has Fade in/out parameters, when it reaches its end, it waits and the bug #1 happens (the DMX parameters must not be reset but they are).
In that case (when scene fades=yes), there is a second bug : when clicking on SCENE1 button again to release it manually, it still waits... The play button has to be clicked for the final release occur. That's not logical because the play button is meant to replay the group for the beginning, not to release a scene.
If SCENE2 is clicked, SCENE1 does not release either, although all scenes are set to Release=Group...

[PolDavril]

(39)
BUG or not ? The BPM detection does not seem to work fine. I have tested it with some drum loops at different tempos, sending the sound directly to the sound card.
Here are the files in a zip.
www.poldavril.be/pldvrl/temp/TEST_Daslight_BPM.zip
When there is no sound, it defaults to 132 and, every 10 seconds or so, it resets to zero, goes back to 132 and so on. Is this intentional ? When there is no sound, I guess that the BMP should stay at zero, for the scenes stop triggering.
When playing one of the drum loops, the BPM value does not update. When the BMP is 80, Daslight stays around 130, when 90 it goes to 150, when 100 to 150-160.
When the audio tempo changes, the BPM does not seem to be updated in realtime. Is that intentional ?

[PolDavril]

(40)
BUG. As already reported by another user for Mac, if a filename contains a dot (other than that of the extension), only the characters before the first dot are displayed in the title bar.
This issue occurs in Windows version too.
Example: The file "Test.Beta9.11.DotInFilename.dvc" is displayed as "Test".
It should be "Test.Beta9.11.DotInFilename".

[PolDavril]

(41)
BUG. In Palette, Color. Each time the fixture tab is selected, the Fan option is enabled, although it's in classic mode. When the mode is set to Advanced and to Classic again, the Fan option becomes deactivated.
Obviously, the Fan option works in Advanced mode only, so it has to be deactivated when in Classic mode. It seems that an init is missing for the Fan option, depending on the current Classic/Advanced mode, each time the fixture tab is clicked.
The same issue in General tab.

[PolDavril]

(42)
BUG. In Palette, Color with Fan. Under some circumstances, when the fan section is turned or resized, fixtures turn to strange and unwanted colors. They do not stay as a color gradient.
*EDIT*: According to the tests, it happens when there is a single color selected in the outer ring and not a color range.

[PolDavril]

(43)
BUG. In Palette, Color with Fan. When "Linear fan from center" or "Linear fan from sides" is selected, the color symmetry is lost with an even number of fixtures. In this case, the two center beams (numbers 4 & 5) should be processed together as a pair for the color symmetry be kept.

[PolDavril]

(44)
BUG. Display problem in Palette, Color. When the color wheel is in Classic mode, the contextual menu HSV/RGB should not popup with a right-click, because this option impacts the Advanced mode only.

[PolDavril]

(45)
BUG. A right-click on the fan options icon should not trigger the fan contextual menu (only a left-click should do it).
The reason is that, after a fan option has been clicked, an unwanted DMX/MIDI mapping menu is automatically displayed.

[PolDavril]

(46)
BUG. In Palette, Fader control. When a fan option is active, a second fader appears but it seems to be useless, as the normal fader does the job.
Furthermore, when this second fader appears, the control becomes wider but it's impossible to resize the palette panel to the right.

**EDIT May 06, 2016** : It's OK with the faders : the first one controls the start value, the second one controls the end value.
However, the resize problem remains.

[PolDavril]

(47)
BUG. In Palette, control fader with Fan option. Just as in the color wheel, with an even number of fixtures, the symmetry of the gradient is lost when "from center" or "from sides" is selected.
The two center fixtures should be processed together as a pair in order to keep the symmetry.