FM3 Firmware Version 10.0 public beta

Status
Not open for further replies.
sol said:
These are the only factory presets which max out after updating to Firmware 10.0 beta -
115, 121, 198, 218, 238, 244, 285, 289, 330, 371
Click to expand...
You may be on a Turbo? When we reworked the factory presets for the NON-Turbo, there were more.

Also... I really recommend the new versions. There's a lot more to them than CPU: new compressors, reverbs, effects, scenes, plus some totally new entries. Tonight I will finish up addressing the comments from the preview release and get the newest versions on the server. Once the firmware is finalized, this release cycle will be complete!
 
Just had something strange happen - lost my ability to control Input Volume with my Expression Pedal set as Input Global Volume (manual P.13) connected to FC6 Pedal 1. Checked Pedal Configs, all seemed to be Ok. It was almost as if not pedal was there. Tried power off, re-booting same. I then did a restore of the FC/Global Settings Backup sysex file ( i did a clean backup immediately after updating to 10.p1 and updating presets) and it’s all OK now. Just FYI for now.
 
I made the update but Despite adjusting the input PAD, some presets still have an unpleasant digital clipping sound — for example, the preset ‘New Country 278’. In some of these presets, the amp block has the Master Volume set to maximum. Lowering it reduces the clipping. Other presets have the same parameter maxed out but don’t produce this harsh sound. I’m using the same guitar on all presets, and most of the older ones didn’t have … will it be fixed With final firmware version? I dont’ know if i should return to Previous firmware…
 
Admin M@ said:
You may be on a Turbo? When we reworked the factory presets for the NON-Turbo, there were more.

Also... I really recommend the new versions. There's a lot more to them than CPU: new compressors, reverbs, effects, scenes, plus some totally new entries. Tonight I will finish up addressing the comments from the preview release and get the newest versions on the server. Once the firmware is finalized, this release cycle will be complete!
Click to expand...
I had tested it on a non-Turbo :). Yes, I do plan to give the new presets a go properly.
 
matthieu said:
I made the update but Despite adjusting the input PAD, some presets still have an unpleasant digital clipping sound — for example, the preset ‘New Country 278’. In some of these presets, the amp block has the Master Volume set to maximum. Lowering it reduces the clipping. Other presets have the same parameter maxed out but don’t produce this harsh sound. I’m using the same guitar on all presets, and most of the older ones didn’t have … will it be fixed With final firmware version? I dont’ know if i should return to Previous firmware…
Click to expand...
What Amp model?

The MV on 10 is expected for non-MV amps...

Continuing to ask "will it be fixed" when we don't know the actual problem isn't going to result in any useful answer.
 
Moke said:
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.
Click to expand...
I can confirm this. As soon as I noticed the new mini-tuner clipping indicator, I immediately checked the input pad and it was unchanged. I just never noticed that my JB-equipped guitar was clipping the input.
 
matthieu said:
I made the update but Despite adjusting the input PAD, some presets still have an unpleasant digital clipping sound — for example, the preset ‘New Country 278’. In some of these presets, the amp block has the Master Volume set to maximum. Lowering it reduces the clipping. Other presets have the same parameter maxed out but don’t produce this harsh sound. I’m using the same guitar on all presets, and most of the older ones didn’t have … will it be fixed With final firmware version? I dont’ know if i should return to Previous firmware…
Click to expand...

I just dialed up the preset to check and not experiencing anything out of the ordinary. Can you post a clip of what oy are talking about?

EDIT: I don't know what this preset sounded like before, first time using it, but dialing back the Compressor level might be what you're looking for to clean up things a bit.
 
So... I installed the new version of the FM3-Edit and then the new 10.0 firmware.

It boosted all my main presets to "OUT OF CPU" state to a point where I couldn't do anything but changing presets or it would crash. I couldn't even edit the presets besides deleting one block and it would crash after that, I couldn't even save the edit.

I had to CLEAR all my main presets and will have to start them over. Thankfully I had some blocks saved in the library, which cuts a hell lot of editing time.

I haven't been able to rebuild the cleared presets (via the FM3-Edit), but will get there eventually. Since I'm not gigging, it doesn't really matter much.

Needless to say that the "OUT OF CPU" presets went for a walk and never came back, so I can't share them. Whatever you guys did, it came out WAY heavier on the CPU use than it was before... My FM3 unit is v1, not turbo nor mark II or whatever, so lower memory/CPU power...

I posted this just to share this occurrence, in case some one else finds the same problem. My rig is made of an FM3, a Mesa Boogie Triaxis and a Synergy Syn5050 power amp, the FM3 and the Triaxis are entangled in the 4 Cable Method on the double side of things, The Triaxis is in the FM3 loop, but the FM3 is also in the Triaxis' loop. These presets didn't even had the AMP and CAB blocks and clocked at about 65% of CPU... new FW and it skyrocketed into oblivion... oh well, it's a chance to make things better...
 
ruso said:
I can confirm this. As soon as I noticed the new mini-tuner clipping indicator, I immediately checked the input pad and it was unchanged. I just never noticed that my JB-equipped guitar was clipping the input.
Click to expand...
Hey where is mini tuner clipping indicator located?
Haven’t noticed it yet lol
 
