This is what I do not understand. How is this happening to some but not others if this is a firmware issue? It definitely happened when I updated.I’m on 1.04 and I’m not having any of these issues you guys are having.
I love the form factor and tones from my FM3 and have no intentions of throwing in the towel, but I have to agree. I was really expecting the firmware and editor to be in better shape at this point. It's obviously not 100% on FAS, I'm sure they didn't factor in a global pandemic and an insidious compiler bug when planning this release. But I was hoping that some of that extra time between what was the expected release date and when units actually started shipping would have resulted in more dev/QA cycles that would have caught some of this stuff.Will go back to 1.03 also.....I guess. Lots of weird stuff going on with 1.04 as well. Pretty disappointing experience so far with this thing. As good as it sounds, I've never owned a unit that has had these many issues and weird things going on.
I can’t see how it can be on some and not others ......are you not seeing a difference between the two ?? Are you looking for it ?
"Refresh after update" does not correct the FM3 Edit issue for me. I believe others have tried this as well without success.FWIW I updated a couple days ago and noticed the display issue in FM3edit in the amp block. I didn't notice any change in the sound. I did the "refresh after update" thing and I believe it corrected the display in FM3edit and everything was normal.
This is an important question and answer to help Fractal track down the problem. If removing FM3 Edit from the equation and editing directly on the unit do the problems go away?I really believe FM3 Edit is the culprit here, not necessarily the FM3 firmware itself. If I edit on the unit, all is fine.
I love the form factor and tones from my FM3 and have no intentions of throwing in the towel, but I have to agree. I was really expecting the firmware and editor to be in better shape at this point. It's obviously not 100% on FAS, I'm sure they didn't factor in a global pandemic and an insidious compiler bug when planning this release. But I was hoping that some of that extra time between what was the expected release date and when units actually started shipping would have resulted in more dev/QA cycles that would have caught some of this stuff.
This is an important question and answer to help Fractal track down the problem. If removing FM3 Edit from the equation and editing directly on the unit do the problems go away?
The issue with FM3-Edit not reading the amp block parameters properly only happens if you have not changed channels on the amp block. If users have changed the amp block channel they will never see the issue.
Boot up, open FM3-Edit, and then go take a look at the amp block settings for either Ideal or Authentic. All of the settings will be shown at the default values. Change the amp block channel. The settings are properly read from the unit and the values displayed in FM3-Edit will change accordingly.
"Refresh after update" does not correct the FM3 Edit issue for me. I believe others have tried this as well without success.
So you've listed specifically the Amp and Delay blocks only.Simple test. Go through every preset and look what Delay is being used on each. You'll see the editor will say every preset uses the same type of Delay block.
It's not just the amp block; it's all blocks.