Someone posted about lackluster audio from his X32 in the studio. This could possibly be remedied with a quality external clock and a better DA for monitoring.
Greg
Bullshit. The word clock has zero affect on actual audio. Believe whatever you *think* you hear, but scientifically it's impossible, and when you remove the 'sample bias' of knowing which source is clocked by what device, listening tests are generally no better than random guesses.
Ah, the "external clock to make the mixer sound better" myth again...I have to believe that these quality, single purpose devices will enhance the quality of the audio processed by the X32.
Someone posted about lackluster audio from his X32 in the studio. This could possibly be remedied with a quality external clock and a better DA for monitoring.
Greg
Hi - Please can I have an answer from someone who actually really knows?
Which pin is hot on the X32 input XLRs?
Thanks
Pauly
Behringer normally include a XLR and jack wiring page in their mixer manuals.
It's missing from the X32 one.
Going by the manuals for the Behringer mixers I have owned (several models, large and small), they seem to follow the above convention of 2 = hot, 3 = cold, 1 = ground.
Unless they've adopted a new standard for the X32 and not told anyone, it would be fair to assume that they've kept to the same configuration.
Karl.
Thanks guys
Yes - I'd also consulted the manual and wiki etc.
I have some old gear that's wires pin 3 hot and now I know phase reversal is in my future
Running firmware 1.15, I found a little bug when remapping the aes50 channels to the "aux inputs" in the routing section: all preamp gains are linked together, the channels work fine and the preamps and phantom work fine, but all channels in that group share the same linked gain and phantom settings. The channels are seperated out correctly and are independant for everything else though it seems.
One other thing that I found wierd was in x32edit (osx) v1.10 - those channels come up as "card", but the ipad says aes50(a1-6).
Gotta say, other than that... Fantastic Job! Love all the changes!
Just realized there is an update to 2.1.2, I was running 2.1.1 - I'll have another look at this weekend's gig.
I tried hard today to create some problems.
Connected the S16 with a cheapo Cat5e STP, let the S16 share outlet with a 4/8 KW amp that I would turn off and on, repatching, changing gains, shaking the cat5, turning off and on lights, firing up a fifty year old hand drill, dimming a high power led par right next to the S16 sharing the same outlet, turning phantom on and off (slight pop as always).
Sadly, mission failed completely. No noise, no flicker in the sync light.
I've got 12 compressors in my rack and all the built-in compressors in the X32 ~:-D~:grin: I have a 1.5KW compressor and a welder that I could employ, but that hardly seems representative for what I'm likely to ever encounter on a showstage.Do you have anything with a compressor or some other large motor that turns on/off like that?
Do you have a variac? It would be interesting to see what happens when the voltage is already low-ish and you do the things that you describe.
Although.... the definition of when the console restarts is somewhere around 95 volts (recalling from memory). When starting as you are from 240v (is that what it is there?), that is much farther of a drop than our starting point of 110-120v. Wonder if that makes any difference.
I don't have a clue of what it takes to mess up the S16.
A few month ago I had noise on my system. Two S16 were located close to a rack of wireless receivers. There were 24 receivers, sennheisers g1 to g3, some AKGs, all with the buildin antennas. I repositioned the S16s by moving them half a meter away from the receivers and then everything was fine. Maybe the S16s are not 100% resistant against electro smog like this.