On 9/12/24 15:17, cyrille henry wrote:
hello,
With default path, or using the -noprefs starting option, Pd is not looking for externals where deken install them. I.E : if I install pmppd with deken, start pd -noprefs, Pd can't find the pmpd object, even with "declare -stdpath pmpd -path pmpd" in the patch
Is this the expected behaviours? I think the deken path should be add to the standard search path. (standard search path are only : patch location, ~/.local/lib/pd/extra/, ~/pd-externals/, /usr/local/lib/pd-externals/, /usr/local/lib/pd/extra/)
it's more complicated. Pd doesn't know about deken (the latter being a pure Pd-GUI thing). deken tries to use the default search path as the default installation path.
but once you started Pd and accepted the ~/Documents/Pd path as the default, deken will remember that selection. you can also set whatever path you want for deken to install externals to, but deken will use it's own (pd-gui) preferences, and not tell the Pd-core about that.
this all works nicely, as long as you don't try to force some specific
settings, e.g. via (-noprefs).
if you know how to use -noprefs, we assume you can also add "-path
/path/to/where/i/told/deken/to/put/stuff" :-)
gfmadsr IOhannes