FM3 freezing problems

F

formynsane

Member
Hi everyone,

Yesterday I was playing with a patch that had always worked fine on FW10. I hadn’t used it in a while, and in the meantime I had updated to FW11.

The patch itself works and uses about 80% CPU. However, when controlling it via Ableton through MIDI, switching back and forth between this patch and another one, the unit started having issues.

Mainly, it would stay stuck on this patch and wouldn’t switch to the other one during the different changes in the song… almost like there was some kind of lag.
In FM3-Edit, sometimes I would click on something and it would take 30 seconds to communicate, or it would just time out. Basically, a whole series of problems.

At that point I did a full backup and updated to FW12.
After reinstalling the DynaCabs, when I opened FM3-Edit to use it, it started refreshing presets and blocks, and it took hours! Then it eventually timed out.
The unit rebooted on that same patch and wouldn’t even let me access the tuner (using the physical button).
I wasn’t able to change patches using the physical switches either… it just freezes there, but it still passes audio — if I plug in the guitar, it plays.

It got late so I went to bed. Tonight I’ll try to figure it out, but in the meantime, has this happened to anyone else? Do you have any suggestions on how to proceed step by step?



Thanks.
 
Also, very rarely, but yesterday was doing it, the input 2 make a buzz sound.

I use input 2 for the piezo pickup on my stereo guitar.

Selecting the piezo and entering in input2 produces a buzz sound like bzzzzzzzz and to resolve I do need to restart the unit.
 
Before starting digging in esoteric bug fixing I suggest to triple check the cables!
1. Try different cables, hubs, whatever... When you are able to be 100% confident on the cables you could
2. inspect your pc/mac/daw... When you are able to be 100% confident on the pc/mac/daw you could
3. start inspecting the preset (maybe also starting from scratch.. just input --> amp --> cab --> output, no controllers, no midi)

Following 3 (if working as expected) you could add all the elements 1 by 1 to find the culprit.
I have never had problems with midi preset/scene selection and usb timing, so the problem may be everywhere (just to mention that this is not a bug)

edit:
the only time I had problems was before the gapless switch.. I was using a lot of controllers to create a gapless flow and this was creating cpu spikes.. but with the gapless implementation I just reduced drastically controllers and I have never had another freeze
 
Ok looks like the patch is corrupted in some ways.
I started the unit holding HOME and started on a 000 patch (empty) and everything looks like working, as soon as I select that patch the issues come back again.

Now the question is: how do I recover that patch or....copy to another one? it's not a simple patch, it includes synth, envelopes and other stuff that I cannot remember how I created. And I've already recorded the track on the album...
 
formynsane said:
Ok looks like the patch is corrupted in some ways.
I started the unit holding HOME and started on a 000 patch (empty) and everything looks like working, as soon as I select that patch the issues come back again.

Now the question is: how do I recover that patch or....copy to another one? it's not a simple patch, it includes synth, envelopes and other stuff that I cannot remember how I created. And I've already recorded the track on the album...
Click to expand...
Hopefully you have a backup?
 
Ok, yesterday I started the unit with 000 patch, setup -> utility -> delete all preferences, delete all patches.
Unit was new.
I just loaded the backup of the default banks and tried some default patches, everything was good.
When I loaded bank D, my custom preset, all were working except the one I had problem the night before.
This time the unit was not lagging or freezing, so I deleted the plexi delay, and added a normal delay and now seems to work fine again. also switching patches with MIDI using Ableton.

The strange behavior was that usually, when it comes to have low cpu, the unit shows a message "cpu limit" and there is no sound, but you are not freezing anything and you have time to manage and to understand, to keep the cpu under a level.

In this case, the CPU was 80% and the sound continued to works...
I don't know...it could be a bug of the CPU % calculator or something like that...

Anyway, plexi delay is rarely used...cause it eats a lot of cpu... :(
 
check for controllers, spikes when changing scene can lead to freezes.
You can also use all the tricks and tips to lower cpu (there are tons of threads on the topic, fastest one is to reduce reverb density, as mentioned by @warlockII )
 
Reverb density is always at low, because it's the first cpu sucker.

What do you mean by check for controllers? I have some parameters of the synth block linked to the LFO
 
formynsane said:
Hi everyone,

Yesterday I was playing with a patch that had always worked fine on FW10. I hadn’t used it in a while, and in the meantime I had updated to FW11.

The patch itself works and uses about 80% CPU. However, when controlling it via Ableton through MIDI, switching back and forth between this patch and another one, the unit started having issues.

Mainly, it would stay stuck on this patch and wouldn’t switch to the other one during the different changes in the song… almost like there was some kind of lag.
In FM3-Edit, sometimes I would click on something and it would take 30 seconds to communicate, or it would just time out. Basically, a whole series of problems.

At that point I did a full backup and updated to FW12.
After reinstalling the DynaCabs, when I opened FM3-Edit to use it, it started refreshing presets and blocks, and it took hours! Then it eventually timed out.
The unit rebooted on that same patch and wouldn’t even let me access the tuner (using the physical button).
I wasn’t able to change patches using the physical switches either… it just freezes there, but it still passes audio — if I plug in the guitar, it plays.

It got late so I went to bed. Tonight I’ll try to figure it out, but in the meantime, has this happened to anyone else? Do you have any suggestions on how to proceed step by step?



Thanks.
Click to expand...
It's using too much CPU. The lower priority MIDI handling thread is being starved.
 
You must log in or register to reply here.
Back
Top Bottom