say it loud: FADERFOX NATIVE SUPPORT!!!!!!!!!!!

snakedogman · Post by **snakedogman** » Sat Dec 01, 2007 11:20 am

what about Sonar's ACT system? Why can't Live get something like that? Or does that only support a limited amount of hardware options as well?

Strepsil · Post by **Strepsil** » Sun Dec 16, 2007 2:00 pm

I upgraded a few weeks ago to Ableton 7 and was amazed to find native Faderfox support still missing.

Please consider getting an update out there as soon as possible - it seems crazy that faderfox and users of their hardware would be snubbed in this way. Having to use customised default set files is a pain!

zeropoint · Post by **zeropoint** » Sun Dec 16, 2007 8:49 pm

+1.....and + another 1.....

tw1nstates · Post by **tw1nstates** » Sun Dec 16, 2007 9:37 pm

Yeah,

Come on I have just got one (recentlyish).

+10

snakedogman · Post by **snakedogman** » Sat Jan 12, 2008 11:33 am

so is anyone using an user generated automap script with their faderfox?
I was just trying to see if I could set it up but I can't get it to work.
Just trying to map the 4 pots by using their cc's on channel 1 and the volume sliders. afaik I've entered to correct channels and cc's but I don't see any movement in Live...
(and yes I've made a "faderfox" directory in the correct place and it shows up in Live's controller list)
Who can tell me where I go wrong? This should work right?

# Config File for User-defined Instant Mappings

# We assume that the controls on your MIDI controller
# send CCs. All controls, except the sliders for volume
# and the encoders for device parameters, are expected
# to use the global channel. CCs are counted from 0-127
# and channels from 0-15.

[Globals]
# The channel that the controller should send on
GlobalChannel: 0
# If your controller is connected via USB, replace ControllerName
# with the name of the respective port. Live will then try to
# recognize the ports for you when you select your Instant-Mappings
InputName: ControllerName
OutputName: ControllerName

[DeviceControls]
# The Encoders will control the device parameters (you can also
# use knobs or sliders). Replace the -1's with the CCs sent by
# the respective controls on your controller. You can also set
# the channel for each controller if it differs from the global
# channel (if you leave the channel of an encoder at -1, Live
# will assume that the encoder uses the global channel).
Encoder1: 40
Encoder2: 60
Encoder3: 80
Encoder4: 100
Encoder5: -1
Encoder6: -1
Encoder7: -1
Encoder8: -1
EncoderChannel1: 13
EncoderChannel2: 13
EncoderChannel3: 13
EncoderChannel4: 13
EncoderChannel5: -1
EncoderChannel6: -1
EncoderChannel7: -1
EncoderChannel8: -1
# Enter the respective map mode for the encoders here. The following
# map modes are available:
# - Absolute
# - Absolute14Bit
# - LinearSignedBit
# - LinearSignedBit2
# - LinearTwoCompliment
# - LinearBinaryOffset
# - AccelSignedBit
# - AccelSignedBit2
# - AccelTwoCompliment
# - AccelBinaryOffset
# Consult the controller's documentation to find out which mode to use.
EncoderMapMode: Absolute
# Buttons used here are expected to not be toggles (i.e., sending
# value 0 every second time you press it).
Bank1Button: -1
Bank2Button: -1
Bank3Button: -1
Bank4Button: -1
Bank5Button: -1
Bank6Button: -1
Bank7Button: -1
Bank8Button: -1
NextBankButton: -1
PrevBankButton: -1
LockButton: -1

[MixerControls]
# Again enter the appropriate CCs for the respective controls.
# If all sliders use the global channel to send their data,
# you can leave the channels at -1. You can, of course, use
# encoders or knobs instead of sliders.
VolumeSlider1: 0
VolumeSlider2: 1
VolumeSlider3: 2
VolumeSlider4: 3
VolumeSlider5: 4
VolumeSlider6: 5
VolumeSlider7: 6
VolumeSlider8: 7
Slider1Channel: 15
Slider2Channel: 15
Slider3Channel: 15
Slider4Channel: 15
Slider5Channel: 15
Slider6Channel: 15
Slider7Channel: 15
Slider8Channel: 15
MasterVolumeSlider: -1
MasterSliderChannel: -1
Send1Knob1: -1
Send1Knob2: -1
Send1Knob3: -1
Send1Knob4: -1
Send1Knob5: -1
Send1Knob6: -1
Send1Knob7: -1
Send1Knob8: -1
Send2Knob1: -1
Send2Knob2: -1
Send2Knob3: -1
Send2Knob4: -1
Send2Knob5: -1
Send2Knob6: -1
Send2Knob7: -1
Send2Knob8: -1
TrackArmButton1: -1
TrackArmButton2: -1
TrackArmButton3: -1
TrackArmButton4: -1
TrackArmButton5: -1
TrackArmButton6: -1
TrackArmButton7: -1
TrackArmButton8: -1
VolumeMapMode: Absolute
SendsMapMode: Absolute

[TransportControls]
# The transport buttons are also expected not to be toggles.
StopButton: -1
PlayButton: -1
RecButton: -1
LoopButton: -1
RwdButton: -1
FfwdButton: -1

