Michael the Midi Fighter Engineer here, first off I apologize for the delay in resolution of these issues.
The last thing I want to do is keep any user waiting, but unfortunately as an employee I cannot always decide where my efforts are focused, for the past month my time has been 125% taken up with another project.
Anyway that project is now complete, and this week I will be working on completing all bug fixes for the firmware and utility.
Ryan - I was completely aware of the rainbow bug when I pushed that firmware, as Stewe pointed out it was not a bug in the firmware itself, but a bug in the midi fighter utility which was exposed by the latest firmware update. While I agree this is sloppy I simply did not have the time to push a full utility release to correct the rainbow issue, yet I had firmware available which fixed issues which many users where complaining about. Given the rainbow issue was only a minor/confusing annoyance which only effected the device while using the utility I decided it was more important users got the fixes they where waiting for.
In regards to the other bug you mentioned, as I’m sure you found when you rolled back this was also how the factory firmware worked. If any LED display on the twister receives MIDI in to set its state it is assumed the software is in control of the state from that point on, this can be confusing when creating a mapping. I initially took this approach trying to solve race conditions caused by lag in MIDI out from host software like Traktor. The next release uses a totally different approach which solves all the lag / display lock up issues.
Appreciate the difficulty with the time and benefit ratio but wanted to say a big thanks from, I’m sure, everyone for an excellent controller. Quality Sir.