FM3 Firmware Version 10.0 public beta

Status
Not open for further replies.
If you are someone like me who prefers the sound of old Factory Presets (9.0)

These are the only factory presets which max out after updating to Firmware 10.0 beta -

115 - Destructive Appetites - Fixed by lowering Dispersion to 20%
121 - MF Euro - Fixed by lowering Dispersion to 20%
198 - Rainbow Dash - Fixed by lowering Dispersion to 20%
218 - Heavily Processed FM3
238 - PolyOctave Pedal
244 - Horrowfest (corrupt) (deleted this)
285 - ’63 Tube Spring Verb - Fixed by lowering Drip to 50%
289 - 1967 All Over Again - Fixed by lowering Dispersion to 20%
330 - Grim Grinning Ghosts - Fixed by lowering Drip to 40%
371 - Stevens Rebel FM3 - Fixed by lowering Dispersion to 40%

You can fix this by slightly lowering the Dispersion value or Drip Value.

[TESTED on a NON-TURBO FM3]
 
Last edited:
Does anyone what the room level and room size in the cab block block was on 9?? Seems too high now, kinda hollow sounding. Thanks Tom
 
Bug:

As i tried the MegaTap Block with the "Brute Force Reverb" the Preset gets silent! CPU is 41%!.
If i look at the unit in the Meters Page, the output Block is Red! switching back to "Bounce" Type, which was ok before didn't help.
When i switch to another Preset the Sound comes Back. This also happened when i switch to the "Echo Room" Type , all gets silent, maybe also other Types.
 

Attachments

trouw2112 said:
Yeah, that's why I was wondering what the settings were before the update
Click to expand...

The settings should be wherever you left them. I think default is room level at zero. Not at my unit right now to verify that. But yeah at my old settings it sounds kind of like a plate reverb crossed with some slap delay. I turned it down pretty far.
 
Rublalup said:
It was on 0db before (I checked before updating due to your post)
Click to expand...
IIRC an 'Input Clip' warning was just added to the FM3 front panel display. The two bigger units have had this for some time now. The Input 1 'Pad' setting hasn't changed, but many FM3 users have likely been technically clipping input 1 for a long time, but were unaware of it. There were many posts about this when the warning indicator was added to the other Gen 3 units.

I have the FM3 Input 1 'Pad' set to 12 dB for my stock EBMM 'Axis' guitars,
 
Last edited:
Moke said:
IIRC an 'Input Clip' warning was just added to the FM3 front panel display. The two bigger units have had this for some time now. The Input 1 'Pad' setting hasn't changed, but many FM3 users have likely been technically clipping input 1 for a long time, but were unaware of it. There were many posts about this when the warning indicator was added to the other Gen 3 units.

I have the FM3 Input 1 'Pad' set to 12 dB for my stock EBMM 'Axis' guitars,
Click to expand...
As I've stated before, on previous FW's my OG FM3 non-turbo would round the waveform's leading edge with Duncan JB's in the the bridge of various Les Pauls unless Input One's Pad was set at -18db, this checked via DAW and without the red LED showing.
 
I'm currently using 9.01 firmware since I'm not a beta guy..
so when Fractal officially release 10.0, should I update Dynacab as well?
 
Moke said:
IIRC an 'Input Clip' warning was just added to the FM3 front panel display. The two bigger units have had this for some time now. The Input 1 'Pad' setting hasn't changed, but many FM3 users have likely been technically clipping input 1 for a long time, but were unaware of it. There were many posts about this when the warning indicator was added to the other Gen 3 units.

I have the FM3 Input 1 'Pad' set to 12 dB for my stock EBMM 'Axis' guitars,
Click to expand...
Is it ok to clip input on occasion ? Like the output ?
 
electroncr said:
Good to know. I did do a backup, so I will give it a try this evening when I get back home. I appreciate the help. It sounds fantastic and really liking the spring reverbs as well.
Click to expand...
Just following up on this. I did try to send the backup system+fc file but it would not save. I noticed that the file would take, but upon reset those setting would never save and would revert. I even tried saving on the device itself.

Preset changes would save, but it always started at Preset 0, no layouts, and with default in global settings (no scales, default pad, default -10dB on output 1).

One thing I did realize, I upgraded the firmware with an older FractalBot. It only said there was a fix for VP4 but mentioned something about a beta flag. Not sure if that’s relevant.

I did revert back to old firmware and I’m back up and my settings save after restart. I’ll wait until the official release since I’ve been gigging.
 
Last edited:
Petrocelli said:
Bug:

As i tried the MegaTap Block with the "Brute Force Reverb" the Preset gets silent! CPU is 41%!.
If i look at the unit in the Meters Page, the output Block is Red! switching back to "Bounce" Type, which was ok before didn't help.
When i switch to another Preset the Sound comes Back. This also happened when i switch to the "Echo Room" Type , all gets silent, maybe also other Types.
Click to expand...

Bug confirmed.

@m_brown
 
Status
Not open for further replies.
Back
Top Bottom