Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.47
edited by Alexander Mott
on 2023/05/05 21:40
Change comment: (Autosaved)
To version 3.1
edited by Alexander Mott
on 2023/05/05 21:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,20 +14,10 @@
14 14  
15 15  * Individual loads defined in ShowRunner™ send commands to individual Fixture Groups in Pharos
16 16  * Scenes in ShowRunner™ can be mapped in order to trigger Timelines in Pharos
17 -* The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT(% class="row" %)
18 -(((
19 -(% class="col-xs-8" %)
20 -(((
21 -(% class="table-condensed" %)
22 -|(% style="width:244px" %)**ShowRunner™ Load Type**|(% style="width:244px" %)**Pharos API Command**
23 -|(% style="width:244px" %)Single-Channel|(% style="width:244px" %)Intensity
24 -|(% style="width:244px" %)RGB|(% style="width:244px" %)Intensity/RGB
25 -|(% style="width:244px" %)Dynamic White|(% style="width:244px" %)Intensity/CCT
26 -)))
27 -)))
28 -* The Pharos controller does any necessary processing to adapt these commands for the fixtures
29 -** For example, if Pharos receives an RGB command for a group containing RGB, HSI, and HSIC fixtures, it will do its best to make sure that the output color is consistent across all the different fixture types
30 -** Certain manufacturer-specific fixture Profiles exist in order to help the Pharos controller achieve a consistent output across multiple different fixture types
17 +* The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT
18 +** Other fixture profiles are still supported: the Pharos controller will do any necessary processing to adapt the commands to the fixtures
19 +*** For example, if Pharos receives an RGB command for a group containing RGB, HSI, and HSIC fixtures, it will mix the DMX channels to achieve a consistent color output across all the different fixture types
20 +*** Certain manufacturer-specific fixture Profiles exist in order to help the Pharos controller achieve a consistent output across multiple different fixture types
31 31  * To control the RGB and white channels of an RGBW fixture separately in ShowRunner™, it is necessary to define separate RGB and White fixtures in the Pharos project 
32 32  ** Add both a generic RGB fixture and a generic White fixture to the layout
33 33  ** Assign each fixture to a different group
... ... @@ -158,7 +158,9 @@
158 158  
159 159  Some things to consider if you are triggering Pharos Timelines with ShowRunner™:
160 160  
161 -* Pharos Fixture Groups do not need to be defined in ShowRunner™ if Timelines are the only intended means of controlling the DMX fixtures
162 -* ShowRunner™ will still execute a scene recall even if the scene is mapped to a Pharos Timeline
163 -** Non-DMX loads in an area with Scene tracking configured will still go to their scene levels
151 +* If Scene Tracking is configured for a ShowRunner™ Area, the Pharos Timeline will be triggered regardless of whether any loads are assigned to the Area
152 +* Scene recalls are still executed even if Scene Tracking is enabled
153 +** Non-DMX loads in an area with Scene Tracking will still go to their predefined scene levels unless they are excluded from the scene
154 +** Pharos DMX loads will go to their predefined scene levels unless they are excluded from the scene, even if they are included in the Pharos Timeline being triggered
155 +* If Timelines are being used to control DMX fixtures, then the Fixture Groups do not actually need to be defined in ShowRunner™ unless direct control of the Fixture Groups is desired
164 164  )))