I’m saying start with an empty preset, just an IN and OUT block that are connected. Then add blocks one by one, without adjusting them to get the basic layout you want. Then start adjusting the blocks to get the sound you want. If/when the problem reoccurs, you will know exactly what caused it. An alternate way to see if it’s a specific problem in a preset is to start with a similar factory preset that contains whatever block you suspect is the culprit and adjust only that block. The factory presets page and specific pages for blocks in the wiki help locate presets using them.
80+% CPU is not the only indication that a preset has trouble. A CPU WARNING indicator regardless of the CPU %, sound breaking up or the unit going silent, squealing, are all indications that the preset has a bad problem. Just like in a general purpose computer, we can inadvertently push it beyond its abilities and it will freak out. When it does it might not have enough resources available to light an indicator or talk to the editor.
Like I was taught by one of my computer mentors when I started programming professionally, “You can make it foolproof, but not damn-fool proof.” A good modeler gives us the power to screw up the sound but not kill it. From my experience making screwed-up presets when deliberately trying to find the edges and work-around things I saw as limitations, Cliff and co. have done a great job of that. I’ve repeatedly made my FM3 spew some bad words because of my actions.
When building/adjusting a preset I take advantage of the Snapshot tool to keep track of the steps I made. I snapshot when something works. If I screw something up and have to restart the unit, I can roll forward to the last snapshot and try again.
Systematically and incrementally making changes will show where the problem lies.
. One more thought, considering other threads. Was the USB always connected when it locked up? If so, can you try it without?
