FM3 Firmware Version 9.01

Paul Bradshaw said:
thanks for the update 🙏 just wondering , has the CPU reporting changed somewhat?

my main preset went from around 75.6% or so to 80.2% ..which is huge, no issues so far, but just curious if there's something i'm missing here

might be related to the cab/preamp quality setting, it seemed like on FW 9 there was less of a Cpu jump between ECO & High Quality (it was around 2-3% increase, and now it's around 6-7)
Click to expand...
From what firmware version?
 
Joel.Brown333 said:
I upgraded to FW 9.01 from 9.00. My only complaint is that I still can't play the guitar any better.
Click to expand...
I would like to file another complaint if you'll allow me
Since the introduction of the new filters a couple FWs ago, these things crawled into all of my presets and are "on" almost always
And with the new Autowah I alsmost changed my name to Kirk Mayer
I want my money back How do I get back to normal?!
 
Wow, just discovered the announcement of 9.01. Really nice lot of goodies in there. Midi clock option thumbs up.

Thanks a lot once more.
 
I noticed that expression pedal on my Behringer FB1010 stopped working as global volume control, and acts like a kill switch now
The output volume is always 100% no matter what the position of the pedal is, except for its lowest position, when it start the tuner. Seems like recent MIDI changes affected something here.

I've configured the FB1010 a couple years ago and can't remember anything about how it was configured and how to try to troubleshoot this.
Other switches and a second pedal work as expected.
Any help would be appreciated, thanks!
 
Chromatizm said:
The output volume is always 100% no matter what the position of the pedal is, except for its lowest position, when it start the tuner. Seems like recent MIDI changes affected something here.
Click to expand...

Check the pedals settings - make sure it is still set as Expression, and hasnt changed to a switch.

Try recalibrating the expression pedal?

Check the parameters in the controller menu to see if there is still a well separated low and high parameter?
 
FractalAudio said:
That's normal:
o Added activity sensing to internal pedals, FC pedals and external controllers. This stops Auto-Engage from activating an effect if the pedal/controller is not connected. This prevents, for example, a Wah being engaged if Auto-Engage is on but no pedal is connected (i.e., you left your expression pedal at home).
Click to expand...
I'm having trouble with this. I can see in the editor that my expression controller is being recognized, and it's correctly showing the movement of the pedal, but auto-engage is no longer activating. I haven't changed anything in my presets, and it's occurring on all of them.
In the screen capture below, you can see that the pedal is beyond midway in its travel, so clearly the message is arriving. But it's not engaging the wah. Yes, I am using Channel A on the Wah, and I've tested this by setting the Channel to "All". Same result.

My expression pedals are EV-2 pedals, and they're both connected directly to the FM3.

I've tried reassigning it to another expression pedal with the same result. It can see that expression controller is sending messages, but it will not engage the wah.

Ideas? Running FW 9.01

1729288146708.png
 
Last edited:
unix-guy said:
Weird... I don't think there's any changes that caused an increase.

You could revert to 9.0 and see if it drops back.
Click to expand...
i'll have to check that at some point, I've since rebooted the PC, turned stuff on and off, and it's still reporting the same sort of CPU level

I'll keep an eye on it, see how it stacks up during band practice, might put the Cab preamp down to ECO in case anything strange happens
 
Last edited:
Is it possible to set a global tempo for a Song? At the moment, the setting in the scene decides.

By the way, in this firmware version the scenes switch almost instantly. Bravo!
 
Sleestak said:
I'm having trouble with this. I can see in the editor that my expression controller is being recognized, and it's correctly showing the movement of the pedal, but auto-engage is no longer activating. I haven't changed anything in my presets, and it's occurring on all of them.
In the screen capture below, you can see that the pedal is beyond midway in its travel, so clearly the message is arriving. But it's not engaging the wah. Yes, I am using Channel A on the Wah, and I've tested this by setting the Channel to "All". Same result.

My expression pedals are EV-2 pedals, and they're both connected directly to the FM3.

I've tried reassigning it to another expression pedal with the same result. It can see that expression controller is sending messages, but it will not engage the wah.

Ideas? Running FW 9.01

View attachment 146987
Click to expand...
I was able to resolve this issue by
  1. Creating a new Preset.
  2. Adding the wah block, assigning the controller to External 2, and setting the Auto-Engage to Fast Pos. That gave me a working wah block that behaved correctly.
  3. Add the new wah block to my library.
  4. Going to the non-functioning wah block in my existing presets and replacing it with the library wah block.
OK, so that gets back to working normally, but I compared the screen shot above with the settings of the new library wah block and they are identical. So the issue is I have no idea why the original wah block stopped working in all of my presets. I didn't change anything in those presets (or anywhere else on my FM3), and they went from working normally one day to not working the next day. Very strange. In my troubleshooting, I tested the TRS cable between the EV-2 and FM3, swapped out the EV-2 for other EV-2 pedals, deleted the controller entirely / rebooted / re-added the controller, and many other things. I haven't been able to identify the source of the problem, which means I don't know how to prevent it from recurring. I know it's possible for a preset to become corrupted (usually due to a user error when saving / powering down), but can that happen to a standard (non-library non-global) block across a range of individual presets? I'm open to thoughts on this one.
 
ethomas1013 said:
Is anyone else seeing the text on the mini-displays getting mis-aligned? The first two displays were doing it and after rebooting it was back to normal. After playing a bit and scrolling through various presets I noticed the middle one is now misaligned. Another reboot and all clear. Since the, I have not been able to reproduce this and don't know what triggered it. But it happened twice so I thought I would report it.

View attachment 146764
Click to expand...

This has happened to me with both (both purchased new) FM3 and FM3 Turbo.

Yikes!!! It just happened again, now, on my new FM3 Turbo. :oops:
 
Last edited:
ethomas1013 said:
Is anyone else seeing the text on the mini-displays getting mis-aligned?
Click to expand...
Obviously it's a lens effect from unremoved screen protectors... ;)

But seriously, it makes me think of fields in some software where if the text gets too long, it is forced to continue on the next line and may change the spacing like here. Sometimes you can disable that to prevent this kind of view.

It does seem to fit with the observation that only the texts that don't fit are doing that? Maybe FAS too can disable it and forgot to do it on some fields? Or maybe it was always so?

So if you're saying it is perfectly fine at some point and then it is not, try to notice if the text is longer than fits there, or if it only happens for certain data that is displayed there.

Upd.: Hm, someone below is showing examples with short texts too...
 
Last edited:
Sleestak said:
I was able to resolve this issue by
  1. Creating a new Preset.
  2. Adding the wah block, assigning the controller to External 2, and setting the Auto-Engage to Fast Pos. That gave me a working wah block that behaved correctly.
  3. Add the new wah block to my library.
  4. Going to the non-functioning wah block in my existing presets and replacing it with the library wah block.
OK, so that gets back to working normally, but I compared the screen shot above with the settings of the new library wah block and they are identical. So the issue is I have no idea why the original wah block stopped working in all of my presets. I didn't change anything in those presets (or anywhere else on my FM3), and they went from working normally one day to not working the next day. Very strange. In my troubleshooting, I tested the TRS cable between the EV-2 and FM3, swapped out the EV-2 for other EV-2 pedals, deleted the controller entirely / rebooted / re-added the controller, and many other things. I haven't been able to identify the source of the problem, which means I don't know how to prevent it from recurring. I know it's possible for a preset to become corrupted (usually due to a user error when saving / powering down), but can that happen to a standard (non-library non-global) block across a range of individual presets? I'm open to thoughts on this one.
Click to expand...
Nope. This didn't reliably fix my issue. It was great yesterday and today. My FM3 was powered down / up several times over the course of that interval. This afternoon, booted up, and the wah will not auto-engage. That same expression pedal works just fine controlling everything else, but the auto-engage would not engage. I had other stuff to work on during the afternoon so I played other patches, and after about 2 hours, switched back to a patch with the wah, and it worked perfectly fine. WHAT THE HECK? I do believe this is an actual bug. I'll test some more tomorrow, but I can't resolve this with any of the settings available to me. This sure seems like it's related to the newly added activity sensing. I would like the option to disable that feature, as it seems to be giving me trouble.
 
I'm running 9.0 on a FM3T.

I'm using factory text options, nothing custom here.
It just happened to me tonight while practicing.
The 2nd picture shows the text off center and slightly raised up.

The 3rd picture is after a reboot.

I have seen this issue now on different machines, started about 6 months ago or more.


FM3T mini display test off 1.jpgFM3T mini display test off 2.jpgFM3T mini display test after reboot 1.jpg
 
The updated pitch algorithm is fantastic! I never really had the need to use it, but now find myself using the Virtual Capo because it works so well.
 
Sleestak said:
Nope. This didn't reliably fix my issue. It was great yesterday and today. My FM3 was powered down / up several times over the course of that interval. This afternoon, booted up, and the wah will not auto-engage. That same expression pedal works just fine controlling everything else, but the auto-engage would not engage. I had other stuff to work on during the afternoon so I played other patches, and after about 2 hours, switched back to a patch with the wah, and it worked perfectly fine. WHAT THE HECK? I do believe this is an actual bug. I'll test some more tomorrow, but I can't resolve this with any of the settings available to me. This sure seems like it's related to the newly added activity sensing. I would like the option to disable that feature, as it seems to be giving me trouble.
Click to expand...
Probably should roll back to the previous firmware and see if it starts working again.
 
Paul Bradshaw said:
i'll have to check that at some point, I've since rebooted the PC, turned stuff on and off, and it's still reporting the same sort of CPU level

I'll keep an eye on it, see how it stacks up during band practice, might put the Cab preamp down to ECO in case anything strange happens
Click to expand...
I have the same problem. Some presets were at 78% on FW 9.0 and now they run at 83% on 9.1 and freeze after 30sec
 
You must log in or register to reply here.
Back
Top Bottom