Changes for page Pharos Configuration
Last modified by Alexander Mott on 2024/02/26 15:10
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -12,28 +12,37 @@ 12 12 13 13 When creating a Pharos project for a ShowRunner™ installation, there are several things to consider: 14 14 15 -* Individual loads definedinShowRunner™ send commands toindividualFixture Groups in Pharos16 -* Scenes in ShowRunner™ can be ma ppedin orderto trigger Timelines in Pharos17 -* The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT(% class="row" %)18 -((( 15 +* Individual loads in ShowRunner™ send group-level commands to Fixture Groups in Pharos 16 +* Scene recalls in ShowRunner™ can be made to trigger Timelines in Pharos 17 +* ((( 18 +The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT* ((( 19 19 (% class="col-xs-8" %) 20 20 ((( 21 21 (% class="table-condensed" %) 22 -|(% style="width:244px" %) **ShowRunner™ Load Type**|(% style="width:244px" %)**Pharos API Command**22 +|(% style="width:244px" %)ShowRunner™ Load Type|(% style="width:244px" %)Pharos API Command 23 23 |(% style="width:244px" %)Single-Channel|(% style="width:244px" %)Intensity 24 24 |(% style="width:244px" %)RGB|(% style="width:244px" %)Intensity/RGB 25 25 |(% style="width:244px" %)Dynamic White|(% style="width:244px" %)Intensity/CCT 26 26 ))) 27 + 28 +(% class="row" %) 29 +((( 30 + 27 27 ))) 32 +))) 33 +))) 28 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 in different groups 32 -* Individual Fixtures can belong to multiple Fixture Groups, allowing ShowRunner™ to send different types of command (e.g. RGB vs CCT) to the same fixture 35 +** For example, 36 + 37 +* 38 + 39 +* ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos 40 +* Fixture Groups defined as single-channel loads in ShowRunner™ 41 +* 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 42 +* 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 -** In this scenario, one group would be defined in ShowRunner™ as an RGB load and one group would be defined as a Dynamic White load 35 35 36 -The basic steps for creating a Pharos Project for use with ShowRunner™ are as follows:45 +The basic steps for creating a Pharos Project for use with ShowRunner™ are: 37 37 38 38 1. Open the Pharos Designer 2 software 39 39 1. In the top-right, click "New Project" and select the type of Pharos controller that will be the primary controller ... ... @@ -47,22 +47,17 @@ 47 47 1. At the top left, click "Manage..." to edit the layout name and dimensions, modify grid settings, and upload a background image if desired 48 48 1. Locate the desired fixture in the Fixture Profile List on the right side of the Layout page 49 49 1*. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles 59 +1*. Pharos also has a large selection of manufacturer-specific profiles which can be used instead of the generics 50 50 1*. Additional generic and manufacturer-specific profiles can be downloaded by clicking the cloud icon on the right, above the fixture profile list 51 51 1. Add fixtures to the layout by dragging them from the fixture profile list 52 52 1*. Every fixture that is added to the layout represents a unique set of DMX addresses 53 53 1*. The fixture number is different than the fixture address, and is automatically incremented by Pharos Designer 2 54 -1*. Fixture properties such as name, shape, and size can be edited using the menu on the right64 +1*. Fixture properties such as name, shape, and size can be edited 55 55 1*. Right-clicking a fixture on the layout will allow you to either "Duplicate" or create a "New Instance" of a fixture 56 56 1**. Duplicating a fixture creates a new fixture with the same profile and properties but that will occupy different DMX addresses 57 57 1**. Creating a New Instance will create a new representation of the fixture without actually creating a new fixture; this allows you to have multiple fixtures represented on the layout that share the same DMX address 58 -1. Create Fixture Groups by clicking the folder icon above the list of fixtures on the left or by right clicking an empty area in the fixture list 59 -1*. Fixture Groups will correspond to individual loads in ShowRunner™ 60 -1*. When a new Fixture Group is created, all currently selected fixtures are automatically added to the group 61 -1**. Clicking a fixture on the layout or in the fixture list will select just that fixture 62 -1**. Ctrl-clicking a fixture will add or remove it from the current selection 63 -1**. Ctrl-dragging on the layout will add multiple fixtures to the current selection 64 -1**. Shift-dragging on the layout will select just the highlighted fixtures 65 -1. Creating a new group will au 68 +1. 69 +1. adsf 66 66 67 67 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™ 68 68 ... ... @@ -70,7 +70,6 @@ 70 70 71 71 = ShowRunner™ Configuration = 72 72 73 -no feedback from dmx 74 74 75 75 76 76 )))