FM9 Firmware Version 11.0

md1234 said:
I can only say i installed this 11.0 when it was released, have my fm9t each day on for hours, also gigged and rehearsed, with presets in 60-73%, and zero problems.
Click to expand...
Yeah, I've always trusted each beta and public release on any FAS unit I've had, and have never had a lockup or any other issue. I wonder if most of these "issues" are just isolated incidents or something.
Maybe I'll install it on my backup unit and give it a run through.
I've watched the comments on the thread for a few weeks and started to get a bit skeptical.
 
I've only been with Fractal for a little over a year, but in that time there's been two or three major firmware releases, and none of them have had this volume of reported issues, and given that almost all of them involve audio dropouts/unit lockups (which are catastrophic in live performance), it's a good bet that there's something crucial that needs to be fixed, and Fractal probably shouldn't have pushed 11 out as quickly as they did (especially when there were quite a few unresolved bug reports with beta 2).

The plugin nuke that they dropped today would explain why they haven't been very present on this thread. Only so many engineers to go around. I just hope that now the plugin is released they'll prioritize fixing the FM9, cause I sure don't feel confident in running FM11 on my Mark II Turbo.
 
Last edited:
Henry said:
I have rehearsed and gigged with it and practice on it every day, no issues with 11 for me.
Click to expand...
That's great, it really is. I didn't have any issues either, until I did. Same with everyone else reporting problems with FW11.

It's certainly not something everyone is experiencing, but enough people have reported similar issues (with presets well below 80%) that it seems very likely that there is SOMETHING off that needs fixing.
 
JAD said:
I've only been with Fractal for a little over a year, but in that time there's been two or three major firmware releases, and none of them have had this volume of reported issues, and given that almost all of them involve audio dropouts/unit lockups (which are catastrophic in live performance), it's a good bet that there's something crucial that needs to be fixed, and Fractal probably shouldn't have pushed 11 out as quickly as they did (especially when there were quite a few unresolved bug reports with beta 2).

The plugin nuke that they dropped today would explain why they haven't been very present on this thread. Only so many engineers to go around. I just hope that now the plugin is released they'll prioritize fixing the FM9, cause I sure don't feel confident in running FM11 on my Mark II Turbo.
Click to expand...
Not really... The developer for the plugins is not the same as the developer for FM9/FM3, and neither is the developer for the Axe Fx III...
 
Add me to the random no output group - happened to me at show Saturday night as well (FM9/FW11). Worked fine at soundcheck, powered off for 1.5h while first act did their show. Quick limited stage turnover (my FM9 was never moved) - powered up, checked tuning on guitars thru Peterson stomp (muted) - good signal on wireless, tuner and FM9 input - run backstage to change - come out and un-mute tuner, quick strum - no output. Quick visual check - still good signal at wireless, Peterson and inputs, nothing muted by accident, reach down and no loose connections. Power off and reboot - and output/sound!! Functioned normally entire show, a bit frustrating as band/crowd restless while I sorted it out (1-2 minutes - reboot felt like forever with several hundred eyes watching). Using very simple preset this gig (less than 60% CPU) - so unlikely to be source. No insights to actual cause - just reporting as another instance of it happening.
 
For what it's worth I've also been having issues when switching between presets. I only use 2 presets and I switch between them using a long press on one of the buttons. When I switch from one preset to the other the unit becomes unresponsive for about 5 or 20 seconds and then starts working again. From memory the audio isn't interrupted just ability to control anything. I've got rehearsal tomorrow so I'll try and get a video and email support. Both presets are around 80% on a fm9 turbo and it's only when switching presets that this happens, no obvious CPU warnings or anything. Didn't happen with the 11 beta firmwares.
 
xpenno said:
For what it's worth I've also been having issues when switching between presets. I only use 2 presets and I switch between them using a long press on one of the buttons. When I switch from one preset to the other the unit becomes unresponsive for about 5 or 20 seconds and then starts working again. From memory the audio isn't interrupted just ability to control anything. I've got rehearsal tomorrow so I'll try and get a video and email support. Both presets are around 80% on a fm9 turbo and it's only when switching presets that this happens, no obvious CPU warnings or anything. Didn't happen with the 11 beta firmwares.
Click to expand...
80% is definitely too high for reliable results...
 
