Fantastic!

Thank you for not only supporting Arm64 Windows with this release, but for doing so for both your in-market USB devices and your past devices. That's excellent for everyone.

Pete
Microsoft

That's Awesome Matthias,

Congrats to you and the whole team, again going above and beyond regards not only developing and releasing the drivers for Windows/arm so quickly, but also ensuring support for the USB interfaces for the last 15 years.

I have always told my clients that RME is a lifetime investment , and you prove it yet again.

I am sure this will generate some good momentum for the Windows users wanting a good mobile solution, looking forward to diving in.

We don't see that and don't want to see (read support) that, sorry.

RME is amazing!!!

Are ARM chips the future for Windows systems?
What is your assessment?

wonderful news .Thanks MC and the team for once again proving why RME are still at the top of the Audio device tree after all these years.

It's not somethingk I'll use personally for a good while I think but I'm so happy to see this as i think Windows ARM has the potential to really challenge Mac Sillicone.

M

No. Maybe it will find its way to certain segment of gear, but trully ARM has no real advantage over x86. Even in consumption if the same node is used.)

Part of x86 apps will be ported to ARM and part never will be ported. And part of it even will not run on ARM. So, ARM will not replace x86 in foreseen future.

I personally do not see any reason go for ARM.

I don't, know my $1000 Samsung X Elite is considerably more powerful than my Macbook Max M1 and runs Windows (yay) quietly with a numeric keyboard!

I decided to give the new driver a spin after for some reason, the latest official driver would sometimes suddenly disconnect my Babyface Pro FS. The cable side on my laptop and interface are both tightly plugged in, I've checked.

Well, the new driver hasn't disconnected my Babyface in whatever way since I installed it 2 days ago. Also, I feel the over all stability of the driver has been much improved! I don't have an ARM machine, but if in the future I'm upgrading to an ARM PC, I won't worry because RME has got my back. Bravo!!!

Happy new year!!!

Is the problem that the BF Pro disconnects gone? I have exact the same problem and tried 1001 hacks and improvements with no luck so far (cable, no power-saving for USB, CPU optimized not to go to sleep states and what-not). I have an "old" AKM Babyface Pro FS btw.

I tried to install the new v1.270 on my AMD Zen+ computer using the uninstaller via rmeinstaller.exe but the result is the previous v1.260, also TotalMix v1.98 does not install and remains v1.97.

Please, what should I do?

Thanks MC, all right.

Thanks, will be added.

Trying to install 1.270 on Windows 10 with a Babyface Pro FS. Have tried installing, uninstalling, restarting, ect. multiple times and noticed the version numbers are not changing in the About section of the Fireface USB settings, saying 1.253. Also, TotalMix says 1.97, not 1.98. The installer is claiming it has installed successfully. Simple oversight or is 1.270 not installing for me?

Windows 10 22H2 x64 over here.

Yes, but I ended up fixing it just now. I uninstalled every old Fireface driver through Windows' uninstaller in the control panel, there were 7 different versions sitting there. In fact, 3 of them are still there, but they won't uninstall lol. But we're 1.270 and Totalmix 1.98 now!! Hoping I can change buffer sizes without horrible glitches and having to unplug and replug the Babyface in now!

EDIT: Spoke too soon. ASIO won't show up. Downgraded to 1.253, ASIO won't show up there either. Something is horribly wrong, I'll keep banging my head against the wall for now

EDIT 2: Sorry for having a soapbox here. Turns out my usb port is totally wrecked from having to unplug and replug constantly. Emailing support now!

The new driver even has an uninstaller, wow

What does this return code from installer / pnputil mean?
Usually "0" means everything ok, does "0xE000023D" indicate an issue?

According to ChatGPT (as google search failed) it means
"The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering."
But also ChatGPT claimed that there is no list of return codes available, this information is from online postings
around issues with graphic driver installation where the same return code is being mentioned.

I had a fresh installation of Windows 10 and MADIface driver 0.9845.
How can this happen? Can I trust those messages?

Sadly, I found no complete list of return codes on the internet.

One more observation: During the driver uninstallation, numerous messages flash across the screen, showing e.g. which registry entries are being deleted.

Is there a way to generate an uninstallation log or capture these messages in a separate window,
with the option to copy them to the clipboard or save the log to a file?

Many thanks.

After driver installation and reboot, all is ok.
Only the WDM driver needed to be re-configured, maybe due to the uninstallation at first.

The latest revision of the 1270 driver works well on my PC. The only thing is, both Total Mix FX and RME USB Settings are not listed in the "startup items" on Windows Tax Manager, and so both programs are not automatically starting up for me. This is strange, as previous driver versions would always auto start when the system reboots. Not this version, though.

Edit: I manually added the programs into the startup folder of my user account by first opening the folder through the Run dialogue: typing "shell:startup" to open it, then I copied the files.

Hopefully the installer could still do it by itself in the next version.

Wasnt It you who was so dismissive about this topic a few months ago and discouraged the topic In a rather rude way to users inquiring if RME would support ARM? Well now

If you happen to be at the NAMM Show next week, visit the Qualcomm Snapdragon booth. We'll have Arm64 PCs and interfaces, including some from RME, plus apps like Cubase, Bitwig Studio, REAPER, and more.

Pete
Microsoft

Is there any benefit to update the current driver 2024-12-18 (driver_madiface_win_09845.zip) in Windows 10 x64 Ver. 22H2 to the latest driver 2025-01-13 (driver_madiface_win_10.zip)? The system runs on a 64-bit Intel processor and uses only the RME ADI-2/4 PRO SE device.

I'm back, with my shiny new Babyface. ASIO is still broken. It just doesnt show up, I've tried FL Studio and Reaper. I can see the fireface_asio_amd.dll and fireface_asio_x86.dll files in the Program Files, but nothing... and then I noticed something just now.
In the readme, there is zero mention of AMD processors, only Intel and ARM. Are AMD processors no longer supported? If I upgrade to Windows 11 with my AMD processor, will these drivers work?

Also, like another user, I had to manually add Totalmix and the Fireface settings to my startup, they no longer automatically start up.

Done all of that multiple times, nothing. I think something is horribly wrong with my Windows, maybe in the registry. I'm currently getting ready to dual boot into a fresh Windows 11 to see what happens. Even when I install older versions of the drivers that previously worked, ASIO just doesn't appear with any of them. The Babyface still pops up and works as a standard audio device, it just doesn't have ASIO. I'll report back, for anyone else in the future googling this that might have the same issues.

EDIT: Fixed it once and for all. I created a dual boot of Windows 11 and installed the drivers there, which worked perfectly. So I went into the registry, searched for ASIO, took a screenshot of every single instance, then came back to Windows 10 and typed out every key and value by hand in every possible directory.
Knowing that my drivers are currently being propped up by 3 toothpicks and scotch tape isn't the best feeling, but it's working perfectly. Something went wrong in the installer, that's all I know.

I found this topic from a while back that seems to be providing the same solution, wish I found it earlier: https://forum.rme-audio.de/viewtopic.ph … 14#p212214
Hope this all helps someone somehow!