Forever Again
Inspired
There’s addressing bugs, then there’s advancements. Both make products better. It’s the natural cycle of software and hardware development.Ultimately, it's not important. Was just a curious question.
There’s addressing bugs, then there’s advancements. Both make products better. It’s the natural cycle of software and hardware development.Ultimately, it's not important. Was just a curious question.
I have no inside knowledge, but it seems to me that over time, Cliff's understanding of the complex behaviors of these circuits advances. It's not there were mistakes before, it's that the firmware gets more and more highly evolved, and represents amp behavior at a higher level.I am curious to know what this means. Does this mean that, something was done incorrectly translating the amp design into the digital domain (meaning - Cliff and Team were wrong...and the amp has been incorrect all along) or a bug/issue in the model itself that could have been introduced over time? I don't mean to be an arse here; I am only curious.
Make sure you really loaded the correct firmware.I updated but my most recent preset didn't make it. I saved the changes to Axe before I updated. I didn't save the preset though. Thankfully it's a variation of a previous preset. BUT here's what's weird - the preset says "EMPTY". Yet the FC-12 has the name of the preset.
I had something similar happen to me when I downloaded the last beta. I erased it from my computer and redownloaded it again. All was good when I transferred it to my Axe. I’m thinking the first download was corrupted somehow.I updated but my most recent preset didn't make it. I saved the changes to Axe before I updated. I didn't save the preset though. Thankfully it's a variation of a previous preset. BUT here's what's weird - the preset says "EMPTY". Yet the FC-12 has the name of the preset.
Ran into an issue with a single preset that caused all sound to drop out a second or two after selecting Channel D of the Drive block. I changed the drive type and it still occurred each time Channel D was selected. It happened a couple of times when selecting Channel C as well.
No sound from any other presets after losing audio in the initial preset. A reboot was the only solution to get sound back. Deleted the preset and loaded it from the backup file and experienced the same issue.
The handful of other presets I tried before switching to this particular preset worked fine, using the same drive block from my Block Library. When this preset was then selected, the audio drop out occurred each time requiring a reboot. Reverted to FW 31.0 and the issue is gone.
This might be a one-off situation but thought I'd share just in case there is an issue hiding somewhere.
CPU is @64%Have you checked the CPU when you do that? High CPU will make the sound drop out of course.
It's called Digital Evolution.I am curious to know what this means. Does this mean that, something was done incorrectly translating the amp design into the digital domain (meaning - Cliff and Team were wrong...and the amp has been incorrect all along) or a bug/issue in the model itself that could have been introduced over time? I don't mean to be an arse here; I am only curious.



I call it iterative design. Over years of familiarizing and implementing a complex problem, you step by step figure it out. Each new step build on knowledge and tools acquired from previous steps. It's how all innovation is structured and moves things forward.I am curious to know what this means. Does this mean that, something was done incorrectly translating the amp design into the digital domain (meaning - Cliff and Team were wrong...and the amp has been incorrect all along) or a bug/issue in the model itself that could have been introduced over time? I don't mean to be an arse here; I am only curious.
Unable to replicate the problem. There were no changes to the Drive block for that particular model. The only change between 31.00 and 31.01 was for the PI Fuzz.Ran into an issue with a single preset that caused all sound to drop out a second or two after selecting Channel D of the Drive block. I changed the drive type and it still occurred each time Channel D was selected. It happened a couple of times when selecting Channel C as well.
No sound from any other presets after losing audio in the initial preset. A reboot was the only solution to get sound back. Deleted the preset and loaded it from the backup file and experienced the same issue.
The handful of other presets I tried before switching to this particular preset worked fine, using the same drive block from my Block Library. When this preset was then selected, the audio drop out occurred each time requiring a reboot. Reverted to FW 31.0 and the issue is gone.
This might be a one-off situation but thought I'd share just in case there is an issue hiding somewhere.
This is what happened to me when I updated to beta 1. Redownload and reupdate fixed the problem.[Problem] All the presets are empty after this upgrade. However, I can see the preset names when I browse them either from the Axe-FX 'Presets' tab or from Axe-Edit. But when I load any preset it is blank, no title, no sound.
View attachment 163559
View attachment 163560
Proceeding to revert to 31.01 Beta 1 now.
**********************
[edit]: all good on beta-1. upgraded again to beta-2, and now everything is normal![]()
I recall that discussion on TGF, cool stuff!I'm impressed.
I can hear the squish from the Plexi models that I hear from my real Plexi's that was (as I remember) missing from previous firmwares.
Well done Fractal!
EDIT:
I don't know if what made it happen was the more accurate response to hotter input signal or the phase inverter but the combined response is really close to what I hear and feel from the real amp.
Fractal is closing the last 1% gap of tube amp emulation realism, which is amazing in itself.