Bug Description
Since I switched to the latest firmware, I’ve been experiencing sudden crashes (red pads of death) repeatedly. For a long time, I wasn’t sure what was causing it. But now, I’m pretty sure it has something to do with the more versatile synth engines VAP, WTFM, and PERC.
It repeatedly happens that the Play+ freezes when I use several of them at the same time. It doesn’t really matter which of the synth engines I use or in which combination. When more than one of these eniges is used, there is the possibility that the freezes happen.
The freezes itself happen at different times. Sometimes they happen when I load one of these synth engines, and sometimes as soon as I try to edit the patch.
The error doesn’t always occur and sometimes disappears after a few hard resets. However, I’ve now managed to save two projects where this bug reliably occurs. Details are provided in the “Steps to Reproduce.”
Things I can already rule out as potential sources of the error:
- Faulty patch file: I always start with an Init Patch and build my desired sound from there. The presets/patches on my Play+ are essentially never used.
- Faulty SD card: I even bought a new one to test this, but the error also occurs with it.
- Faulty power adapter: The issue occurs both with the original adapter and cable, as well as with various other adapters and cables.
- Deleting workspace folder
Steps to Reproduce
- Download and unzip the Attachement
- Copy the two projects on your Play+ SD-card
- Start Play+
Project “BR_Tilt_Edit_Synth”:
- Load the project
- Menu → Synths
- Select Synth 1 or Synth 2 (both WTFM)
- Edit the selected Synth OR load another synth engine (when the selected engine is VAP, WTFM or PERC it freezes, when it is another engine it works fine)
Project “BR_Tilt_WTFM+PERC”
- Load the project
- Menu → Synths
- Select Synth 2
- Load PERC as the synth engine
Occurrence / Frequency
Sometimes
Found in Firmware
- Version: 1.1.0
- Build: 1708
Attachments
2 Likes
Have you tried deleting workspace folder and retrying? Of course save anything before doing so, but sometimes that folder can get corrupted and fixes when you do this.
That is something I have already tried, without success. Multiple times. I added it to my list of things I already tried.
1 Like
I am still running into this issue as well. Weeks of work and I’m lucky if I can get it open after opening a new project, then turning it off and back on again, then loading the new song. Lo and behold, im using a VAP and WTFM synth, though I have a feeling the PERC synth is still troublesome. Either way, for every project this has occured to me on, the WTFM is always in use. I really hope they find a fix soon as it is incredibly frustrating, to say the least.
I have started to load a new project before shutting down. Idk if it helps, tbh, or just soothes my headache with superstition. Regardless, shutting the device down mid set to load a song is a serious issue for an $800 piece of equipment.
Finally, someone else who has the same problem. I was beginning to think I was the only one working with the internal synths. By now, I’m almost 100% sure that WTFM is the main issue.
Yesterday, I tried working on a track where I used all 8 voices for a WTFM. As soon as I tried adjusting the LFOs, the entire project crashed. This time, it even happened without the red pads of death.I think this indicates that the issue is very fundamental.
The error was also reproducible when I started a new project.
I’m currently considering switching back to the previous firmware. I’d actually like to experiment with PERC, but in this state, it’s unfortunately too unstable for me. With the previous firmware, I never had problems of this magnitude.
If most of my songs weren’t written in the current firmware, I’d do the same, tbh. Every time I want to use the WTFM synth, it’s a roll of the dice on whether I’ll get to finish the song. I just avoid using it entirely and hope that polyend views this as enough of a priority to fix in the near future.
2 Likes