X32 Discussion

Re: DAW playback during production

Tried a search...how do install the X USB update on my MacBook? Or can someone please walk me through what is necessary. I have a remote using my X32 R and MacBook next week.
Thanks!
 
Last edited:
Re: DAW playback during production

Dear John,
To update the firmware on the X-USB card, download the Mac Firmware updater from an X32 Product Page. Here is a link: Downloads

Two files will be in the zip file, one for 32-bit systems and another for 64-bit. This page from Apple helps you determine which you have: How to tell if your Intel-based Mac has a 32-bit or 64-bit processor

With the X32-Rack powered up and connected, run the appropriate file and follow the instructions. Note that to open the file, you may need to command+click and choose "open" rather than the traditional double click.

Hope it helps!
 
Re: Routing possibilities (or lack thereof)

Dan McCoy said:
Heck you could buy two consoles next to each other to handle the extra load at that price and still be way under the cost for anything that could do single input patch routing
Click to expand...

Or do what a few of us do, combine the X32 with a Rack or Core and one or more S16 and have lots of routing options that way for very little extra money.
However, such solutions quickly get complicated and prone to mistakes, so it isn't something I would "sell" as a preferred solution, just an option that exists if and when needed.
 
Re: Routing possibilities (or lack thereof)

Still running 1.13… Didn't want to update until the big one came out. When I finally do update (after iPad app and new Edit) can I just go to 2.03? Or do I need to step up in order? 1.15 then 2.03? And when I do I will be able to load my Scenes using Edit? Sorry for the ignorance and yes I have been reading. It just seems that there is a lot of different info in the threads. I use my MBP on stage to mix in ears and the newer members in the band are going to use Mix Station because they have Android. And does anybody know the answer to the questions about the reverbs being dumbed down?
 
Re: Routing possibilities (or lack thereof)

Billy Peiffer said:
Still running 1.13… Didn't want to update until the big one came out. When I finally do update (after iPad app and new Edit) can I just go to 2.03? Or do I need to step up in order? 1.15 then 2.03? And when I do I will be able to load my Scenes using Edit? Sorry for the ignorance and yes I have been reading. It just seems that there is a lot of different info in the threads. I use my MBP on stage to mix in ears and the newer members in the band are going to use Mix Station because they have Android. And does anybody know the answer to the questions about the reverbs being dumbed down?
Click to expand...

You should update to 1.15 to ensure full compatibility with current versions of X32-Edit and X32-Mix, and gain a couple of minor features as well. Can't remember if the Mixing Station Andriod app cares if the firmware is 1.13 or 1.15, but there is no reason not to go to 1.15.
Loading scenes into 2.03 should work, but there were some inconsistencies reported by some users indicating that scenes might need to be verified before used in a live situation that matters. What I've tested have been OK.
 
Re: Routing possibilities (or lack thereof)

Per Søvik said:
You should update to 1.15 to ensure full compatibility with current versions of X32-Edit and X32-Mix, and gain a couple of minor features as well. Can't remember if the Mixing Station Andriod app cares if the firmware is 1.13 or 1.15, but there is no reason not to go to 1.15.
Loading scenes into 2.03 should work, but there were some inconsistencies reported by some users indicating that scenes might need to be verified before used in a live situation that matters. What I've tested have been OK.
Click to expand...


Is 2.03 just an assumed release?
 
Re: Routing possibilities (or lack thereof)

Brett Tippet said:
Is 2.03 just an assumed release?
Click to expand...

Sorry, the current is 2.02, my bad. 2.03 will presumably be released along with the apps when it's all ready.
As I understand it, there are compatibility issues between the newest iOS release and the current OSC server that is part of 2.02.
 
SanDisk Cruzer Fit CZ33 64GB USB Flash Drive

I purchased a SanDisk Cruzer Fit CZ33 64GB USB Flash Drive (SDCZ33-064G-B35) - a tiny USB2 micro flash drive. It came formatted to exFAT (no U3 mentioned on packaging). I downloaded the HP USB Disk Storage Format tool and formatted the flash drive to FAT32 on my Win7 PC. The drive mounts on my PC's and my wife's Mac. It will not mount on either of my X32 (1.1.5). :blush:


I do a 1-pass secure erase and format to FAT32 on my wife's Mac and now it mounts on my X32's. :)~:-)~:smile:


Just wanted to share my experience.


