PacoCasanovasOld
Fractal Fanatic
public beta in terms of FAS is like having official releases from other companies.
That's not what I said at all.it seems your main issue, judging from other comments in this thread, is that "things should not go wrong with anything Fractal releases."
That's not what I said at all.
no beta should be released until that issue can be resolved
We know that a corrupted preset can also lock up the AF2, again that simply shouldn't be possible.
they either need to fix this or if it can't be fixed, they should disable...
Having it lock up and crash should not be acceptable.
Actually, Microsoft skewed it two decades ago when they started charging money for Windows beta.i'm sure google skewed everyone's definition of "beta" with gmail being in beta stage for so long, and other companies followed suite and used it more as a marketing technique to sell their product.
Not the same thing AT ALL. A bug that crashes the system is in a completely different category than a bug where a feature doesn't work or a setting doesn't show the right value or even AE not showing the same info as the AF2. When there's any possible scenario where just operating the product can stop it from responding to controls or stop producing sound, this is a what we call a "show stopper" bug and most companies will pull their firmware and fix that sort of bug before releasing it again to the public, beta, alpha or whatever!but more specifically, the notion of "they shouldn't release a beta until it doesn't crash the system" is basically saying "they shouldn't release a beta until all the bugs are gone"
A bug that crashes the system is in a completely different category....most companies will pull their firmware and fix that sort of bug before releasing it again to the public, beta, alpha or whatever!
they did.
it's not like they know and willingly release a firmware beta with that category of bug haha. but that's exactly what a beta is for! right?
I really like the last beta firmware. Dial-in a good sounding amp is now very simple (ok, not only due to the last beta but since the v11) and this is really a significant step in the right direction. For example, I really get a nice AC30 sound with default settings, only by slightly adjusting the drive/bass/med/high to taste (like a real amp ^^). No more needs to tweak the advanced settings for hours
My opinion is the focus now should be put on IRs, finding more easy ways to deal with the massive amount of possibilities that we have with them. I'm sure that many people lose a lot of time in their presets by tweaking the amp while the "issue" in their sound is coming from a wrong selected IR.
I'm still trying here to promote a "matching cab" IR option in the cab block that would automatically select an IR according to the amp in front of it.
A way to set the amp block speaker parameters to a new default based on the IR that is loaded would be cool.
BTW, is the Tiny Terror modelled in 15 or 7 watts mode?
public beta in terms of FAS is like having official releases from other companies.
***cough*** line 6 *** cough***
So when does the public Beta become a release? I mean does one wait until no more issues are reported, makes sense just asking as I don't know.