Once the number of Bitmap Fixtures that are needed have been patched, there are some additional steps to take to be ready to pixel map, including creating a Bitmap Layout view, and importing the images that are going to be used for pixel-mapping into the console’s Images Pool.
The Bitmap Fixture is added in the console’s Setup>Patch & Fixture Schedule window just like any other type of fixture. The Bitmap Fixture Engine feature in MA2 v3.2 is essentially like having a simple media server in the console that is accessed via a layer, just like accessing a layer of an external media server. Also, by using a Bitmap Fixture, there was no need for any sort of external signal merging, which further simplified the setup of the control system. This was both for programming ease as well as for budgeting, especially since I already had two active media servers on the show already. I decided to use the MA2’s Bitmap Fixture Engine feature, released in v3.2, rather than add an external media server just for pixel-mapping.
With these two impactful visual elements in the design, I knew pixel-mapping would be an integral part of my programming work. The 63 Nexus panels were mounted onto independent vertical trusses and configured to spell out the word, “AMPLIFY,” which represented the theme of the event. The 48 DreamPanels, (or, as I like to call them, the DreamyPanels) were mounted in four-by-three arrays on four sides of a truss “cube,” an element I referred to as “the scoreboard.” Here are some of the reasons why I’ll be using it again in the future.įor the design, I chose to work with two different types of LED fixtures - Ayrton’s DreamPanel Twin and Chauvet’s Nexus 4×4. On a recent project, I had the opportunity to use the Bitmap Fixture Engine in a grandMA2 console and, as a result, I discovered an easy new way to pixel-map.
0 kommentar(er)
