FM3 Firmware Version 12.0 public beta

[heardsoundcircuits]

I don’t know if I’m going crazy but version 12 sounds SIGNIFICANTLY better in tone and feel. Strumming the first chord after updating was a real “wow” moment.

 

[nicolasrivera]

I don’t know if I’m going crazy but version 12 sounds SIGNIFICANTLY better in tone and feel. Strumming the first chord after updating was a real “wow” moment.

Not Crazy, it does. And Cliff even managed to make it even better-er. This FM3 BETA was released past monday, on Thursday Cliff posted a new Axe FX FW that makes the preamp modeling even better!

 

[Paul Bradshaw]

Thank you for recording both firmwares to compare.
This shows what a great step is made again in the amp modeling.

yes, thanks paul. i cannot say if the 2203 sounds more realistic, never had one, but 12 sounds better to my ears.

fellow UK brit, always follow Paul's vids, keep it up! love these mate!

thanks everyone for the feedback , much appreciated

 

[Elton Oliveira]

Yeah, just crashed for the 3rd time for me. The first block is the pitch block, set to an octave divider.

It happened to me several times since Firmware 11. And I use Octave Divider in the first block too. @unix-guy

 

[Ckopnuo]

Great job, thank you! Never used more than several tens of user slots.

 

[Sergius9]

You will need FracTool for this:

• Select tab CabList
• Check Cab->Presets
• Uncheck Check scenes cab use
• Press Refresh - be patient, this will take about 5 minutes
• Save file as e.g. cabs.csv
• Close FracTool as you cannot run FracTool and FM3-Edit at the same time
• Open cabs.csv in a text editor
• Search for the string U 512
• From here on you will see: A cab (identified by number and name) and after a separator (e.g. comma) several presets using this cab
• Start FM3-Editand start remapping cabs 512+. I would do it like this:
  • Move one cab to a different location
  • Edit the presets using this cab
  • Repeat this sequence for all 512+ cabs

Great tip and Tool. However, my list listed some Factory presets as using User cabs. I have not modified any of the factory presets. Makes me wonder if it also missed some User presets using User cabs...

 

[HaPe57]

Great tip and Tool. However, my list listed some Factory presets as using User cabs. I have not modified any of the factory presets. Makes me wonder if it also missed some User presets using User cabs...

View attachment 163111View attachment 163112

Right now I am on holiday and I cannot access my FM3. The suggested procedure worked fine for me. Please check in your Editor if e.g. preset 83 is really using cab U007. Do this for all cab channels in this preset. Maybe it is a muted cab.

 

[Sergius9]

Right now I am on holiday and I cannot access my FM3. The suggested procedure worked fine for me. Please check in your Editor if e.g. preset 83 is really using cab U007. Do this for all cab channels in this preset. Maybe it is a muted cab.

I had already checked all channels of the cab block before posting. Some factory presets did not the user cab listed in any channel/slot. Others did which is weird because I installed the new presets 9.02 recently and have not modified a single thing on any of them.

 

[andrezuppe]

Installed the Beta right now.
I did a quick A/B recording before/after the update of a distorted patch based on an AFD100 + my profiled cabinet (IR) extracted from my kemper. I know very well how it sounds this patch, because is the core of my live rig setup.
The new beta 12 has improved a lot from the 11FW in the way that the distortion and the overall sound of the amp is much more thick.
More rawness, more overtones, it feels more in your face.
Love the job you did Fractal team!!!!!

 

[unix-guy]

It happened to me several times since Firmware 11. And I use Octave Divider in the first block too. @unix-guy

Good info.

Maybe there's a bug in the Pitch block, or at least the Octave Divider type.

@m_brown - FYI

 

[vangrieg]

Good info.

Maybe there's a bug in the Pitch block, or at least the Octave Divider type.

@m_brown - FYI

I have a pitch block on most of my presets, never had them crashing. But I never used the octave divider.

 

[Sergius9]

Right now I am on holiday and I cannot access my FM3. The suggested procedure worked fine for me. Please check in your Editor if e.g. preset 83 is really using cab U007. Do this for all cab channels in this preset. Maybe it is a muted cab.

I just re-downloaded and re-installed the 9.02 presets. Some of the Factory Presets point to User IRs. Not sure whose bug it is...

 

[unix-guy]

I just re-downloaded and re-installed the 9.02 presets. Some of the Factory Presets point to User IRs. Not sure whose bug it is...

This is probably related the User IR slot reduction and related editor bug making Legacy IRs appear to be in User slots.

Check from the hardware.

 

[Thie1984]

Hi there ,i installed the beta 12 yesterday and everything went smooth , but today no sound from any preset ,the only way i get sound coming out of the unit is New preset - Input 1 connected to Output 1 , but as soon as i add a AMP Block nothing comes out ,the preset leveling tool does not work too ........ anyone else got that issue ?

 

[Poparad]

Good info.

Maybe there's a bug in the Pitch block, or at least the Octave Divider type.

@m_brown - FYI

More like "octave divide by 0," amirite?

 

[RobbyDeeMusic]

Hi there ,i installed the beta 12 yesterday and everything went smooth , but today no sound from any preset ,the only way i get sound coming out of the unit is New preset - Input 1 connected to Output 1 , but as soon as i add a AMP Block nothing comes out ,the preset leveling tool does not work too ........ anyone else got that issue ?

This happened to me once, somehow the input level was brought down while upgrading to new FW, so check the input level.

 

[seclusion]

yes I did a reset on a few presets that solved something.

 

[BAKE]

Just noticed this TUBE HARDNESS low setting on the all amps.

 

[alehop]

Based on what you said above, and what I am quoting at the bottom of this post, I have a question. Please don't flame me as my question is well intended, and I have no complaints about my non-turbo FM3. I just want to know the following:

I almost exclusively use presets I created, not the factory installed ones. With the last non-beta release I have been running into a lot of cpu exceeded notifications rendering the presets unuseable without modifications to remove blocks. Seems reverb definitely has a negative impact there.

So my question is at what point does a user like me say they are happy with the FM3 (non-turbo) and while the new features are desireable, loading the new firmware starts to create more cpu issues and as a result I should just accept the limitations of my product given time that has passed since I purchased it, and no longer update the firmware.

Again, please don't flame me. I am not complaining, I just don't want to degrade the performance of my FM3 to add new functionality that while desireable, is really more advanced than the capabilities of my unit.

"This firmware version includes major improvements to sound quality and performance. As a result, some presets now require more CPU. Older Factory Presets may exceed 80% CPU usage, especially on the standard (non-Turbo) FM3. To address this, new Factory Presets have been created for firmware 10.0+. These are not installed automatically and must be downloaded separately:

Yes that's a fair point. In the same boat with a non turbo unit. Be nice to have some guidance as to how suitable that unit is for a given firmware release?

 

[alehop]

I still do not know why anyone would want anything but Fractal Audio when chosing a modeler. I have had mine for over 4 years. I was blown away when I purchased it. Inspiration, creativity through the roof! The beauty in Fractal is that they are always trying to improve on their existing products FOR FREE and not quick to release a new product every few years. Forum and support are off the charts too! Forever a Fractal family member. Thank you!

cannot agree more! Hope they keep this exact philosphy forever and I will never buy another modeler that's for certain