Log in
Register
Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Simon Eves" data-source="post: 97424" data-attributes="member: 4463"><p>Re: Live Musical Theater</p><p></p><p></p><p></p><p>There really doesn't seem to be any need for an arbitrary limitation like this. Back in the days of custom hardware and expensive non-volatile memory (like in the 01V), fair enough, but the CPU and main memory in the X32 surely has to be fairly generic, and flash memory is dirt cheap. I guess there is still a finite amount of memory dedicated to scene storage, and the size of the data for each scene is variable, but even so it seems like there must be space for a lot more than 100.</p><p></p><p>I got my X32 about two months ago, and am using it right now for a student production of the musical "Gypsy". I didn't want to have to get my head around the scene recall system, so I avoided it completely and wrote a custom tool to control the mixer from QLab. You make cues with high-level user-readable OSC commands (e.g. "/mute Rose", "/unmute BabyJune") and it translates to low-level mixer commands (e.g. "/ch/01/mix/on OFF"). Our current QLab file has 234 cues, of which maybe 15 are regular sound effects cues, and the rest are configuration stuff for the mixer then actual mute/unmute or DCA assignment commands for the 18 wireless mics. I have two students in the booth for sound. One is triggering QLab along with the script, and the other is riding faders for active channels, and tweaking the EQ and dynamics. We've got most of the bugs out of it now, which is good because in two weeks we switch to Les Miserables, with 24 wireless mics and a bigger louder band! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Once we're done, I'd be happy to tidy up the tool (it's just a Python script, in conjunction with a third-party OSC module which I got from the guys on x32user.net, some of which are here too) and give it away to anyone here who might be interested?</p></blockquote><p></p>
[QUOTE="Simon Eves, post: 97424, member: 4463"] Re: Live Musical Theater There really doesn't seem to be any need for an arbitrary limitation like this. Back in the days of custom hardware and expensive non-volatile memory (like in the 01V), fair enough, but the CPU and main memory in the X32 surely has to be fairly generic, and flash memory is dirt cheap. I guess there is still a finite amount of memory dedicated to scene storage, and the size of the data for each scene is variable, but even so it seems like there must be space for a lot more than 100. I got my X32 about two months ago, and am using it right now for a student production of the musical "Gypsy". I didn't want to have to get my head around the scene recall system, so I avoided it completely and wrote a custom tool to control the mixer from QLab. You make cues with high-level user-readable OSC commands (e.g. "/mute Rose", "/unmute BabyJune") and it translates to low-level mixer commands (e.g. "/ch/01/mix/on OFF"). Our current QLab file has 234 cues, of which maybe 15 are regular sound effects cues, and the rest are configuration stuff for the mixer then actual mute/unmute or DCA assignment commands for the 18 wireless mics. I have two students in the booth for sound. One is triggering QLab along with the script, and the other is riding faders for active channels, and tweaking the EQ and dynamics. We've got most of the bugs out of it now, which is good because in two weeks we switch to Les Miserables, with 24 wireless mics and a bigger louder band! :) Once we're done, I'd be happy to tidy up the tool (it's just a Python script, in conjunction with a third-party OSC module which I got from the guys on x32user.net, some of which are here too) and give it away to anyone here who might be interested? [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
Top
Bottom
Sign-up
or
log in
to join the discussion today!