Found a weird bug. I routinely use GGD Cali for my IRs, and I just loaded a new one into the cab manager. Every time I try and load that specific IR into the cab block, the FM3 makes a permanent "eeeeeeee" sound and freezes until I shut it off manually.
What is "GGD Cali"?
Sounds like a GGD cali problem.Found a weird bug. I routinely use GGD Cali for my IRs, and I just loaded a new one into the cab manager. Every time I try and load that specific IR into the cab block, the FM3 makes a permanent "eeeeeeee" sound and freezes until I shut it off manually.
FWIW, my GGD Oversized Cali exported WAV’s are working just fine on my end.Found a weird bug. I routinely use GGD Cali for my IRs, and I just loaded a new one into the cab manager. Every time I try and load that specific IR into the cab block, the FM3 makes a permanent "eeeeeeee" sound and freezes until I shut it off manually.
FWIW, my GGD Oversized Cali exported WAV’s are working just fine on my end.
The rest of mine are as well. But I've been using them for years and this is literally the first time this has ever happened, so I think it was pretty reasonable to presume it was bug-related.
I have 2 Moog Exp Pedals on my board and they work the same after upgrade to 8.Hey, don´t know if anyone already tested or if is having the same issue as myself.
My Moog Expression pedal with this beta release is not working propertly, after several calibrations, when I engage the expresion the block turns on but the range of the wha wha is quite low when activated, don´t know if I am expressing well for your understanding.
Can someone check please ?
Thanks
It could be a 'corrupt' user cab slot, even if it shows up as empty. I have experienced such a thing in the past.
Try clearing it in Manage Cabs (right click > Clear). Or use Fractal-Bot to send a valid IR to that slot.
My guess is that those who are reporting large CPU decreases, were using Amp blocks with CPU-heavy tweaks, such as some Speaker parameters, Output Compression etc.
By resetting the amp block, as advised in the current release notes, those parameters are reset to default, and therefore release the CPU load.
IF that's the case, the reports are based on incomparable situations.
Maybe I'm getting confused between units, but I thought the amp block was typically modelled on a separate core from the core that runs the UI and most of the rest of the effects, so higher or lower CPU usage amp block settings wouldn't show on the CPU usage readout, because it's only measuring the core that runs the rest of the grid and the UI.
Tried it and nothing greyed out man, strange .....Found a bug: After "Preset > Save a copy ..." (FM3 Edit), the FM3 screen is greyed out. (Greyed out = similar when you scroll through presets on the unit itself without entering one).
I need to manually change presets to "activate" the normal screen.