Ableton Forum

edit: update below

Ok, I did some more research.
The problem occurs when you have some MIDI remote script selected.
The original Launchpad script does not introduce any noticeable lag,
with ClyphX I had the impression that there is a minimal lag
(hard to even notice it) and LiveOSC was the one that led to
the described problem. Perhaps because it's quite complex ?
Or because it accesses network resources ? Who knows...

So it's possible to use ClyphX to do the trick as I described !
There is one problem left: The clip only (re)triggers with MIDI CC
values of 64 or above and Live unfortunately does not offer a way
to change this.
You could use the free version of Bome to output an additional
MIDI note or MIDI CC with a static value higer than 63 whenever
you turn the knob on your controller.

So...one last post.
I've found a solution to do it inside Live and for free !
...in Windows.

I use a VST called CC Rider, you can get it here:
http://web.archive.org/web/200707031435 ... /tools.php
CC Rider generates and outputs MIDI CC. Nothing else.

Now here is what I did:


Yellow boxes:
Assign the volume of track 1 to your MIDI controller sending a MIDI CC, here #7.
The volume is the parameter that will go back to a default value automatically.

Set up a Track with CC Rider on it.
Assign a parameter of CC Rider (here CC #2) to the same MIDI CC, here #7.

Blue box:
Route the output of CC Rider to a loopback device, here MIDI Yoke Out 4.
Activate MIDI Yoke In 4 as MIDI Remote in the preferences.

Red line:
Set up a MIDI track for a ClyphX clip: [] (LSEQ) DUMMY ; 1/VOL 108
This clip will reset the volume on track 1 when reaching the 2nd loop.
Assign this clip to the MIDI CC that CC Rider outputs, here #2.
Note: You have to send this CC from outside Live when assigning
as Live does not allow manual editing of MIDI mapping and CC Rider
won't send when in mapping mode. Live acts as showstopper again...

Now you have the same result as when simply assigning the ClyphX clip
to MIDI CC #7 - the clip will only (re)trigger when CC #7 is 64 or higher.
In the lower half it will reset the volume even if you are still
moving your controller.

Green line:
Now we force CC Rider to only output values between 64 and 127 by setting
the mapping range to 0.50 (or higher) - 1.00. VOILA, the clip always retriggers !

Make sure NOT to use the same CC number, here #7, for CC Rider to output.
Everything would freak out because of the loopback and the different
parameter ranges we've set.

A bit fiddly to set up, but it works great, is stable, you can save it with your set
and there is no need for Max4Live, Bome or anything else.
Of course you can optimize all this - CC Rider may sit on track 1 without
doing any harm and the ClyphX clip may also sit on the track 'MIDI CC output'
for example.