Q Light Controller+

Hi.

1) On the music track, if displayed once, visualisation of audio disappears when u come back after visiting an other section like functions.

2) It could be usefull to allow user to set the measures 0 starting point after, or before the begin of the wav file.

3) Precision between mp3 / wav files is so big that it could be usefull too to not allow mp3 import, or implement a warning.

4) For all tracks (particulary on music one), a lock button would be welcome, that allow to move cursor without editing track.

5) On timeline, allowing to set labelled markers should be usefull, and...

6) ...Displaying Grid enables grid magnetism. I suggest to split that with 2 separate buttons. 1 for grid, an other for magnetism (grid and markers if implemented).

7) Timeline again, i used a bpm detector for my stuff... i obtain values around 128.97 or something like that. Is this possible to allow decimals to the bpm selector ? Integrated detector ?

8) A great great thing wold be to have the opportunity to set EVEN the steps durations with measures unity.

9) Displaying grid allows to click on an empty track space to set the cursor on timeline. Function disabled when grid is hidden...

10) Timeline should always be visible, as the zoom tool (even the track graphic may be).

11) I suggest to drastically improve zoom level for help in small (fast) adjustments.

12) When navigating ahead on show, names of tracks and functions Mute/Solo are no longer visibles. I suggest to make them smaller, but visibles.

13) Navigation with alt + mouse wheel is usefull, as the vertical navigation with mouse wheel only. I suggest a zoom with Ctrl + mouse wheel based on the position of the pointer.

14) I don't know the best way to programming sequences and i use chases power as longer as i can. Setting a colour on a chaser sets it for the entire chaser. it could be cool to allow to set colour for steps (and secondarily for a better display of the in/out).

15) Repetitive and fast moves in chasers, for obtain perfect synchro are not so easy (especially with seconds fractions). In the steps list for a chaser, is this possible to implement a "checkbox system" to set same values for selected steps (i know it's possible for all steps, but choosen ones) ?

16) EFX in tracks ?

17) Contextual functions on tracks are up, down and rename. Why not delete ?

I had some bugs and crashes up to there but i can't say how for now. I saw that select numerous times a chaser without unselect the other can occur some problems in the long run. I will study that soon.

Excellent job guys.

Thx a lot and Good Luck !

I am also struggling with precision. I find if I start the sound clip anywhere except from the start the light events to not trigger at the same instant of the music as when I run from the start. One tends to program to music events when selecting a piece of track then setting the lights and then playing just that part again.

Now when I run it from the start some tracks are like maybe a half second out.

My suggested solution for this would be to optionally set a time to start value. This will allow me to set a lot of scenes to start at 2s.18s.74 - that way you re-align the track at runtime.

Oamze, I've edited your post and numbered all your suggestions otherwise it would be impossible to answer them.

1) is a known behaviour. I'll see if there's a smart solution
2) don't understand
3) for precision use Wave files. Unfortunately precision doesn't depend on QLC+, as audio decoding is performed by third party libraries (libmad and linsndfile)
No way to remove mp3 support

4) I agree. Never found the time to implement it but I will
5) More datails please
6) In Cubase they're a single funcionality too. Why having a grid without the possibility to perfectly align an item to it ?

7) Might be possible but I'm not sure about the final precision anyway. In my opinion, for electronic music, 128,97 bpm is 129 bpm.

8) don't understand
9) don't understand
10) if you use a lot of tracks, yes I agree. Same thing for the track list on the left (12)
11) Ok
13) I need to try this one
14) don't understand
15) I need to think about this. Not so easy to implement
16) EFX are timed loops. Shows go only forward in time. I implemented a similar thing in RGB Matrices to export a Matrix as a Sequence. I might think of doing the same for EFX but it's not the same thing as EFXs are not step-based
17) Ok, this can be added

Ok. Some pictures instead of my perfect english
1) Ok fine.
2) on exp1.jpg
3) Ok
4) Ok
5) on exp1.jpg
6) Ok. I was thinking grid as graphic help first, then magnet tool incidentally, as photoshop.
7) 128.97 works fine with 129 preset. U're right.
8) on exp.jpg
9) on click.jpg
10) yes i made 1 track by type of fixture
11) 12) 13) Ok
14) on exp1.jpg
15) Unfortunately, i can't help.
16) I see.
17) fine !

Thanks for patience ^^

Number 9 and 17 implemented.

I still don't understand number 2, sorry.

Number 8 is VERY tough to implement

About number 14...it would be nice for RGB fixtures. But what about non-RGB ones ? When changing something in QLC+ I always have to keep in mind the plethora of different products out there and most of them are still non-RGB.
In any case implementing such feature would require a dramatic change to the code

Number 4 implemented