[These presets crash the FM3]
The latest official 1.06
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.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.
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.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.
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.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.
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:
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.
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
Known bug and already fixed for next release.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.
Thank you
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
You sure the tempo light isn't because Reaper is sending out a high tempo?
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.
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?
There's a refresh in Manage Cabs, I believe. I was not referring to Refresh After Firmware...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...????