[fixed 2.1] Fader output max.
#14
(10-09-2021, 10:37 PM)PragmaLab Wrote: The issue with that the Cuelist itself does not know anything about faders or executors - it only knows it’s own values.

I really, really do not understand your issue. The whole idea is that a cuelist stores tons of values for all kind of channels, but the intensity channels (dimmer)  are overruled by the fader that controls the intensity.That's the whole and main purpose of a sub fader isn't it?

As I explained above the fader-level for the dimmer is stored in the cuelist itself (this is not the value of the dimmer attribute of a fixture, but rather the value you set with a fader). Adding a default 0% option is easy, but this also means that a cuelist assigned to an executor button will have its internal "fader" dimmer value set to 0%, hence it will not output anything.

(10-09-2021, 10:37 PM)PragmaLab Wrote: This has indeed been a design choice at the beginning and as it turns out a rather bad one (especially in this specific case) and I am not sure wether we’ll ever be able to change that in the current generation of consoles.

what exactly is it your are telling me after 4 years waiting for this issue to be addressed? That the design choice is indeed really bad I already knew. But of course this can be addressed, if you can set the default to 100%, you can also set the default to 0% for sub faders as used in cuelists. The chimp is the only console that has this flaw, I've never encountered it in any other console
I already outlined the implications that a change like this has on cuelists assigned to executors (or magic sheet) in this thread and the issue itself is far bigger and work intense than just changing the default value.

(10-09-2021, 10:37 PM)PragmaLab Wrote: I‘ll discuss that internally with the developers, but obviously I can’t make any promises.

Not asking for promises, I'm asking for fixing bad design choices as a service to users of your consoles. Great all these 'wizard sheets' and new features that were introduced during the last four years. Decent submaster behaviour should be priority imho

I really understand your frustration concerning this issue, but to be fair (as it is a fundamental issue in the code base; as explained above). I agree, decent Submaster behaviour should be a priority, but so should be fixing many other bugs (some of them which are affecting far more users)

The way to address this would be to move all sub-fader settings and cuelist state itself to the faders / executors making them far more than just a "remote control" of a fader, as then the fader is basically being played back rather then the cuelist. Afaik, this change means rewriting about 80% of the consoles core and structure, and thus I do not see it happening for the current generation of consoles.
Reply



Messages In This Thread
[fixed 2.1] Fader output max. - by Hans - 17-11-2017, 09:35 AM
RE: Fader output max. - by WesleyHouben - 28-11-2017, 12:38 PM
RE: Fader output max. - by Hans - 28-11-2017, 10:25 PM
RE: Fader output max. - by Angelo - 15-12-2017, 01:06 PM
RE: Fader output max. - by PragmaLab - 16-01-2018, 05:58 PM
RE: Fader output max. - by denishessberger - 11-09-2020, 01:42 PM
RE: Fader output max. - by PragmaLab - 08-11-2020, 03:51 PM
RE: Fader output max. - by denishessberger - 09-11-2020, 02:33 PM
RE: Fader output max. - by PragmaLab - 04-09-2021, 08:46 PM
RE: Fader output max. - by denishessberger - 08-09-2021, 02:28 PM
RE: Fader output max. - by PragmaLab - 10-09-2021, 08:44 PM
RE: Fader output max. - by denishessberger - 10-09-2021, 09:16 PM
RE: Fader output max. - by PragmaLab - 10-09-2021, 10:37 PM
RE: Fader output max. - by denishessberger - 29-09-2021, 12:47 PM
RE: Fader output max. - by denishessberger - 04-04-2022, 10:50 PM
RE: Fader output max. - by PragmaLab - 24-06-2022, 09:44 PM
RE: Fader output max. - by PragmaLab - 21-07-2023, 10:08 PM

Forum Jump:


Users browsing this thread:
1 Guest(s)