A professional CD player or old school cart machine will play the sound then automatically move to the start of the next track and wait for your command. They want you to play one sound, then diddle around setting up the next sound. I've done shows on analog tape, on CD players, on iPods, on iTunes or Windows Media Player, and all of these are relentlessly linear. Now imagine this massive CD player is set up so well you can command it from a single button once it has been programmed. A CD player that can play a dozen tracks at the same time, or one after another, at different volumes, panned to different speakers. Think of it like a CD player on steroids. So that's 500 words, and what does QLab actually do? Shareware tends to keep the look and feel of the underlying GUI and that means it is faster to learn it and smoother to use it in a multi-application work flow. Oh, and a small annoying and productivity-related thing notice that shareware is usually better about adhering to GUI standards? Commercial software tends to use unusual functions for the control keys, hide the menu bars, and won't even permit re-sizing of the application window. The philosophy is to find problems so they can be fixed which is directly opposed to the marketing-driven philosophy of mainstream software that says the way to sell the software is to slap lawsuits on anyone who dares mention it doesn't work very well. The shareware philosophy is to build a product good enough that people will want to support you in return. And not cripple-ware or nagware, either.Īn aside. With all that out of the way, what do you want this for? Well - QLab is easy to understand, plays well with all hardware, plays any file the Mac can play (leveraging QuickTime to do so), takes up very little system overhead.and, oh yeah, the basic version is free. of which I will say no more less my blog get shut down by angry marketing people. It is also not the only professional-level software for its specific application - Sound Cue System for Windows is in a similar price range, and of course there is SFX. It is also not a Cart Machine (although Figure 53 has a digital one of those, too.) Also, there is no Windows or Linux version (although there are other, similar software tools). It is not a mixer, a signal processor, or a Digital Audio Workstation. It is from Figure 53 and is designed for use in theater and similar live-playback situations. If you just need to bypass their mac so you can access the lightingĬonsole too, a simple Midi Solutions MERGER will take the two midi outputsįrom your systems & merge them into one input of the console.QLab is audio playback software for the Macintosh. > Midi device you might add? Probably no. > Are they willing to let you install a driver if necessary for the USB to > Are they willing to let you dictate what settings you need setup on the > They are willing to let you add a second USB to midi interface? YES > their light board but it is not accessible. > They already have a midi in on their mac rig but it's tied up? It goes > Do you already have a midi out on your mac rig? YES > What app are they running lights with on the Mac? Qlab v2 > interface to the one plugged into the lighting board. > changing the AUDIO MIDI SET UP utility to route request from my midi I thought perhaps plugging in a second USB-MIDI interface > by sending MSC to their lighting via a midi interface out of a lock mac > Their mac is running lights only? They are triggering lights via Qlab v2 > So your mac is running Qlab only? Both computers are running Qlab v2. They are willing to let you add a second USB to midi interface? YES They already have a midi in on their mac rig but it's tied up? It goes to their light board but it is not accessible. What app are they running lights with on the Mac? Qlab v2ĭo you already have a midi out on your mac rig? YES I thought perhaps plugging in a second USB-MIDI interface and changing the AUDIO MIDI SET UP utility to route request from my midi interface to the one plugged into the lighting board. Their mac is running lights only? They are triggering lights via Qlab v2 by sending MSC to their lighting via a midi interface out of a lock mac I can't access. So your mac is running Qlab only? Both computers are running Qlab v2. > the list of MSC cues in their version of qlab. > plugging in and out via the Qlab preferences panel to have my mac trigger > interface into the 2nd mac via it's wired keyboard and then do some > that computer (via wifi?) or perhaps just plugging in a second midi-usb > I want to trigger light cues from my mac without physically plugging into > the second mac running qlab that is hooked up to a midi interface that I I am working in a venue that doesn't like me touch their stuff.
0 Comments
Leave a Reply. |