At the onset, things looked positive, tho we had a few hiccups with
the way Plogue utilized the 4 processors. (Oh - quad-core mac pro
running snow leopard an QLab 1.3.5 - which may make this all invalid -
but it's what the theater has licences for...)
Unfortunately, we discovered a fairly unpredictable instability - at
varying time increments, Plogue would begin to sound, well, like a bad
80's synth. It would, I think, begin to lose synch within the
aggregate, or maybe just start dropping samples, tho that is a TOTAL
guess... Turning Plogue off and on would fix the problem.
Unfortunately, that's not an option mid-cue...
However, AU Lab was standing by in the wings; we implimented a shift
from Plogue into AU Lab for our last tech, and it's been stable and
solid since (about a week of previews w/ afternoon rehearsals and an
opening Friday...)
Some notes:
We're not doing any live fader moves, plug in changes, or any other
dynamic change within AU Lab - it's just providing a bunch of
Parametric EQ (1991 JBL speakers) and 5 channels of delay.
The graphic interface is misleading - meters are totally inaccurate.
The engineer stops & starts the AU Lab processing at intermission.
Of course, having written this, I'm anticipating total catastrophic
failure in Tuesday's show...
But, honestly, this could offer a solid lo-cost solution for real-time
plugins until they've been built into the QLab codec...
<><><><><><><><><><><>
-Rob Kaplowitz
Please forgive me if there are any unexpected words or spellings; I'm
sending from a phone that has a mind of it's own.
________________________________________________________
WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!
Change your preferences or unsubscribe here:
http://lists.figure53.com/listinfo.cgi/qlab-figure53.com
> But, honestly, this could offer a solid lo-cost solution for real-time
> plugins until they've been built into the QLab codec...
Well, uh.... oh, never mind ;-)
C-)