The Official Sequential/DSI Forum

Synthesizer that freezes

Synthesizer that freezes
« on: August 07, 2021, 05:13:32 AM »
Problem of the day:

Create a patch ... and there comes a time when the device freezes.
Repeat a patch and once again the device freezes.
The problem may be with the modulation matrix or the sequencer. As soon as you put a little too much, it freezes.
Result: 2 hours of work lost.
This problem has happened several other times.

When the machine freezes, can it be unlocked?
Is there a way to get the lost work back?


It's frustrating, frankly, to pay and to have a device that lets you go in the midst of work. Can you imagine that behind some people, there may be a timming to be respected, a project to be fulfilled, responsibilities?
If the machine is not working as it should, why did you market it?

For me this synth is also not usable live.

I like this device, I paid for it, but I am disappointed with this issue.
It's stressful. You have to save very often. Turn off, turn on again.
You imagine live
Paper & Pencil.
Prophet 6, Rev2, Pro3

Re: Synthesizer that freezes
« Reply #1 on: August 07, 2021, 05:41:27 AM »
I experienced this exact freezing problem on my last (new) PRO 3 SE (the third item I had to send back due to various issues).
It happened to me several times, each time when I was recording modulations in real time in the sequencer section. The unit then stopped making sound and I could not exit the sequencer screen, only turn it off.
However, I have not been able to reproduce the error.

Re: Synthesizer that freezes
« Reply #2 on: August 14, 2021, 08:12:41 AM »
This happened to me twice within one week last month...once as I was prepping a set list, and the second time during rehearsal before our church service.  Neither time did I make any significant changes from the saved patch...probably just some filter or envelope tweaks.  Makes me very nervous about using it live.

Re: Synthesizer that freezes
« Reply #3 on: August 14, 2021, 01:08:50 PM »
Iíve created some pretty dense patches and not run into this. What FW version are you all on? Have you reported it to support?