Shows - some bugs

[Federico Reghenzani]

Hi Guys!

I've started to use shows in QLC+, but I found some bugs that make it hard to use. Each bug is reproducible on Linux x64 and Windows 7 64bit so I think they aren't platform-dependent.

**1. [SHOW] Crash on add music to show**
*Description*: QLC Crash
*Steps to Reproduce*: Create a new show, add music file via toolbar without creating a scene. (If you create a scene before, it works correctly)

**2. [SHOW] Show overlapping problem**
*Description*: Add files/scenes overlapping some other is not permitted but dragging with the mouse, overlapping is allowed.
*Steps to Reproduce*: e.g. adding a scene from 00:00 to 20:00, set the cursor to 10:00, try to add music file: is not allowed due to overlapping. Insert the music file at 30:00 and drag it to 00:00: is allowed.

**3. [ALL] Timing problem**
*Description*: Fade in/Fade out/Hold fields (in show, in chaser funtion, etc.) accept only this format: xxs.xx.
*Accepted examples*:
- 02s.10
- .50

*Rejected examples and qlc sets to zero (should be accepted...)*:
- 02s
- 1m2s.20
- 1m.20

(Maybe you could use the QTimeEdit widget?)

**4. [SEQUENCES] Sequences edit the function values**
*Description*: I don't know if this is a bug, but when executing a sequence, the relative function changes "main" value.
*Steps to reproduce*: add a function and set to 255 one channel, next create a sequence with one or more steps with value 100 for that channel. If you start the sequence, function takes the value 100 and does no reset to 255 at the end (or at the stop) of the sequence.

**5. [VIRTUAL CONSOLE] QLC freeze, multiple buttons.**
*Description*: Press multiple buttons linked to shows cause the freeze of QLC (but the music still working!).
*Steps to reproduce*: create 2 shows, assign them to two buttons, press both button.

**6. [GENERAL] Resume after suspend PC cause (very big) memory leak in QLC.**
*Description*: as title, only on linux. QLC freezed.

**7. [SHOW] Random values in light**
*Description*: "Sometimes" when programming sequences via show section, QLC stops to assign correct value to channel: for example, I insert 200 200 200, deselect-reselect that step, the values are 100 100 100 :S. I'm sorry can not be more accurate about this bug

**8. [VIRTUAL CONSOLE] Feature request**
Probably for show and music buttons can be useful to have a progress bar on the buttons or nearby.



QLC Version: 4.4.1, I'm going to retest this bug in 4.5.0
In the future when I'll have time, I'll to try to help you patching these problems

[Massimo Callegari]

1. The reproduction steps are wrong. You are not allowed to add audio without a track. The toolbar icon is disabled. Please write the exact steps.

2. Reproduced. Gonna think a way to fix it

3. "Accept only" statement is not true. If you write a number without any letter it takes as seconds. For the other cases I can evaluate an improvement

4. I think it's the correct behaviour. Scenes in Shows are used as "temporary" values holder. So I guess you always have the last values set

5. Do your shows have both audio tracks ? Cause multiple audio playback is not supported

6. I ONLY use Linux and it doesn't happen to me. Please detail this finding

In general, the word "problem" is an opinion. What is a problem for you might not be a problem for others. I would think twice before using it

[Federico Reghenzani]

Thank you for reply Massimo

1- Toolbar icon is disabled only for the first show, from second show remains enabled (attachment). (Create a show, add a track, create another show, add music)

3- Ok, I had not seen this behavior, but I think is a little counterintuitive

5- Yes, the problem appears when both shows have audio tracks.

6- I'm not sure how to test this, however I'll try it on another linux machine.


My "problem" words didn't want be a polemic, rather, I write here to try to enhance a tool that I find wonderful

[Massimo Callegari]

OK, #1 fixed

3. Point of views

5. In the end I think I have to add a "big popup of death" to inform people that multiple audio is not supported. It's written in the documentation but I think nobody reads it.