Differences

This shows you the differences between two versions of the page.

--- ai:examples:movingscreens:movingscreens [2018/12/04 15:29] – [Upper part: the hung segments] icke_siegen
+++ ai:examples:movingscreens:movingscreens [2018/12/05 13:57] (current) – icke_siegen
@@ Line 8: / Line 8: @@
 ^ published: | here |
 ^ tested in version: | Ai v8 |
-^ download: |  |
+^ download: | {{ :ai:examples:movingscreens:stagepatch.zip |Stagepatch}}, {{ :ai:examples:movingscreens:models.zip |Models}}\\ The models are distinct as for their UV mapping - make sure to load the correct model into each screen. |
 //Hint: click the images to show them larger.//
@@ Line 75: / Line 75: @@
   * top-left, there are some [[ai:modules:controller:constant|constants]] to define the general position: ''X_Pos'', ''Y_Pos'' and ''Z_Pos'' set where the segment generally is (its origin), and ''Susp_Width'' and ''Susp_Height'' let us fine-tune how the segments are rigged (the smaller the suspension distance, the more tilt can be acchieved with a little winch travel)
   * ''Winde 1-3'' is a subpatch. It takes the global ''Artnet Input'', ''Artnet Universe'' and ''Height''. Also, the IDs of the winches are exposed as inputs and need to be set to match which winch is located where. The patch then takes the Artnet data and calculates the height of each of the three points (left, right, back). These results are then send to the next subpatch ''Calculate''. For an explanation of the calculations [[#winde_1-3getting_the_absolute_height_data|see below]].
-  * ''Calculate'' is the subpatch where the magic happens: from the height data for each point the absolute position and rotation of this segment is calculated. Inputs are the constants defined and the positions from the previous subpatch - outputs are position and rotation (angle) data. For an explanation of the calculations [[:tbd.|see below]].
+  * ''Calculate'' is the subpatch where the magic happens: from the height data for each point the absolute position and rotation of this segment is calculated. Inputs are the constants defined and the positions from the previous subpatch - outputs are position and rotation (angle) data. For an explanation of the calculations [[#calculate|see below]].
   * two [[ai:modules:controller:monitor|]] modules were inserted here only to monitor the computed angels
-  * [[ai:patches:EulerToQuaternion|]] is another subpatch which is [[:tbd.|explained below]]. It converts the computed rotation data to another dimension (Quaternions).
+  * [[ai:patches:EulerToQuaternion|]] is another subpatch which is [[#eulertoquaternion|explained below]]. It converts the computed rotation data to another dimension (Quaternions).
   * ''x_corr'' is a fader to allow for minor corrections of the x position - its value is also sent into the Calculate subpatch
   * finally, bottom-left is the screen fixture for this very segment:
@@ Line 153: / Line 153: @@
-{{:ai:examples:movingscreens:moving_screens_eulertoquaternion.png?450|}}
+{{:ai:examples:movingscreens:moving_screens_eulertoquaternion.png?450|Euler To Quaternion}}
+(This concludes the top part - the calculations for the hung models)
+==== Lower part: Mediaspinners, standing on the ground ====
+{{:ai:examples:movingscreens:bottom_mediaspinners.png?450|Mediaspinner Screens}}
+This part is pretty much straight-forward: each one of the six screens which are standing in mediaspinners on the ground is represented by its own screen fixtures so that each one can be loaded its own model (again, distinct by the UV mapping), and can be controlled, as per the y roation, via Artnet from the Mediaspinner controller.
+This is done in a little subpatch: MediaSpinner ArtNet
+=== MediaSpinner ArtNet ===
+{{:ai:examples:movingscreens:mediaspinner_artnet.png?300|Mediaspinner ArtNet subpatch}}
+This subpatch simply allows to set the DMX addresses per mediaspinner - each one takes two DMX channels as 16bit. From the given start address per spinner, the next channel is computed. Then the ''ArtNet Input Large'' gets us the values, which are then being combined to a 16bit value (0...65,535), which is then normalized (0...1) and multiplied by the full travel (450 degrees). The result is returned, and used as y_rotation parameter ''y Angle Adj.'' for the respective spinner.
+==== Bottom: the projector outputs ====
+{{:ai:examples:movingscreens:projectors.png?450|Projector outputs}}
+Finally, at the very bottom of the stagepatch, the projectors are defined. Note that again we didn't use softedge, but assigned each screen to a specific projector - see [[ai:examples:advancedoutputpatch:advancedoutputpatch|]] for details (essentially it is disabling ''Use All Fixtures'' per projector, and patching the screen fixture outputs to the respective inputs).