X32 Discussion

Re: X32 Discussion

I had problems with playback through the firewire port. It had to do with going through my external hard drive. I have been doing 24 track recording through the usb and have not had a problem using a macbook pro with 8 gig of ram at 2.66 ghz. I also have been able to record 24 tracks to the system drive and Protools does not recommend it but I have been doing this for virtual soundcheck.
 
Re: Request: Dual mono delay

True, and there's a 31-band that can be inserted, and a 4-band (and low-cut) on the channels.

A Q of 10 (about 1/6 of an octave, or close to that) doesn’t go very far with omni’s or ringing out monitors.

It’s like a physician doing surgery with a hatchet instead of a scalpel.

Prior to moving to digital, I had an outboard parametric just for the omni. I've lived without it now. The results aren’t perfect, but it's acceptable.

I've got no bones to pick with Behringer on it. We've had an X32 in production for about five months. It's a great board, especially at that price point. Service and support have been great.

An insertable parametric with higher Q's would be very useful.

Eric H.
i imagine it would be easier to just change the software on the current eq, rather than writing another fx...
 
Re: X32 Discussion

After reading that supposed review of the X32 I almost can't believe that it was real. The Presonus also has 16 buss's total. And only two effect buss's. I have never used only two buss's for effects. Many digital effects cut out during setting changes as well. This is nothing new. The Presonus does not have DCA's and he complains that they are level only. He has never used an analog desk with VCA's. And I wonder how many Pro digital desks he has actually used.I have been on the Yamaha's, Midas's, and even tried the new Roland's.He says he doesn't miss the flying faders because he only has 24 channels. He doesn't get the advantage of recalling all of the channel parameters during a recall. He does mention the fact that x32 also recalls the preamp settings but I don't think the preamps in the Presonus sound better than the 32's and I have been using Presonus preamps with another of my digital boards. The reverbs in the x32 sound pretty damn good. Not like my high end lexicons but for live I can live with the difference. They sound better than the ones that came in the Midas Pro 2. He also talks about getting the Xcontrol to work with the board. Set the address and go. I am glad I purchased the X32. I have been using it for FOH, monitors, as well as a recording desk and find it so easy to go from one use to another. Just hit scene recall and it is all there. And with sends on faders setting mixes is a breeze. Also like the solo follows select option. Great when mixing monitors. I just can't believe that was a real review and I think some of his reasoning shows how flawed it is. As for the recording software that comes with the Presonus, how does it compare to DAWS like Logic, Nuendo, Cubase, and Protools.
 
Re: X32 Discussion

Dont mind these stupid messages. I have seen very similar messages and they come from presonus sales people. Shameful they use fake messages to try to influence people.
Curios what behringer will release at namm. cant wait to see but unfortunately cant be there. so i hope you guys can make pix and post here :) :)
 
Re: X32 Discussion

Same here, been using USB 16in / 16out since day 1 and no problems at all, I had crackling with firewire and could never get it to work for me ???

On Windows PC's in particular, there are some not so great chipsets and/or drivers running around out there. If you are having issues with either interface, the first thing you should do is update the drivers for either your USB or FireWire. If that still doesn't help, in particular with firewire you may have to switch to a different chipset - the TI based firewire chips seem to have the best reputation on audio forums, and for add-in cards in particular SIIG seems to come up over and over as being good cards with good drivers.

But if USB works for you better that's all that matters! Just understand from a technical standpoint and all things being equal (a stable chipset and reliable drivers) Firewire will always have less overhead and latency over USB. So when speccing that next machine, if it comes down to one without FW or a questionable FW chipset and one with a good FW chipset, I'd personally pick the one with the better Firewire support just to have it.
 
Re: X32 Discussion

On Windows PC's in particular, there are some not so great chipsets and/or drivers running around out there. If you are having issues with either interface, the first thing you should do is update the drivers for either your USB or FireWire. If that still doesn't help, in particular with firewire you may have to switch to a different chipset - the TI based firewire chips seem to have the best reputation on audio forums, and for add-in cards in particular SIIG seems to come up over and over as being good cards with good drivers.

But if USB works for you better that's all that matters! Just understand from a technical standpoint and all things being equal (a stable chipset and reliable drivers) Firewire will always have less overhead and latency over USB. So when speccing that next machine, if it comes down to one without FW or a questionable FW chipset and one with a good FW chipset, I'd personally pick the one with the better Firewire support just to have it.
Personally I was surprised how well the usb works - thought I would need to upgrade to firewire - used on an Compaq laptop and now on a I3 windows 8 netbook come small format laptop with reaper.
 
Re: Request: Dual mono delay

i imagine it would be easier to just change the software on the current eq, rather than writing another fx...

Even if the Q was higher, general shaping and feedback control is going to use more filters than are available.

Nesting a 31-band would probably lead to ok results. But, then it's impossible to see the resulting slope.

Eric H.
 
Re: old scenes

Has anyone tried this, or has Behringer spoken to this?

(I'd be leery of doing this the same-day of an event. Although, I haven't heard of anyone bricking an X32.)

Eric H.

We wiped.the board and.loaded each channel. Really disappointed. I can't.update my.board without losing scenes. I just bought a second board and run bands.often at the same.venue. now I have to.choose between updating and having a preset of.a.band. hell I.might ad well have an analog board.
 
Re: old scenes

We wiped.the board and.loaded each channel. Really disappointed. I can't.update my.board without losing scenes. I just bought a second board and run bands.often at the same.venue. now I have to.choose between updating and having a preset of.a.band. hell I.might ad well have an analog board.

