GotMetalBoy
Power User
Revision 1.3 has been uploaded.
Cliff, will Revision 1.3 work with Firmware 1.13 or is that a typo?
Revision 1.3 has been uploaded.
Cliff, will Revision 1.3 work with Firmware 1.13 or is that a typo?
Hi Al,@FractalAudio I see no way of retrieving the current preset number, is it possible ?
Yes, check specs 1.13 i think it's now returned with preset nameHi 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.
The Midi Spec document has is own numbering. This is independent of the Firmware numbering.
Is this info discussed in this thread intended for developers or all midi controller users?
I have AXE III on the way, and i also own a Liquid Foot Mini. Should i be reading this to program my LF Mini ?
No you don't need to read this to program your LF. Jeff, the owner of FAMC should be reading it, so he can update the LF+ firmware, so it can sync with the Axe-Fx III.
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.Yes, check specs 1.13 i think it's now returned with preset name
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 just on the verge of diving in to said Looper functionality, and I'll let you know what I find.Is there a bug in Firmware 1.15? While my Looper-Block is recording, the Rec und Play Button are active. After getting the Looper status with 0x0f 0x7f I will get Bit 2 (Play) is set. I never get back Bit 1 (Record)! Same behaviour at Half Speed!
I’ve been doing a lot of the above and never had that problemSo 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 just on the verge of diving in to said Looper functionality, and I'll let you know what I find.
If the looper only plays the loop I get:
F0 0 1 74 10 F 2 cs F7
My post was not directed at you or I would have quoted you like above. Just trying to help the community...
However, the response you are getting back indicates that you are in overdub mode (both play and record buttons are lit). Which is the default behavior when you press the record button the second time after you record the loop. So the response your getting above is the correct one in that case. There is an option to change what the record button will do after the second press in the looper settings. I'm not at my axefx so I can't look at what is being returned for the looper state, but if nobody else chimes in I'll take a look tonight and verify the return strings your getting.
If record and play are lit, it should be returning 3Oh, I am sorry. I missunderstood. BTW: Good Job with the EXCEL tab! I like it!
Die I missunderstood the documentation? The response from the Axe-FX III is there described as setted bits. So if the Axe-FX sends a "2" then the Bit 1 is set! That means "Play". Bit 2 is overdub! Is this right or did I missunderstood the MIDI-Sysex-Spec?