October 2024: Fractal Audio's VP4 Virtual Pedalboard added to the wiki.
Difference between revisions of "Presets"
Jump to navigation
Jump to search
m (moved Preset loading/switching to Preset switching) |
|||
| Line 7: | Line 7: | ||
=User contributions= | =User contributions= | ||
| − | ==Preset | + | ==Preset management: sharing presets between Axe-Fx II and Axe-Fx II XL== |
* Presets created on the Axe-Fx II XL can be loaded in the Axe-Fx II via Axe-Edit. | * Presets created on the Axe-Fx II XL can be loaded in the Axe-Fx II via Axe-Edit. | ||
| − | ==Preset | + | ==Preset management: importing presets== |
* Beside the factory presets, you can load other users' presets into your Axe-Fx. Presets have a .syx file extension. Presets are available through the user forum and Axe-Change for example. | * Beside the factory presets, you can load other users' presets into your Axe-Fx. Presets have a .syx file extension. Presets are available through the user forum and Axe-Change for example. | ||
* If you use [[Fractal-Bot]], [[Axe-Edit]] or a MIDI librarian such as Snoize SysEx Librarian (Mac) or MIDI-OX (Windows): make a connection between your computer and the Axe-Fx, load the .syx file and send it to the Axe-Fx. The Axe-Fx is always ready to receive presets in this way. If you upload a preset onto the Axe-Fx this way, the preset is not yet stored on the Axe-Fx but kept in a buffer. If you want to keep it on the Axe-Fx, select a preset slot and save it. | * If you use [[Fractal-Bot]], [[Axe-Edit]] or a MIDI librarian such as Snoize SysEx Librarian (Mac) or MIDI-OX (Windows): make a connection between your computer and the Axe-Fx, load the .syx file and send it to the Axe-Fx. The Axe-Fx is always ready to receive presets in this way. If you upload a preset onto the Axe-Fx this way, the preset is not yet stored on the Axe-Fx but kept in a buffer. If you want to keep it on the Axe-Fx, select a preset slot and save it. | ||
* Preset files are also kept in bank files. You can use Axe-Edit to pick individual presets from a bank file. | * Preset files are also kept in bank files. You can use Axe-Edit to pick individual presets from a bank file. | ||
| − | ==Preset | + | ==Preset management: preset switching speed== |
* Cliff: "The II does a few things different to try to make patch changes more seamless." [http://forum.fractalaudio.com/axe-fx-ii/39341-axe-fx-ii-spill-over-vs-axe-fx-std-ultra.html#post535112 Source] | * Cliff: "The II does a few things different to try to make patch changes more seamless." [http://forum.fractalaudio.com/axe-fx-ii/39341-axe-fx-ii-spill-over-vs-axe-fx-std-ultra.html#post535112 Source] | ||
* Cliff: "Dropout is only 20-30 ms. If you are experiencing more than that then your MIDI controller is not programmed properly." [http://forum.fractalaudio.com/axe-fx-ii-discussion/58589-preset-switching-latency-2.html#post732479 Source] | * Cliff: "Dropout is only 20-30 ms. If you are experiencing more than that then your MIDI controller is not programmed properly." [http://forum.fractalaudio.com/axe-fx-ii-discussion/58589-preset-switching-latency-2.html#post732479 Source] | ||
* Firmware 11: "Improved preset switching speed, in some cases drastically improved". | * Firmware 11: "Improved preset switching speed, in some cases drastically improved". | ||
* For gapless switching, use [[Preset scenes]]. | * For gapless switching, use [[Preset scenes]]. | ||
| + | |||
| + | ==Preset management: sending presets to the Axe-Fx using a MIDI librarian == | ||
| + | * Cliff: "There are two possible destinations for a preset: the edit buffer or a defined preset number. The destination is encoded in the data. If it's not going to the edit buffer then the preset was harvested from a hard drive somehow. When you load a preset with Axe-Edit it sets the destination bytes. However if you use a librarian then the preset may go to the edit buffer or to a defined preset location depending upon the destination bytes. You can identify the preset destination from the data. If the seventh byte is 7F then it will go into the edit buffer, otherwise it will go into preset memory. For example: F0 00 01 74 03 77 7F 00 goes to the edit buffer whereas F0 00 01 74 03 77 01 02 will go to bank B preset 2 (patch 130)." [http://forum.fractalaudio.com/axe-fx-ii-discussion/58581-help-loading-presets-using-sysex-librarian.html#post732659 Source] | ||
[[category:Presets and effects]] | [[category:Presets and effects]] | ||
[[category:Software]] | [[category:Software]] | ||
Revision as of 11:07, 11 April 2014
Contents
Manual
4.1 Presets — 6 Global Blocks — 10.2 Preset Utilities — 13 Backing Up and Restoring
User contributions
Preset management: sharing presets between Axe-Fx II and Axe-Fx II XL
- Presets created on the Axe-Fx II XL can be loaded in the Axe-Fx II via Axe-Edit.
Preset management: importing presets
- Beside the factory presets, you can load other users' presets into your Axe-Fx. Presets have a .syx file extension. Presets are available through the user forum and Axe-Change for example.
- If you use Fractal-Bot, Axe-Edit or a MIDI librarian such as Snoize SysEx Librarian (Mac) or MIDI-OX (Windows): make a connection between your computer and the Axe-Fx, load the .syx file and send it to the Axe-Fx. The Axe-Fx is always ready to receive presets in this way. If you upload a preset onto the Axe-Fx this way, the preset is not yet stored on the Axe-Fx but kept in a buffer. If you want to keep it on the Axe-Fx, select a preset slot and save it.
- Preset files are also kept in bank files. You can use Axe-Edit to pick individual presets from a bank file.
Preset management: preset switching speed
- Cliff: "The II does a few things different to try to make patch changes more seamless." Source
- Cliff: "Dropout is only 20-30 ms. If you are experiencing more than that then your MIDI controller is not programmed properly." Source
- Firmware 11: "Improved preset switching speed, in some cases drastically improved".
- For gapless switching, use Preset scenes.
Preset management: sending presets to the Axe-Fx using a MIDI librarian
- Cliff: "There are two possible destinations for a preset: the edit buffer or a defined preset number. The destination is encoded in the data. If it's not going to the edit buffer then the preset was harvested from a hard drive somehow. When you load a preset with Axe-Edit it sets the destination bytes. However if you use a librarian then the preset may go to the edit buffer or to a defined preset location depending upon the destination bytes. You can identify the preset destination from the data. If the seventh byte is 7F then it will go into the edit buffer, otherwise it will go into preset memory. For example: F0 00 01 74 03 77 7F 00 goes to the edit buffer whereas F0 00 01 74 03 77 01 02 will go to bank B preset 2 (patch 130)." Source
