SysEx Explorations

Filter:

03 08 = Filter1
04 08 = Filter2

00 00 = Type
01 00 = Freq
02 00 = Q
03 00 = Gain
04 00 = Level
05 00 = Balance
06 00 = Bypass Mode
07 00 = R Offset
08 00 =
09 00 = Pan L
0A 00 = Pan R
 
Flange:

06 07 = Flanger1
07 07 = Flanger2

00 00 = Rate
01 00 = Tempo
02 00 = Depth
03 00 = Feedback
04 00 = Bass
05 00 = Treble
06 00 = Bass Freq
07 00 = Treble Freq
08 00 = Time
09 00 = Manual
0A 00 = LFO Phase
0B 00 = LFO Type
0C 00 = LFO Hicut
0D 00 = Auto Depth
0E 00 = Mix
0F 00 = Level

00 01 = Balance
01 01 = Bypass Mode
02 01 = Global Mix
03 01 =
04 01 = Phase Reverse
05 01 = Dry Delay
 
Four more (I didn't do all the blocks):

Graphic EQ:

06 06 = GEQ1
07 06 = GEQ2

00 00 = 63
01 00 = 125
02 00 = 250
03 00 = 500
04 00 = 1K
05 00 = 2K
06 00 = 4K
07 00 = 8K
08 00 =
09 00 = Level
0A 00 = Balance
0B 00 = Bypass Mode
 
Mixer:

09 08 = Mixer1
0A 08 = Mixer2

00 00 = Gain1
01 00 = Gain2
02 00 = Gain3
03 00 = Gain4
04 00 = Pan1
05 00 = Pan2
06 00 = Pan3
07 00 = Pan4
08 00 = Master Level
09 00 = Output Mode
 
Parametric EQ:

08 06 = PEQ1
09 06 = PEQ2


00 00 = Freq1
01 00 = Freq2
02 00 = Freq3
03 00 = Freq4
04 00 = Freq5
05 00 = Q1
06 00 = Q2
07 00 = Q3
08 00 = Q4
09 00 = Q5
0A 00 = Gain1
0B 00 = Gain2
0C 00 = Gain3
0D 00 = Gain4
0E 00 = Gain5
0F 00 =

00 01 = Level
01 01 = Pan
02 01 = Bypass Mode
03 01 =
04 01 = Type 1 (Low)
00 00 = Shelving
01 00 = Peaking
02 00 = Blocking
05 01 = Type 5 (High)
 
Phaser:

0A 07 = Phaser1
0B 07 = Phaser2


00 00 = Order
01 00 = Rate
02 00 = LFO Type
03 00 = Tempo
04 00 = Depth
05 00 = Res
06 00 = Freq
07 00 = Freq Span
08 00 = LFO Phase
09 00 = Mix
0A 00 = Level
0B 00 = Balance
0C 00 = Bypass Mode
0D 00 = Global Mix

That's it for now.
 
chase: thanks man. I have a little Perl script here that'll format all that stuff for the wiki. I'll get it up later today. :)
 
Thanks to everyone. This is really helpful.


I wanted to make one more argument, to emphasize why
this sysex business is important, and to raise an issue
with the design of all these types of devices.

Think about how your big rack works. You have a couple different
units in there, maybe one dedicated to reverbs, one to delays, etc.
each of these units has its own midi-PC controlled patch bank. So
you change the configuration by sending multiple PCs.

This is actually _simpler_ than an all-in-one design like the
Axe-Fx, because having multiple PCs factors the configuration
space, reducing the combinatorial complexity that occurs if you
only have one set of PCs.

This may seem a little pointy-headed, but it's one of those things
that becomes obvious when you start trying to layout your patches.

To put it in short techno-speak, all-in-one units with one patch-bank
address space do not scale. With each added effect type, the
configuration space grows multiplicatively.


Simple Example: I typically use
3 distinct delay configurations
2 distinct reverb configurations
2 distinct chorus configurations

That's really not that much. But it's still 12 different configurations,
not counting variations in the amp/cab block. With the naive PC/CC setup,
that means 12 separate patches. When all is done, I end up with 30 - 50
patches, where it feels like just a few should be enough.
Managing this is more painful than it should be.


Maybe for the "Axe-Fx II" Cliff can fix this problem. It's easy to do
in principle; you allow separate PC addressing for different device types,
so you can configure them in their own "sub-banks", and select them
independently. You have to do it without eating up MIDI channels
(which is something that happens in the big rack), but that doesn't
seem like a big problem.

In the meantime, the only practical solution is to try to set up a
few special "re-configuration" sysex messages, to help reduce the
patch space. Every little bit helps a lot; in the simple example,
reconfiguring delays on the fly saves a factor of 3, which is huge.


Anyway, maybe this is all obvious, but I wanted to say it as
clearly as I could. I'm guessing that I'm not alone...
 
I think I know what you mean.
It would be like having a virtual rack within the Axe-fx.
You would have to assign a channel to each block and save every effect to a preset per block.
It's possible this would acquire a lot of memory.
On the other hand, since you would be able to make combinations you wouldn't need that many, at least no 128 or so per effect.
Lets say you can assign a PC to each block.
you build a virtual rack in the axe-fx and save different variations of edffect blocks.
Channel1 = Amp
Channel2 = Drive
Channel3 = Delay
Channel4 = Modulation
Channel5 = Harmonizer
.....
Channel16= Reverb
Save different amp settings into amp presets
Same for the rest of the blocks.

On your pedal, simply program the combinations you want.
I read a post about someone who would like to change channels on an amp.
This way it could work.
I've been thinking the same about the harmonizer.
I have to copy a preset for each variation in key, scale, voice1 and voice2.
Wouldn't it be simpler if I could save these variations in separate harmonizer blocks and simply send a PC on the harmonizer channel.

Lets say you would only have 128 presets on the Ax-fx.
But these would be 128 virtual racks, so only variations in routing.
But the rest of the memory is used to save effect block presets.

You would the be able to make a whole lot more combinations than you can now.
Perhaps the only limitation would be that you only would have 15 blocks per General preset.
So Channel 0 would be the preset on the Axe-fx and the remaining 15 cahnnels could be assigned to each block in that preset.
 
gjungman said:
Thanks to everyone. This is really helpful.


I wanted to make one more argument, to emphasize why
this sysex business is important, and to raise an issue
with the design of all these types of devices.

Think about how your big rack works. You have a couple different
units in there, maybe one dedicated to reverbs, one to delays, etc.
each of these units has its own midi-PC controlled patch bank. So
you change the configuration by sending multiple PCs.

This is actually _simpler_ than an all-in-one design like the
Axe-Fx, because having multiple PCs factors the configuration
space, reducing the combinatorial complexity that occurs if you
only have one set of PCs.

This may seem a little pointy-headed, but it's one of those things
that becomes obvious when you start trying to layout your patches.

To put it in short techno-speak, all-in-one units with one patch-bank
address space do not scale. With each added effect type, the
configuration space grows multiplicatively.


Simple Example: I typically use
3 distinct delay configurations
2 distinct reverb configurations
2 distinct chorus configurations

That's really not that much. But it's still 12 different configurations,
not counting variations in the amp/cab block. With the naive PC/CC setup,
that means 12 separate patches. When all is done, I end up with 30 - 50
patches, where it feels like just a few should be enough.
Managing this is more painful than it should be.


Maybe for the "Axe-Fx II" Cliff can fix this problem. It's easy to do
in principle; you allow separate PC addressing for different device types,
so you can configure them in their own "sub-banks", and select them
independently. You have to do it without eating up MIDI channels
(which is something that happens in the big rack), but that doesn't
seem like a big problem.

In the meantime, the only practical solution is to try to set up a
few special "re-configuration" sysex messages, to help reduce the
patch space. Every little bit helps a lot; in the simple example,
reconfiguring delays on the fly saves a factor of 3, which is huge.


Anyway, maybe this is all obvious, but I wanted to say it as
clearly as I could. I'm guessing that I'm not alone...


How are you planning to reconfigure your delays?
 
Guys, so here's something weird. When I download patches from my Axe-Fx Standard, SysEx Librarian always says the manufacturer is "Warner New ME". And when posting those files here, people have complained that they wouldn't work with their Axe-Fx. That patches they download are listed as "Brooktree" with the manufacturer ID.

Today I tried to use Stringtheorist's Paisley patch on my Axe-Fx -- opened it in SysEx Librarian and tried to send it to my unit. But it refused to load it up. Manufacturer, in SysEx Librarian was listed as...you got it...Brooktree. So I opened the file up in OxED, selected the 4th block (7D) and switched it to (01). So block 2, 3 and 4 went from 00 00 7D to 00 00 01 -- that's Brooktree --> Warner New Music, according to the manaufacturer ID codes. After that change: it worked. The patch was accepted by my Axe-Fx.

All this says is the SysEx ID is embedded in patch dumps. That's annoying. :)
 
iaresee said:
Guys, so here's something weird. When I download patches from my Axe-Fx Standard, SysEx Librarian always says the manufacturer is "Warner New ME". And when posting those files here, people have complained that they wouldn't work with their Axe-Fx. That patches they download are listed as "Brooktree" with the manufacturer ID.

Today I tried to use Stringtheorist's Paisley patch on my Axe-Fx -- opened it in SysEx Librarian and tried to send it to my unit. But it refused to load it up. Manufacturer, in SysEx Librarian was listed as...you got it...Brooktree. So I opened the file up in OxED, selected the 4th block (7D) and switched it to (01). So block 2, 3 and 4 went from 00 00 7D to 00 00 01 -- that's Brooktree --> Warner New Music, according to the manaufacturer ID codes. After that change: it worked. The patch was accepted by my Axe-Fx.

All this says is the SysEx ID is embedded in patch dumps. That's annoying. :)
I'm not sure where you get the translation of SysEx ID to an actual name (what software are you using, simply out of curiosity?, or is that part of OxED?), but you can change the Axe-Fx's SysEx ID.
The default is 125. (Also known as 7D in hex.)
I/O menu, MIDI page, 6th parameter down.
 
godprobe said:
iaresee said:
Guys, so here's something weird. When I download patches from my Axe-Fx Standard, SysEx Librarian always says the manufacturer is "Warner New ME". And when posting those files here, people have complained that they wouldn't work with their Axe-Fx. That patches they download are listed as "Brooktree" with the manufacturer ID.

Today I tried to use Stringtheorist's Paisley patch on my Axe-Fx -- opened it in SysEx Librarian and tried to send it to my unit. But it refused to load it up. Manufacturer, in SysEx Librarian was listed as...you got it...Brooktree. So I opened the file up in OxED, selected the 4th block (7D) and switched it to (01). So block 2, 3 and 4 went from 00 00 7D to 00 00 01 -- that's Brooktree --> Warner New Music, according to the manaufacturer ID codes. After that change: it worked. The patch was accepted by my Axe-Fx.

All this says is the SysEx ID is embedded in patch dumps. That's annoying. :)
I'm not sure where you get the translation of SysEx ID to an actual name (what software are you using, simply out of curiosity?, or is that part of OxED?), but you can change the Axe-Fx's SysEx ID.
The default is 125. (Also known as 7D in hex.)
I/O menu, MIDI page, 6th parameter down.

He gets it from here: http://www.midi.org/techspecs/manid.php

A Midi manufacturers association purports to issue assigned ID's to various companies, a service for which they charge a fee. This is your basic marketing bunk. There's no real need for it, if you are addressing messages to a rack full of devices, you just need to make sure no two use the same ID, and you need to know what ID each is using. Perhaps some brain-dead devices do not allow you to configure the ID, I don't know. I doubt the patches iarcee tried to load were rejected by the Axe-Fx, if that were the case it surely would have rejected the one he edited, since it no longer contained the ID 7D (125). More than likely it was the librarian software that refused to send it, which, in my opinion, makes it brain-dead software.
 
Back
Top Bottom