PPS: Other applications like RX advanced show the same wrong output-order now, although the driver setting says differently:

Hi Matthias,

what an honour! :-) You were the one who introduced me to RME hardware during a trade-show of the last millennium. Thanks for taking care!

I just tried to counter-intuitively change the order in the Global-tab, which in facts makes Nuendo "see" the cards in a different order again, but still all the settings created for this system aren't valid anymore (see screenshot):

Looks strange, if you ask me ... 8-/

TIA for any info!

/Dietz

I am confused. You need the AES card to be the first ASIO device? But your screenshot shows that you 'sorted' the MADI card as first. After Apply restart the ASIO host.

PS: It seems as it is a hardware-problem rather than a settings issue. This DAW is a dual-boot hybrid, so I'm able to use OS-X with the very same hardware. ProTools sees both cards as expected, but like under Windows there's no sound produced by the AES card, just by the MADI card.

Strangely enough the TotalMix loop-back of the AES-card that feeds DigiCheck NG works as expected.

... seems as there's something broken on the physical output-side of that card.

Thanks for your help, Matthias.

I followed your advice thoroughly, although I didn't completely understand the "WDM"-part of your message.

In fact, both cards are now working again, so it may indeed have been a hardware issue that caused the initial problem. But the order of the cards shown by the ASIO driver is still reversed. Is there any way (for mere mortals like me) to fix this?

That's exactly the problem: Global tab's card order says "AES = (1), MADI = (2). Still the ASIO driver as seen by applications like RX or Nuendo reads: "AES = (2), MADI = (1)".

The device number in the brackets is crucial for ASIO applications, it seems. Nuendo's routing relies on it entirely, for example. All existing projects will open without (or with erratical) output routing.

Of course I could re-route everything now, but this is a no-no in case of more complex setups (hardware I/Os, for example) ---- and what if this order changes out of nothing _again_?

Re: "Reset all I/Os": That's part of the problem: It just doesn't get reset, at least not the part that's seen by the ASIO applications. I just had an hour-long TeamViewer-session with my system assembler, but neither him nor I can find the place where this info got stored. Maybe the file is write-protected, somehow? (I do all of this with Administrator rights).

... I'm sure _you_ know where Windows stores this data, don't you?

TIA,

/Dietz

Huh! 8-/

I already removed and re-inserted both cards, I re-installed the drivers - still nothing changed in the way how the cards are presented within the ASIO applications. If there's just one of the two, there's no additional numbering in brackets shown. As soon as there are both the numbering is there, and since two days it's wrong.

I can't easily swap the slots on the MoBo, but I'll keep that in mind as last resort.

Is this something Steinberg people should know about (after all, only the ASIO-side of things is concerned)? Or is this purely a Microsoft issue? ... but everything is fine in Windows itself.

TIA,

/Dietz

Steinberg might need the number to identify multiple identical cards, but as our driver integrates these into one I am not sure this is really needed.

DC Playback (and maybe more) is not (yet) compatible to the manually changed card order, so if you need that you should reverse the swap in the Global tap.