Always consult the official Owners Manuals first

Difference between revisions of "Tempo"

From Fractal Audio Wiki
Jump to navigation Jump to search
 
(129 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
__TOC__
 
__TOC__
−
=Tempo menu=
+
=Channels or X/Y=
  
−
When tapping the Tempo button on the processor hardware or Tempo switch, the Tempo menu appears on the hardware GUI. It will disappear after a few seconds. Some devices let you specify how long it stays on-screen (Global menu).
+
*''' Axe-Fx III''', '''FM9''', '''MF3''': 4 channels
 +
* '''Axe-Fx II''', '''AX8''', '''FX8''': no
  
−
On the Axe-Fx III, the Tempo button is also a shortcut to the Controllers menu.
+
=Tempo button and menu=
  
−
=Tempo: global or per-preset=
+
When tapping the Tempo button on the device, the Tempo menu appears on the hardware display.
  
−
You can specify in the Tempo menu if you want the set tempo to apply to all presets or per preset.
+
On the Axe-Fx III, FM9, and FM3, the Tempo button also is a shortcut to the [[Controllers_and_modifiers|Controllers menu]].
  
−
=Tapping tempo=
+
=Tap tempo=
  
−
The Global menu lets you specify how Tap Tempo works:
+
The [[Global Settings menu]] lets you specify how tapping tempo works:
  
−
'''Average''' — averages the tempo to the last ten taps. Usually a wise choice
+
; '''Average''' : Averages the tempo to the last 10 taps. Average is usually a wise choice if you can't get the first taps right, and is the default setting.
  
−
'''Last Two''' — uses only the most recent two taps to determine the tempo. Acts faster but also less precise
+
; '''Last Two''' : Uses only the most recent two taps to determine the tempo. This acts faster but is also less precise.
  
−
=Syncing effects to tempo=
+
Tap Tempo needs at least two taps to calculate.
  
−
You can assign effect parameters such as Time or Rate to a specific tempo, like 1/4 or 1/8 Dotted, instead of specifying the number of milliseconds. That will make the effect depend on the global or preset tempo. Tapping a different tempo will change the rate of the effect.
+
See the <q>[https://forum.fractalaudio.com/threads/tap-tempo-issues.151565 Tap tempo issues]</q> discussion for more information.
  
−
Important: after assigning a parameter to a tempo, you can no longer adjust the time in the effect manually!
+
=Tempo per preset or global=
  
−
=Accuracy of the tempo LED=
+
You can specify whether you want to the tempo to apply to all presets (global) or per preset.
  
−
<blockquote>"The tempo LED is handled by a low-priority thread so it isn't rock solid and the higher the CPU usage the less solid it will be." [https://forum.fractalaudio.com/threads/does-the-tempo-led-actually-flash-in-time.51049/#post-658471 source] </blockquote>
+
=Tempo per channel or scene=
  
−
=Tempo in firmware Ares=
+
Tempo is part of the [[Controllers_and_modifiers|Controllers block]]. That block has 4 channels, so a preset can have 4 different tempos which allows setting separate tempos per scene.
  
−
Tempo is part of the internal controllers. The Controllers block in firmware Ares has 4 channels. This means that each preset can have 4 different tempos.
+
=Syncing to the tempo=
  
−
=Auto-activating a Delay by tapping Tempo=
+
You can assign effect parameters such as Time or Rate to a specific tempo, as 1/4 or 1/8 Dotted, instead of specifying the number of milliseconds. That will make the effect depend on the global or preset tempo. Tapping a different tempo will change the rate of the effect.
  
−
Read this: [[Delay block]]
+
Important: After assigning a parameter to a tempo, you can no longer adjust the time in the effect manually!
  
−
=Tempo and MIDI=
+
=Metronome=
  
−
==MIDI CCs==
+
The Tempo menu contains a metronome. Read this: [[Metronome]]
  
−
'''Tempo''': defaults to CC 14 on the Axe-Fx II, AX8 and FX8. Keep it this way to avoid issues. The III lets you assign the Tempo CC manually. FM3: ?
+
=Remote control=
  
−
'''Metronome''': CC 122. FM3: ?
+
==Footswitch==
  
−
==Showing the tempo on a foot controller==
+
Scroll to the Tempo CC in the I/O menu and hit Enter. Click the switch on the footswitch that you want to assign the Tuner to.
  
−
The Axe-Fx II, MFC-1010, AX8 and FX8 show the tempo.
+
Or configure it manually by assigning the Tuner MIDI CC to a switch on a MIDI controller.
  
−
Fractal Audio's FC series indicate the preset tempo on an Axe-Fx III. 3rd-party MIDI controllers can also show tempo when they have been programmed to act as a client to the Axe-Fx III, using Fractal Audio's protocol, or when using real-time sysex as [http://www.fractalaudio.com/downloads/misc/Axe-Fx%20III%20MIDI%20for%203rd%20Party%20Devices.pdf documented here].
+
Read <q>[[Expression pedals and external switches]]</q> for more information.
 +
 
 +
==MIDI CC==
 +
 
 +
The default MIDI CC for the Tuner is 14 on the Axe-Fx II, AX8, and FX8. Keep it like this to avoid issues.
 +
 
 +
The Axe-Fx III, FM9, and FM3 let you set the Tuner CC manually in the I/O menu.
 +
 
 +
==MFC-101==
 +
 
 +
The [[MFC-101 MIDI foot controller]] has a dedicated Tempo command for the Axe-Fx II when it's running in Axe-Fx Mode.
 +
 
 +
==FC-6 and FC-12 foot controllers==
 +
 
 +
The [[FC-6 and FC-12 foot controllers]] have a dedicated Tempo action.
  
 
==MIDI Clock==
 
==MIDI Clock==
  
−
Read this: [[MIDI#MIDI_Clock|MIDI Clock]]
+
Read <q>[[MIDI#MIDI_Clock|MIDI Clock]]</q> for more information.
 +
 
 +
==DAW==
 +
 
 +
<blockquote>
 +
'''FRACTAL AUDIO QUOTES'''
 +
<HR>
 +
 
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/bug-audible-glitch-when-using-midi-tempo-linked-to-the-delay-time.161248/post-1931097]
 +
It all depends on the accuracy of your DAW. If I set the BPM to 130 and the accuracy is 5ms it will occasionally go to 131 BPM on my system here. If I lower the accuracy to 2ms then it doesn't do that. And this is as would be expected. 130 BPM is 2.167 beats per second. MIDI Clock is 24 messages per beat. So that's 52 messages per second or a message every 19.2 ms. 129 BPM translates to 19.38 messages per second. So your messages need to be accurate down to fractions of a ms.
 +
</blockquote>
 +
</blockquote>
 +
 
 +
=Tips, tricks and troubleshooting=
 +
 
 +
==LED accuracy==
 +
 
 +
<blockquote>
 +
'''PREVIOUS GENERATIONS'''
 +
<HR>
 +
 
 +
<blockquote>
 +
[https://forum.fractalaudio.com/threads/does-the-tempo-led-actually-flash-in-time.51049/#post-658471]
 +
The tempo LED is handled by a low-priority thread so it isn't rock solid and the higher the CPU usage the less solid it will be.
 +
</blockquote>
 +
</blockquote>
 +
 
 +
==Tempo and Beats Per Minute (BPM) values==
 +
 
 +
The [http://wiki.fractalaudio.com/axefx2/index.php?title=Owners_Manuals Owner's Manuals] list the tempo values with the BPM equivalents.
 +
 
 +
==Show BPM on the Performance Page==
 +
 
 +
If you add Controllers > Tempo as the first control on a Performance Page on the Axe-Fx III, FM9, or FM3, you'll always see the preset's BPM value when switching presets from your foot controller.
  
−
=Tempo guide=
+
==Auto-activate a delay by tapping tempo==
  
−
The [http://wiki.fractalaudio.com/axefx2/index.php?title=Owners_Manuals Owner's Manuals] contain a Tempo Cross Reference guide.
+
Search the [[Delay block]] page for <q>auto delay</q>.
  
−
=SysEx commands for tempo=
+
==SysEx commands for tempo==
  
−
[[media:Axe-Fx-II-XL-Delay-Tempos.pdf |Here's a list]] of all SysEx commands for each tempo setting in the [[Delay block]] in the Axe-Fx II XL.
+
These are useful:
 +
* Fractal Audio: <q>[[media:Axe-Fx-II-XL-Delay-Tempos.pdf|List of all SysEx commands for each tempo setting in the Delay block in the Axe-Fx II XL]]</q>.
 +
* Kamilkisiel.net: <q>[http://www.kamilkisiel.net/axefx_tempo.html Fractal Audio Tempo SysEx Generator]</q>.
  
−
=Ticking tempo noise=
+
==Bleed-through tempo noise==
  
 
Audible bleed-through of the tempo signal can occur if the MIDI cable is not properly shielded. Use high-quality, properly shielded MIDI cables.
 
Audible bleed-through of the tempo signal can occur if the MIDI cable is not properly shielded. Use high-quality, properly shielded MIDI cables.
Line 68: Line 119:
 
[[category:Axe-Fx2]]
 
[[category:Axe-Fx2]]
 
[[category:FM3]]
 
[[category:FM3]]
 +
[[category:FM9]]
 
[[category:Axe-Fx3]]
 
[[category:Axe-Fx3]]
 
[[category:FX8]]
 
[[category:FX8]]
Line 73: Line 125:
 
[[category:Sounds]]
 
[[category:Sounds]]
 
[[category:Remote]]
 
[[category:Remote]]
 +
[[category:All]]

Latest revision as of 17:21, 8 April 2024

Channels or X/Y

  • Axe-Fx III, FM9, MF3: 4 channels
  • Axe-Fx II, AX8, FX8: no

Tempo button and menu

When tapping the Tempo button on the device, the Tempo menu appears on the hardware display.

On the Axe-Fx III, FM9, and FM3, the Tempo button also is a shortcut to the Controllers menu.

Tap tempo

The Global Settings menu lets you specify how tapping tempo works:

Average 
Averages the tempo to the last 10 taps. Average is usually a wise choice if you can't get the first taps right, and is the default setting.
Last Two 
Uses only the most recent two taps to determine the tempo. This acts faster but is also less precise.

Tap Tempo needs at least two taps to calculate.

See the Tap tempo issues discussion for more information.

Tempo per preset or global

You can specify whether you want to the tempo to apply to all presets (global) or per preset.

Tempo per channel or scene

Tempo is part of the Controllers block. That block has 4 channels, so a preset can have 4 different tempos which allows setting separate tempos per scene.

Syncing to the tempo

You can assign effect parameters such as Time or Rate to a specific tempo, as 1/4 or 1/8 Dotted, instead of specifying the number of milliseconds. That will make the effect depend on the global or preset tempo. Tapping a different tempo will change the rate of the effect.

Important: After assigning a parameter to a tempo, you can no longer adjust the time in the effect manually!

Metronome

The Tempo menu contains a metronome. Read this: Metronome

Remote control

Footswitch

Scroll to the Tempo CC in the I/O menu and hit Enter. Click the switch on the footswitch that you want to assign the Tuner to.

Or configure it manually by assigning the Tuner MIDI CC to a switch on a MIDI controller.

Read Expression pedals and external switches for more information.

MIDI CC

The default MIDI CC for the Tuner is 14 on the Axe-Fx II, AX8, and FX8. Keep it like this to avoid issues.

The Axe-Fx III, FM9, and FM3 let you set the Tuner CC manually in the I/O menu.

MFC-101

The MFC-101 MIDI foot controller has a dedicated Tempo command for the Axe-Fx II when it's running in Axe-Fx Mode.

FC-6 and FC-12 foot controllers

The FC-6 and FC-12 foot controllers have a dedicated Tempo action.

MIDI Clock

Read MIDI Clock for more information.

DAW

FRACTAL AUDIO QUOTES

[1] It all depends on the accuracy of your DAW. If I set the BPM to 130 and the accuracy is 5ms it will occasionally go to 131 BPM on my system here. If I lower the accuracy to 2ms then it doesn't do that. And this is as would be expected. 130 BPM is 2.167 beats per second. MIDI Clock is 24 messages per beat. So that's 52 messages per second or a message every 19.2 ms. 129 BPM translates to 19.38 messages per second. So your messages need to be accurate down to fractions of a ms.

Tips, tricks and troubleshooting

LED accuracy

PREVIOUS GENERATIONS

[2] The tempo LED is handled by a low-priority thread so it isn't rock solid and the higher the CPU usage the less solid it will be.

Tempo and Beats Per Minute (BPM) values

The Owner's Manuals list the tempo values with the BPM equivalents.

Show BPM on the Performance Page

If you add Controllers > Tempo as the first control on a Performance Page on the Axe-Fx III, FM9, or FM3, you'll always see the preset's BPM value when switching presets from your foot controller.

Auto-activate a delay by tapping tempo

Search the Delay block page for auto delay.

SysEx commands for tempo

These are useful:

Bleed-through tempo noise

Audible bleed-through of the tempo signal can occur if the MIDI cable is not properly shielded. Use high-quality, properly shielded MIDI cables.

Retrieved from "https://wiki.fractalaudio.com/wiki/index.php?title=Tempo&oldid=87976"