Set tempo via MIDI

Manual, page 89.
There's nothing about midi or tempo on page 89.

I suspect you're thinking of assigning tap tempo but I also think the OP is asking about setting a specific tempo via midi, which I don't think is possible currently.

I think this was asked for Axe Fx III some time ago but was not added to the Midi spec.

Edit:

Maybe you meant page 98 which is where the Tap Tempo settings are?
 
Per their manuals, both the Axe III and FM3 sync their tempos to MIDI Beat Clock received at the MIDI In port. Neither will transmit MIDI clock to other devices, but they should sync to it.
 
Per their manuals, both the Axe III and FM3 sync their tempos to MIDI Beat Clock received at the MIDI In port. Neither will transmit MIDI clock to other devices, but they should sync to it.
It would really by nice if it could just be changed via midi with a single value...
 
There's nothing about midi or tempo on page 89.

I suspect you're thinking of assigning tap tempo but I also think the OP is asking about setting a specific tempo via midi, which I don't think is possible currently.

I think this was asked for Axe Fx III some time ago but was not added to the Midi spec.

Edit:

Maybe you meant page 98 which is where the Tap Tempo settings are?
Page 89 in The manual i have. Yes.
 
Is it possible to set tempo via midi in FM3 ? Using CC# or something ? Thanks

Yes... but as a Midi Novice my explanation will be muddled, I am sure...

I use Bandhelper for setlists and schedule, and to send Midi to change my AXE III presets, scenes, blocks on/off and to set tempo bpm. This is how I do it in Bandhelper, but YMMV, and there is probably a much easier way somehow...

Example: my midi preset file named 'TEMPO120' sends this RAW MIDI (HEX Code) :
F0 00 01 74 10 14 78 00 79 F7

where F0 00 01 74 10 is the Fractal Audio company code
14 is the cc I want
78 00 sets value at 120 bpm
79 is the XOR checksum

F0 00 01 74 10 14 7D 00 7C F7 sends 125
F0 00 01 74 10 14 7E 00 7F F7 sends 126
F0 00 01 74 10 14 7F 00 7E F7 sends 127
F0 00 01 74 10 14 00 01 00 F7 sends 128
F0 00 01 74 10 14 01 01 01 F7 sends 129
F0 00 01 74 10 14 02 01 02 F7 sends 130

and so on... works like a charm. I send Tempo with every song selection. Now, if I can just Midi this into my drummers head...
 
Yes... but as a Midi Novice my explanation will be muddled, I am sure...

I use Bandhelper for setlists and schedule, and to send Midi to change my AXE III presets, scenes, blocks on/off and to set tempo bpm. This is how I do it in Bandhelper, but YMMV, and there is probably a much easier way somehow...

Example: my midi preset file named 'TEMPO120' sends this RAW MIDI (HEX Code) :
F0 00 01 74 10 14 78 00 79 F7

where F0 00 01 74 10 is the Fractal Audio company code
14 is the cc I want
78 00 sets value at 120 bpm
79 is the XOR checksum

F0 00 01 74 10 14 7D 00 7C F7 sends 125
F0 00 01 74 10 14 7E 00 7F F7 sends 126
F0 00 01 74 10 14 7F 00 7E F7 sends 127
F0 00 01 74 10 14 00 01 00 F7 sends 128
F0 00 01 74 10 14 01 01 01 F7 sends 129
F0 00 01 74 10 14 02 01 02 F7 sends 130

and so on... works like a charm. I send Tempo with every song selection. Now, if I can just Midi this into my drummers head...
You flipped 126 and 127 but regardless, there you go!
 
Yes... but as a Midi Novice my explanation will be muddled, I am sure...

I use Bandhelper for setlists and schedule, and to send Midi to change my AXE III presets, scenes, blocks on/off and to set tempo bpm. This is how I do it in Bandhelper, but YMMV, and there is probably a much easier way somehow...

Example: my midi preset file named 'TEMPO120' sends this RAW MIDI (HEX Code) :
F0 00 01 74 10 14 78 00 79 F7

where F0 00 01 74 10 is the Fractal Audio company code
14 is the cc I want
78 00 sets value at 120 bpm
79 is the XOR checksum

F0 00 01 74 10 14 7D 00 7C F7 sends 125
F0 00 01 74 10 14 7E 00 7F F7 sends 126
F0 00 01 74 10 14 7F 00 7E F7 sends 127
F0 00 01 74 10 14 00 01 00 F7 sends 128
F0 00 01 74 10 14 01 01 01 F7 sends 129
F0 00 01 74 10 14 02 01 02 F7 sends 130

and so on... works like a charm. I send Tempo with every song selection. Now, if I can just Midi this into my drummers head...
Oh, I totally forgot about using sysex.

However I think that's device dependent. Probably not exactly the same for FM3, but maybe.
 
Yes... but as a Midi Novice my explanation will be muddled, I am sure...

I use Bandhelper for setlists and schedule, and to send Midi to change my AXE III presets, scenes, blocks on/off and to set tempo bpm. This is how I do it in Bandhelper, but YMMV, and there is probably a much easier way somehow...

Example: my midi preset file named 'TEMPO120' sends this RAW MIDI (HEX Code) :
F0 00 01 74 10 14 78 00 79 F7

where F0 00 01 74 10 is the Fractal Audio company code
14 is the cc I want
78 00 sets value at 120 bpm
79 is the XOR checksum

F0 00 01 74 10 14 7D 00 7C F7 sends 125
F0 00 01 74 10 14 7E 00 7F F7 sends 126
F0 00 01 74 10 14 7F 00 7E F7 sends 127
F0 00 01 74 10 14 00 01 00 F7 sends 128
F0 00 01 74 10 14 01 01 01 F7 sends 129
F0 00 01 74 10 14 02 01 02 F7 sends 130

and so on... works like a charm. I send Tempo with every song selection. Now, if I can just Midi this into my drummers head...

Wow, It is working fine on my AxeFX3 but I really have to make it work on my FM3 !

Where can I get the hexadecimal sequence refering to the FM3 ?

Also I don't undrrstant what is the OR checksum... could you explain please ?

Thanks a lot for your help.
 
Wish I could - sorry. I just used a source I found a while ago to create those SYSEX lines and they work... I don't know the ins and outs.
 
The checksum is an XOR of all the previous bytes.
So for the example:
F0 00 01 74 10 14 78 00

F0 XOR 00 = F0
F0 XOR 01 = F1
F1 XOR 74 = 85
85 XOR 10 = 95
95 XOR 14 = 81
81 XOR 78 = F9

But since the value (and actually all the values other than the initial F0 byte) is just 7 bits you lop off high bit and end up with 79 as the checksum.
 
Last edited:
Also I don't undrrstant what is the OR checksum... could you explain please ?
A checksum is a method of error detection that adds a number at the end of the string.

"XOR" is "exclusive or," which is a logical operation that you perform on the date to calculate the checksum. Google can explain it better than I can.
 
The checksum is an XOR of all the previous bytes.
So for the example:
F0 00 01 74 10 14 78 00

F0 XOR 00 = F0
F0 XOR 01 = F1
01 XOR 74 = 85
85 XOR 10 = 95
85 XOR 14 = 81
81 XOR 78 = F9

But since the value (and actually all the values other than the initial F0 byte) is just 7 bits you lop off high bit and end up with 79 as the checksum.

I have some difficulties to follow your explanation... are your numbers rights ?
 
Back
Top Bottom