OK let me be perfectly clear, I've got an Odessa and a HEL, so I've spent my money to support this. That said, I am honestly a bit baffled at the design choices and just wanted an *honest* explanation of why there will be no firmware updates. Look, I get XAOC doesn't want to update the firmware or have to support users bricking their units. But *field programming* a field programmable gate array is not impossible, not impractical, and honestly not even that hard once you are supplied the compiled config file for the chip.
Yes FPGA software tends to be windows-specific, and this causes PITA situations on Macs which many musicians run. I get that. But I also think it's a little arrogant to think that someone got the FPGA design absolutely perfect the first time around and there's nothing that could be added or improved upon or small bugs to fix? These are common issues in all integrated development and software projects. Virtually everyone has chosen to make it possible to update the firmware on their modules:
All of these manufacturers decided that it would be best to allow them to fix and expand their modules after initial release. In many cases the feature-set grew beyond what was initially envision or old idea that were previously difficult to implement are solved. Look at the Shapeshifter, look at the E352. Look at any of the 1010 modules, or especially the mutable modules that all have alternative firmwares written for them. Literally all the manufacturers are taking an "updatable-firmware" approach and I'm honestly a little bit baffled why there is such hostility over questioning such an obvious design choice? Does it not seem obvious that an FPGA-based module *could* and maybe *should* have firmware updates, even if they are just bug fixes?
Modules like the Black Noir saw new effects and bug fixes quickly after its release. Orthogonal has been doing a decade-long campaign of improving the ER-modules with constant new firmware updates. Tiptop fixes bugs. WMD does the same. et al.
There's a degree of arrogance to design an FPGA module and then say 'I'm done; it's perfect'. We're all human here, to err is not a crime. To pretend like it couldn't be fixed though....
Look I get it, you don't want people doing their own updates. But again, I've mentioned you could offer a pay-service for upgrades. Maybe in 1 year you have new ideas for the Odessa you want to implement; does that mean I need to buy version 2 even if it's running the exact same hardware?