• Registered: 2024-06-28
  • Posts: 7

Topic: ASIO gone Babyface Gen1

Dear Team,

after updating my ancient but still rocksolid Gen1 Babyface to new Driver Version 1250 and updated Firmware, ASIO is completely gone. Totalmix and as device in Windows still works fine.
Tried following:

- different USB Ports
- driver reinstall
- driver rollack to 1246
- entered / left CC Mode
- deleted Fireface Files in system32 before Driver reinstall

Tried 3 different DAWs, Cubase, Bitwig and freshly installed Reaper. My RME Fireface is not selectable as an ASIO Device anymore.
I am on Win10 Pro 10.0.19945.

What could cause this?

Thank you for any hints how to solve this

2 Reply by waedi (edited by waedi 2024-06-29 02:24:48)

  • waedi
  • DAW Mastermind
  • Offline
  • From: Swiss Zürich
  • Registered: 2020-12-08
  • Posts: 4,474

Re: ASIO gone Babyface Gen1

Sure it is not still in CC-mode ?
I would try FUT and reinstall the newest driver and do a cold-reboot of the computer.

M1-Sequoia, Madiface Pro, Digiface USB, Babyface silver and blue
  • Registered: 2024-06-28
  • Posts: 7

Re: ASIO gone Babyface Gen1

nope, in device Manager it is named RME Babyface now, in CC it was "(Serialnumber) + Babyface"

  • waedi
  • DAW Mastermind
  • Offline
  • From: Swiss Zürich
  • Registered: 2020-12-08
  • Posts: 4,474

Re: ASIO gone Babyface Gen1

Is Totalmix working ? The Fireface Settings do open ?

M1-Sequoia, Madiface Pro, Digiface USB, Babyface silver and blue
  • From: Valencia, Spain
  • Registered: 2024-04-18
  • Posts: 57

Re: ASIO gone Babyface Gen1

Hello

Seems you know what you doing, the only advice I can offer is take a look Windows Security (if you are using it) and check if Memory Integrity is enabled, this feature blocks some drivers that Windows could consider "dangeours".

Hope this helps and if RME Staff do not help here I would contact support

UCX II 106/34/104 v1.253 TM1.97 - PC Win11 23H2 / Fedora WS 40 - Reaper 7.25
  • Registered: 2024-06-28
  • Posts: 7

Re: ASIO gone Babyface Gen1

waedi wrote:

Is Totalmix working ? The Fireface Settings do open ?

Yes, all working, i can even audit normally via headphones and "RME Lautsprecher" device.

The only thing missing is to be able to select it as an ASIO Device. Wasapi seems to ve selectable via cubase, then i can go via Windows Devices.

Maybe i try it on my laptop this evening

  • Registered: 2024-06-28
  • Posts: 7

Re: ASIO gone Babyface Gen1

tonpalt wrote:

Hello

Seems you know what you doing, the only advice I can offer is take a look Windows Security (if you are using it) and check if Memory Integrity is enabled, this feature blocks some drivers that Windows could consider "dangeours".

Hope this helps and if RME Staff do not help here I would contact support

Ok, will check that this evening, thank you smile

8 Reply by hziHelmut (edited by hziHelmut 2024-06-29 23:20:50)

  • Registered: 2024-06-28
  • Posts: 7

Re: ASIO gone Babyface Gen1

Ok, i tested it on my laptop and ASIO is present here.
So something messed up on my machine - i can not think off anything i changed between working and non working but the firmware / driver update.

To completely remove the RME Drivers from my System - is it enough to just uninstall it in programs/features and then wipe the rest in device manager/cold reboot?   

Any Regedit stuff that could cause this behavoir?
At least it is not the Babyface Device itself...

9 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 25,557

Re: ASIO gone Babyface Gen1

https://forum.rme-audio.de/viewtopic.ph … 14#p212214

MS no longer allows absolute paths in Windows' own installer, which is the one that we use for driver installation. Realtive paths for ASIO are not supported by several DAWs.

Our workaround: The Windows installer writes relative paths, but after that our own installer overwrites four entries with an absolute path. Examples:

USB Series
HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{Long_string_always_different}\InProcServer32, , C:\Windows\SysWow64\fireface_usb_asio.dll

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{Long_string_always_different}\InProcServer32, , C:\Windows\SysWow64\fireface_usb_asio.dll

Same two entries for fireface_usb_asio_64.dll


MADIface Series
HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{{Long_string_always_different}}\InProcServer32, , C:\Windows\SysWow64\madiface_usb_asio.dll

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Classes\CLSID\{{Long_string_always_different}\InProcServer32, , C:\Windows\SysWow64\madiface_usb_asio.dll

Same two entries for madiface_usb_asio_64.dll


Run a search for these ASIO dlls in regedit to find the matching InProcServer32 entries, and check that InprocServer32 has absolute path (F3 to jump to further finds. Or use a better reg editor like Registry Workshop).


Only in case of updates from an older driver:
The path changes in the registry seem to require either to reboot, or to unplug/replug the device after the driver installation, then reboot. Make sure to perform a complete cold boot. Windows Fast Start is not enough as 'reboot'.

Regards
Matthias Carstens
RME

MC's Website

  • Registered: 2024-06-28
  • Posts: 7

Re: ASIO gone Babyface Gen1

Thank you very much Matthias, this was the right hint.
I had to reproduce the entrys from working maschine and could not place C:\Windows\SysWow64\madiface_usb_asio.dll on all places.
In Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{ECE3DEFE-B1FA-4927-ABBF-F21656F27C39}\InProcServer32
it had to be C:\Windows\system32\fireface_usb_asio_64.dll here.


One Question:
on Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\PnpLockdownFiles\%SystemRoot%/system32/fireface_usb_asio.dll

the Owners Entry contains oem17.inf
!fireface_usb.inf_amd64_e6491b7e50cf2997
!fireface_usb.inf_amd64_d80f9c82c579d8e6

Is the ! some negation? Im just wondering why this differs, on my Laptop with Fireface freshly installed this entry only contains oem120.inf.
Some User Privilege is set here?

Anyways, thank you and anyone else here for you urgent and very helpful responses - you guys are real Pros! smile

11 Reply by MC

  • MC
  • MC
  • Administrator
  • Offline
  • From: Germany/Thailand
  • Registered: 2007-04-06
  • Posts: 25,557

Re: ASIO gone Babyface Gen1

And I already regret to have given all this information - this is a mess!

You added entries to the registry for the MADIface series driver - although you don't use that driver at all?

You modiified entries that did not need any modification? Only the four entries with InProcServer32 must be changed.

I wrote EXAMPLES. The long string after CLSID is different on every computer, so adding my complete example to a computer does not change anything.

(Changed my text in post #9 to prevent further errors).

Regards
Matthias Carstens
RME

MC's Website

  • Registered: 2024-06-28
  • Posts: 7

Re: ASIO gone Babyface Gen1

nah, you misunderstood. I looked on entries on my laptop and compared them to my buggy mainOS before to make no wrong decisions. Absolute Paths i added were once :
C:\Windows\system32\fireface_usb_asio_64.dll
and once C:\Windows\SysWow64\fireface_usb_asio.dll. This was something you did not mention and i had to get from other source (my Laptop...).

Only modified the 4 InProcServer32 entries that were already existing, not any Madiface stuff - Babyface works as expected now, all good smile
Still no clue why it messed up like this.
Thank you again!