Skip to Content

Changes for page Pharos Configuration

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

Summary

Details

Page properties
Content
... ... @@ -14,10 +14,20 @@
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
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
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
21 21  * 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 
22 22  ** Add both a generic RGB fixture and a generic White fixture to the layout
23 23  ** Assign each fixture to a different group
... ... @@ -103,7 +103,7 @@
103 103  
104 104  = ShowRunner™ Configuration =
105 105  
106 -ShowRunner™ is able to control fixtures in Pharos by sending group-level commands directly to Fixture Groups that are defined in the Pharos project, triggering Timelines that are defined in the Pharos project, or both. Note that ShowRunner™ does not receive feedback from the Pharos controller, so fixture feedback as shown in the ShowRunner™ UI is only accurate if ShowRunner™ sent group-level commands. Changes to fixture levels caused by a Timeline are not reflected in the ShowRunner™ UI. A video tutorial of setting up Pharos loads and configuring Scene Tracking is [[available on our YouTube channel>>https://www.youtube.com/watch?v=Y63C_vnATec&list=PLhxgcngAeiD_pCRxFDwX5eg0O56OjNdHf]].
116 +ShowRunner™ is able to control fixtures in Pharos by sending group-level commands directly to Fixture Groups that are defined in the Pharos project, triggering Timelines that are defined in the Pharos project, or both. Note that ShowRunner™ does not receive feedback from the Pharos controller, so fixture feedback as shown in the ShowRunner™ UI is only accurate if ShowRunner™ sent group-level commands. Changes to fixture levels caused by a Timeline are not reflected in the ShowRunner™ UI.
107 107  
108 108  In order to control DMX fixtures on a Pharos controller with ShowRunner™, it is necessary to make sure that the ShowRunner™ configuration has the correct settings for the Pharos controller. Under the "LightingControllers" section of the ShowRunner™ configuration, locate the entry for the Pharos controller. Under the "Properties" section, verify that the "IpAddressOrHostname" matches the IP address or hostname of the Pharos controller. The "ApiPort" only needs to be changed if the HTTP port for the Pharos controller's web server has been changed from the default 80. Once the Properties for all Pharos controllers have been updated, load the configuration to the processor.
109 109  
... ... @@ -148,9 +148,7 @@
148 148  
149 149  Some things to consider if you are triggering Pharos Timelines with ShowRunner™:
150 150  
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
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
156 156  )))