User Tools

Site Tools


ai:examples:movingscreens:movingscreens

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
ai:examples:movingscreens:movingscreens [2018/12/05 10:52] – [Bottom: the projector outputs] icke_siegenai:examples:movingscreens:movingscreens [2018/12/05 13:57] (current) icke_siegen
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) (This concludes the top part - the calculations for the hung models)
Line 159: Line 159:
 ==== Lower part: Mediaspinners, standing on the ground ==== ==== Lower part: Mediaspinners, standing on the ground ====
  
-{{:ai:examples:movingscreens:bottom_mediaspinners.png?450|}}+{{: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 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.
Line 167: Line 167:
 === MediaSpinner ArtNet === === MediaSpinner ArtNet ===
  
-{{:ai:examples:movingscreens:mediaspinner_artnet.png?300|}}+{{: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. 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.
Line 173: Line 173:
 ==== Bottom: the projector outputs ==== ==== Bottom: the projector outputs ====
  
-{{:ai:examples:movingscreens:projectors.png?450|}}+{{: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). 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).
  
ai/examples/movingscreens/movingscreens.1544007140.txt.gz · Last modified: 2018/12/05 10:52 by icke_siegen

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki