[Bug?]Missing Input labels in AFCC

Fuse AudioFuse
#1

The latest version of AFCC is behaving incredibly well. However, since the last update (2.0), I’ve noticed a couple of things.

Firstly, on the input/output screen, on inputs that aren’t used and don’t have specific names, the input numbers don’t appear until you click on the space as if you were going to change them. Clicking away then reveals the input number. It’s a minor thing, but I’m pretty sure that’s a bug.

Secondly, very occasionally, AFCC loads up but every input/output tag is missing, the preset doesn’t show and instead of the device showing “AudioFuse 16Rig - [Device Name]” it shows the serial number instead of the device name. It has only happened on a few occasions and shutting down AFCC and restarting it fixes it.

Both are minor things, but just wondering if anyone else has experienced this and if Arturia is aware.

FYI, I’m running a Mac Studio M1 Max, 64GB RAM, Sequoia 15.3.2.

#2

HI @Failed_Muso

I’ve relisted this as it sounds like they could be bugs, so The Arturia Devs will see it.

HTH!

1 Like
#3

Hello @Failed_Muso !

Thanks for your report. Even minors bugs should be reported :slight_smile:

The first one is a little GUI issue, I logged it, it will be fixed for the next release.

I’m more interested by the latter, where the AFCC does not initialized well.
Can you confirm some points for me please ?
When you launch the AFCC and this happens:

  • does the 16Rig is already powered since some time (10/20 seconds is enough) ?
  • does the AFCC buttons and faders works ?
  • can you confirm that restarting the AFCC (without rebooting the 16Rig) is fixing the issue ? (It’s what I understand but I just want to be 100% sure)

Thanks for your feedback.

Cheers !

1 Like
#4

I have AFCC set as a launch item at login so it automatically fires up. My power up procedure is always the same and goes in this order…

  1. Turn on Mac
  2. Turn on AF 16Rig, X8 IN and X8 OUT within 10 seconds of turning on Mac
  3. Log in to Mac
  4. AFCC launches

When the issues occurs, AFCC is completely unresponsive. Shutting down AFCC and restarting it fixes the issue.

Let me know if you need anything else.

1 Like
#5

Awesome ! Many thanks for this very clear description of the issue.

I’ll try to reproduce and hopefully fix it in the next release.

Have a good day.
Cheers !