X32 Firmware 4.06

[Madelyn Westfall]

Werecommend to periodically check for new updates, for the latest features and improvements. Our development team is eager to react to customer suggestions and to amaze you with improvements and new features. Visit behringer.com to download the latest firmware, install the update and enjoy the full potential of your X32.

If you were using your P16 b4 upgrade, make sure your CAT6 is connected to X32 console to your stagebox or direct to the P16. Go to ROUTING move the arrow key to P16 you will see your precious settings.

I have a poorly performing Pegasus 2 R8 unit that I am trying to troubleshoot. A colleague reconfigured it from Raid0 to Raid5 earlier this year. When I attempt to configure it back to Raid0, I am getting extremely poor performance - erratic r/w speed compared to how it was originally performing before being switched to Raid5.

Disk health appears to be all OK. In an attempt to fix, I downloaded the most recent firmware but am getting a CRC error when I try to execute the firmware upgrade. I tried to update via CLI, but hit the same CRC error. I tried different versions of the firmware - including the original 2015 firmware already on the Pegasus - but still the same error.

Just an FYI. After investigation it turns out that there is an issue with the latest Pegasus32 Promise Utility (4.06.0000.04) and it will give a CRC error when attemptin to update firmware on the Pegasus2. This will be fixed next Promise Utility release, but the workaround is to use an earlier version of the Promise Utility. Version 4.06.0000.01 has been tested and works when updating firmware on a Pegasus2.

Having the same CRC error trying to update the firmware of a Pegasus2 R6 wiht Promise Utility 4.06.0000.04. Fails with CRC error. Fails using terminal. I did what was suggested here and reverted back to Promise Utility 4.06.0000.01. The problem is that when you use check updates, the first and only item that shows up is an upgrade to 4.06.0000.04, which is proven not to work, The firmware update is not shown. The solution is to revert to 4.06.0000.01, manually download the firmware file, and thengo into terminal and type below. This took many many hours to figure this out. Had to piece several different posts,

You can update firmware from the Promise Utility as well, as mentioned previously, go to the promise downloads page and manually download the firmware file. To update firmware, unlock the Promise Utility and navigate to the Admin tab on the top bar, 'firmware update' is one of the options.

Hey guys, my Mac (ventura) detects fireface in class compliant mode. But when CC mode is off, the driver 4.06 is NOT working. I've allowed those drivers to not be blocked, but wit comes with a sample rate of 32000 HZ, meaning the Mac is not even detecting the hardware, flash tool is also not working so I can't even update the hardware. Can anyone help?

Hello, I installed 4.06 driver (clicked allow in settings and rebooted my mac), and I see that device is recognised in the Fireface USB Settings app. However my mac and total mix do not see it, as well as other apps. I'm on Ventura 13.0.1 (For the reference I tried to install previous version of the driver couple weeks ago when I was on Monterrey - it was the same thing)

Is there any indication on when the DriverKit driver will come out of beta, and become official? There's got to be some Apple deadline, right? Just this week when I updated to Ventura 13.1, macOS warned me that the current RME driver will not be supported in future versions - without being any more specific.

I've done a fresh install of Ventura with 4.06, and the volume control issue I had has gotten worse. Not only do I lose the ability to control volume with my volume keys on the keyboard/OS itself, I can no longer use the physical volume knob on my Fireface UC to 'reset' the bug to allow physical volume key controls. Only thing that fixes it now is a soft reboot of macOS.

To reiterate the issue, after an extended period of uptime, pressing the volume up/down keys on the keyboard brings up the volume up/down display, but nothing happens. Volume stays the same. Even if using the volume slider in the mission control/top right hand corner menu bar, it will not control audio. Changing the volume via the Fireface UC knob itself 'fixed' the issue until it came back, which required another turn of the dial. This workaround no longer works post fresh install.

The system becomes very sluggish every now and then. The problem seems to be with TotalMix, which sometimes uses up to 100% cpu time. The mouse moves very erratic (stays at one point, then jumps to the next, etc), and mouse clicks are not registered or only after several seconds.

And indeed, after upgrading to 11.7.2 today, the driver wasn't loaded and the UFX wasn't recognized. I reinstalled 3.27, rebooted, and it is working again. Bit disappointed in this. Please let me know if I can help in any way, send log files, whatever.

There is a major problem when I use Logic Pro X with my BF Pro FS in Native mode. When you hit play it just keeps stuttering. If I switch to another interface or the Mac's internal interface the problem stops completely. When logic is used in rosetta mode the session opens fine with my RME interface. This points to a driver issue which is causing the playback to stutter when Logic is running in native mode. I have tried with Logic's internal plugins or with plugins that run natively but the problem persists on the RME interface. No issues when used with another interface! Hopefully this problem can be fixed when the final version of the driver comes out. Without that the interface is completely unusable in native mode. The same session runs smoothly with my Fireface 800!

Yes, from finder its fine. Only playing from the DAW is the issue. I also own a fireface800 and there is no problem at all with that. So its an issue with the usb driver that works with the Babyface Pro FS...

I have tried the driver 327 and the latest 4.06 beta and both creates the same kind of clicks and momentary stops the music, using Ableton with a basic project with less than 10 tracks.

I have already uploaded the new firmware.

Hi guys,

I just switched my old Mac Pro for a mint Mac Studio, with Monterey.

My audio interface is one of the first Fireface UFX, version 1.58 (It seems to me that I couldn't update it when I wanted to add the remote controller years ago because it was one of the first ones).

Dumb question but did you connect your Fireface directly to your MacBook or are you using an USB hub?

This could cause severe issues at least if caused dropouts and breaks / stops with logic pro.

Actually starting to experience some dropouts and issues when recording within Ableton Live. 32bit/88k. Normally works without any issues. Also starting to glitch within Zoom. Currently on MacOS Ventura 13.1.

Okay so after sitting down and testing, it doesn't seem to be the driver. Switching USB ports seems to have fixed the issue so seems more like a failing port. No glitches since. I'll continue to monitor.

MC, there is definitely something up with Apple's OS. I decided to try one more time, installing the 327DK to remove, and then 4.06 Driver fresh install. Now the UFX+ is discovered with USB2.0 or USB3.0 cable and I am not getting the glitches via either cable type. I was definitely on 4.06 when I tested this yesterday, and the firmware was already 54. It's as though there is some bug in MacOS where a driver is installed partially or with some kind of restriction on i/o, because today this works as I'd expect it to work, and the only change has been removal of driver and reinstall of Driverkit. I am very exasperated with how many things do not work properly on the current machines/OS. I can't even update this year old MBP16 to Ventura as the OS update fails to complete and bricks the entire machine requiring a revert to Monterey.

3a8082e126