Q Light Controller+

Sourceforge ate my posting - grr! Thanks for the brilliant work on the latest beta. Here are some observations (Ubuntu).

1) Removing a sequence from a scene removes the scene as well (that may have happened before)
2) Pressing the next or previous step buttons puts the cue list into play mode. This is particularly alarming if the durations are set to zero as it spins round at high speed (as per the warning on the help page). It may have done this before but I don't remember it doing so

Thank you for the crossfade sliders! They're looking very promising, but have some problems.

3) The sliders only cause a jump to the next scene if they're linked
4) Moving the linked sliders away from the end stop and then back to the same end stop causes a jump to the next scene - I don't think it should progress until the sliders have been brought to the other end stop
5) I don't think the cue list should wrap when using the sliders - I don't know if this happens with physical consoles though
6) The external input for the right hand slider needs to be inverted - pushing the physical slider up moves the on-screen slider down
7) There is no feedback from the crossfade sliders (to a BCF2000)
8) It would be good if the sliders moved when doing timed transitions
9) Rather than talking about "primary" and "secondary" sliders, would it be more intuitive to talk about "current" and "next" steps?
10) The field widths for the fader values aren't quite wide enough, so the widget gets wider when a fader shows "100%"
11) The crossfade properties tab of the cue list has an Auto Detect button for each slider. I suggest toggling one "on" should toggle the other "off" or you tend to teach one slider and then overwrite it when you teach the second
12) The crossfade sliders move in design mode - ordinary sliders don't

Hello Matthew, thank you very much for your detailed report !
I'll start looking at them one by one soon.
For now, my quick replies:
6) you're right
7) totally forgotten to add it !
10) trivial to solve
11) good point
12) the idea here was to allow a "start" intensity before playing the Cue, but I guess it could be done in Operate mode only

Some more info here.

3) how should they behave when they're not linked ?
5) Opinions. Some might like it wrapping around, some others not. For now I'd just leave it as it has always been
6) I've inverted the "next step" slider. (pushed on GIT) Now it should look more natural against an external controller
7) I've added the feedback code. If I push it online, can you test it within today and give me a feedback ?
10) Should be solved now. Can you please double check ?
11) I've improved it a bit but I'm still not happy
12) I checked this and cue list sliders are disabled in design mode. How did you manage to move them ? With the BCF2000 ?

Wow - many thanks!

3) I suppose they should change scene when both faders hit the end stop. Otherwise, you'd get a jump in levels when the scene changes.
5) I agree that's not a major issue, but I think wrapping is more appropriate for a repeated sequence than a programmed show, which has a definite start and finish. Certainly the wrapping should remain as an option. Let's see if anyone else has thoughts on this.
7) I could test from the git repository but a .deb would be easier and I should be able to do that tonight.
10) Will do.
11) Will look.
12) Yes, I think I must have done.

Unfortunately I cannot build a deb and share it publicly, otherwise it would become a new release and I should build also the windows and OSX versions.
Result: a mess.

If you contact me on my email address I can try to provide a dropbox link with a deb just for you. No promises though.
By the way, 32 or 64 bit ?

Just back from holiday so I haven't had time to check much, but it looks like some great work has been done! So, just a few opinions to throw into the discussion so far.

3) and 4) The sliders should operate in the same way linked or unlinked (except, obviously, linked sliders have to move together). Nothing moves on in the chaser until the moment when both sliders are at the opposite end of their travel. See further details here:

https://sourceforge.net/p/qlcplus/discu ... 0d36/#3b6b

5) I can't see a good reason for the chaser not to wrap around – the more things that work the same, the better. Put a blackout scene at the end of the chaser to avoid wrapping around accidently.

8) Would be good, but if the transition is between collections, one function in the collection would have to be nominated to have its timings monitored.

9) "Current" and "next" is much clearer.

10) Something funny seems to have happened to fader widths in channels groups and the simple desk as well, causing them to be too narrow for values and labels set up in 4.3.3. (Ubuntu 12.04). Don't know if this is related.

Good then, cause 1,3,6,7,10,11,12 are fixed and online now
I have to write some more code for the audio input part and then I think I can release a beta2 or a stable one.