Arturia Driver

[Lilliana Adames]

EDITI investigated an issue that could be linked to the AudioFuseControlCenterAgent which is running in the background. If the driver does not help, please try to force quit the agent process, reboot the interface and retry.

Please note that there will probably be a hotfix version of the AFCC if we found that there is a problem in it.

So everything is very strange and the root cause seems to be Windows 11 and the way Analog Lab and other apps handle the ASIO driver stack. In the past (month ago or something like that) everything has worked well.

My rig has a Soundblaster Audigy 5/RX card. Analog Lab works fine with its Creative Asio driver. Though when I start the program I get a message that Asio 4All was launched with 44Khz. But when I look into settings it is Creative ASIO. I guess Analog Lab just loads just any sound driver at start-up and then switches to your own settings.

Hello! I own Audiofuse Rev 2. For some reason, on my main computer I can only use the old USB driver version 4.67.0 that came with Control Center 2.1.3.8. As soon as I install the new Control Center 2.2.1.842 and driver 2.0, all my music software stops seeing the ASIO device. However, sound works well in Windows.

Thanks for the answer. I not only removed the driver, but also tried to clear everything that remained after it: folders in program files and programdata, undeleted driver files in the c:\windows\system32 folder, and even all keys mentioning Audiofuse in the system registry. I also installed the new driver before and after connecting the device to the computer. And I also assumed that the problem might be related to the connection to USB 3.0 and tried using other connectors, including USB 2.0. Nothing helped.

I just got a prompt to update my Audiofuse control software + driver to (presumably) the latest version. Upon going through this grueling process requiring multiple reboots and repeating the same actions a number of times, the software was installed and seemed to be functioning.

However, my audiofuse (rev2) was not, ending up in what seemed to be a reboot loop. Updating it to firmware 1.2.3 solved that problem, but unfortunately that firmware version is unusable for me so I need to use 1.1.1. Going back to that firmware version re-introduced the boot loop issue. Reverting both the firmware and the software to an earlier version solves all problems.

I read the NAMM news and was pleasantly surprised at this new product from Arturia, the Audiofuse USB interface with PC, Mac, iOS, Android & Linux compatibility. I think I am going to get one, not just because of its Linux support but because it looks like a neat interface with ADAT support amongst others.

Very interesting to me at least. It has the possibility of becoming a replacement for a Duet on my Macbook Pro, but the question of course comes down to, how do the preamps sound. I like the possibility of hooking it to a tablet as well, means I could throw it on my iPad with my keyboard attached and have some fun as well.

Nope. RME, Sound Devices, come to mind immediately. And actually a few manufacturers like Focusrite worked directly with the FFADO folks IIRC to support development of the drivers for some of their interfaces, but could have the last part a bit blurry:)

AUM is the best thing on iOS for me. Fits my workflow as it is, stable and flexible.

There are things I'd like to see in future, but those are only to fasten the already speedy workflow, like presets for full channel config, or even multiple channels at once (since AU midi), ms or sample delay module - as far as I remember these were confirmed by dev as future plans.

Regarding Babyface, imo RME makes the best interfaces on the market. You can get a cheaper one for sure and probably run into its limitations at some point, or stability issues or drop of support when the next new comes. This one I'm using for 5 years now, originally bought as mobile solution for my laptop, when iPads became a thing for music making they made it Class Compliant and still supported for pc, mac, ios - it's around 10 years old product now, discontinued 2 years ago and it still has probably the most stable drivers and the most flexible routing app available. Decent sounding clean preamps, built like a tank.

Cons:

Using the breakout cable can be messy.

Would be nice if you could power it from iPad, but with two preamps with switchable phantom power it's to be expected and with split usb cable included you can power it from usb charger or power bank without PSU.

My intention is to gather the necessary information to operate these buttons with a basic LUA tool, which only makes these transport buttons work. The transport buttons are:

From left to right:

If in the end I manage to create the tool, I will publish it here so that anyone can use it. The objective is to make it as simple as possible, without the need to use Duplex. Make it a simple tool made on purpose.

Does anyone have information on how the tool should be focused? As I understand it, with an LUA file and another additional XML could be built. But I still do not understand how MCU / HUI protocols works with Renoise.

I think those 6 buttons, and others of the Keylab MK2 do not send MIDI messages, but they work with the MCU protocol (which I do not really know how it works). If they were normal buttons for the MIDI input, I would be no problem.

It would be necessary to develop all this to create a specific tool. Everything that I advance will be published here. Maybe other users can build their tools for other control keyboards that use MCU or HUI.

In 2003, the Mackie Control Universal (MCU) protocol was introduced, combining together functionality from Mackie Control, Logic Control and HUI into a single protocol. DAWs which support MCU (in addition to those which support HUI) include Ableton Live, Studio One, Cubase, and Reason.

With this installed, Duplex works correctly with the 49-key MKII keylab. The transport buttons work and also the illumination of these buttons when activating the output. It is not completely complete. There are some things that need to be finished. But this works with Duplex.

The final tool would be something similar, but it would only work for the Arturia KeyLab mk2 49 and the Arturia KeyLab mk2 61 (only change the name of the device, I think). I think it could achieve more flexibility with the controls, to have more control options.

Regarding the sending of data from the hardware (KeyLab mk2 49) to the tool. How to print these messages? That is, how to obtain them? Thus, functions could be executed.

hardware (KeyLab mk2 49) -> LUA tool & Renoise [edit: this part is resolved!]

I have not found any guide or documentation to create this type of tool. And certainly, I do not understand very well how Duplex is built to extract from it everything necessary to interpret these messages and thus be able to execute specific functions.

Hi Raul. Good to see another keylab user here and thanks for building the 49 version. i was unsure if they changed the button configuration. I built this as a fit for purpose as you may found out to that only the keyboard worked with Renoise.

I am no lua coder, My background is C# C++ for AR and VR. When i was building this I had to ask arturia for some of the sysex documentation that was confidential. I am unsure of the process of building a standalone plugin so someone else might have to help out there, or documentation. however I Picked MCU as the default as it was the first general DAW compatibility and it is just a standard guideline for connecting midi to a DAW.

For the moment I have noticed a difference of 12 notes on the transport buttons. In the KeyLab mkII 61 it seems that it uses the octave 6, while in the KeyLab mkII 49 the octave 7 is used. I am not sure because I do not have a KeyLab mkII 61.

With all this, I can already assign any function to any of these controls. Even with automatic repetition capabilities. For example, to move right between the tracks, it is not necessary to press 1 time for each track jump, but to keep pressed. This avoids wear down the buttons so much.

To be perfect, I would need to know how to send the messages (MIDI Out) to synchronize the lighting LEDs for each control. For example, the PADs are multicolored, just like the buttons below the faders. The rest are monocolor. I guess they will have only 3 states, off, low brightness and maximum brightness.

To synchronize the state of the buttons, the tool needs to have a checkbox or on / off switch. When it is turned on, some API notifiers will always be in action. They will be responsible for detecting, for example, when the PLAY button is turned on or off, for a function to send an OUT message to the KeyLab hardware that instructs the Play / Pause LED to turn on or off. And so with the rest of buttons.

3a8082e126