1. How will the whole thing work with multiple instances of Camomile
VST3/AU/LV2 calling multiple instances of [pd~ ].
Each Camomile instance would use a seperate Pd subprocess. Where's the
problem?
2. How will the whole thing work with GUI and VST3/AU/LV2 parameters
and presets.
I guess the Camomile plugin has a regular GUI and just dispatches
parameter changes, etc. to the [pd~] subprocess.
3. Given that different DAWs deals with multi-threading in different
ways (being Reaper one of the smartest in this area) how
Camomile is already threadsafe. Using [pd~] changes nothing in this regard.
Christof
On 13.01.2021 16:10, alfonso santimone wrote:
Hi all,
i think that Alexandre's one is an interesting question.
I think we have to do a bunch of test in "real life" DAW working context.
Interesting points are
1. How will the whole thing work with multiple instances of Camomile
VST3/AU/LV2 calling multiple instances of [pd~ ].
2. How will the whole thing work with GUI and VST3/AU/LV2 parameters
and presets.
3. Given that different DAWs deals with multi-threading in different
ways (being Reaper one of the smartest in this area) how the whole
thing work.
I guess is all a matter of extensive testing.
The last thing in Alexandre's message is another interesting topic.
From my point of view wouldn't be a problem but probably for
Camomile's based VST to reach the non-pd community would be better to
distribute just a simple plugin.
So from the point of the VST/AU/LV2 designer the [pd~ ] solution it's
really promising. From the end user's point of view not so much i
guess and the Camomile-ELSE and Camomile-name_the_libraries ways seem
a more viable solution.
www.elgallorojorecords.bandcamp.com/
<https://elgallorojorecords.bandcamp.com/>
soundcloud.com/alfonsosantimone <http://soundcloud.com/alfonsosantimone>
www.facebook.com/alfonsosantimone
<http://www.facebook.com/alfonsosantimone>
On Wed, Jan 13, 2021 at 3:41 PM Alexandre Torres Porres
<[email protected] <mailto:[email protected]>> wrote:
Em qua., 13 de jan. de 2021 às 05:58, Pierre Guillot
<[email protected] <mailto:[email protected]>> escreveu:
I'm not sure what do you mean by "you can compile the
vst/.au/whatever with it".
If you want to distribute a plugin that use externals without
compiling Camomile, I guess one solution would be to ship a Pd
distribution with the externals in the plugin bundle and use
the [pd~] object to start a process with this embedded Pd
binary (that would be able to load the external). Or you can
ask the user to install Pd and the required externals if you
don't want to ship a complete Pd distribution with the plugin.
I'm just trying to understand what is the difference and advantage
of compiling camomile with externals, which is possible and we've
already made that happen at least for the ELSE-Camomile =>
distribution https://github.com/emviveros/Camomile-ELSE
<https://github.com/emviveros/Camomile-ELSE>
Not that we'll stop, now that we're here, we'll stay I guess :)
but I just wanna make sure what's the motivation. And I guess the
only difference is that you can ship/distribute/sell/give away
just a single plug-in binary without Pd and anything 'else' ;)
_______________________________________________
[email protected] <mailto:[email protected]> mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
<https://lists.puredata.info/listinfo/pd-list>
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