Odibrom said:
So... I installed the new version of the FM3-Edit and then the new 10.0 firmware.

It boosted all my main presets to "OUT OF CPU" state to a point where I couldn't do anything but changing presets or it would crash. I couldn't even edit the presets besides deleting one block and it would crash after that, I couldn't even save the edit.

I had to CLEAR all my main presets and will have to start them over. Thankfully I had some blocks saved in the library, which cuts a hell lot of editing time.

I haven't been able to rebuild the cleared presets (via the FM3-Edit), but will get there eventually. Since I'm not gigging, it doesn't really matter much.

Needless to say that the "OUT OF CPU" presets went for a walk and never came back, so I can't share them. Whatever you guys did, it came out WAY heavier on the CPU use than it was before... My FM3 unit is v1, not turbo nor mark II or whatever, so lower memory/CPU power...

I posted this just to share this occurrence, in case some one else finds the same problem. My rig is made of an FM3, a Mesa Boogie Triaxis and a Synergy Syn5050 power amp, the FM3 and the Triaxis are entangled in the 4 Cable Method on the double side of things, The Triaxis is in the FM3 loop, but the FM3 is also in the Triaxis' loop. These presets didn't even had the AMP and CAB blocks and clocked at about 65% of CPU... new FW and it skyrocketed into oblivion... oh well, it's a chance to make things better...
Click to expand...

And the release notes were clear on this :) reverbs and compressors are the main culprits of higher CPU.
 
Odibrom said:
So... I installed the new version of the FM3-Edit and then the new 10.0 firmware.

It boosted all my main presets to "OUT OF CPU" state to a point where I couldn't do anything but changing presets or it would crash. I couldn't even edit the presets besides deleting one block and it would crash after that, I couldn't even save the edit.

I had to CLEAR all my main presets and will have to start them over. Thankfully I had some blocks saved in the library, which cuts a hell lot of editing time.

I haven't been able to rebuild the cleared presets (via the FM3-Edit), but will get there eventually. Since I'm not gigging, it doesn't really matter much.

Needless to say that the "OUT OF CPU" presets went for a walk and never came back, so I can't share them. Whatever you guys did, it came out WAY heavier on the CPU use than it was before... My FM3 unit is v1, not turbo nor mark II or whatever, so lower memory/CPU power...

I posted this just to share this occurrence, in case some one else finds the same problem. My rig is made of an FM3, a Mesa Boogie Triaxis and a Synergy Syn5050 power amp, the FM3 and the Triaxis are entangled in the 4 Cable Method on the double side of things, The Triaxis is in the FM3 loop, but the FM3 is also in the Triaxis' loop. These presets didn't even had the AMP and CAB blocks and clocked at about 65% of CPU... new FW and it skyrocketed into oblivion... oh well, it's a chance to make things better...
Click to expand...

You should be able to delete a block with a red cpu warning. If you backed up prior to updating you can recover your presets. I have the old FM3 with average cpu pre update at about 73-75. I went red and turned down echo density which got me out of the red. Also turned down dispersion. Comps I don’t use but if you do, delete those 1st.
 
matthieu said:
I made the update but Despite adjusting the input PAD, some presets still have an unpleasant digital clipping sound — for example, the preset ‘New Country 278’. In some of these presets, the amp block has the Master Volume set to maximum. Lowering it reduces the clipping. Other presets have the same parameter maxed out but don’t produce this harsh sound. I’m using the same guitar on all presets, and most of the older ones didn’t have … will it be fixed With final firmware version? I dont’ know if i should return to Previous firmware…
Click to expand...
Here is a pic of preset 278.
Nothing has been changed and this is what I have.
master volume not maxed out.
Edit:
This is with the updated presets.
Screenshot 2025-05-12 at 6.41.08 PM.png
 
Last edited:
BROCKSTAR said:
And the release notes were clear on this :) reverbs and compressors are the main culprits of higher CPU.
Click to expand...
All cool, the presets weren't THAT good and were kind of experimental. The major tone factor in my rig is the Triaxis, as the FM3 works as FX only, at least so far as I'm not gigging nor rehearsing....


skolacki said:
You should be able to delete a block with a red cpu warning. If you backed up prior to updating you can recover your presets. I have the old FM3 with average cpu pre update at about 73-75. I went red and turned down echo density which got me out of the red. Also turned down dispersion. Comps I don’t use but if you do, delete those 1st.
Click to expand...
Every time I deleted a block, the FM3 froze the instant I tried to do anything else, either move the cursor in the layout page or save the preset as it was. I tested this over 10 times, always with the same result: frozen FM3.

Nuke it was the solution that worked best, used the FM3-Edit - Preset Manager tool. As the EQs and some other FXs were already in my library, easy peazy lemon squeezy to bring back the major sound of the 1st, 2nd and 3rd preset. I'm yet to bring back everything else back on track, but building time is also fun.
 
Status
Not open for further replies.
Back
Top Bottom