How this would Handle the HDCP Copyprotection at all

If you use an
Hyperion DPR-16 that has AES EBU Outs
or the Cheepest option

Nuprime-X H16-AES Only AES Outs aviable!

How this Devices feed the Stream to an AES DAC what happen to that Copypotection???

Is that Possibel to use that Card in between at all???

I guess all AES Out streams become PCM Format to an DAC right? And SACD may be DSD or DoP ?

But what happen to HDCP or Copyprotection than???

1.Since users might not have Windows sounds disabled yet you'll get a full blast notification sound - maybe related to https://forum.rme-audio.de/viewtopic.php?id=43300 - not sure if it was a success or error sound

2. You turn down the main volume (since not checked the default connection) and start playback of any fine

Result: Music playing on full blast since default main out is connected to "Phones" instead of "Analog 1/2"

Expected: Default main out is connected to "Analog 1/2" (which I think is the most used output) - with this I wouldn't have get "blasted"

Obviously there are quite a few variables I need to trouble shoot here, but I wanted to try reducing the number of inputs/outputs connecting to Cubase anyway... just because I only need 32 at the moment.

Not saying it's related, but still... just want to run through variables/tests.

Is there a reason I can only reduce down to 128, and not 64 or 32?

In my setup, the main and backup signals from two desks are routed to MADI A-1 and MADI B-2. It would be great if these could be remotely switched to inputs 1–64 via OSC.

Thank you in advance and best regards,
sewi

There's one on sale now, but it's missing the barn doors for two of the ports. ChatGPT said that can be an issue with stable connections, while the seller claims it's working for them. 

So yeah, maybe RME's going to have a sale soon or something Anyone using a RayDAT on Linux? I know there's only community support at this time, but that seems sufficient.

Florian

The only thing that bothered me is that the 8 stereo outputs in windows were all called the same (RME HDSPe AIO), impossible to know which one is which without selecting it.

So I identified the wdm devices and made a script to rename the outputs : enjoy if that's bothering you too ! (elevated powershell)

Add-Type @"
using System;
using System.Runtime.InteropServices;
using System.Security.AccessControl;
using System.Security.Principal;
using Microsoft.Win32;

public class RegOwner {
    [DllImport("advapi32.dll")] static extern bool OpenProcessToken(IntPtr h, int acc, ref IntPtr tok);
    [DllImport("advapi32.dll")] static extern bool LookupPrivilegeValue(string host, string name, ref long luid);
    [DllImport("advapi32.dll")] static extern bool AdjustTokenPrivileges(IntPtr tok, bool dis, ref TP tp, int len, IntPtr p, IntPtr r);
    [StructLayout(LayoutKind.Sequential, Pack=1)]
    struct TP { public int Count; public long Luid; public int Attr; }

    static void EnablePriv(string priv) {
        IntPtr htok = IntPtr.Zero;
        OpenProcessToken(System.Diagnostics.Process.GetCurrentProcess().Handle, 0x28, ref htok);
        TP tp; tp.Count=1; tp.Luid=0; tp.Attr=2;
        LookupPrivilegeValue(null, priv, ref tp.Luid);
        AdjustTokenPrivileges(htok, false, ref tp, 0, IntPtr.Zero, IntPtr.Zero);
    }

    public static void TakeOwnerAndGrant(string subKey) {
        EnablePriv("SeTakeOwnershipPrivilege");
        EnablePriv("SeRestorePrivilege");
        var key = Registry.LocalMachine.OpenSubKey(subKey,
            RegistryKeyPermissionCheck.ReadWriteSubTree,
            RegistryRights.TakeOwnership);
        var acl = key.GetAccessControl(AccessControlSections.None);
        acl.SetOwner(WindowsIdentity.GetCurrent().User);
        key.SetAccessControl(acl);
        var acl2 = key.GetAccessControl();
        acl2.SetAccessRule(new RegistryAccessRule(
            WindowsIdentity.GetCurrent().User,
            RegistryRights.FullControl,
            InheritanceFlags.None, PropagationFlags.None,
            AccessControlType.Allow));
        key.SetAccessControl(acl2);
        key.Close();
    }
}
"@

