Correct.

No.

Thank you for all the answers,
@Marc S: my problem is that in the AVB Network the Digiface is noticed as the same interface wheter the Digiface A or the Digiface B is connected. Totalmix does notice the difference. The inputstreams of the m32 and 1610 notice that this are different interfaces but the Digiface uses the same input streams. Here are the screenshots:
https://www.dropbox.com/s/wz3i6tf1x4tmj … 5.png?dl=0
this is the Digiface A in the 1610 environment and this:
https://www.dropbox.com/s/j3k9zhowh1ztl … 3.png?dl=0
is the Digiface B in the m32 environment. The Digiface inputstrems stay the same thou it are different Cards and the streams were connected to the m32 ad. Thats what I meant with "computers" and "soundcards".

@MC: I thought with the storage of setups I could work arround this problem.

@uwekirst: thank you for the info

I allready tried. Keeps The Name Digiface A thou I am connected to the Digiface B. Thats why i renamed it to "Digiface". When an other computer is connected it shows RME Digiface when you don't rename it. Thou it's named otherwise in my computer the Digifaces keep the name an other computer gives them. This works when you have one Digiface in your setup, but not when you have more.

Wait, now that I reread your initial post and have a second look at the screen shots: You do have 2 Mac systems right?
It's not that you have both Digifaces connected to one Mac, correct? Because that won't work. Each computer only supports one connected Digiface at a time.

Everybody in the studio should be able to use his/her own laptop. With the setup stored to the digiface depending in what room they are ( what digiface they are connected to). Thats what I thought would be possible. Normally there work two systems the same time, sometimes with different samplesrates. So the systems shouldn‘t be connected. Sometimes you set the system up that you get 1 avb stream from the other studio. (Thou this is not the usual working case it should work undependent and the computer should react to the interface connected)

Hi Marc S,
Yes, regarding your last paragraph it is correct. The solution would be that the computer would identify the digiface by the hardware id. That would also be the case if somebody uses a digiface in the studio and anotherone at home.
Will it be possible to change that? Or at least  a workarround with the storage of different inputstream setups (on the computer, when there is no non-voltatile storage on the hardware)

Hey there blacknap,

Did you ever find a solution to this? Like a human solution or differing approach?

We've just done the same thing in our research lab of three rooms using one AVB network, I didn't anticipate that the digiface's would be this difficult to handle and it's a big mess...

To Marc S:

"So what you request is that the RME application on the computer stores one setup per hardware id, correct? So that when you connect Digiface A to Computer 1, and then swap it with Digiface B to Computer 1, they show up as different devices with different settings and thus make different connections within the network?"

Yes! And also when there are multiple users (digiface avb) on the network, they don't all show up with the same name!

I have other issues that would be solved with non-volatile memory, but perhaps there is a way to store the stream assignments via the device it is connected to? E.g. a 12Mic, or a 1620?

Please help Marc!

The digiface AVB Controller supports storing the configuration of the (current) selected device or of all devices detected in a network in one file / a set of files. Storing is by network id (mac address). The solution in you case should be just reopen the file with the configuration you want after you connected the digiface. The loading will fail of course, if the mac address(es) stored in the file(s) do(es) not exist within the network. The files are .xlm, so you can view them.