Possible BUG(s)? Looper State responses in 3rd Party MIDI interface

[simonp54]

When PLAYing and then pressing the RECORD, the AxeFX screen shows REC, PLAY and OVERDUB lit up. The bitmask shows PLAY and OVERDUB, but not RECORD. Should it?

There are possibly some other permutations based on comments i've seen from other users (in the 3rd party thread)

FW 1.15 Sep 7 2018 USB 1.06 FPGA 16

 

[simonp54]

@FractalAudio, I notice some other items have been indicated as fixed in next release, can you let us know if this is one of them. Thanks

 

[shorek]

It's not a bug, you should go to Looper block ,
Second Rec option, Play or Overdub,
Don't forget to store it

 

[DavezHear]

It's not a bug, you should go to Looper block ,
Second Rec option, Play or Overdub,
Don't forget to store it

Yes it is a bug. Simon is not talking about the second press action, he is talking about the SysEx "return value" being incorrect (Bit 0 doesn't turn on) when the record button is active. Doesn't matter if it record armed, recording or overdub, still returns bit 0 as 0 and it should probably be 1 in all those cases. See my spread sheet of return values, the ones highlighted in red are wrong, cells in yellow are returning duplicated values.

Axe-Fx III Third-Party MIDI Spec

 

[FractalAudio]

Fixed for next release.