Q Light Controller+

It's been a while since I've posted anything but that doesn't mean I haven't been accumulating a few thoughts and experiences with QLC+:

Some of these may have been noted before and perhaps some have not.

-- I have noticed that when Channel groups are added, they do not show in simple desk until restart

-- I still find that the RGB matrix editor is the area that is most prone to crashing the program. I've very much gotten in the habit of saving my project before doing anything with the RGB matrix editor.

-- I experimented with the web access and I know it's in the experimental stages, but it does seem to be quite slow and buggy for me. Solo frames don't always seem to work, the layout is not consistent with what QLC displays, and I've even experienced the buttons triggering different things than they should. I was experimenting with using an iPad to run QLC instead of a touchscreen monitor, but it's very clear that this isn't going to be feasible for a bit (which is fine, I certainly understand that there is a lot of work that it takes to make this happen). Not complaining, just providing feedback.

And now a few suggestions.

-- It would be nice to have a way to release overridden channels (from the simple desk) with a fade (gradually) kind of like how the stop all functions button has selectable fade times. I use the simple desk a lot, but if I make changes that will be very noticeable, I'm always a little hesitant to release the simple desk.


-- I know this sounds like a little bit of an out-there request, but it would be kind of awesome if I could store PDF manuals for lights in QLC. Of course, I can and do store them on my machine, but it would be really awesome if they were just in QLC. Even better would be if the manuals could be stored with the fixture definitions, but I'm sure that would present a big copyright issue.

-- Live editing is great. I love it and I use it almost every time I gig. One thing that would be even more awesome is if there were a way to edit the Virtual Console without having to completely black out the lights. For example, if the last scene could hold while editing the simple desk, it would be epic.

That's about it for now, time to get to work!

Hi

>-- I still find that the RGB matrix editor is the area that is most prone to crashing the program. I've very much gotten in the habit of saving my project before doing anything with the RGB matrix editor.

I use mostly RGB matrices, and the editor hasn't crashed on me for a long time.
Can you provide steps to reproduce a crash ? Or does it happen randomly ?

Unfortunately it's pretty random except to say that it generally seems to be tied to the animation of the matrix in the UI. That is to say that whenever I'm doing something and the animation is going, that's when I'm most likely to see a crash.

Just had the RGB matrix function crash now while doing Test Run and changing the pattern type.

OK thanks, I managed to reproduce a crash too.

EDIT - I think all crashes while in test run are fixed with this patch
https://github.com/mcallegari/qlcplus/pull/334


But it still crashes in live edit mode...
I'll look into it later.

Another small issue that I should mention, I continue to have issues with the interface when using a 1024x768 monitor. I don't always program on the machine that has a display with this resolution (it's a touchscreen), but when I do, I'm constantly clicking the resize window button...

This is probably due to the number of sliders and playback sliders in the simple desk configuration. See Manual Parameters Tuning under the advanced topic - left top.

Chris,

I believe you are correct, but I've actually done that before and now it's back. It's likely that I could probably fix it, but I'm more making the suggestion that perhaps there be a way to address this without this level of manual intervention...