FM3 Firmware Version 9.02 public beta (3)

Status
Not open for further replies.
Ba55Man1ac said:
Yep, fair enough on the beeta. It's been happening since fw 9.01 (first crast was 12th Oct). At that time I added a filter block & removed the wah w/envelope follower modifier. It crashed almost every gig until I replaced the filter block with a shunt on 30th Nov as detailed here. No more crashes until 2 days ago. Although previous crashes the audio would still be metering (front panel LEDs) with no audio output, this time there was no metering.

Gigging 2 nights a week, every week, different venues.

Not trying to be argumentative, just hoping to improve the product.

Cheers!
Click to expand...
I think the only thing was your wording on the previous post, i.e. talk of your confidence in the FM3 being shattered and maybe going back to an analog board b/c of it. Seemed unwarranted for a beta. ;)

It'll all get worked out eventually.
 
skolacki said:
I had that happen not long ago, same thing with the meters. With my FM3 I have had multiple crashes since new, none of which were repeatable. A few times resulted in dimed volume out of control noise. It’s not often but I have to wonder if the FM3 is more crash prone compared to the higher powered units. If you were using Ultrares IR’s maybe the cpu spike caused it? I try to stay below 75% on my worst channels.
Click to expand...
You bring up a good question skolacki, "is the FM3 more crash prone than other Fractal units?" I thought I was the only one! I bought a non headphone FM3 about 3 years ago from FAS and it was prone to lock up at least once every 3-5 usages. I should have contacted support but I never really used it live and I didn't want to have to pay for shipping. It only ever happened when editing a preset (connected to USB or not). I ended up moving to another FM3 that had a headphone jack and this one doesn't lock up nearly as much but every once in a while it will lock up when editing a preset from the front panel (connect to USB or not).
 
mortega76 said:
You bring up a good question skolacki, "is the FM3 more crash prone than other Fractal units?" I thought I was the only one! I bought a non headphone FM3 about 3 years ago from FAS and it was prone to lock up at least once every 3-5 usages. I should have contacted support but I never really used it live and I didn't want to have to pay for shipping. It only ever happened when editing a preset (connected to USB or not). I ended up moving to another FM3 that had a headphone jack and this one doesn't lock up nearly as much but every once in a while it will lock up when editing a preset from the front panel (connect to USB or not).
Click to expand...

I have a non-headphone FM3 and have never had a crash outside one time that I loaded a bad IR. I have had times where I tried to push the CPU a bit too much, that results in a muted block which at first glance can seem like a crash. These days though most my presets are below 70% CPU so haven't had that issue in a long time.
 
Having the dame problem i had with 9.02 beta 1 wich was fixed with beta 2 . Some presets are cpu overload when on beta 2 ans 9.01 were 79%
 
I'm using beta3 and had no issues this weekend with lots of rehearsal, editing and a gig. From my own experience editing and changing effects with an already high CPU may be part of the problem [just a wild guess]. Would suggest anyone that is having issues, take a look at the CPU and if you are pushing much beyond 70%, back it off a little. That has worked for me - and loving the new firmware - the updated vibe is great.
 
Will Chen said:
I have a non-headphone FM3 and have never had a crash outside one time that I loaded a bad IR. I have had times where I tried to push the CPU a bit too much, that results in a muted block which at first glance can seem like a crash. These days though most my presets are below 70% CPU so haven't had that issue in a long time.
Click to expand...
I forgot to mention, my non-headphone FM3 would lock up and all audio processing would stop. All I would hear is a dry guitar signal. The GUI would lock up as well leaving me with a power cycle as my only option. My headphone FM3 has only locked up like this maybe once or twice.
 
I think we should distinguish between a CPU overload, where the unit is unresponsive (lock up), and a situation where the unit responds normally but one or more blocks become red (crash) and there is no audio output.
 
md1234 said:
I think we should distinguish between a CPU overload, where the unit is unresponsive (lock up), and a situation where the unit responds normally but one or more blocks become red (crash) and there is no audio output.
Click to expand...

A crash from my perspective is failure of the unit, what people are calling a lock up, only remedied by a restart. The unit muting a block is a safety measure to prevent a crash (EDIT: In fact when the unit, muting comes with the message "CPU LIMIT EXCEEDED" and further detail that the preset exceeds 100% CPU usage. That's a prevented "overload")
 
@Will Chen see the images attached to the quoted post:
Anton Karelin said:
I switched the Dyna-Cab to Legacy in FM3-Edit 1.07.06. Immediately after that, the sound disappeared in all presets.
Starting from the AMP block, everything is red. Rebooting fixed the issue, I couldn't reproduce it again.
The meters showed this:
Click to expand...

unix-guy said:
That's essentially a "crash"...
Click to expand...

Those crashes seem to be not reproducable (at the moment) and are (imo) different from regular (and also expected) lock ups and overloads from high demanding presets/users.
 
I've got a non-headphone FM3 and it's been surprisingly stable. I leave it on most of the time in the studio and it just always works.

That said, it HAS crashed under certain conditions. A couple times, when trying to load someone else's preset I would get a blast of white noise at full amp volume (I run in 4CM, so it just pumped full volume into my FX return).

The other time it crashes (and I can get it to crash this way any time I try this), is when I try to unplug the midi out cable from the midi controller end (not the fractal end). At that point, the screen flashes some garbage, and then the whole unit reboots. This has happened on any firmware version. Maybe it doesn't like a little 5v zap? Not sure if the problem is on the controller end (I use a Piratemidi Bridge 6), or on the FM3 end. Eventually I'll learn to not re-route my midi cables while the unit is turned on. 🤓
 
Possible bug:

In FM3 Edit 1.07.06, in the Phaser block, if I change the Tempo parameter to any value, and then try to Undo, the Tempo parameter value is changed to "None" instead of the previous value.

Edit: seeing this in a Delay block as well. In fact many entry boxes (not sure what they're called? non-knobs) have a similar behavior. It seems they return to a default value instead of the previous value? The Boost Type in the Amp Block for example, always returns to "Neutral" after an undo.
 
Last edited:
Elton Oliveira said:
NEW FEATURES & UPDATES

DRIVE BLOCK UPDATES

•Improved PI Fuzz model. The new model also allows changing the type and quantity of diodes used in the transistor feedback paths, adds a “Wicker” switch which removes the feedback capacitors and adds a “Tone” switch which allows bypassing the tone circuitry.
•Added PI Fuzz – Triangle model. This is based on a 1971 “Triangle” Big Muff PI. Thie model also includes the Tone Wicker mods.
•Added PI Fuzz – Ram’s Head model. This is based on mid-70’s “Ram’s Head” Big Muff PI. The model also includes the Tone Wicker mods.
•Added PI Fuzz – Russian model. This is based on a Sovtek produced “Civil War” Big Muff PI. The model also includes the Tone Wicker mods.
•Added Colortone Booster model based on a Colorsound Power Booster (with added Master control).
•Added Colortone OD model based on a Colorsound Overdriver (with added Master control).
•Added MOSFET Distortion model based on an Ibanez MT10 Mostortion.
•Added Super Fuzz model based on a Univox Superfuzz. The model also features a tone control which allows varying the frequency of the notch. Use the Bias control to simulate the “Octave” control found on some clones.
•Added Integral Pre type to the Drive block. This is based on a TC Electronics Integrated Preamp
•Updated DS1 Distortion model to Second Edition specs.
•Improved Tube Drive 4-Knob model. If you are using this model in a preset a soft reset of the block is recommended to load the new default values.
•Added Tube Drive 5-Knob model.

PHASER BLOCK UPDATES

•New Vibe algorithm in Phaser block. The default values have changed for the Vibe models and existing presets are automatically updated to the new defaults. If you have edited the default values you may wish to audition your presets accordingly.
•Added “FO Mode to the Phaser block. When set to UNIVIBE the amplitude of the LFO is roughly proportional to the LFO Rate. When set to NORMAL the amplitude is constant. NORMAL allows deeper phasing at slow rates than would be possible with an actual Univibe.
•Added Low Cut and High Cut controls to Phaser block for the wet path.
•Added Modern Vibe model to Phaser block. This is based on a classic UniVibe but with modern input buffer and LFO.
•Changed Exponent to “VCR Shape” in Phaser block as this more accurately describes the control function.

OTHER BLOCK UPDATES

•Improved Filter block Touch-Wah detector behavior.
•Improved Sweep Delay algorithm in Delay block. Added selectable filter type.
•Improved Quad Diffusor algorithm in Multitap Delay block. The new algorithm now has stereo output with adjustable spread and LFO controlled filters.
•Exposed Algorithm type in Multitap Delay block. This allows changing the underlying algorithm without changing the various parameters. This can be used to experiment with different algorithms without losing parameter settings as occurs when changing the Type.
•Added Ducking control to Tremolo block. This reduces the intensity of the effect as you play louder.

FIXES

•Improved active sensing pedal controllers for auto-engage modifiers. Active sensing is more sensitive now.
•Corrected internal pedal jacks configured as switches being ignored due to active sensing update.
•Various general CPU use improvements.
•Fixed resistor mistakenly attached across drive pot on Plexi 2204 model.
•Fixed Phaser block LFO Reset now working properly for some types.
•Fixed wrong Miller capacitance value in Brit 800 models (probably not audible).
•Fixed CPU Limit warning remaining on-screen in some cases after resolved.
•Pedal inputs configured as switch inputs are no longer affected by activity sensing at startup.
Click to expand...
I know nobody seems to care but it would be great to have a more sophisticated looper block.
 
Lou Lab said:
I know nobody seems to care but it would be great to have a more sophisticated looper block.
Click to expand...

I like the looper and use it a lot but yeah, it’s simple. I have no idea of what resources are available for an improved looper. Probably not much.
 
Played this beta today with no issues. Every amp I tried sounds better in general too. I played the JC-120, the Supro, the Ampeg 1, the Soldano Lead and the Jmp1. Tried the new drives and vibe. Thank you Fractal Audio team for this killer update.
 
Status
Not open for further replies.
Back
Top Bottom