[pd~] takes a "-fifo <numblocks>" argument, which effectively determines
the latency. And yes, plugin authors should add this to the plugin
latency
(https://github.com/pierreguillot/Camomile/wiki/How-to-create-new-plugins#latency)
On 13.01.2021 19:08, alfonso santimone wrote:
If [pd~ ] adds additional latency i think this is potentially
problematic. if it is of some known quantity its value has to be sent
to the DAW for Plugin Delay Compensation. If it is unknown it can give
troubles.
BTW i gonna make some tests in the next days to see how the whole
thing goes about [pd~ ] in Camomile.
thanks!
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 4:26 PM Christof Ressi <[email protected]
<mailto:[email protected]>> wrote:
I'm just trying to understand what is the difference and
advantage of compiling camomile with externals
IIUC, externals are only possible via [pd~] (unless you directly
link the externals with Camomile, as is the case with
ELSE-Camomile). [pd~] obviously has some overhead and adds
additional latency.
On the other hand, I think it wouldn't be too hard for Camomile to
support externals out of the box, but they need to be compiled
with PDINSTANCE. Shipping them next to the actual VST plugin might
confuse some DAWs, so they should be placed in a well known
directory (which could be handled by an installer). This is what
"Waves" does on Windows: "%PROGRAMFILES%/VSTPlugins/Waves" only
contains the "WaveShell-VST.dll" shell plugins; the actual
plugins, libraries and resources reside in "Program Files
(x86)/Waves".
Christof
On 13.01.2021 15:31, Alexandre Torres Porres 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] <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
