Long filenames can lead to presumed corrupt /workspace folder (includes solution)

[Sandroid]

Bug Description

It is apparently possible to corrupt the /workspace folder or some of its content.
This can lead to being stuck at boot.

This was initially reported by @cjclip here:

The Polyend Synth suddenly stopped working without any apparent reason (Resolved)

[IMG_2864.HEIC] One day, I simply turned on the synthesizer, and it wouldn’t start and it gets stuck on the loading screen, with the power button becoming unresponsive. Any ideas on how to fix this? I tried performing a hard reset (holding the reset button and the power button), and a recovery procedure was initiated, but it didn’t help either. As I noticed, this error started occurring frequently after I uploaded my own samples into the Grain synthesizer or used patches created from my sam…

Most likely cause

If you run into this issue, check your filename lenghts, specifically for your samples if you are using custom samples.

In can lead to a scene that can’t be loaded correctly, thereby causing this state. If that is the case, check the filenames of any newly added samples.

Alternative Workaround

1. Remove the sd card and delete the /workspace folder
2. Insert the card into the device again and start
3. The system will create a fresh /workspace for you

Caution: this will delete any unsaved progress you may have had.

Steps to Reproduce

1. Turn off the device and remove the sd card
2. Replace the /workspace folder on the card with the one provided in the attachment
3. Insert the sd card and turn on the device
4. The device will hang on boot

Occurrence / Frequency

Always (with the provided workspace)

Found in Firmware

• Version: 1.0.1
• Build: 1459

Attachments

workspace.zip (6.5 KB)

[Sandroid]

I can confirm this is reproducable with the attached workspace.

@cjclip do you remember what the last things were, that you may have done/changed in this project?
Anything that may help limit/focus what to look out for?

[cjclip]

Yes, this issue occurs after I leave custom Grain synthesizers created from my own samples and patches in the last working scene. That’s where the problem lies.

[cjclip]

You might try creating your own patches using your samples in the Grain synthesizer, and most likely, after turning it off and on, the synthesizer will not start.

[Sandroid]

Oh hang on… this makes me think of something…

is it possible that you may have deleted samples from the SD card for the GRAIN, but not changed it within the GRAIN parameter itself?

[Sandroid]

i’ve created a multiple grain patches before without issues, hence why i’m asking if you maybe moved/deleted samples for your grain patches?

[cjclip]

No, nothing like that

[cjclip]

I tested the new beta version and the issue with GRAIN patches persists. Adding them to the working Scene or attempting to load a saved scene using these patches bricks the synthesizer and requires manually deleting the workspace folder.

The archive contains sample files and scenes with patches.
Polyend Patches Problems.zip (2.5 MB)

I would like to receive an official response regarding this issue. Currently, creating custom GRAIN with own samples patches is not a functional feature.

[cjclip]

I thought the issue was due to using Stereo Samples, but working with Mono samples didn’t yield any results. The error persists.

[Sandroid]

I’ll have a look what is happening with your patches.
I currently have not encountered any issues creating GRAIN patches, so i’m curious to see the difference between your approach and mine. Maybe i can find something that seems weird.

[cjclip]

I found the following correlation. The synthesizers stop launching if there is more than one GRAIN in the scene. I’ll now check what happens with the factory patches if I load three of them simultaneously.

[cjclip]

@Sandroid

I’ll have a look what is happening with your patches.
I currently have not encountered any issues creating GRAIN patches, so i’m curious to see the difference between your approach and mine. Maybe i can find something that seems weird.

The system GRAIN patches work without errors. What could possibly be wrong with the user patches? Could the problem be related to long names? Hmm…

[Sandroid]

Maybe. I’m currently cooking some food.

I’ll make sure to check it out later

[cjclip]

And I’m cooking some beats. I found the error. It was an issue with overly long file names.

[BROCKSTAR]

eww beats as in the food or is that beets lol? May your grain engine forever be messed up now!

Lol kidding! glad you found a fix!

[cjclip]

In general, it’s important to keep an eye on the length of file names across all Polyend products, as there is an issue with this.

[Sandroid]

Not per se an issue, but more of a gatcha based on limitations of the FAT32 filesystem.

Either way - i’m glad it got solved. So i take it can close this issue then?

[cjclip]

Yes
See how quickly you need to solve bug problems? ))

[Sandroid]

For future reference:

this issue was caused by filenames that are too long and were not within the limitation of the FAT32 Filesystem.

If you run into this issue, check your filename lenghts, specifically for your samples if you are using custom samples.

[ligriv13]

Is this limitation on names of samples and folders a reason why my sample folder disappears on my og play. Sorry not really had the time or patience to mess with it. Just curious if anybody’s try this