Faderfox with control surface unpredictable

[icedsushi]

I'm using a Faderfox LV2 & have always used the supplied midi map Live Set included on the Faderfox CD & modified it from there. I have this saved as my default template. Since Live 7, LV2 is supported as a control surface, so I'm thinking to switch over.

When I select "LV2 LX2 LC2 LD2" as a control surface, the track select response to the LV2 is slower, about than half the speed. This is both with or without the previous midi mappings deleted. Live response to the Faderfox is much better & zippy with the old fashioned midi mappings, without any control surface support.

When I twist the rotary encoders quickly a few notches at a time, the track selected will only go across one track at a time, it misses a lot of notches unless I turn it very slowly. The rate of track scene & track selection is the same rate regardless of how fast the know is twisted. When using the control surface option I must twist very slowly to get it to detect each midi message. It can be unpredictable as well, sometimes it selects the next track when twisted, sometime it does not.

The scene select rotary is quicker with control surface selected than it is with midi map. It skips ahead more scenes than it should when twisted quickly.

[Ableton_David]

Hi, please contact Ableton technical support about your issue: http://www.ableton.com/support. Thank you.

[icedsushi]

OK, thanks, done. I was also wondering if anyone else has had the problem...

[oblique strategies]

Same issue here with Faderfox LD2 & LX1.

[icedsushi]

Yeah I never heard back from Ableton about a solution. Apparently this is just the way automap mode is with the Faderfox? Using your own midi map performs way better than automap so I've always done that & avoided automap.

But makes you wonder why they even bothered to add the Faderfox automap function if the performance is much worse...it just adds unnecessary trial & errors when you could use the supplied templates & be done with it.

[oblique strategies]

So far, selecting tracks using the encoder on the LX1 & the Track Select buttons on the LD2 is the only problem I've experienced. I haven't used the LD2 for a long time because it used to crash Live almost every time I used it (in either MIDI map & Control Surface modes).

I just got it out to test it again, & something has changed with either the current Live version or Mac OS X that has made it stable. And I like the Control Surface functions so well that I'm using it.

I've been using the LX1 in MIDI map mode for a long time, & just switched over to Control Surface mode. So my experiences using the faderfoxes in Control Surface mode is quite new.

I'm in a testing phase right now, seeing how much I have to adapt my sessions & ways of working to get the most out of the Faderfoxes. I work in Quad a lot, & the LD2 isn't perfect for that, but for stereo work it's great!

Let us know what Ableton has to say... I am weary of troubleshooting other issues, or I'd open a dialog about this with them myself.

[icedsushi]

They haven't said anything since when I reported it in November so I'm assuming what you see is what you get. Selecting tracks was the main problem for me too. Interesting you find an improvement, I'll have to revisit it with the current version.

Is it necessary to delete your midimaps & have a blank template for the control surface to work? I seem to remember trying it both ways.

[madlab]

As usual, maybe there's a solution with M4L... Which is obviously only half a solution because all the faderfox owners don't want to use M4L.

[ollyb303]

Hmmm, I've been using my 3 faderfoxes since Live 6 (when I used Mathius' templates from the disc), then with 7 automapped (except my DJ2, which I map manually as it's technically a Traktor controller) and now with 8 (same as 7). I can honestly say I never noticed any difference in response. There has always been a few milliseconds lag, which has never been an issue for me - it makes no practical difference...