Greg Ferguson
Legend!
It behaves like the FX3 and FM9. When the situation is way out of control then threads starve and the system can't do anything.
It behaves like the FX3 and FM9. When the situation is way out of control then threads starve and the system can't do anything.
Interesting and a bummer at the sameHow many controllers do you have in your preset?
I have a few presets which are guaranteed to freeze the FM3 with CPU not hitting 80%. I've reported/shared them to Fractal, but apparently those are not fixable due to many controllers used. I use Pitch followers and Envelope followers quite extensively. Some of my presets are below 80% but 100% freeze a device after an attempt to switch a scene, etc.
It is also affecting scene switching speed - when such preset is processing the sound (i.e. guitar volume knob is not 0), the scenes will not switch until I'm muting the guitar - I believe this is due Pitch followers producing a high load on CPU blocking other actions to keep the sound flowing.
Also, FM3 freezes quite often when uploading an IR from Cab-Lab 4 to such preset - no issues with presets which are not close to 80% and have less controllers. So I work on IRs using simplified presets and them transfer them to the main presets. Keep this in mind just in case.
Try removing a few controllers like Pitch followers if you use them and see if stability improves. This works for me, but I keep running the device on the edge anyway, as I'm not gigging a lot these days and can wait for the rebootThe only bad thing is that my device sends a loud pop to the speakers when switching off and on, so when I'm plugged in directly into the speaker without volume control such as Genelec monitors, it brings some discomfort.
I'm rarely have any freeze issues with the presets over 80% if the controllers are not used.
I actually hacked the preset up last to accommodate the 76% but I can still send it if you think that’s worth looking into.
Great tip! I have both out 1/2 eq enabled but only use the out 2 for personal monitors which I do add a little eq on but I’ll disable out 1. Thanks for that.
I already have the reverb on economy, I don’t think I can take another hit to reverb but I’ll note that and explore it as an option.
Interesting. I can run up to 83-85pct without stalling the patches but rarely use more than 3-4 controllers. Maybe also check fast/medium/slow action of the controllers and exp pedals, and use of the preamp and preamp quality in the cab blocks that also affect cpu usage.
Oh, thank you for sharing this bit. I just replaced Shiva with Cornfed in my template and everything became three times slower - up to the point, where removing pitch controllers from AMP's EQ (I'm crazy, I know) and a few other placed didn't actually help, the scenes are not switching until I stop playing. I've shared the preset with Fractal yesterday again, but maybe this is the answer to the issues I'm having.
I had this before FW7 and stopped using followers on Amp's input and gain because of that. But that's not the case any more, I didn't hear any crackling for a long long time. Only occasional volume jumps when you play a chord and it suddenly decides that it's time to change the input drive value at some point
I don't think it's an issue with Input Trim because that is essentially a pure pre-gain level control.
I'm sorry to hear that, mate!Found out the hard way tonight... I knew running presets to 80% was a bad idea so I've kept things hovering around 77-78% thinking I was safe. WRONG! Mid gig I change to my Michael Jackson preset to play "Black and White". Here comes the big opening guitar riff and... nothing! FML
so moral of the story, don't go past 76% because from what I've seen on the FM3 is a fairly large spike in CPU (up to 2-3%) around whatever the baseline CPU is at. I don't experience freezes with the FM9 when it hit's 80% but I'm going to follow suit with that unit too.
Happened to me more than once - the worst part of that is not the freeze itself, but that "Output" knobs do nothing in this case. I expected them to be "after" everything as manual says, but once the unit goes sqeak, they will not reduce the sound, only shutting the unit off helps.
Yes, you are right. I was really to surprised to find out about that. That's why it was taking me so long while leaning over. So it's definitely a CPU-related problem, right? I'll see what I can do to reduce the load of the patch. Still don't get why someone decides to use a scale up to 100 and you can't go over 75. That doesn't make any sense to me at all!
I do not know. We have a computer inside Fm3, so many things could go wrong in theory, and CPU overload to cause this is pretty much the least possible candidate imo.
