Can it be that the “hot zone “ on the vanilla’s Linux version is very narrow in general?
Have you tried #purrdata ? I wonder if it’s more smooth there…
My flatpack of Purr Data starting kicking up errors for being unmaintained, so I deleted it and went to their website, where I found a relative recent Ubuntu deb. https://github.com/agraef/purr-data/releases
But trying to install it relies on the library lbgsl127, which seems not to exist??
There are other errors. Is this project just dead? I liked Purr Data package.
The following packages have unmet dependencies.
purr-data : Depends: libgsl27 (>= 2.7.1) but it is not installable
Depends: libmagick++-6.q16-9t64 (>= 8:6.9.12.98+dfsg1) but it is not installable
Depends: libmagickcore-6.q16-7t64 (>= 8:6.9.10.2) but it is not installable
Recommends: ladspa-foo-plugins but it is not installable
Recommends: invada-studio-plugins-ladspa but it is not going to be installed
Recommends: swh-plugins but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
E: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. purr-data:amd64=2.20.1+git5350+fb224e03-1 is selected for install
2. purr-data:amd64 Depends libgsl27 (>= 2.7.1)
but none of the choices are installable:
[no choices]
I've got a #PD question: If I want to do a sub patch where part of it is visible in the main patch - like say a loop player where I can see the array of steps - and I want to have three of them, Can I write a separate PD file and use that three times or do I need to cut and paste the same code three times?
If I want my three patchers but I want to initialise them with different send names or filenames, can I embed the PD file into a subpatcher and put the sends and file loaders around it and still make the visible interface available?
.... I feel like this is obviously possible now that I'm writing it....