Prevent the grabber from beeing B in Composed views

[derpeter]

We had some talks at 33c3 (e.g. LoraWAN) where the operator often selected B for the slides an A for the CAM. I cant think of scenario where this makes sense. At least we should think of a config option that disables the Slides for beeing selected for B.

[CarlFK]

1. Sometimes the font is large enough. like "YES!" "Questions?" simple phrases "we can do better..."

2. I like putting stale (not updated in a while) slides in B. This gives the viewer reassurance that they haven't changed. A great example is during Q&A when the presenter is obviously operating their laptop but the projector still says "Q&A" - it is nice to know there really is nothing to see.

[benjaminwand]

+1 @CarlFK , also it is super annoying when you click a and the computer does b.

I think that most of the dumb cases of slides in b happen because of voctomix switching channels and then the mixer-angel 'goes back' and doesn't understand what is happening. Switching channels is another patronizing case of you click a and computer does not not-a.

[MaZderMind]

We currently make it really hard to do this, but I would not want to stop people from doing it. but I can see situations where it might be useful, for example:

• Single-Word Slide which the Speaker refers to
• Document-Camera on Slide-Input
• On-Stage-Camera on Slide-Input

I would rather not "prevent" it from happening but work more on explaining the mixer angles why this is discouraged, as we do already when we do angel trainings.

[fightling]

Because composites can be described by strings in voctomix 2 white and black listing would be quite easy to implement.

[fightling]

With VOC2MIX you already can remove the slides from the buttons in the toolbar.sources.b:

[toolbar.sources.a]
buttons = cam1, cam2, cam3, slides

[toolbar.sources.b]
buttons = cam1, cam2, cam3

Now slides can't be set for channel B anymore:

(see documentation)