Petrocelli
Inspired
Windows Keyboard shortcut for Block initialise! Strg (German Keyboard) = CtrlWhat is that?
Last edited:
Windows Keyboard shortcut for Block initialise! Strg (German Keyboard) = CtrlWhat is that?
What does ctrl+ I actually do?Just tested on Beta 4 with Factory Preset 063 (6160s). Changing Scenes is fine for me. Even if the change the Amp block channel. However, If I type Cmd + I with the Amp block selected on Scene 1 the FM3 freezes.
I can confirm. After doing exactly these steps, my FM3 was frozen. Tried it twice.Played with the "5153" Preset, Scene 4 (Blue 50W). Changed Cab Block to Dyna Cab with the 5153 Speakers (Dyn2+Ribbon). Changed Amp Block to PVH 6160 Block Crunch. All good, then pushed "Strg + I" to initialise the Amp Block - FM3 hangs and i had to power cycle!
What does ctrl+ I actually do?
Maybe provide more details...
Definitely sounds like that amp model has a problem still.Went to a preset with a peavey crunch and it froze my FM3. When I restarted it it was stuck at the loading screen. Had to do this like 4 times to get it to boot fully, but it was still frozen. So then I booted it in safe mode and deleted the presets that were causing problems.
When I had this issue, then so long as I turned the rotary knob as the first thing I did after boot, I was able to get away from the problematic preset.I’ve been leery to try mine the past couple days because I do use the 6160s and 5153 presets often (in fact when I last turned it off I think it was still in preset 063). I assume there’s a good chance the Fractal moderators will announce here once they’re sure it’s fixed so we can know when it’s safe to use those presets again? I think tomorrow I’ll turn it on and if I’m right and it’s on one of the presets that can crash FM3s I’ll quickly just change presets for now should be fine.
whoah whoah whoah, I have a dud preset on mine that I cant delete cause it insta hits max CPU so I've just been avoiding it... how does one boot in safe mode to remove it?Went to a preset with a peavey crunch and it froze my FM3. When I restarted it it was stuck at the loading screen. Had to do this like 4 times to get it to boot fully, but it was still frozen. So then I booted it in safe mode and deleted the presets that were causing problems.
From FM3 Manual page 113whoah whoah whoah, I have a dud preset on mine that I cant delete cause it insta hits max CPU so I've just been avoiding it... how does one boot in safe mode to remove it?
You can’t go to manage presets on edit and delete ? Just make sure your listening source is turned off.whoah whoah whoah, I have a dud preset on mine that I cant delete cause it insta hits max CPU so I've just been avoiding it... how does one boot in safe mode to remove it?
Sometimes it’s better to open a blank preset on the modeler’s front-panel then save it over the problem preset.You can’t go to manage presets on edit and delete ? Just make sure your listening source is turned off.
Woah, thank you for this. I always store my most used preset in this location. Need to change it I guess and just keep it empty or for experiments.The FM3 will boot with an empty initialized preset in location “000”. You can STORE this to any other location to overwrite a problematic preset.
I guess the question I have is whether the “000” is just temporarily in memory and either everything is bumped to the next higher number until something is done with the preset (overwrite or save in an empty location). The only thing I could see being an issue is if every preset space is used. I’ve never done the procedure so I’m not sure exactly what happens, but I would hope this procedure wouldn’t force a user to lose a wanted preset.Woah, thank you for this. I always store my most used preset in this location. Need to change it I guess and just keep it empty or for experiments.
I'd say loading the empty preset without overwriting anything would be a better solution (a preset might be saved in the future FW or fixed on Fm9/Axe3), no need to overwrite anything imo