le RC-300 peut envoyer du signal MIDI clock, mais pas en recevoir.

La ruse vient du Tape Tempo.

Dans le RC-300, aller dans Memory Edit, and page all the way to the end to Assign Controllers. I used controller 8, cause it didn't have any default assignments.Set it to ON, Target to MEM Tempo (tap), and for Source I used CC#64.

Dans le sequenceur (ex Ableton) créer un clip de 1 ou 2 mesures. Ne contenant que le control data, sans aucune note. Draw in CC#64 on every beat, avec la valeur 127.

Si l'on veut se servir du rhythm track du RC-300, then you only want to play this for a measure or 2, not loop it continuously, otherwise it retriggers the start of the pattern at every beat.

Router la sortie de la piste vers le MIDI OUT de l'ordinateur, puis connecter vers le MIDI IN du RC-300, et voilà! Le RC-300 suivra whatever tempo your sequencer is playing at.

I attached a .mid file of one bar with 4 beats of CC#64. You can just drop it in a track in your sequencer. There is no reason you need to use CC64, but you don't want to pick something that is likely to be already used, like 1 or 7.

RC-300 : Go to assignment 8, Receive trigger from CC64.
Assign target Tempo (NOT tap tempo), set the min at 60, max 187

In ableton build a single shot (non looping) dummy clip, and bring up CC64 envelope.
Draw the desired tempo into the clip, with a CC value of 0 being 60 BPM and 127 is 187 BPM. (You can choose any min and max)
Place clip on a new scene, name the scene with the same tempo.

Now when ever you launch that scene, you will have ableton and the looper lock to the new tempo at the same time. No drift, no latency, and so far no glitches.... (looks around nervously) So you can just tell the @#$! what tempo to be at, leave the drums on but muted, and bam!

Now the tap tempo would have been more of an option but the way I have my RC300 loops set up I can't use its warp engine. But that is fine, because now I have the RC300 following Ableton perfectly I can set up dummy clip scripts to dump loops into Ableton clips then clear the looper ready for more new loops   , or playback old loops from earlier in the jam/gig/etc, or have extra looping tracks in Ableton so I can have even more loops! Not to mention the RC300 has the outputs to be able to discreetly route loops, so now I have an incredibly flexible FX chain on every loop. Now just to build a new controller...

I have tempo control over the RC300 using a single rotary midi controller sending a CC value.

Ableton is running as my midi master

Ableton sends midi clock to TB midi stuff which is set up to external sync (so I can have it displaying tempo)

A rotary control sends CC 1 and 2 from TB midi stuff to Ableton

CC 1 is assigned to Abletons tempo, and CC 2 is routed through a track in Ableton to the midi in on the RC300 where it is assigned to tempo.

Assign the same tempo Min/Max range for on Ableton and RC300 assignment. I am using 60 to 187, good range, and gives only whole number tempos.

Now have tempo control with a 127 bpm range with no drift or silly start/stop msgs or dreaded sys ex msgs.

Also cool, stole a little visual metronome from one of the other TB Midi stuff pages so now I have a tempo read out, visual metronome, click track volume control, and tempo control knob all in a little 2 inch box on the ipad.

---------

Pour trigger la grosse caisse sur le tempo du RC-300:

1) Brancher un micro (piézoélectrique de préférence) sur la grosse caisse.

2) brancher la prise dans un Drum trigger up to a midi percussion module avec de sorties MIDI configurables.

3) Rélger le MIDI OUT du trigger vers le message CC#64 avec une valeur de 127.

4) Dans le RC-300, aller dans Memory Edit | Assign Controllers. Trouver un contrôleur libre, genre 8. Mettre à ON, Target to MEM Tempo (tap), et Source à CC#64.

NOTE 1: Don't use this to trigger the Rhythm Track or it will restart on every beat.

NOTE2: Le batteur devra avoir un moyen de désactiver le trigger lorsque chaque beat ne sera pas frappé.