Kingston also makes a nice little micro USB flash drives (I haven't tested them).


The micro flash drives are nice as they don't stick out from the mixer and won't get bumped or smashed damaging the drive and/or the USB jack.


I have also used SP (Silicon Power) 16GB USB 3 flash drives successfully with my X32's.
 
HELP - P16 Routing - Time sensitive request

We are launching a new campus tomorrow. Today we setup an x32rack on stage in HA Remote mode. We have an x32 FOH. I've got everything working perfectly except the P16 stuff. This is of utmost importance and I am stuck. On an S16, you can set a config that automatically routes (say config 1) AES50-A ch33-48 to the P-16 Outs on the S16. Then on the x32 you just route the x32 P16 channels to the AES50A outs (33-48) in two 8 channel chunks. Got that work no problem. Now that I've replaced the s16 with the x32 rack, I cannot figure out how to control what is fed to the P16. In P16 outs on the x32rack you can route various local signals to the P16 but I cannot figure out how to route stuff coming from FOH console to it. Is it possible to route anything non local to the P16 outputs on the x32rack?
 
Last edited:
Re: HELP - P16 Routing - Time sensitive request

Dan McCoy said:
If anyone has an answer and can call my cell 609-202-4988 I would love this. Thanks
Click to expand...
Sent you a text. You need to route to inputs. AES50A33-48 to Input 17-32, then input 17-32 to P16.

It doesn't really make sense to have a set-up like that, but I guess the idea is to be able to use the Rack for monitor mix or stand alone, and the scenario described is only one of many.
Without being 100% sure, I don't think there is anything in firmware V2.02 that makes it easier to route to P16 out, so the AES50A 33-48 that contains the P16 would have to go into some of the input channels on the Rack, and assuming that the channels 1-16 carry what's connected on stage, I think it makes sense to leave those channels alone and use the channels 17-32 that are not connected to anything in the current setup.
 
Re: HELP - P16 Routing - Time sensitive request

Dan McCoy said:
We are launching a new campus tomorrow. Today we setup an x32rack on stage in HA Remote mode. We have an x32 FOH. I've got everything working perfectly except the P16 stuff. This is of utmost importance and I am stuck. On an S16, you can set a config that automatically routes (say config 1) AES50-A ch33-48 to the P-16 Outs on the S16. Then on the x32 you just route the x32 P16 channels to the AES50A outs (33-48) in two 8 channel chunks. Got that work no problem. Now that I've replaced the s16 with the x32 rack, I cannot figure out how to control what is fed to the P16. In P16 outs on the x32rack you can route various local signals to the P16 but I cannot figure out how to route stuff coming from FOH console to it. Is it possible to route anything non local to the P16 outputs on the x32rack?
Click to expand...
Problem resolved. Well sort of. Thanks to John Dinicola and Chase from Behringer/Midas who both separately called me and also to Dan Mortensen who called me. Turns out I discovered a hole in the featureset of the x32rack. It's not a true replacement of an S16. An s16 has the ability thru configs to route AES50A inputs (33-48) to its Ultranet P16 outs 1-16. An x32rack CANNOT do this. If you have an S16 connected to an x32rack you can pass the P16 from FOH => AES50A -> AES50B to S16 (P16) but if you have inputs that appear on the FOH x32 only you can't pass them to the X32rack P16 outs. The 2.0X software needs to either add functionality to the P16 tab on the routing page to allow you to choose A(B)XX as sources to send to the P16(x) as you can now with the Direct Outs etc or they need to add a tab on the Routing Home page to allow this. For now I built a 175 foot shielded ethernet cable tonight to run from FOH P16 to the P16D for stage IEMs. This is just a backup if I don't have time to get it properly routed tomorrow morn through the S16
 
Re: HELP - P16 Routing - Time sensitive request

whoever just texted me from international... thanks! You just came up with a brilliant workaround. Route AES50A 33-48 to input 17-32 of the x32rack and then route direct output 17-32 to P16. Chews up x32rack channels but not an issue because I would need another S16 to fill them anyway.
 
Re: HELP - P16 Routing - Time sensitive request

Per Søvik said:
Sent you a text. You need to route to inputs. AES50A33-48 to Input 17-32, then input 17-32 to P16.

It doesn't really make sense to have a set-up like that, but I guess the idea is to be able to use the Rack for monitor mix or stand alone, and the scenario described is only one of many.
Without being 100% sure, I don't think there is anything in firmware V2.02 that makes it easier to route to P16 out, so the AES50A 33-48 that contains the P16 would have to go into some of the input channels on the Rack, and assuming that the channels 1-16 carry what's connected on stage, I think it makes sense to leave those channels alone and use the channels 17-32 that are not connected to anything in the current setup.
Click to expand...



Per - Thanks. I was typing my below post when you posted this. I tried this this morning and couldn't get it to work. Ended up routing through to the S16 on AES50B and it worked after I fixed a routing issue. Turns out the same routing fix made your suggestions work too (went back after service and tested it.)One thing I would add to your suggestion is to make sure your P16 tap points are IN/LC so it's a straight passthrough for the x32rack from FOH. Don't need to have two consoles fighting each other.

Also - ran into one problem the boys at Behringer (JOHN D - for you) should see. I patched Inputs 17-24 to AES50A 33-40. For some reason Channel 17 config didn't remap to A33. I didn't know this at first. It drove me nuts to understand why the vocal mic wasn't patching through to P16 Channel 1. All other patching worked. Then I noticed that Channel 17 showed no input. EVEN going and pressing the select button in the input routing to remap did not work. I had to move off the AES50A33-40 to something else and then back on to get it to remap. No clue what happened but it drove me nuts for 25 mins afterward. It's all working well now. I think every press of the knob button should send the remap command and not force you off and then back.
 
Last edited:
Re: HELP - P16 Routing - Time sensitive request

Per Søvik said:
Sent you a text. You need to route to inputs. AES50A33-48 to Input 17-32, then input 17-32 to P16.

It doesn't really make sense to have a set-up like that, but I guess the idea is to be able to use the Rack for monitor mix or stand alone, and the scenario described is only one of many.
Click to expand...
We chose to use the X32rack instead of an S16 for several reasons. 1) The ability to have low cost backup if the X32 FOH fails. 2) I was told it can emulate an s16 (which is partially true - except for the P16 piece). It was less then 200 more to provide the benefits in 1). I want to ultimately have all my channels available if I need them so getting the ability to directly route P16 outs from AES50 is paramount. Your solution is a workaround.
 
Last edited:
Top Bottom