Missing objects

[klangschmied]

Thanks for the nice patch!

Two issues:

1. Loading in Pd there a missing objects:

0-poly_grain-L: no such object
0-poly_grain-R: no such object
soundfiler read: : No such file or directory

2. Running in plugdata
   I want to run the patch in plugdata on iOS (v0.8.3), but there is a problem, the abstraction "ys.granular_main" did not load with the main-patch, every time I have instantiated it again. This is for sure a problem with the plugdata-version.
   To overcome this bug I want to assign the parameter $0, $1 and $2 with absolute values, but what are these parameters for to instances?

[yannseznec]

hey! thanks so much for the report.

I've just fixed the "0-poly_grain-L: no such object" errors, they weren't effecting anything but they are annoying. this bug report gave me the chance to track them down.

The "soundfiler read: No such file or directory" error is a bit more annoying to fix but it also doesn't have any real effect. this is caused because when you make a ys.granular_main.pd patch it takes two arguments - an instance number and an (optional) filename for loading a sound file on startup. if you don't put a filename as a second argument then the patch will start without a sound loaded, and it will throw that error because soundfiler is being sent a message to load a file without a name. it works just fine anyway.

I don't actually know how to avoid this error message, but I'll look into it at some point.

With regards to your second question - I haven't tried this system in plugdata in a while, so I haven't run into this problem but I can test it. With regards to the specific parameters you ask - I've mentioned just above, but they are:
$1 -> a specific instance number. this can be any integer, it allows you to have multiple instances of ys.granular_main open simultaneously and allows for easier integration with external mappings and controls.
$2 -> a filename for a sound to be loaded on startup

I'm not sure what you mean exactly by $0, I don't think I'm using that in the ys.granular_main patch. If I am, it's because $0 in Pure Data generates a unique variable number that is consistent within a patch.

In any case, I'll have a look at how the patch runs in Plug Data, it would be nice for it to work normally there and I can't see why it wouldn't.

[klangschmied]

thanks yann for your extensive explanation, make sense for me. Let me know your experience with your pd-patch in plugdata on iOS (the instantiation-problem occurs only on the iOS version of plugdata). And I got it to work with loading a sound via $2 with the whole filename (fe. xyz.wav).

[klangschmied]

Did you investigate the behaviour in plugdata on iOS? What I really like to use is a store/recall mechanism, where I can store interesting sets of parameters and recall it with a mouseclick (like preset object in Max)? Is this possible on Pd?

[yannseznec]

Hey! I'm finally following up on this.
I haven't implemented a slick store/recall preset system, though I am aware that some things like that exist in external libraries.
You can do this in a sort of manual way with the messages - you can see in the help window in the patch how I made a message box that is full of parameter values. you can make your own, with whatever values you want hardcoded in there, and then trigger that set of values with a bang object or any other method you choose. It would take more work to have those values set automatically from the GUI, but it is also possible. It's not really a priority for me to make just now, though!

[yannseznec]

I am testing the patch on PlugData iOS now - I am having a similar experience. It does not load the main patch in the same way as it does on the desktop, but it (sometimes) loads the patch if you create a new main patch. I am not certain this is something I can fix myself, but I'll poke around a bit more.
However it works remarkably well on the phone, once it is loaded! It's my first time trying PlugData for iOS, I'm impressed. The interface is a bit tricky to use on a phone screen, so maybe I should make a new UI for it one day.

[klangschmied]

Thanks for your reply and effort. I already had setup two hardcoded parameters-boxes and trigger them with a button.
BTW iOS implementation: Sometimes I can load the main-patch, when I manually instantiate it again, but would be nice if it is working by default. I already ask in the discord server...maybe iOS PlugData v0.9 would solve the problem.
Let me know if your further experience and enhancements.