Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.18
edited by Alexander Mott
on 2023/05/05 19:09
Change comment: (Autosaved)
To version 1.13
edited by Alexander Mott
on 2023/05/05 18:44
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -12,24 +12,11 @@
12 12  
13 13  When creating a Pharos project for a ShowRunner™ installation, there are several things to consider:
14 14  
15 -* Individual loads defined in ShowRunner™ send commands to individual Fixture Groups in Pharos
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
31 -* If it is desired to control the white channel separately from the RGB channels of an RGBW fixture, then it must be defined in the Pharos project as two separate RGB and W fixtures that are grouped separately and defined separately in ShowRunner™
32 -* Fixtures can belong to multiple Fixture Groups, allowing ShowRunner™ to send different types of command (e.g. RGB vs CCT) to the same fixture 
15 +* The Pharos API limits commands to single-channel (intensity), RGB, and intensity/CCT
16 +* ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos
17 +* Fixture Groups defined as single-channel loads in ShowRunner™
18 +* For RGBW fixtures, it may be a good idea to define them as separate RGB and W fixtures so that ShowRunner™ is able to control the white channel separately from the RGB channels
19 +* Fixtures can belong to multiple Fixture Groups, allowing ShowRunner™ to send different types (e.g. RGB vs CCT) of command to the same fixture 
33 33  ** Useful for certain situations, such as HSIC fixtures that need to be controlled as color-changing (RGB) in some situations but dynamic white (intensity/CCT) in others
34 34  
35 35  The basic steps for creating a Pharos Project for use with ShowRunner™ are:
... ... @@ -58,6 +58,7 @@
58 58  1.
59 59  1. adsf
60 60  
48 +
61 61  Note: Due to limitations with the API, only single channel, RGB, or Intensity/CCT load types can be defined in ShowRunner™. Other fixture types are controllable, but the types of command that ShowRunner™
62 62  
63 63  = Device Configuration =