Not a Bug FM3 freeze

E

Enrico85

New Member
Hi, I bought the FM3 tubo mk II (fw 10) 3-4 months ago, and yesterday, during band rehearsals, it unexpectedly froze. It wouldn't respond to any commands. I had to reboot, and then everything was fine for now. I should point out that the preset has a CPU load of between 82 and 84 percent. Has anyone had this type of problem? It would be terrible during a live performance.
Thanks @MkKoY
 
Yeah, that's to be expected when you run it too hot. I've said for years now they need to rescale the CPU usage. Make "actual" 82% show as 100% or something to that effect. Because you're like, oh, 80%? I still have a 5th of my DSP available - let's add more blocks!
 
I had the same problem with cpu usage around 79% but one scene was bumping to 82-83%. I scaled down my preset a bit removing a block I wasn't using. Now I hit around 77% max and I hope I will be stable. A system error log would be nice to know what went wrong cause I had zero warnings and a lot of freezes.
 
zebric21 said:
I had the same problem with cpu usage around 79% but one scene was bumping to 82-83%. I scaled down my preset a bit removing a block I wasn't using. Now I hit around 77% max and I hope I will be stable. A system error log would be nice to know what went wrong cause I had zero warnings and a lot of freezes.
Click to expand...

Under help on the editor there's a view log for block library and preset translation logs, unless you meant you wished it showed on the hardware itself then disregard.
 
Ugly Bunny said:
Yeah, that's to be expected when you run it too hot. I've said for years now they need to rescale the CPU usage. Make "actual" 82% show as 100% or something to that effect. Because you're like, oh, 80%? I still have a 5th of my DSP available - let's add more blocks!
Click to expand...

This. Once you accept the idea that 80% = 100% from a stability perspective, you'll never, ever run into an issue with overload again.
 
zebric21 said:
I had the same problem with cpu usage around 79% but one scene was bumping to 82-83%. I scaled down my preset a bit removing a block I wasn't using. Now I hit around 77% max and I hope I will be stable. A system error log would be nice to know what went wrong cause I had zero warnings and a lot of freezes.
Click to expand...
There's no logging as that would require additional processing and storage... And a filesystem... Maybe more.

Also, as a very experienced systems administrator I can say that logs rarely help when a system locks up... Because a locked up system can't do anything, including writing logs ;)
 
zebric21 said:
I had the same problem with cpu usage around 79% but one scene was bumping to 82-83%. I scaled down my preset a bit removing a block I wasn't using. Now I hit around 77% max and I hope I will be stable. A system error log would be nice to know what went wrong cause I had zero warnings and a lot of freezes.
Click to expand...
A "problems log," more commonly known as an issue log or error log, is a record used in project management and computing to document, track, and manage problems, issues, or errors that arise during a project or within a system. In project management, an issue log provides a central, visible record of problems affecting timelines, budgets, or outcomes, assigning accountability for resolution. In computing, an error log is a file containing detailed information about system events and malfunctions, used for troubleshooting and monitoring. Log it´s very important, that helps managers track the issues.
 
hi guys, this happend me too, and i was on 69%. I wrote it to Diego Pezzati, and him told me for a reset.
It happened to me twice last year, then never again. Yesterday, it happened again, and I had the preset at 69%.
It's a strange bug, and I don't think it's CPU-related.
 
Also, just before freezing, I hear a kind of "ticking" in my headphones and then everything freezes. I have to restart the machine.
 
MkKoY said:
hi guys, this happend me too, and i was on 69%. I wrote it to Diego Pezzati, and him told me for a reset.
It happened to me twice last year, then never again. Yesterday, it happened again, and I had the preset at 69%.
It's a strange bug, and I don't think it's CPU-related.
Click to expand...
This happened to me using the pitch block for a whammy effect. The sound started to act funny and I lost sound completely after a while. The unit worked normal but without sound. A reset fixed everything later.
 
zebric21 said:
This happened to me using the pitch block for a whammy effect. The sound started to act funny and I lost sound completely after a while. The unit worked normal but without sound. A reset fixed everything later.
Click to expand...
yes after first time, i updated firmware to 9 (if i remember), and issue disappear. Yesterday (Fw 10), happend again. But i repeat, it's a stranger bug. I can't reply if i want. So i don't know, how i can fix this.
 
skolacki said:
At 82-84% you are asking for trouble. Run at 75% and you won’t have issues.
Click to expand...
... errrr... My main preset is at 60+ %. I don't use any amp or cab blocks, it's FX galore only with some dose of controllers and that kind of jazz. My FM3 (1st gen) was just fine until today when it simply froze, first was a black screen, then after reboot, it froze. Some how I got the FM3-Editor to communicate with it and erased a Phaser FX from the chain...It solved the issue, BUT the preset's CPU was way below the red line mark...

I'm not saying the 75% CPU red line isn't correct, only adding some data to the fire...

The preset is kind of a bit crazy with loops out for preamp tones and back in for more FX processing... and has lots of continuous controls assigns on expression pedals...
 
Odibrom said:
... errrr... My main preset is at 60+ %. I don't use any amp or cab blocks, it's FX galore only with some dose of controllers and that kind of jazz. My FM3 (1st gen) was just fine until today when it simply froze, first was a black screen, then after reboot, it froze. Some how I got the FM3-Editor to communicate with it and erased a Phaser FX from the chain...It solved the issue, BUT the preset's CPU was way below the red line mark...

I'm not saying the 75% CPU red line isn't correct, only adding some data to the fire...

The preset is kind of a bit crazy with loops out for preamp tones and back in for more FX processing... and has lots of continuous controls assigns on expression pedals...
Click to expand...

Cpu usage depends on what is running in each scene. Some drives use more or less cpu depending on which drive model and it’s the same for most blocks. Maybe you’re hitting a combo that is higher than 60%. 75 isn’t the redline 80% is. I give it some breathing room. When you freeze up is it showing a cpu exceeded error?
 
You must log in or register to reply here.
Back
Top Bottom