Only on very complex, high resolution LED stages will you need to use 2 or more processors and thus 2 or more outputs. The processor divides it over the 4 screens. So you only have to send out one signal from your computer's output. Tip! Keep in mind that 4 screens like this are still controlled by a single LED processor. We've included a Photoshop mockup in the bottom right to help you get the idea of how the processor relates to the stage. This is done to minimize the data sent along the cable connecting the LED screens. In the LED processor, they might be arranged something like the image below. The annoying thing is that the 4 screens are positioned like that on the stage, but not in the LED processor. Now imagine your stage is a bit more complex and looks like this: This means you probably lose a bit of the top and bottom of your composition, but your circles will still look like circles and not squished eggs. By first matching the output shape, you've made sure your input slice has the same aspect ratio as your output shape. This means that you will exactly see that part on your LED wall. What you have now is a slice that takes a 2x1 piece of your composition and places it in the top left of your output. ![]() Now scale it up until it fills the entire Input Selection stage again, Make sure you hold down both Shift and Alt to scale proportionally from the center! Drag it back to the center, letting the snapping do the hard work for you. This will place your slice exactly in the same place as it has on the Output Transformation stage. Now switch over to the Input Selection stage, right click the Slice, and hit Match Output Shape. Output MapĬreate a new setup, and on the Output Transformation stage, you make your single slice 384x192 pixels in size and place it exactly in the top left of your output. You could of course render all your content to this scale before show, but it's much easier to use the Advanced Output. It's only interested in the 384x192 pixels in the top left of that signal. In this case the regular video signal is 1024x768, but it could be any standard video resolution. ![]() The processor will only take the top left part from a regular video signal. The output your processor expects would look something like this: Let's say your LED wall is 384x192 in resolution. The processor takes the top left part of the video signal and shows it on the LED wall. In the case of a single LED screen, setup is relatively simple. I personally use Soundflower (2Ch) channel 2 and Loopback to both route SMPTE back to Qlab and also as a line out signal on the Right channel.Įdit: If you don't own Loopback and don't want to invest $99, you could create two SMPTE cue in Qlab, (one soundflower and one built in output), nest them in a group and choose "Start all children simultaneously".Įdit #2: I always forget about MTC! Instead of using SMPTE to control your audio files in Qlab, you could create one MTC cue and one SMPTE cue in Qlab, (MTC on the built-in IAC bus and SMPTE on the built-in output), nest them in a group and choose "Start all children simultaneously".A LED processor usually takes a single video input (DVI/HDMI/VGA/composite) and divides this signal over the connected LED walls. ![]() Check out chapter 14 - p103 of the manual so if you have MOTU AudioDesk or Digital Performer, you could play your 5 tracks, generate timecode from the sequencer and sync your video in Arena that way.Īnother approach would be to generate SMTPE directly from Qlab and sync your audio files using the timecode trigger function. Your MOTU 828mkII can generate SMPTE timecode using the MOTU SMPTE console.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |