Add Zoom, Edge to Focus Palettes (as User Setting)

I would like Focus palettes to store Zoom and Edge information in it. I would like to see this as an option in User settings.

This would save me from having to use a macro for selective preset recording (and thus not using a hard key on the console) every time I want to store a position.

It makes little sense to just store pan and tilt info, because the zoom has an influence on the actual position; SL full body is a different position than SL head.

Also, the edge needs to change depending on where on stage your light hits, because of the change in distance.

I can imagine you do not want to break current workflows, but please make this into an option in settings.

Parents
  • Surely this completely breaks the premise of a 'focus' palette and is the exact use case for a preset?

  • I am not sure, since a preset stores every parameter, unless you type a lot or make a macro to exclude certain parameters. In my opinion, the size and edge belong to the focus of a light as it would when you focus a conventional. Can you imagine leaving the edge and zoom alone while focusing your conventionals?

  • Zoom and Edge also heavily affect beam params such as shutters, iris, gobos, animation. How will these be treated if zoom and edge are nested in focus palettes?
    Commonly, you don't use a light in a preset, or any palette, without giving it intensity but you don't record the intensity in the preset. So I don't really see the need for it here?
    I also assume that you use lots of Macro in your programming, so Macros are already part of your workflow, and therefor aren't really the problem here?

Comment
  • Zoom and Edge also heavily affect beam params such as shutters, iris, gobos, animation. How will these be treated if zoom and edge are nested in focus palettes?
    Commonly, you don't use a light in a preset, or any palette, without giving it intensity but you don't record the intensity in the preset. So I don't really see the need for it here?
    I also assume that you use lots of Macro in your programming, so Macros are already part of your workflow, and therefor aren't really the problem here?

Children
No Data