Finally found some time to play with the app. It’s really cool and makes pisound so much more useful! I tried to my own patches, but ran into two problems:
Loading the patch from usb didn’t work
Manually copying the patch worked but now when I start the app it disconnects when accessing the list of patches.
I know a new version is comin soon and maybe that will solve my issue, but still… How am I supposed to prepare patches to work with the pisound app exactly? I did copy the .yml file from one of the included patches and modified it, but maybe I’m missing something… Any heads up?
Also, is the yml file needed for the app to be able to copy things from usb?
Did you get any error during USB importing? What output did the app give you?
The blokas.yml file is used to provide metadata about the patch, like the display name, description, the entry point patch, etc… The file should be customized for each patch you add. The app does support having ‘main.pd’ patches in separate subfolders, in that case it provides limited patch view with the name taken from the folder name the main.pd is in.
After more testing yesterday evening I have found the problem: I had left the “image” property in the YAML file but hadn’t specified any image. That would crash the pisound app.
Adding a PNG solved the problem.
So now everything works, except for the patch copying from USB. Haven’t gotten around testing that yet, but now I have a little suspicion… do I have to put all the patches I want to copy into a folder called “puredata-patches” on the USB drive?
Correct The Pisound App - Pisound Documentation We did it this way to avoid scanning any large HDD drives that could be connected with unrelated information. By placing stuff in ‘puredata-patches’, you explicitly show your intent to import just those files.
Thank you for reporting this, we’ll get this fixed in the update, it should be possible not to specify or include image property in the yml file.
