Well, I've only tested it with 6.0+ presets. As far as I know though, the structure of the SYX files hasn't changed since v1.0 of the Axe-FX II came out, so technically it SHOULD work on ALL firmware versions of the Axe-II.
Definitely won't work on Standard/Ultra presets though, as those SYX files are radically different.
I'd appreciate it if anyone who is experiencing crashes can email me their SYX files so I can test of edge cases here. My email is:
devan (AT) axe-pad DOT com
Thanks!
Nice work! How does one get a hold of the sysex spec for the presets?
Any chance you could make this to open up Standard or Ultra files too? That would a tremendous resource to translate files over from the previous Axe.
An XML output that included meaningful tag names would be sweet too.
I took a go at creating XML from the CSV export, but the values in the CSV don't correspond to the values in the preset per se as far as I could tell?
For example, in a preset with a Drive block with the drive set at "2.01", there is no "2.01" value anywhere in the CSV export.
I was wanting the XML to do a "difference" between two presets.
The difference would let me see, quickly, only the parameters that were changed.
So, for example compare a downloaded preset and quickly see what AMP block parameters are different than the defaults.
I think this would be valuable to see what tweaks are being made by folks.
Richard
The app throws an exception when I try to open a preset. Running Win Vista Biz 32bit;
Exception occurred at address 0101B17E
Exception code C0000005: Access Violation
Process PID=2256 Image: F:\AxeFX Reporter\AxeFXReporter\AxeFXReporter.exe
Thread 1 Handle=000000B8 TID=1928
EAX=00E51128 EBX=00F6B784 ECX=00000014 EDX=00000020
ESI=00E510E0 EDI=00000014 EBP=0012FD0C ESP=0012FC7C
EIP=0101B17E FLG=00010206
Call Stack:
0101B17E
004304E0
004272A7
00427914
004316B2
010BE4E8
76E0E1C6
76E0E199
Really nice! Thank you for you work!
Would be easy for you to add a "save as image" option?
Levi
One has to spend HOURS looking at SYX files in a hex editor, and doing a lot of guessing and testing!
No specs here - I've just had to trace signals sent between Axe-Edit and the Axe-FX and extrapolate the info... I had to do the work for AxePad anyhow, and so AxeReporter was just a side project I did with the leftovers...
Hmmm.... *puts on thinking hat* ...
An XML output that included meaningful tag names would be sweet too.
I took a go at creating XML from the CSV export, but the values in the CSV don't correspond to the values in the preset per se as far as I could tell?
For example, in a preset with a Drive block with the drive set at "2.01", there is no "2.01" value anywhere in the CSV export.
I was wanting the XML to do a "difference" between two presets.
The difference would let me see, quickly, only the parameters that were changed.
So, for example compare a downloaded preset and quickly see what AMP block parameters are different than the defaults.
I think this would be valuable to see what tweaks are being made by folks.
Richard
One has to spend HOURS looking at SYX files in a hex editor, and doing a lot of guessing and testing!
No specs here - I've just had to trace signals sent between Axe-Edit and the Axe-FX and extrapolate the info... I had to do the work for AxePad anyhow, and so AxeReporter was just a side project I did with the leftovers...
Hmmm.... *puts on thinking hat* ...