With all of the identified issues regarding MIDI, when can we expect an update to resolve these issues? I’m sure you have all been busy with the software and newly released hardware but please don’t leave us hanging.
Yep, the midi situation definitively needs some improvements.
I’ve recently noticed some pretty severe midi jitter in my set up with 16rig. What issues have been identified? I’ve taken a look around the forum specific to the 16rig and haven’t come across people experiencing similar things, so I assumed it was some other component of my set up. It seems to have to do with MPE data in my case…
Yay for the update. I’m not sure it affects anything I’m currently using the device for, and there have been no MIDI issue updates. I appreciate that you are working to improve, but can we focus on the items people have brought forward? MIDI needs to be fixed, please.
They did improve one thing I requested. Adding dB range below -60dB, so it doesn’t immediately drop off from audible sound to nothing.
AudioFuse 16Rig firmware update 1.3.3 and AudioFuse Control Center 2.2.2 now available!
AudioFuse 16Rig Resources
2 Likes
We got the update, and now there’s a metering issue.
In the Control Center (Analog outputs), the monitor level matched the phones’ level on the last firmware update.
In 1.3.3, you must turn the volume up to almost -50 to get the meters on the front panel to move. If you click Mono, then the levels match.
Anyone else having this same issue?
Hey Williams,
Sorry to hear about the issue with your 16Rig.
Could you explain in detail under which conditions you see nothing on the meters, and how using the mono button changes what you see?
Also, which audio source are you using, at what volume, and what are the Output Level values for your Monitor and Phones on the 16Rig?
I also recommend you to contact our support team, which will help you to fix the issue or report it if a problem is confirmed:
https://www.arturia.com/fr/support/ask-for-help
Kind regards,
I’ve since gone back to 1.2.2 and things are fine there, or at least what I’m used to seeing. Things may have changed for the operation of the front panel/Control center.
Running any audio from YouTube, Pro Tools, or standalone virtual instruments, on Firmware 1.2.2, the levels on the meters between Monitor and Phones always match.
On Firmware 1.3.3, on the Phones, the meters, usually between -12 and -6. The Monitor doesn’t match anymore. It’s not until I turn up the volume knob and hit around -65 do I see the meters start to move. It’s strange.
I just got the updates and thought it was a bug too so I was checking here.
Now I realise what’s happening: previously, we were seeing in the metering the signal that is sent to output BEFORE the volume knob is applied. Now we see AFTER the volume knob, therefore it’s closer to the actual volume being output compared to what could be output by the device.
Am I correct?
I was also thinking this, but I shouldn’t have to turn my volume up to above -65.2 to start seeing the level on the output meter. If I hear music, I should see some level. The level is like 10 o’clock before anything starts moving. It’s strange to me.
Arturia did indeed confirm that there an an issue with the firmware. Here’s the response I received.
"So, we are currently looking at this issue and just end up reproducing similar problems.
In fact, this issue would seem to be Sample Rate related and isolated to 48/192Khz only.
I just logged this and forwarded all the details to our Q.A department for them to investigate this issue and for them to work on an appropriate fix.
So, of course, if too annoying for now, the best would be to either:
-Stick to other unaffected Sample Rates (44.1 / 88.2 / 96 / 176.4 Khz)
-Stay / Revert back to 1.2.2 FW revision"
Glad to get a response from support about this and hopefully it’ll be sorted soon.
1 Like
Nice, good to know!
Am I correct that this affects the meters but nothing related to the sound itself?
1 Like
I believe so.
Installed 1.3.3 tonight and now my ADAT inputs are silent regardless of mixer leveling. I have two Audiofuse X8in units with word clocking set up and everything worked pretty well on 1.2.2. I can confirm when I play those instruments that the appropriate metering lights light up on the X8in’s. I also was dinking around before applying the update and happened to play some of the ADAT channels; I heard them just fine before the update.
I did not see anything in the release notes that would obviously cause this (I don’t use force SMUX). Tomorrow I will go back to 1.2.2 and verify that the ADAT channels work.
1 Like
Hello.
Another issue have been reported on ADAT IN 2:
- Signals routed to channels 9/10 are now received on channels 13/14
- Signals routed to channels 11/12 are now received on channels 15/16
- Signals routed to Channels 13/14 are now received on channels 9/10
- Signals routed to Channels 15/16 are now received on channels 11/12
This have already been adressed and will be released along with the VuMeter fix as soon as we can.
Is that your issue ? If no, you definitly should contact our support team in order for us to track and fix the bug: Ask for help | Arturia - The Sound Explorers
4 Likes
Hey,
Also note that ADAT port 2 won’t work until there’s a signal in ADAT port 1.
This may be related.
Bests
3 Likes
All kinds of problems with this firmware with Adat. Channels all over the place and all my preset saves dont work. Loading Factory preset at least gets the adat channels right again but I lost all my labels and have to basically start from scratch again. A lot left to be desired here Arturia. This is far from pro level and far from what I’ve come to expect from all your other products. The Rig16 and the 8 in and 8 expansions boxes just don’t seem to be worth the hassle.
1 Like
Hey,
Just wanted to inform you that the fix for the ADAT channels is about to be released.
Kind regards,
4 Likes
Niks do you have updates 'bout AFCC mixer control via DAW/VST Host using Host Output port (now midi learn works but messages are not received by the mixer)?