Have you contacted the guys from Behringer that post here? My bet is there was a major change in firmware architecture somewhere around 1.09 or 1.10. There may not be a way to bring back old work, but it would be wise to ask the support team. Do you anticipate updating firmware every week or month? Sometimes you should wait for exactly the reason you mention: you have show files.

Welcome to the land of first adopters. Like many products the X32 is a work in progress and there will probably be another 3 or 4 firmware updates before it's considered "mature." Some of those updates may not be backward-compatible, but we can hope that Behringer addresses that issue.

I had the uncomfortable experience of updating a mixer at a gig because the BE's saved show was from a desk that had the newest (1 week old) firmware. It updated flawlessly, but there were still the minutes of uncertainty until it rebooted and came back with the splash screen.
 
Re: old scenes

We wiped.the board and.loaded each channel. Really disappointed. I can't.update my.board without losing scenes. I just bought a second board and run bands.often at the same.venue. now I have to.choose between updating and having a preset of.a.band. hell I.might ad well have an analog board.

Copied from th release notes of FW1.10:

Notes:
• Due to additional scenes parameters (matrix bus options: signal tap, x-over filter in EQ and phase
reverse) all scenes that use matrix buses should be checked, because previously created scenes do
not contain these additional parameters yet. In order to make old scenes consistent with Firmware
1.10 it is recommended to initialize the console, then load and immediately save back each scene.


We followed this instructions and didnt loose a single scene, so what the hell are you guys talking about

Uwe
 
Re: old scenes

Have you contacted the guys from Behringer that post here? My bet is there was a major change in firmware architecture somewhere around 1.09 or 1.10.
It was stated in one of the update documents that the upgrade wasn't compatible with the old scenes and needed to be re-saved.

@op What happens when you try to load an old scene?

The saved files are text-only and can be edited by hand.

If this is the same issue that was described in the update document then I also think that you don't need to downgrade the firmware.

The steps would be:

1. Initialize console in the setup page. Remember, this doesn't wipe your entire board. It only loads your console factory default scene, just like any other scene you are loading. This step ensures that later added functionality doesn't interfere with the old configuration. They really need to rename that function since most people thinks it wipes the complete console of all stored data (factory reset) witch it don't.

2. Load your old saved scene.

3. Re-save the scene. This stores the additional configurations used by the new firmware

4. Repeat ALL STEPS for all old scenes

If your problem is of a different nature, please describe...

As a side note. If I got this right, a factory reset is performed by holding down 'undo' while booting
 
Last edited:
Re: X32 Discussion

On Windows PC's in particular, there are some not so great chipsets and/or drivers running around out there. If you are having issues with either interface, the first thing you should do is update the drivers for either your USB or FireWire. If that still doesn't help, in particular with firewire you may have to switch to a different chipset - the TI based firewire chips seem to have the best reputation on audio forums, and for add-in cards in particular SIIG seems to come up over and over as being good cards with good drivers.

But if USB works for you better that's all that matters! Just understand from a technical standpoint and all things being equal (a stable chipset and reliable drivers) Firewire will always have less overhead and latency over USB. So when speccing that next machine, if it comes down to one without FW or a questionable FW chipset and one with a good FW chipset, I'd personally pick the one with the better Firewire support just to have it.

Hi Eric

Thanx for the info :) I think I've just been lucky so far as I'm recording live on an oldish laptop with Reaper through usb and it work's fine but I want to get a better firewire card for my pc in the studio as it has an on-board fw but it's not working out.
I'm going to look for a good fw card soon.

Thanx
Andre
 
Re: old scenes

No, it won't.

The earliest firmware I could find on behringer site was v1.03.
Then out of interest if you re-set the console to the original firmware - what would it revert to? presume it would be the version it came with at the time - can't recall what mine came with maybe it was 1.03 (first batch at Thomann)
 
Re: old scenes

We wiped.the board and.loaded each channel. Really disappointed. I can't.update my.board without losing scenes. I just bought a second board and run bands.often at the same.venue. now I have to.choose between updating and having a preset of.a.band. hell I.might ad well have an analog board.

If you just learn to follow instructions, it is not a problem. You can't be disappointed by the product because you don't want to learn or don't want to follow instructions.
Save your work, keep it updated and you'll have no problem.
 
Re: Request: Dual mono delay

Even if the Q was higher, general shaping and feedback control is going to use more filters than are available.

Nesting a 31-band would probably lead to ok results. But, then it's impossible to see the resulting slope.

Eric H.

I dunno, bands of parametric and a hi-pass on the input and another 6 on the output gives you a fairly high degree of control. If I found myself using more than 6 bands on parametric on a wedge and still had problems I'd look a mic placement rather than attacking it with more eq. You milage may vary I guess. :)
 
Re: old scenes

Then out of interest if you re-set the console to the original firmware - what would it revert to? presume it would be the version it came with at the time - can't recall what mine came with maybe it was 1.03 (first batch at Thomann)
Reseting the console doesn't replace the firmware to any other firmware.

The reset is a special piece of program in the installed firmware that revert the console to a precise state, i.e. Factory state.

As the x32 is a sophisticated computer there is alway a risk that memory can become corrupt due to i.e. power glitch (this is why an ups always are recommended for digital consoles!) the factory reset all memory and data to a clean state. Think of it like a corrupt disk that you format and can start fresh with.

The firmware isn't touched with this operation since it is read-only data and can be re-loaded by other methods.
 
Last edited:
Handy Hints

Hey you guys, I know that it's well noted that the apples fit perfectly in the special holder on the X32, but I just wanted to add that my tests indicate that bananas fit just as well (albeit with a slight overlap)...

fruit_holder.png

Pretty sure you can't do THAT on a Presonus! :p