Ultima discussione 4 g fa

Forum RME User Forum

forum.rme-audio.de ↗

Forum PunBB in inglese. 12 sezioni seguite: Linux, Product Reviews, user reports, case studies, etc., Vintage stuff, HDSP(e) series, Miscellaneous, TotalMix FX, ADI-2 & 2/4 Pro series, ADI-2 DAC series, AVB/Dante - Network based devices, MADI/AES Premium Line, FireWire & USB series, Tips & Tricks e DIGICheck.

Discussioni al giorno
2
Discussioni raccolte
227
Messaggi al giorno
12
Sezioni
12
Fonti seguite
16
Motore
PunBB

Ultime discussioni

Raccolte ogni 4 ore dal feed pubblico del forum. Riproduciamo solo il titolo, il link e l'inizio del messaggio; ogni link rimanda alla fonte.

Windows Driver Update 1.277 Causing Desktop Issues...

Now the Desktop is loading properly. Not sure what is happening or why, but so far all is fine. Ghosts in the machine. Windows 10 with the latest updates as of 09/27/26 and an RME UFX. I've just updated my driver from 1.276 to 1.277. Upon a Restart, my Desktop does not load properly until I either use Task Manager to Restart Windows Explorer or, once a few Icons appear on my Taskbar, I randomly open an app or two. Using Device Manager to roll back to driver 1.276 and my Desktop loads properly after a Restart. Anyone else experiencing this?

Windows Driver Update 1.277 Causing Desktop Issues...

Now the Desktop is loading properly. Not sure what is happening or why, but so far all is fine. Ghosts in the machine. Windows 10 with the latest updates as of 09/27/26 and an RME UFX. I've just updated my driver from 1.276 to 1.277. Upon a Restart, my Desktop does not load properly until I either use Task Manager to Restart Windows Explorer or, once a few Icons appear on my Taskbar, I randomly open an app or two. Using Device Manager to roll back to driver 1.276 and my Desktop loads properly after a Restart. Anyone else experiencing this?

Windows Driver Update 1.277 Causing Desktop Issues...

Now the Desktop is loading properly. Not sure what is happening or why, but so far all is fine. Ghosts in the machine. Windows 10 with the latest updates as of 09/27/26 and an RME UFX. I've just updated my driver from 1.276 to 1.277. Upon a Restart, my Desktop does not load properly until I either use Task Manager to Restart Windows Explorer or, once a few Icons appear on my Taskbar, I randomly open an app or two. Using Device Manager to roll back to driver 1.276 and my Desktop loads properly after a Restart. Anyone else experiencing this?

Durec playback silent

To make it simple: I activate durec on input channel 9, which has a microphone connected, and on output ADAT 5/6. After recording, i use the rmewavprocessor to produce 1-channel files, and all recorded sound is present as three files: - m g_I_09_vocal.wav - m g_O_19_guitar rec L.wav - m g_O_20_guitar rec L.wav But when I try to play the files back on the UFXII itself, channel 9 playback set to 1 and ADAT 5/6 playback set to 2/3, only the microphone sound is present. It shows signal on ADAT 5/6 (options set to postfx), but it remains silent. I understand, that the microphone file has number nine, since it is channel 9. But I have no idea why the guitar tracks are numbered 19/20. This is the signal path I "invented" to be able to record all channels. Hardware input channels can be recorded and do play back. But some are different: Guitar Input on channel 11. Fader down. In Ableton, source of guitar track is ext. in. channel 9, that goes to a stereo guitar bus, routed to ext. out 5/6. In TotalMix, signal arrives in software playback channels 5/6. Since there is no possibility, to record that in UFX, I route software playback 5/6 to ADAT 5/6 and activate durec recording here. Is that overcomplicated? Actually everything works fine, except that hardware output recordigs stay silent on the interface. Band recordings with many channels are perfectly captured on SSD, but it would be great to immediately hear what we just played in rehearsal. What am I missing? Thanks for all support

Durec playback silent