SubQ · Post by **SubQ** » Sat Jan 12, 2008 2:52 pm

anyone can shed a light into this

snakedogman · Post by **snakedogman** » Mon Jan 14, 2008 12:32 pm

looks like our prayers have been answered people! According to this post the new update for Live 7 (7.02) will in fact contain
MIDI Surface Controller support for Faderfox LV1, LX1, LV2, LX2, LC2 & LD2!

SubQ · Post by **SubQ** » Mon Jan 14, 2008 12:43 pm

this means... we won!!!

snakedogman · Post by **snakedogman** » Mon Jan 14, 2008 1:12 pm

*high-fives SubQ*

mrweasel · Post by **mrweasel** » Mon Jan 14, 2008 1:33 pm

Has anybody tried it yet.
Is it a thorough support that takes advantages of all the faderfoxes' capabilities?
For example, is there any clip feedback with the LX2's leds?

mrweasel · Post by **mrweasel** » Wed Jan 16, 2008 2:49 pm

Oh Yeah Baby

> Do you know how the new Faderfox support in the new Ableton
> > Live 7.0.2 beta works?
> > Did you have any say in its implementation at all?

there are implemented my own scripts

> > When I purchased my LV2 and LX2 a few years ago, it said in
> > the manual that "We reckon that in the foreseeable future
> > Ableton will bring out a special driver for micromodul. With
> > this all assignments (according to our sets) will be
> > available without loading a special set."

exactly

> > It looks today like something is finally underway, although I
> > would have thought Ableton and Faderfox would have worked
> > hand in hand much earlier to make this happen.

I was waiting a long time to get this thing from ableton.....without
success.
now I have developed my own scripts and these will be part of the next
updates of v 6 & 7.

> >
> > I am wondering what the breakdown of this automap support is
> > and if Ableton takes full advantage of the Faderfox modules'
> > power -For instance, does Ableton send clip on/off feedback
> > messages to the LX2 in order to know what clips are running or not?

yes

> > -Is it now possible to record enable or mute/solo several
> > tracks in Ableton and to see that status on the LX2?

yes

> > -On the LV2, is there a possibility to scroll through tracks
> > like on your original template, but with a Mackie control
> > behaviour so that if you delete track 2 for instance, track 3
> > atutomatically falls into place.
> > (that way you can remove add and reorder tracks and still
> > scroll through your tracks as everything is updated thanks to
> > the Ableton driver)

yes

these scripts are one of the best remote supports
almost all functions on my controllers are supported by the scripts.

cheers
mathias

mrweasel · Post by **mrweasel** » Wed Jan 16, 2008 4:26 pm

Things can only get better can only get better now I've found support

the support will be described in the LIVE lessons....I hope perfectly.

the support is very similar to my own template files.

for the LX2:
you should use the internaly setup 1 (description in the LX2 manual):

blue1 = 12 first slots of track 1
green1 = 12 first slots of track 2
red1 = 12 first slots of track 3

blue2 = launch/stop of track 1 to 6
green2 = mute/solo of track 1 to 6
red2 = rec of track 1 to 6

blue3 = free 12 buttons for FX or other
green3 = selection of track 1 to 12
red3 = launch of the first 12 scenes

of course you can use one of the setup 2 to 12 to build your own set
and to combine some live assignments with free assignments.

you can also launch the first 12 clips on each of the first 12 tracks by the
LX2.
reassign any launch-keys in LIVE if you want to use other as the first 12
slots/scenes.

here are some differents to my templates:

- launch of the first 12 slots in each track by the key group 'slot launch'
on LV2/LC2 (also on LX2)
- launch of the first 12 scenes by the key group 'scene launch' on LV2/LC2
(also on LX2)
- controlling of the parameters in the selected device (the 8
best-of-parameters) by encoders in group FX3/FX4
- stick controls the X/Y area in the selected device (FX1/FX2 group)
- switching between track-view and clip-view by shift + lower
pot-ctrl-button
- switching between session-view and arrangement-view by shift + upper
pot-ctrl-button
- hide/show of the track/clip-window by pushbutton of encoder C (in main
group)

- no track monitor control
- no control of the loop-start/length and gain in the clip-parameters
- no control of monitor volume & crossfader
(these things are currently not possible in LIVE but will be coming soon)
you should map these things by yourselve on demand.

it's possible to override all automatic mappings.

the scripts handle 12 tracks (LV2/LC2/LX2/LD2) and 16 tracks (LV1/LX1).

and of course all the button-led's works how you expect.

...it's really amazing...

cheers
mathias

skeet · Post by **skeet** » Wed Jan 23, 2008 2:04 am

Hell YES!! It's been so long I was waiting for that.
Just begging for this update...

davec1 · Post by **davec1** » Wed Jan 23, 2008 3:25 pm

hurray for that!

supamonsta · Post by **supamonsta** » Thu Jan 24, 2008 2:16 pm

cool

but I'll have to upgrade to live 7 to get this.... another $$$$$$$$

anyway to get the upgrade for live 6 ? live 6.0.2 for instance ???

cheers and long life to faderfoxies