AFCC Update changed names of the system audio channels (Windows) + Rant about the routing matrix

Fuse AudioFuse
#1

(AudioFuse 16rig owner here)

Hey all

So first, a rant because I updated AFCC to the last version published weeks ago and that renamed all the channels on Windows.
This wouldnt be important if the visiocall softwares werent relying on that and were all fucked up. Then it took me a while to find again which channels were supposed to do what.

Which leads me into another related rant :
The routing grid might be super flexible, it’s a massive PITA to decypher when you need to quickly connect 2 things, in addition to be actually weirdly restricted. I just want to capture loopback but nothing gets into loopback. I have a complicated setup just because of that, using auxes to reroute my main mix into a free pair of channels that I can use to make people in visio calls hear what I hear exactly.

This is super painful. I wish Arturia would provide an alternative interface to that routing grid that would just be like the recent Focusrite interface where you just say This Input goes into That channel. It’s just a form, a sequence of statements about what goes where.

breath

Ok now I ranted I can go back to work.

#2

Hi Klaim, your rant justified !

A few things that might help:

• Renamed channels: Windows and call apps remember devices by name, so the update broke their saved picks.

Reselect in each app + set the right one as Default Communication Device in the classic Sound panel.
You can also rename endpoints yourself (Sound panel > Properties) to something like “Call Out” so it’s readable. Might get reset on the next driver update though.

• Loopback: On Windows it doesn’t show up in the AFCC matrix and seems ASIO-only, and forum users hit the exact same wall. Your aux reroute is basically the right workaround for now.

• The “this input goes to that output” idea is a good one, and MiniFuse already has something closer with SLS. I’ll pass it on to the AFCC team along with the renaming issue.

1 Like
#3

Thanks!

Note about the first point: for some reason the default devices in windows didn’t change (I properly set them every time there is a new audio device plugged in for the first time), it’s only the names.
I’m not sure why that confused the visiocall softwares because I thought they would identify audio devices without the name, but maybe not. OR their “id” changed when we update AFCC?