RME HDFX_1.0.7.0 Microphone Driver for Windows XP/Vista/7/8/8.1/10 (x86;x64)
Driver Info
Driver Date
28.11.2012File Size:
1.46 MBDownload URL:
https://download.mictests.com/drivers/audio/RME/HDFX-1-0-7-0/Windows.zipMD5 Hash:
c526b87c48523cdc0afcfdd4bec23923Operating System
Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10OS Architecture
x86, x64Manufacturer
RMEDriver Files
- /TotalMixFX.chm
- /TotalMixFX.exe
- /hdspe_fx.cat
- /hdspe_fx.exe
- /hdspe_fx.inf
- /hdspe_fx.sys
- /hdspe_fx_64.sys
- /hdspe_fx_asio.dll
- /hdspe_fx_asio_64.dll
- /liesmich.txt
- /readme.txt
Driver Strings
[liesmich.txt]RME Intelligent Audio Solutions
HDSPe MADI FX
Treiber f?r Windows XP/Vista/7/8, 32 und 64 Bit
Wichtige Informationen: Treiber Version 1.07
Dies ist der Treiber der HDSPe MADI FX. Er unterst?tzt kein anderes RME Audiointerface.
Hinweise zum Treiber
-----------------
- Die HDSPe MADI FX erfordert eine aktuelle Version von DIGICheck.
Installation
-------------
Neuester Treiber:
http://www.rme-audio.de/download/hdspe_fx_win_xxx.zip
Neueste Firmware:
http://www.rme-audio.de/download/fut_hdspe_fx_win.zip
Die Firmware kann nur aktualisiert werden wenn der Treiber bereits installiert ist.
Sowohl Treiberinstallation als auch Firmware-Update sind im Handbuch detailliert beschrieben!
*** Erstmalige Installation von RME Audio Interfaces unter Windows 7 ***
Die im Handbuch beschriebene Vorgehensweise ist korrekt und bleibt weiter g?ltig, bis auf den Start der Treiberinstallation. In Windows 7 hat Microsoft den automatischen Start des Treibersoftware-Aktualisieren-Dialogs entfernt. Daher muss nach der fehlgeschlagenen Installation der Dialog manuell gestartet werden.
- Taste Win, Ger?te-Manager eingeben, und diesen per Enter aus der Liste starten.
- Das Ger?t erscheint mit einem gelben Warndreieck. Normalerweise schon korrekt in der Rubrik Audio-, Video- und Gamecontroller (Plug & Play erkennt ein Multimedia-Ger?t).
- Mit rechter Maustaste auf das Ger?t klicken, im Kontextmen? 'Treibersoftware aktualisieren' ausw?hlen.
- Es erscheint der Dialog 'Treibersoftware aktualisieren'. Die restliche Vorgehensweise entspricht der im Handbuch beschriebenen.
----------------------
1.07, 29.11.2012
- TotalMix FX 0.988
- Der Start einer Audioaufnahme f?hrt nicht mehr zum Stop einer bereits laufenden MIDI-Aufnahme
- AC-3 Playback steuert das Non Audio Bit am AES-Ausgang
- Kan?le unter ASIO umsortiert, AES und Phones ganz hinten.
- Hinweis: Die Option 'Optimize for multi-client mixing' arbeitet nicht bei einer Buffer Size von 4096
----------------------
1.06, 09.11.2012
- TotalMix FX 0.986
- Unterst?tzt internen Sync (erfordert Firmware 84-16 oder h?her)
----------------------
1.05, 10.09.2012
- ASIO Direct Monitoring war deaktiviert
----------------------
1.04, 05.09.2012
- TotalMix FX 0.984
----------------------
1.03, 05.07.2012
- TotalMix FX 0.983
- Some smaller changes
----------------------
Copyright RME 11/2012
Alle Rechte vorbehalten. Windows XP/Vista/7/8 sind Warenzeichen der Microsoft Corporation. ASIO ist ein Warenzeichen der Steinberg Media Technologies GmbH.
[readme.txt]
RME Intelligent Audio Solutions
HDSPe MADI FX
Driver for Windows XP/Vista/7/8, 32 and 64 Bit
Important information: Driver version 1.07
This is the Windows driver of the HDSPe MADI FX. No other RME audio interface is supported.
Notes on the driver
-----------------
- The HDSPe MADI FX requires the latest version of DIGICheck.
Installation
-------------
Latest driver:
http://www.rme-audio.com/download/hdspe_fx_win_xxx.zip
Latest firmware:
http://www.rme-audio.de/download/fut_hdspe_fx_win.zip
The firmware update is not possible unless the driver had been installed before.
Both driver installation and flash update are explained in detail in the manual!
*** First time installation of RME Audio Interfaces under Windows 7 ***
The procedure and instructions found in the manual are correct and stay valid, except for the start of the installation. In Windows 7 Microsoft removed the automatic start of the Driver Software Update dialog. Therefore this dialog has to be started manually after the failed driver installation.
- Hit the Win key, type 'Device Manager', start the Device Manager by selecting it from the list and hit Return.
- The device is shown with a yellow warning symbol. Usually it is already found in the correct category, Sound, Video and Game Controller (Plug & Play detects a multimedia device).
- Right click on the device and select 'Update Driver Software' from the context menu.
- The dialog 'Update Driver Software' appears. Now follow the instructions given in the manual.
----------------------
1.07, 11/29/2012
- TotalMix FX 0.988
- Starting audio recording does no longer stop an already runing MIDI recording
- AC-3 playback steers Non Audio Bit at the AES output
- Channel order under ASIO changed, MADI now starts with channel 1
- Note: The option 'optimize for multi-client mixing' does not work with a buffer size of 4096
----------------------
1.06, 11/09/2012
- TotalMix FX 0.986
- Supports internal Sync (requires firmware 84-16 or higher)
----------------------
1.05, 09/10/2012
- ASIO Direct Monitoring had not been active
----------------------
1.04, 09/05/2012
- TotalMix FX 0.984
----------------------
1.03, 07/05/2012
- TotalMix FX 0.983
- Some smaller changes
----------------------
Copyright RME 11/2012
All rights reserved. Windows XP/Vista/7/8 are trademarks of Microsoft Corporation. ASIO is a trademark of Steinberg Media Technologies GmbH.
Devices Information
-
/hdspe_fx.inf
[ids]- PCI\VEN_10EE&DEV_3FC7&REV_D5
- PCI\VEN_10EE&DEV_3FC7&REV_D6
[version]- Signature
$Windows NT$ - Class
MEDIA - ClassGUID
{4d36e96c-e325-11ce-bfc1-08002be10318} - Provider
RME - DriverVer
11/29/2012,1.0.7.0 - CatalogFile
hdspe_fx.cat
[strings]- MediaCategories
SYSTEM\CurrentControlSet\Control\MediaCategories - GUID.Analog_12
{BE8C3700-EE19-4411-AFB2-C14F37B770F2} - GUID.AES1
{BE8C3711-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX1
{BE8C3719-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX2
{BE8C371A-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX3
{BE8C371B-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX4
{BE8C371C-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX5
{BE8C371D-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX6
{BE8C371E-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX7
{BE8C371F-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX8
{BE8C3720-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX9
{BE8C3721-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX10
{BE8C3722-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX11
{BE8C3723-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX12
{BE8C3724-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX13
{BE8C3725-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX14
{BE8C3726-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX15
{BE8C3727-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX16
{BE8C3728-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX17
{BE8C3729-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX18
{BE8C372A-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX19
{BE8C372B-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX20
{BE8C372C-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX21
{BE8C372D-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX22
{BE8C372E-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX23
{BE8C372F-EE19-4411-AFB2-C14F37B770F2} - GUID.MADIFX24
{BE8C3730-EE19-4411-AFB2-C14F37B770F2} - GUID.Phones
{BE8C3744-EE19-4411-AFB2-C14F37B770F2} - DiskDescription
RME Driver Installation Disk - DeviceDescMadi
RME HDSPe MADI FX - DeviceDescMadiface
RME MADIface XT - hdspe_fx.DeviceDesc
RME HDSPe FX series PnP driver - hdspe_fx.SvcDesc
RME HDSPe FX Audio Device - hdspe_fx.Wave1.szPname
HDSPe FX Analog - hdspe_fx.Wave2.szPname
HDSPe FX AES - hdspe_fx.Wave3.szPname
HDSPe FX Phones - hdspe_fx.Wave4.szPname
HDSPe FX MADI (1-8) - hdspe_fx.Wave5.szPname
HDSPe FX MADI (9-16) - hdspe_fx.Wave6.szPname
HDSPe FX MADI (17-24) - hdspe_fx.Wave7.szPname
HDSPe FX MADI (25-32) - hdspe_fx.Wave8.szPname
HDSPe FX MADI (33-40) - hdspe_fx.Wave9.szPname
HDSPe FX MADI (41-48) - hdspe_fx.Wave10.szPname
HDSPe FX MADI (49-56) - hdspe_fx.Wave11.szPname
HDSPe FX MADI (57-64) - hdspe_fx.Wave12.szPname
HDSPe FX MADI (65-72) - hdspe_fx.Wave13.szPname
HDSPe FX MADI (73-80) - hdspe_fx.Wave14.szPname
HDSPe FX MADI (81-88) - hdspe_fx.Wave15.szPname
HDSPe FX MADI (89-96) - hdspe_fx.Wave16.szPname
HDSPe FX MADI (97-104) - hdspe_fx.Wave17.szPname
HDSPe FX MADI (105-112) - hdspe_fx.Wave18.szPname
HDSPe FX MADI (113-120) - hdspe_fx.Wave19.szPname
HDSPe FX MADI (121-128) - hdspe_fx.Wave20.szPname
HDSPe FX MADI (129-136) - hdspe_fx.Wave21.szPname
HDSPe FX MADI (137-144) - hdspe_fx.Wave22.szPname
HDSPe FX MADI (145-152) - hdspe_fx.Wave23.szPname
HDSPe FX MADI (153-160) - hdspe_fx.Wave24.szPname
HDSPe FX MADI (161-168) - hdspe_fx.Wave25.szPname
HDSPe FX MADI (169-176) - hdspe_fx.Wave26.szPname
HDSPe FX MADI (177-184) - hdspe_fx.Wave27.szPname
HDSPe FX MADI (185-192) - hdspe_fx.Midi1.szPname
HDSPe FX MIDI - hdspe_fx.Midi2.szPname
HDSPe FX MADI1 MIDI - hdspe_fx.Midi3.szPname
HDSPe FX MADI2 MIDI - hdspe_fx.Midi4.szPname
HDSPe FX MADI3 MIDI - KSNAME_Wave1
hmfxwave0 - KSNAME_Wave2
hmfxwave1 - KSNAME_Wave3
hmfxwave2 - KSNAME_Wave4
hmfxwave3 - KSNAME_Wave5
hmfxwave4 - KSNAME_Wave6
hmfxwave5 - KSNAME_Wave7
hmfxwave6 - KSNAME_Wave8
hmfxwave7 - KSNAME_Wave9
hmfxwave8 - KSNAME_Wave10
hmfxwave9 - KSNAME_Wave11
hmfxwaveA - KSNAME_Wave12
hmfxwaveB - KSNAME_Wave13
hmfxwaveC - KSNAME_Wave14
hmfxwaveD - KSNAME_Wave15
hmfxwaveE - KSNAME_Wave16
hmfxwaveF - KSNAME_Wave17
hmfxwaveG - KSNAME_Wave18
hmfxwaveH - KSNAME_Wave19
hmfxwaveI - KSNAME_Wave20
hmfxwaveJ - KSNAME_Wave21
hmfxwaveK - KSNAME_Wave22
hmfxwaveL - KSNAME_Wave23
hmfxwaveM - KSNAME_Wave24
hmfxwaveN - KSNAME_Wave25
hmfxwaveO - KSNAME_Wave26
hmfxwaveP - KSNAME_Wave27
hmfxwaveQ - KSNAME_Midi1
hmfxmidi1 - KSNAME_Midi2
hmfxmidi2 - KSNAME_Midi3
hmfxmidi3 - KSNAME_Midi4
hmfxmidi4 - Proxy.CLSID
{17CCA71B-ECD7-11D0-B908-00A0C9223196} - KSCATEGORY_AUDIO
{6994AD04-93EF-11D0-A3CC-00A0C9223196} - KSCATEGORY_RENDER
{65E8773E-8F56-11D0-A3B9-00A0C9223196} - KSCATEGORY_CAPTURE
{65E8773D-8F56-11D0-A3B9-00A0C9223196} - ASIO_NAME
ASIO HDSPe FX - ASIO_GUID
{164D78FD-5AD0-48b3-8CAC-E08471200D5B}