You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[RFC6763, DNS-Based Service Discovery](https://www.ietf.org/rfc/rfc6763.txt)
36
+
-[ANSI E1.37-5 – 2024 General Purpose Messages for E1.20 RDM](https://tsp.esta.org/tsp/documents/docs/ANSI%20E1.37-5%20-%202024.pdf)
36
37
37
38
38
39
# Terms and definitions
@@ -408,6 +409,7 @@ The child list (Table 20) contains a list of one of the following nodes:
408
409
| CustomId | 0 or 1 |[Integer](#user-content-attrtype-integer)| The Custom ID is a value that can be used as a short name of the Fixture Instance. This does not have to be unique. The default value is 0. |
409
410
| CustomIdType | 0 or 1 |[Integer](#user-content-attrtype-integer)| Defines the CustomID Type this object belongs to. |
410
411
|[ChildList](#node-definition-childlist)| 0 or 1 | A list of graphic objects that are part of the layer. |
412
+
| Comment | 0 or 1 |[String](#user-content-attrtype-string)| Comments for this Objects. |
411
413
412
414
413
415
@@ -433,6 +435,7 @@ The child list (Table 22) contains a list of one of the following nodes:
433
435
|[Matrix](#node-definition-matrix)| 0 or 1 || The location and orientation of the object inside the parent coordinate system. |
434
436
|[Classing](#node-definition-class)| 0 or 1 |[UUID](#user-content-attrtype-uuid)| The Class the object belongs to. |
435
437
|[ChildList](#node-definition-childlist)| 0 or 1 || A list of graphic objects that are part of the group. |
438
+
| Comment | 0 or 1 |[String](#user-content-attrtype-string)| Comments for this Objects. |
436
439
437
440
438
441
### Node Definition: FocusPoint
@@ -457,6 +460,7 @@ The child list (Table 24) contains a list of one of the following nodes:
457
460
|[Matrix](#node-definition-matrix)| 0 or 1 || The location and orientation of the object inside the parent coordinate system. |
458
461
|[Classing](#node-definition-class)| 0 or 1 |[UUID](#user-content-attrtype-uuid)| The Class the object belongs to. |
459
462
|[Geometries](#node-definition-geometries)| 1 || A list of geometrical representation objects that are part of the object. |
463
+
| Comment | 0 or 1 |[String](#user-content-attrtype-string)| Comments for this Objects. |
460
464
461
465
462
466
### Node Definition: Fixture
@@ -505,6 +509,7 @@ The child list (Table 26) contains a list of one of the following nodes:
505
509
|[Mappings](#node-definition-mappings)| 0 or 1 || The container for Mappings for this fixture. |
506
510
|[Gobo](#node-definition-gobo)| 0 or 1 || The Gobo used for the fixture. The image resource must conform to the GDTF standard. |
507
511
|[ChildList](#node-definition-childlist)| 0 or 1 || A list of graphic objects that are part of the layer. |
512
+
| Comment | 0 or 1 |[String](#user-content-attrtype-string)| Comments for this Objects. |
508
513
509
514
Note: _The fixture has no `Geometries` node as geometry is defined in a GDTF file._
510
515
@@ -588,6 +593,7 @@ EXAMPLE An example of a node definition is shown below:
@@ -632,6 +638,7 @@ The child list (Table 28) contains a list of one of the following nodes:
632
638
| UnitNumber | 0 or 1 |[Integer](#user-content-attrtype-integer)| The identification of a fixture on its position. </b> Use this as an alternative numbering scheme if the planning and programming numbering is different. |
633
639
| CustomIdType | 0 or 1 |[Integer](#user-content-attrtype-integer)| Defines the CustomID Type this fixture belongs to. A Custom ID Type defines to which group of objects this objects belongs as an additional object identifier. The types for the custom ID Types are defined below. |
634
640
| CustomId | 0 or 1 |[Integer](#user-content-attrtype-integer)| The CustomId ID is an identifier for the instance of this fixture within the Custom ID Type that can be used to activate / select them for programming. |
641
+
| Comment | 0 or 1 |[String](#user-content-attrtype-string)| Comments for this Objects. |
635
642
636
643
637
644
@@ -675,6 +682,7 @@ The child list (Table 30) contains a list of one of the following nodes:
675
682
| CustomIdType | 0 or 1 |[Integer](#user-content-attrtype-integer)| Defines the CustomID Type this fixture belongs to. A Custom ID Type defines to which group of objects this objects belongs as an additional object identifier. The types for the custom ID Types are defined below. |
676
683
| CustomId | 0 or 1 |[Integer](#user-content-attrtype-integer)| The CustomId ID is an identifier for the instance of this fixture within the Custom ID Type that can be used to activate / select them for programming. |
677
684
|[ChildList](#node-definition-childlist)| 0 or 1 | A list of graphic objects that are part of the layer. |
685
+
| Comment | 0 or 1 |[String](#user-content-attrtype-string)| Comments for this Objects. |
678
686
679
687
680
688
## Node Definition: VideoScreen
@@ -716,6 +724,7 @@ The child list (Table 32) contains a list of one of the following nodes:
716
724
| UnitNumber | 0 or 1 |[Integer](#user-content-attrtype-integer)| The identification of a fixture on its position. </b> Use this as an alternative numbering scheme if the planning and programming numbering is different. |
717
725
| CustomIdType | 0 or 1 |[Integer](#user-content-attrtype-integer)| Defines the CustomID Type this fixture belongs to. A Custom ID Type defines to which group of objects this objects belongs as an additional object identifier. The types for the custom ID Types are defined below. |
718
726
| CustomId | 0 or 1 |[Integer](#user-content-attrtype-integer)| The CustomId ID is an identifier for the instance of this fixture within the Custom ID Type that can be used to activate / select them for programming. |
727
+
| Comment | 0 or 1 |[String](#user-content-attrtype-string)| Comments for this Objects. |
719
728
720
729
721
730
EXAMPLE An example of a node definition is shown below:
@@ -734,6 +743,7 @@ EXAMPLE An example of a node definition is shown below:
734
743
<Sources>
735
744
movie.mov
736
745
</Sources>
746
+
<Comment> Example Comment </Comment>
737
747
</Fixture>
738
748
```
739
749
@@ -776,6 +786,7 @@ The child list (Table 34) contains a list of one of the following nodes:
776
786
| UnitNumber | 0 or 1 |[Integer](#user-content-attrtype-integer)| The identification of a fixture on its position. </b> Use this as an alternative numbering scheme if the planning and programming numbering is different. |
777
787
| CustomIdType | 0 or 1 |[Integer](#user-content-attrtype-integer)| Defines the CustomID Type this fixture belongs to. A Custom ID Type defines to which group of objects this objects belongs as an additional object identifier. The types for the custom ID Types are defined below. |
778
788
| CustomId | 0 or 1 |[Integer](#user-content-attrtype-integer)| The CustomId ID is an identifier for the instance of this fixture within the Custom ID Type that can be used to activate / select them for programming. |
789
+
| Comment | 0 or 1 |[String](#user-content-attrtype-string)| Comments for this Objects. |
779
790
780
791
781
792
EXAMPLE An example of a node definition is shown below:
@@ -798,6 +809,7 @@ EXAMPLE An example of a node definition is shown below:
798
809
<ScaleHandeling>UpScale</ScaleHandeling>
799
810
</Projection>
800
811
</Projections>
812
+
<Comment> Example Comment </Comment>
801
813
</Projector>
802
814
```
803
815
@@ -1654,6 +1666,7 @@ The defined MVR_REQUEST message Attributes are specified in Table 74.
| Type |[String](#user-content-attrtype-string)| Not Optional | Defines the type of the message. Should be MVR_REQUEST- |
1656
1668
| FileUUID |[UUID](#user-content-attrtype-uuid)| Last MVR File from station | The UUID of the requested MVR file. If not set, the last available file is sent. |
1669
+
| StationUUID |[UUID](#user-content-attrtype-uuid)| Not Optional | UUID for the station inside the network. This UUID should be persistent across multiple start-ups of the same software on the same computer |
1657
1670
| FromStationUUID | Array of [UUID](#user-content-attrtype-uuid)|| The UUID of the station that you want to retrieve the MVR from. |
1658
1671
1659
1672
The defined MVR_REQUEST error response Attributes are specified in Table 75.
@@ -1737,6 +1750,7 @@ The defined MVR_NEW_SESSION_HOST message Attributes are specified in Table 76.
| Type |[String](#user-content-attrtype-string)| Not Optional |Defines the type of the message. Should be MVR_NEW_SESSION_HOST |
1739
1752
| ServiceName |[String](#user-content-attrtype-string)| Empty | New mDNS Service Name to connect to. If Empty, ignore. Cannot be set together with ServiceURL |
1753
+
| StationUUID |[UUID](#user-content-attrtype-uuid)| Not Optional | UUID for the station inside the network. This UUID should be persistent across multiple start-ups of the same software on the same computer |
1740
1754
| ServiceURL | [String](#user-content-attrtype-string) | Empty. | New WebSocket Service URL to connect to. If Empty, ignore. Cannot be set together with ServiceURL
1741
1755
1742
1756
The defined MVR_NEW_SESSION_HOST error response Attributes Attributes are specified in Table 77.
@@ -1783,6 +1797,7 @@ Normally FixtureIDs are numeric to allow range selection. For Descriptive displa
1783
1797
A similar concept is the multipatch. Sometimes you want to group multiple objects behind the same FixtureIDNumeric or CustomId. This can be objects of the same GDTF Type, but not forced to be. When you select the FixtureIDNumeric or CustomId from the multipatch parent, all objects that reference this object in multipatch
1784
1798
parent should also be selected.
1785
1799
1800
+
If the device supports the RDM protocol, the FixtureIDNumeric corresponds to the RDM PID 0x0656 DEVICE_UNIT_NUMBER.
0 commit comments