Add Maintenance Channel and Capabilities

Report an issue that you found while using QLC+ 5.x.
Please provide as many details as you can, a sample workspace if available and don't forget to read the forum posting guidelines first !
Post Reply
rayconsole
Posts: 27
Joined: Tue May 21, 2019 9:35 am
Real Name:

Currently there is no Maintenance preset in qlcchannel.h and no related capabilities in qlccapability.h. We have done some research into the maintenance functions used by fixture manufacturers and have created an initial list of functions. We propose to implement the following functions as described in https://github.com/mcallegari/qlcplus/w ... on-presets

In qlcchannel.h we will add the following presets:

Maintenance

In qlccapability.h we will add the following presets:

LampOn
LampOff
ResetAll
ResetPanTilt
ResetPan
ResetTilt
ResetMotors
ResetGobo
ResetColor
ResetCMY
ResetCTO
ResetEffects
ResetPrism
ResetBlades
ResetIris
ResetFrost
ResetZoom
SilentModeOn
SilentModeOff
SilentModeAutomatic

Have we missed any presets or are there any presets in the list above that are not needed?
Kind regards,
Ray Console Team
Ray Console. The robust lighting control console with a modularly extendible software that is intuitively usable for amateur users. The console uses the QXF fixture format used by QLC+ and will be ready to order in spring 2020. rayconsole.com
Top
User avatar
mcallegari
Posts: 4710
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:
Contact mcallegari

Well, capability presets were initially introduced to define behaviors visible in previews (2D/3D)
Maintainance is irrelevant in that sense and what you're proposing is surely an incomplete list of presets (each manufacturer does what they want on maintainance channels)
For example, resetting tilt makes sense in the real world, but not in a simulated preview, which doesn't suffer from mechanics issues.

So, to be honest I don't see a reason to introduce such presets, and then review 1100+ fixtures once again.
Otherwise, please explain the cases where the effort justifies a QLC+ improvement
Top
rayconsole
Posts: 27
Joined: Tue May 21, 2019 9:35 am
Real Name:

The old QXF structure only uses groups and then lets the user enter whatever name they like. This is very simple but also very restrictive. Because users can name functions as they like it is impossible to create features that act on all fixtures. For example if you are controlling a system via ArtNet with hanging lamps. To get any intensity output you have to set the DMX for each individual fixture by searching through the user defined name for lamp on. If there was a preset it would be possible to just have one button to turn the lamp in every fixture or off in every fixture. Furthermore, with a preset for lamp on, it would be able give the user some kind of feedback if they try and set an intensity before having turned the lamp on.

These are functions that you may find quite valuable in the future. We wish to implement them now in Ray Console. We would undertake the initial review of fixtures (we are doing this anyway for shutter and strobe presets).
Ray Console. The robust lighting control console with a modularly extendible software that is intuitively usable for amateur users. The console uses the QXF fixture format used by QLC+ and will be ready to order in spring 2020. rayconsole.com
Top
rayconsole
Posts: 27
Joined: Tue May 21, 2019 9:35 am
Real Name:

Are there any more comments? If not we will prepare the changes for review on Github.
Ray Console. The robust lighting control console with a modularly extendible software that is intuitively usable for amateur users. The console uses the QXF fixture format used by QLC+ and will be ready to order in spring 2020. rayconsole.com
Top
User avatar
mcallegari
Posts: 4710
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:
Contact mcallegari

ok, then please insert the new ones between PrismEffectOff and Alias.
thanks
Top
Post Reply

Return to “QLC+ 5 Issue reports”