To make it simple: I activate durec on input channel 9, which has a microphone connected, and on output ADAT 5/6. After recording, i use the rmewavprocessor to produce 1-channel files, and all recorded sound is present as three files: - m g_I_09_vocal.wav - m g_O_19_guitar rec L.wav - m g_O_20_guitar rec L.wav But when I try to play the files back on the UFXII itself, channel 9 playback set to 1 and ADAT 5/6 playback set to 2/3, only the microphone sound is present. It shows signal on ADAT 5/6 (options set to postfx), but it remains silent. I understand, that the microphone file has number nine, since it is channel 9. But I have no idea why the guitar tracks are numbered 19/20. This is the signal path I "invented" to be able to record all channels. Hardware input channels can be recorded and do play back. But some are different: Guitar Input on channel 11. Fader down. In Ableton, source of guitar track is ext. in. channel 9, that goes to a stereo guitar bus, routed to ext. out 5/6. In TotalMix, signal arrives in software playback channels 5/6. Since there is no possibility, to record that in UFX, I route software playback 5/6 to ADAT 5/6 and activate durec recording here. Is that overcomplicated? Actually everything works fine, except that hardware output recordigs stay silent on the interface. Band recordings with many channels are perfectly captured on SSD, but it would be great to immediately hear what we just played in rehearsal. What am I missing? Thanks for all support

Durec playback silent

To make it simple: I activate durec on input channel 9, which has a microphone connected, and on output ADAT 5/6. After recording, i use the rmewavprocessor to produce 1-channel files, and all recorded sound is present as three files: - m g_I_09_vocal.wav - m g_O_19_guitar rec L.wav - m g_O_20_guitar rec L.wav But when I try to play the files back on the UFXII itself, channel 9 playback set to 1 and ADAT 5/6 playback set to 2/3, only the microphone sound is present. It shows signal on ADAT 5/6 (options set to postfx), but it remains silent. I understand, that the microphone file has number nine, since it is channel 9. But I have no idea why the guitar tracks are numbered 19/20. This is the signal path I "invented" to be able to record all channels. Hardware input channels can be recorded and do play back. But some are different: Guitar Input on channel 11. Fader down. In Ableton, source of guitar track is ext. in. channel 9, that goes to a stereo guitar bus, routed to ext. out 5/6. In TotalMix, signal arrives in software playback channels 5/6. Since there is no possibility, to record that in UFX, I route software playback 5/6 to ADAT 5/6 and activate durec recording here. Is that overcomplicated? Actually everything works fine, except that hardware output recordigs stay silent on the interface. Band recordings with many channels are perfectly captured on SSD, but it would be great to immediately hear what we just played in rehearsal. What am I missing? Thanks for all support

MADIface ASIO Driver for Linux (Rocky Linux - RHEL)

It appears to me that Microsoft Windows is moving away from being an Operating System to an Artifical Intelligence engine. It is unavoidable IMHO to start replacing Windows at some point time in the very near future to an alternative OS by not later than e.g. 2-3 years. After long considerations I decided for Rocky Linux, the defacto successor of CentOS, to replace Windows. I. Rocky Linux is binary identical to the industry grade RHEL and has like Windows LTSC a life of 10 years. Now, I'm am wondering if an ASIO driver (MADIface USB) driver could become available for Linux as well. Or is there a workaround for that purpose? I know that there is one available for MacOS, which is a derivative of UNIX, if I'm not wrong. Would it be a big effort to rewrite the MADIface for MacOS code to e.g.a RHEL compatible MADIface version?

MADIface ASIO Driver for Linux (Rocky Linux - RHEL)

It appears to me that Microsoft Windows is moving away from being an Operating System to an Artifical Intelligence engine. It is unavoidable IMHO to start replacing Windows at some point time in the very near future to an alternative OS by not later than e.g. 2-3 years. After long considerations I decided for Rocky Linux, the defacto successor of CentOS, to replace Windows. I. Rocky Linux is binary identical to the industry grade RHEL and has like Windows LTSC a life of 10 years. Now, I'm am wondering if an ASIO driver (MADIface USB) driver could become available for Linux as well. Or is there a workaround for that purpose? I know that there is one available for MacOS, which is a derivative of UNIX, if I'm not wrong. Would it be a big effort to rewrite the MADIface for MacOS code to e.g.a RHEL compatible MADIface version?

MADIface ASIO Driver for Linux (Rocky Linux - RHEL)

It appears to me that Microsoft Windows is moving away from being an Operating System to an Artifical Intelligence engine. It is unavoidable IMHO to start replacing Windows at some point time in the very near future to an alternative OS by not later than e.g. 2-3 years. After long considerations I decided for Rocky Linux, the defacto successor of CentOS, to replace Windows. I. Rocky Linux is binary identical to the industry grade RHEL and has like Windows LTSC a life of 10 years. Now, I'm am wondering if an ASIO driver (MADIface USB) driver could become available for Linux as well. Or is there a workaround for that purpose? I know that there is one available for MacOS, which is a derivative of UNIX, if I'm not wrong. Would it be a big effort to rewrite the MADIface for MacOS code to e.g.a RHEL compatible MADIface version?

