Faderfox LV2 with Live 12

[luct.melod]

Hi, all! I recently picked up a Faderfox Micromodul LV2 for a good price. I had always heard good things about the Faderfox controllers and decided to try one myself. I like the build, but I am having a little trouble implementing it.

First things first:

• Running Ableton 12.0.20

• Windows 10 Pro

• Audio interface: Tascam US-4x4HR (not using as MIDI interface for the LV2)

• USB MIDI being used with the LV2 (Neewer USB-C cable)

Here's how I've set up communication in Live's settings:

• Input: LV2_LX2_LC2_LD2 Input (USB MIDI) -- track off, sync off, remote ON, MPE off

• Output: LV2_LX2_LC2_LD2 Output (USB MIDI) -- track off, sync ON, remote ON

Most functions seem to be working on the LV2 in my project as I would expect (although I am still quite new to this device, so I'm not totally clear on the function of some things).

I am able to select different scenes and clips. The faders control the volume level of each track, and the joystick modifies pan when that option is selected on the LV2.

The primary problem I'm having is with how the LV2 seems to "take over" activating the tracks. Each track is inactivated when I load my project. I set the key mode on the LV2 to "selected track, track ctrl." I am able to launch clips and stop clips using the buttons at the bottom of the LV2.

But I cannot make the track active. I cannot click to activate the track. It immediately goes back to grey.

When I try to use the LV2 to activate tracks, the tracks also immediately go back to grey. The activate button flashes quickly, but doesn't stay active. The same happens with solo and arm buttons on the LV2. The lights on the LV2 for "solo" and "rec" will stay lit when I hit them, but the track in Live does not stay soloed or armed (the tracks will only flash the solo button but not actually be soloed, for example).

The only LV2 button that seems to work (maybe) as expected is "mon," which switches the monitoring on tracks from "auto" to "off."

I hope I've provided enough information for somebody to provide some much-needed help! I have a feeling this is a case of user error, but I just can't figure it out.

Thanks so much for any help you can provide for a new user of this classic device!

[luct.melod]

I have a little more information after further testing.

The LV2 controls Live fine if I only use MIDI Out from the device. I am able to activate tracks, assign FX1 on the joystick controller, etc.

However, if I enable MIDI In, Live shows that the device is continuously sending MIDI In and Out messages. I think my problem with activating tracks when using both MIDI In and Out is because Live is reading information from the device rapidly. Once I try to activate a track, Live immediately gets a signal to deactivate it.

I have tried using both my MIDI In/Out to USB-C cable and the MIDI In/Out on my Tascam US-4x4HR. Both give the same result.

By using just MIDI Out from the LV2, I'm able to control Live, but I don't receive visual feedback on the LV2. For example, if I enable track 1, the green light on the LV2 does not illuminate, which makes sense -- it's not receiving feedback from Live to show changes.

I consider this a bit of progress at least! Any ideas as to why my system is continuously receiving MIDI In and Out signals if I try to enable two-way communication? It almost seems like a feedback loop.

[luct.melod]

Posting the solution to my own question for posterity -- hopefully this will help someone in the future.

I noticed that I seemed to be having a problem with a MIDI feedback loop. Live was continually registering MIDI messages both to and from the LV2, even though I wasn't moving any controls.

The LV2 helpfully includes a "feedback killer" that can be enabled and disabled. Instructions for doing so are in the manual. Essentially, enter the settings mode and activate the red LED for tracks 7-12 to enable the feedback killer.

This makes me wonder in what instances a user would not want the feedback killer enabled, since this controller is specifically for Live and apparently using it in Live results in a feedback loop. Perhaps the option to disable just no longer makes sense with more recent versions of Live that have a built-in driver for devices like the LV2.

Anyway, I hope this helps anyone else who decides to try this controller. I really like it so far! Very compact with lots of smart built in mappings and plenty of opportunities for customizability. The little joystick is very fun to map to macro controls.