Non-responsive pads and clipping audio

Had a couple of glitches this afternoon, and I’ve had both happen in the past, too.

  1. I had stepped away from the Synth for a few minutes, and when I came back I found all the pads to be non-responsive. The buttons and knobs were all still fine. Rebooting it resolved the problem.

  2. A few minutes after that, I was making some adjustments to the reverb settings and it started clipping the audio. Shortly after that, the audio cut out completely and didn’t come back until I switched to a different scene.

In both cases, I was working my custom scenes I’d built from init.

I just had this happen to me as well tonight. I stopped playing it for about 10 minutes and came back and my blue grid was unresponsive but my yellow and purple grid was fine. All 3 were fine and working when I left it there though, but came back and the blue grid was dead. Weird!

Reloaded the scene and worked fine afterwards.

I’ve had a couple of non-responsive moments - also fixed by rebooting. I putting down to the Synth to objecting to me playing about with settings too much, too quickly! Wasn’t a real problem, perhaps a reminder that saving your work frequently is a good idea to avoid losing changes.

Hidden content - click to view

Moderator comment: Unnecessary incendiary comment. Please refrain from doing that. - @Sandroid

I just created a Backstage login so I could share the same error. I had the Synth turned on today and stepped away for about an hour, and when I came back I can only get 1-2 grids producing sound at a time. For some scenes it’s 0 grids, for only a couple (Venus theory lakeside and moods, Stazma noisebox ) all 3 work. Most often it’s only a single working grid, but the color which works depends on the scene.

I have tried 1) loading new presets on the non-working grids, 2) unplugging everything for 5 minutes and then rebooting, 3) reflashing the 1.01 OS and 4) doing an emergency reset, and none of these worked.

I was able to init a new scene and produce audio with 3 grids, but after saving it as a scene, when I reolad the scene it no longer produces sound, even after a reboot.

Super bummed that I basically have a non-functional Synth now, because I was really enjoying it. Hoping some other reset procedure can be suggested soon so I don’t have to return it already! :frowning:

Hey @sbm. Sorry to hear about issues.

Will you please update your bug report to follow the provided bug template? It makes it a lot easier for everyone who has to try and reproduce the problems. You can find the template if you start a new Bug topic and then copy/paste it in here.

Also, if you don’t mind, please attach your custom scenes.

It’s worth a chance to check but make sure all 3 grids are on LOCAL: ON.

Click the main encoder by the screen and go to “synth” and check and make sure all 3 colored engines are set to LOCAL MODE: ON for internal sounds.

I checked local status and that didn’t work. Also tried triggering midi from an Elektron box and it would only work for the channels that were actively working on the Synth - same as playing on the Synth itself. I tried changing the midi channels on the Polyend and the channels that worked/didn’t work would follow the midi channel change.

I’ve also tried flashing back to the 1.0 firmware because I ran run out of things to check and had no luck.

In case someone else gets this problem, I finally was able to get the Synth working again by deleting all of the content from the SD card except firmware, rebooting (which allowed me to init and save new scenes fine), then copying back the other scenes/patches/samples directories to the SD card. I didn’t copy over the Scenes/globalSettings file, and am wondering if it was the bringer of bad vibes.

2 Likes

If something goes haywire… usually it’s best to try to delete the /workspace folder and/or the globalSettings file.

  • /workspace is the last known state of your open project/scene (saved or unsaved). So be careful when deleting this as any unsaved changes will be gone afterwards
  • globalSettings should be self explanatory

It looks like some setting must have been weird. But i’m glad you got it working again :heart:

3 Likes

This is how REV reverb was designed: we didn’t want to limit the ranges so it’s all “sweet spot”, but instead allow you to get into strange territory if you need to… With maximum Time = 100, and changing Diffusion or Size from 100 down towards 0, reverb results in extremely long and very noisy tails which can overwhelm the output completely. To get out of this state, all you need to do is lower the Time to at least 99 which should bring back stable audio output. Warp reverb model is especially designed to go into such extremes.

Similar is true for DEL delay Feedback which goes up to 150% and can produce wild sounds.

1 Like

Has anyone been able to reproduce this reliably?

Is that a new model, or do you mean Warp?

1 Like

Yes, I mean Warp, I’ll correct it above. Sorry.

1 Like