unix-guy said:
80% is definitely too high for reliable results...
Click to expand...

I hope Fractal addresses this at some point. I'm not sure this paradigm of max CPU limits changing from firmware to firmware, as well as some of the max limits not being exposed to the user is optimal in the long run. I appreciate the flexibility built into Fractal's architecture such that artificial limits are not enforced. However, part of their appeal beyond the unrivaled detail in their modeling is their reputation for rock solid reliability. Those two features are some of the reasons the pros love this gear.

Firmware bugs are inevitable, particularly in betas, and I am not referring to issues stemming from them. There should be a predictable compromise between the flexibility to push the limits of the firmware/hardware versus confidence that you will not experience lockups or output drops during performance. Those two goals, max flexibility and reliability, can be oppositional, and perhaps never fully reconciled, but ultimately, I think reliability and predictability has to prevail.

With that said I have never had a problem with my FM9 during a performance. Just getting a bit nervous as I see the max CPU limit and unexposed limits shifting down. Maybe it is unavoidable though as the firmware and features mature and push the hardware to its limits.
 
Last edited:
Mine seems to do the no sound thing every time I use it had to restart in the middle of a gig again this weekend, pretty much missed a whole song, did it again today after I reinstalled firmware and re did my preset. Hope a fix comes soon, I have a large conference to play the 21st and can’t have it lay down on me.
 
  • Really Sad
Reactions: KFF
With the output problem, does a system reset make sense and/or have those experiencing this tried a reset?
 
RDH said:
Mine seems to do the no sound thing every time I use it had to restart in the middle of a gig again this weekend, pretty much missed a whole song, did it again today after I reinstalled firmware and re did my preset. Hope a fix comes soon, I have a large conference to play the 21st and can’t have it lay down on me.
Click to expand...
Why not downgrade to fw10?
 
playmusic said:
I hope Fractal addresses this at some point. I'm not sure this paradigm of max CPU limits changing from firmware to firmware
Click to expand...
It doesn't really change...

The CPU consumption can change as firmware changes. Sometimes more, sometimes less.

jodyinalaska said:
I run at about 79% most of the time and I’ve never had any issues. I’m thinking the meter should be changed so 80% is 100%. 20% just sitting there extra doesn’t make sense to me. Make it 100 and people will definitely stay away from it…….😉
Click to expand...

That won't happen because it's not really practical.

It's not "extra"... These devices are (specialized) computers. What happens when you run your computer at 100%?

If you artificially constraint the CPU you are pretty much guaranteeing some will be wasted.
 
unix-guy said:
It doesn't really change...

The CPU consumption can change as firmware changes. Sometimes more, sometimes less.
...
Click to expand...

I am not referring to the changes in CPU consumption such as you see with new features, changes to models, or greater/lesser efficiencies in the code. That is as expected.

Recommendations on max CPU usage when I first got my FM9, several firmware versions ago, were for about 80% or even a few percentage points above. Now I seem to be seeing recommendations for max CPU usage trending lower than that. Sometimes down to 70%.

Maybe it is only anecdotal, but it appears as if there are a greater number of issues being reported than previously with presets that are under 80%. Wondering if some of the "behind the scenes" processes that don't show up in that CPU usage number have gotten hungrier. Or maybe, those reports of lockups or output drops could be better explained by issues other than CPU consumption. No clue. Just echoing my maybe erroneous sense that recent firmware has resulted in recommendations towards a more conservative use of CPU when designing presets.

Any process that could potentially impact proper and full operation, would optimally be included in the CPU usage number. No unreported hidden processes that impact usage. That way you know exactly how high the indicated CPU number can be in your preset. Either that or it would be useful to know that there will be either a fixed or max CPU usage number for "system" overhead. Either of those would better enable you to calculate max CPU usage.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom