FM3 Firmware Version 2.00 Public Beta 1

Thanks to everyone for testing out the beta version of 2.0 and finding the bugs that will enable Fractal to get it sorted before the official release of the 2.0 firmware. This is a really helpful process.
 
cnaufel said:
[These presets crash the FM3]
Click to expand...

Today I helped to discover that at least one of these presets contains an "illegal" modifier in the delay block, which explains why it was crashing. This vindicates the beta firmware in my opinion, though it may need to be equipped with guard rails to prevent something like this from happening.

May I ask if you converted or edited these using FracTool or any other 3rd party software? @cnaufel -- answer here or send me a PM.
 
Last edited:
Admin M@ said:
Today I helped to discover that at least one of these presets contains an "illegal" modifier in the delay block, which explains why it was crashing. This vindicates the beta firmware in my opinion, though it may need to be equipped with guard rails to prevent something like this from happening.

May I ask if you converted or edited these using FracTool or any other 3rd party software? @cnaufel -- answer here or send me a PM.
Click to expand...
First I checked all my presets that froze the unit. Than saved them using the Preset Management from FM3 Edit. Picked them and right clicked and SAVE all of them in a row.
 
cnaufel said:
First I checked all my presets that froze the unit. Than saved them using the Preset Management from FM3 Edit. Picked them and right clicked and SAVE all of them in a row.
Click to expand...
I think Matt was asking if you loaded them into your FM3 via "conversion" from presets that were from something like Axe Fx II or AX8.
 
unix-guy said:
I think Matt was asking if you loaded them into your FM3 via "conversion" from presets that were from something like Axe Fx II or AX8.
Click to expand...
Ahhh!! Good question! You guys are much smarter than me 😉. They were indeed initially ported from my AX8 some time ago and converted with Frac Tool. They were sitting without any issues im my FM3. With 1.06 version, no issues...when upgraded to Beta...crash.
 
FWIW here is my experience with the 2.0b so far:

Improvements:
  • CPU usage is down about 5-7% on most of my presets. I also notice that I can use processing power up to 85%-87%, whereas with 1.06 it was cut off at 80%-83%
  • FM3-Edit is MUCH faster/responsive
  • Pausing and resuming communication on FM3-Edit is instant.
  • I no longer experience USB audio dropouts while using FM3-Edit.
  • Disconnecting the USB cable and reconnecting while FM3-Edit is running reconnects and works without freezing or requiring FM3-Edit restart.
Potential Issues:
  • When I would turn on the FM3 it would initialize with my TRS treadle pedals in the on position, somewhere mid-sweep. I am using auto engage. This meant my tone had a cocked Wah sound. Upon changing presets and changing back the proper settings would be restored and my correct non-cocked Wah tone would be back. (Turn on FM3 it loads Preset 000, Scene 5 with a cocked Wah sound>Change to preset 1; change back to preset 0; cocked Wah sound gone as intended and stored)
I solved this issue by re-calibrating my TRS treadle pedals. Preset file attached below.
--
  • I can corroborate the Archon Bright Fat switch dropout bug. I am on Mac OSX High Sierra 10.13.6
  • The screen illumination appears to have changed, but this may be intended. Here are my findings posted in another thread about that potential issue:
dejoblue said:
Here's a sanity/placebo check. Looks like maybe the side illumination was made more diffuse and maybe that makes it appear to have more contrast? Or, more likely, just placebo from the process of staring at your screen waiting to power cycle the firmware update; seeing the black screen and then the fresh illuminated screen. These are with the factory film protector on (I'm one of those guys; 2 years from now when I peel off my 40" TV it will look brand new :)~ and so will my FM3!)

EDIT: Yeah, coming back to these, 2.0 is definitely brighter/has more diffusion of the side lights. Turned my screen down to 20% and am fine with it; hopefully saves screen burn in/out time. :)

1.06 Brightness:



_____
_____

2.0b Brightness:

Click to expand...
 

Attachments

  • 000_Deja Main.syx
    24.1 KB · Views: 2
Last edited:
cnaufel said:
Ahhh!! Good question! You guys are much smarter than me 😉. They were indeed initially ported from my AX8 some time ago and converted with Frac Tool. They were sitting without any issues im my FM3. With 1.06 version, no issues...when upgraded to Beta...crash.
Click to expand...

Well, case closed then. The presets are incompatible.
 
I have problems with midi in the editor, I put a number in the value and don't change or save in the editor or fm3
 

Attachments

  • midi.JPG
    midi.JPG
    129 KB · Views: 15
Jesuis_lm said:
I have problems with midi in the editor, I put a number in the value and don't change or save in the editor or fm3
Click to expand...

I'm having the same problems with the MIDI block. It turns out that when you enter numbers on the hardware or software, the changes to take hold but the display isn't updating to reflect that. If you move the selector/cursor to a different field and back, it'll update, though.
 
Installed a couple days ago. No problems here. USB working good, Edit seems faster and no freezes.

Only thing I keep getting is that the tap tempo light goes crazy every time I open reaper.

Thanks FAS. Please fix the virtual capo in the next release 🙏🏻
 
Rublalup said:
Installed a couple days ago. No problems here. USB working good, Edit seems faster and no freezes.

Only thing I keep getting is that the tap tempo light goes crazy every time I open reaper.

Thanks FAS. Please fix the virtual capo in the next release 🙏🏻
Click to expand...

You sure the tempo light isn't because Reaper is sending out a high tempo?
 
Stratoblaster said:
I noticed that after installing this firmware all of my user IR's, which were all non-Ultrares IR's, showed up in Italics in the "Manage Cabs" FM3-Edit screen which I understand indicate UltraRes processed IR's (which are supported but truncated in the FM3 AFAIK).

The IR's sounded unchanged but I didn't test at a level, nor spend any time, to see if the IR's were actually changed/processed.

I just observed the label names changed to Italics in FM3-Edit and immediately reloaded them with no processing...they now show as regular/un-processed IR's like before.

I just thought I'd share the observation; might be the intended behavior, etc. but was unexpected at my end.
Click to expand...

unix-guy said:
I know some have faced a similar issue on the Axe Fx III where Axe-Edit seems to be confused about the IRs. There's a tool somewhere in the editor to rescan/refresh the cabs and that corrects the display. Maybe try to do that?
Click to expand...

The "Refresh After New Firmware" ran on FM3-Edit immediately after the firmware upgrade.

I fired up the FM3 the other day and all of my uploaded non-UltraRes user cabs labels were showing in Italics again in "Manage Cabs".

Ran "Refresh After New Firmware" again manually and nothing changed.

Re-uploaded the IR's and the labels read as regular, un-processes UltraRes IR cabs and stayed that way throughout the session.

Fired up the FM3 yesterday and the labels were showing in Italics again in "Manage Cabs".

I suspect this is simply a cosmetic bug...????
 
Stratoblaster said:
The "Refresh After New Firmware" ran on FM3-Edit immediately after the firmware upgrade.

I fired up the FM3 the other day and all of my uploaded non-UltraRes user cabs labels were showing in Italics again in "Manage Cabs".

Ran "Refresh After New Firmware" again manually and nothing changed.

Re-uploaded the IR's and the labels read as regular, un-processes UltraRes IR cabs and stayed that way throughout the session.

Fired up the FM3 yesterday and the labels were showing in Italics again in "Manage Cabs".

I suspect this is simply a cosmetic bug...????
Click to expand...
There's a refresh in Manage Cabs, I believe. I was not referring to Refresh After Firmware...

It's definitely a display bug and exists in Axe-Edit, too.
 
You must log in or register to reply here.
Back
Top Bottom