We would like to remind our members that this is a privately owned, run and supported forum. You are here at the invitation and discretion of the owners. As such, rules and standards of conduct will be applied that help keep this forum functioning as the owners desire. These include, but are not limited to, removing content and even access to the forum.

Please give yourself a refresher on the forum rules you agreed to follow when you signed up.

Search results for query: *

Users: JackEddyCO
Order by date

J
Third-Party MIDI Spec

Wait! I'm seeing the "0x64" error message when I send a Tempo Tap command as well The Temp Tap command still does it's thing (help in setting the tempo), but still the error message response is sent back. Wacky!
- JackEddyCO
- Post #180
- Feb 28, 2019
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

I too am seeing this error message when I send a valid Tuner On/Off command. The tuner goes On or Off in response to my commands, but the "0x64" error message is also being sent back. Other commands I send don't result in an "0x64" error message. Is there something funky with the current...
- JackEddyCO
- Post #179
- Feb 28, 2019
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

So far, the only bug I've found in firmware v1.15 is that if you switch the Preset via the AF3 front panel, then use MIDI to change the Scene, occasionally the AF3 doesn't give you a SET/GET SCENE (COMMAND 0CH) back, as it normally does. But I haven't dived in to Looper functions much. I'm...
- JackEddyCO
- Post #113
- Sep 12, 2018
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

Ah! There it is! I'd missed it in the new spec (and am a little surprised my old code still reads the preset name okay). Thank you much.
- JackEddyCO
- Post #111
- Sep 10, 2018
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

Hi Al, Did you ever find a way to query the current preset number, or is that something upon which us mere mortals are still waiting? Thank you.
- JackEddyCO
- Post #103
- Sep 9, 2018
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

Sorry for the hijack, everyone. In C, XOR is accomplished like this: result = byte1 ^ byte2;
- JackEddyCO
- Post #31
- Jul 22, 2018
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

Checksum: Yes, it's the same as for the II. Very simple: XOR all the bytes in your midi message before and up to the checksum byte. AND that value with 0x7F, and boom, there's your checksum.
- JackEddyCO
- Post #29
- Jul 22, 2018
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

Cool. I will reach out to Cliff. Thanks for responding, man.
- JackEddyCO
- Post #25
- Jul 22, 2018
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

Ah HA! You lead me to the problem. I was preparing an answer for you, documenting my meticulous checksum-generation algorithm, providing my SysEx commands and responses received from Axe-FX III, and mentioning Axe-FX III's firmware version just to be... ...Whaaaaa? Oops, I still had 1.12...
- JackEddyCO
- Post #24
- Jul 22, 2018
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

Has anyone tried sending the query commands listed in doc with success? When I send Get Scene, Query Patch Name, or Query Scene Name via the old fashioned hardware MIDI port, I get an "0x64" error response back from the Axe-FX III.
- JackEddyCO
- Post #22
- Jul 22, 2018
- Forum: Axe-Fx III Discussion
J
Third-Party MIDI Spec

Can you please share the list of effect IDs?
- JackEddyCO
- Post #21
- Jul 22, 2018
- Forum: Axe-Fx III Discussion