I think it needs FW 11 primarily because 10.01 is a silly number to end a FW history
Hmmm. Not too sure about that. When was the last time anyone from Fractal even posted anything about fixing the existing AX8 bugs? Last thing I remember was a thank you and goodnight message as the AX8 lights were turned off and the door was locked and bolted. Even the recent AX8 Edit update has bugs.I think patience is the key guys. Cliff and FAS never cease to amaze us
I tend to agree here..but who really knows ( besides CC).....From many years-past comments from Cliff and other Fractal staffers, here and other places like TGP, Rig-Talk, etc, you could arrive at your own conclusion. Mine is that AX8 is really, truly done and will never get another update.
I would SO love to be wrong .
The gist is: Cliff himself did\does all firmware code work for Axe-II, but he never did AX8\FX8 himself. Those were jobbed out to other(s) staff who are long gone. The AX8\FX8 firmware was developed separately and they only ported in Cliff's block code (the algorithms that make it sound the way it does, Cliff's most critical IP).
I got the impression it's either not possible, or at least a real time-consuming PITA for Cliff to dive in there and create AX8 updates himself at this point. Whereas it's (relatively) easy for him to apply his latest Ares code to the II, release it and reap the praise.
All this IMO. Educated guess? Never say never? (wait, I already did above...)
I got the impression it's either not possible, or at least a real time-consuming PITA for Cliff to dive in there and create AX8 updates himself at this point. Whereas it's (relatively) easy for him to apply his latest Ares code to the II, release it and reap the praise.
The problem which came to my mind:From many years-past comments from Cliff and other Fractal staffers, here and other places like TGP, Rig-Talk, etc, you could arrive at your own conclusion. Mine is that AX8 is really, truly done and will never get another update.
I would SO love to be wrong .
The gist is: Cliff himself did\does all firmware code work for Axe-II, but he never did AX8\FX8 himself. Those were jobbed out to other(s) staff who are long gone. The AX8\FX8 firmware was developed separately and they only ported in Cliff's block code (the algorithms that make it sound the way it does, Cliff's most critical IP).
I got the impression it's either not possible, or at least a real time-consuming PITA for Cliff to dive in there and create AX8 updates himself at this point. Whereas it's (relatively) easy for him to apply his latest Ares code to the II, release it and reap the praise.
All this IMO. Educated guess? Never say never? (wait, I already did above...)
I'm working on Ares 2.00 for the AX-8. It's difficult though since the processor isn't as powerful and I'm having difficulty getting the new algorithms to run in the allotted time. I've also been sick all week and only have enough strength to work a couple hours a day.
I'm working on Ares 2.00 for the AX-8. It's difficult though since the processor isn't as powerful and I'm having difficulty getting the new algorithms to run in the allotted time. I've also been sick all week and only have enough strength to work a couple hours a day.
no other gear has ever been EOL'd with existing bugs...Well, all I will say is that for the future, once bitten, twice shy. If the AX8 gets left in limbo with known bugs, that says enough about a company for me.
Well, all I will say is that for the future, once bitten, twice shy. If the AX8 gets left in limbo with known bugs, that says enough about a company for me.
I'm working on Ares 2.00 for the AX-8. It's difficult though since the processor isn't as powerful and I'm having difficulty getting the new algorithms to run in the allotted time. I've also been sick all week and only have enough strength to work a couple hours a day.