Fireface UCX II – request to restore full WDM surround mo

Hello Matthias / RME Support, I am using a Fireface UCX II on Windows 11 with the current Fireface USB driver 1.277. I would like to ask whether it would be possible to restore the full WDM surround mode selection in the Fireface USB driver, similar to what was recently added back to the HDSPe 4.64 driver. What I specifically need is a native 5.1 Side speaker configuration: FL / FR / FC / LFE / SL / SR instead of the current 5.1 Rear configuration: FL / FR / FC / LFE / BL / BR My surround speakers are physically placed at approximately ±110 degrees, and I mainly use the UCX II for native 5.1 PC gaming. For games, these two layouts are not necessarily equivalent. Games and game audio engines can query the Windows WDM speaker configuration and may render the sound field differently depending on whether the last two speakers are reported as Side or Rear. Because of this, remapping the output channels afterward in TotalMix does not really solve the problem. By that point, the game may already have rendered the audio according to the speaker layout reported by Windows. This seems to be the same issue that was discussed in the older Fireface UC thread: “Fireface UCX - 5.1 Speaker Configuration in Windows incorrect” https://forum.rme-audio.de/viewtopic.php?id=29246 Older USB drivers used to offer both 5.1 Side and 5.1 Rear configurations, while later drivers removed the Side 5.1 option and changed 5.1 to rear speakers. There is also a more personal reason why I wanted to ask about t

Fireface UCX II – request to restore full WDM surround mo

Hello Matthias / RME Support, I am using a Fireface UCX II on Windows 11 with the current Fireface USB driver 1.277. I would like to ask whether it would be possible to restore the full WDM surround mode selection in the Fireface USB driver, similar to what was recently added back to the HDSPe 4.64 driver. What I specifically need is a native 5.1 Side speaker configuration: FL / FR / FC / LFE / SL / SR instead of the current 5.1 Rear configuration: FL / FR / FC / LFE / BL / BR My surround speakers are physically placed at approximately ±110 degrees, and I mainly use the UCX II for native 5.1 PC gaming. For games, these two layouts are not necessarily equivalent. Games and game audio engines can query the Windows WDM speaker configuration and may render the sound field differently depending on whether the last two speakers are reported as Side or Rear. Because of this, remapping the output channels afterward in TotalMix does not really solve the problem. By that point, the game may already have rendered the audio according to the speaker layout reported by Windows. This seems to be the same issue that was discussed in the older Fireface UC thread: “Fireface UCX - 5.1 Speaker Configuration in Windows incorrect” https://forum.rme-audio.de/viewtopic.php?id=29246 Older USB drivers used to offer both 5.1 Side and 5.1 Rear configurations, while later drivers removed the Side 5.1 option and changed 5.1 to rear speakers. There is also a more personal reason why I wanted to ask about t

Fireface UCX II – request to restore full WDM surround mo

Hello Matthias / RME Support, I am using a Fireface UCX II on Windows 11 with the current Fireface USB driver 1.277. I would like to ask whether it would be possible to restore the full WDM surround mode selection in the Fireface USB driver, similar to what was recently added back to the HDSPe 4.64 driver. What I specifically need is a native 5.1 Side speaker configuration: FL / FR / FC / LFE / SL / SR instead of the current 5.1 Rear configuration: FL / FR / FC / LFE / BL / BR My surround speakers are physically placed at approximately ±110 degrees, and I mainly use the UCX II for native 5.1 PC gaming. For games, these two layouts are not necessarily equivalent. Games and game audio engines can query the Windows WDM speaker configuration and may render the sound field differently depending on whether the last two speakers are reported as Side or Rear. Because of this, remapping the output channels afterward in TotalMix does not really solve the problem. By that point, the game may already have rendered the audio according to the speaker layout reported by Windows. This seems to be the same issue that was discussed in the older Fireface UC thread: “Fireface UCX - 5.1 Speaker Configuration in Windows incorrect” https://forum.rme-audio.de/viewtopic.php?id=29246 Older USB drivers used to offer both 5.1 Side and 5.1 Rear configurations, while later drivers removed the Side 5.1 option and changed 5.1 to rear speakers. There is also a more personal reason why I wanted to ask about t

227 discussioni raccolte dal 1 settembre 2026. Segui questo forum con una parola chiave →