$names = @{
    "i_hdspwave1_44"   = "AIO Analog 1-2"
    "i_hdspwave4_44"   = "AIO Phones"
    "i_hdspwave5_44"   = "AIO AES"
    "i_hdspwave6_44"   = "AIO SPDIF"
    "i_hdspwave7_44"   = "AIO ADAT 1-2"
    "i_hdspwave8_44"   = "AIO ADAT 3-4"
    "i_hdspwave9_44"   = "AIO ADAT 5-6"
    "i_hdspwavea_44"   = "AIO ADAT 7-8"
    "i_hdspwave7_44_8" = "AIO ADAT 8ch"
}

$render  = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\MMDevices\Audio\Render"
$nameKey = "{a45c254e-df1c-4efd-8020-67d146a850e0},2"
$wdmKey  = "{233164c8-1b2c-4c7d-bc68-b671687a2567},1"
$strip   = '^Microsoft\.PowerShell\.Core\\Registry::HKEY_LOCAL_MACHINE\\'

Get-ChildItem $render | ForEach-Object {
    $propsPath = "$($_.PSPath)\Properties"
    $props = Get-ItemProperty $propsPath -EA SilentlyContinue
    if ($props."{b3f8fa53-0004-438e-9003-51a46e139bfc},6" -notlike "*RME*") { return }

    $wdm = $props.$wdmKey
    $key = ([regex]::Match($wdm, 'i_hdspwave\w+')).Value
    if (-not $names.ContainsKey($key)) { return }

    $nativeSubKey = $propsPath -replace $strip, ''
    [RegOwner]::TakeOwnerAndGrant($nativeSubKey)
    Set-ItemProperty $propsPath -Name $nameKey -Value $names[$key]
    Write-Host "OK: $key -> $($names[$key])"
}

Restart-Service audiosrv

PS : don't know if AIO is the only card concerned, maybe RME could check on that for future updates ?

I attempted to update the firmware of my AoX-D unit using haox_flash_tool_1.3.2-67 under Windows 10, upgrading from the original 1.0 firmware to the latest version.

Unfortunately, the update completed with the following message:
"Programming Status: Failed with error Flash update error , blank"

After quitting the tool and restarting the flash tool again, the unit now reports the following revisions:

PCIe Core: 67

Network Processor: 0.0.0

In addition, my BNC MADI expansion board is showed as “not connected”, although it is physically installed and was working previously.

Another issue is that the Settings tab identified the unit as an AoX-M, and initially both the settings and routing pages showed Milan channels instead of Dante channels, which was quite concerning...

I managed to find an older 1.1 firmware package with its bundled driver, and attempted a downgrade. The downgrade process completed successfully and I restarted the system, but the firmware versions still show:

PCIe Core: 67

Network Processor: 0.0.0

After another reboot, the Dante channels returned in the routing panel, but the BNC expansion board is still not detected (revisions are the same as I listed above).

Could you please advise on the next steps? I noticed in another forum thread that someone received an internal recovery tool to restore the card in a similar situation. If applicable, would it be possible for me to receive that tool as well?

Best,
Antal

Your device ran into a problem and needs to restart.

Stop code:
SYSTEM_THREAD_ EXCEPTION_NOT_HANDLED (0x7E)
What failed:
hdsp_64.sys

What ever driver I try its crashing by hdsp_amd.sys on v4.62 and v4.61
or crashing by hdsp_64.sys

This started happening few days ago and i haven't been able to make it run pass login screen. Always BSOD with error. Even if i remove all drivers as soon i start new driver install it crashes with the same error.

Is this card dead? Anyone with same issues?

Thanks