Hi again,
I want to use some patches of mine as VSTs in my DAW without using "pdvst". Is there a different wrapper for pd? "pdvst" cannot send MIDI Data or receive audio, what's really sad. Is there any better wrapper or something alike?
regards
pd as VST within DAW? (not using "pdvst")
Hi again,
I want to use some patches of mine as VSTs in my DAW without using "pdvst". Is there a different wrapper for pd? "pdvst" cannot send MIDI Data or receive audio, what's really sad. Is there any better wrapper or something alike?
regards
There's this new project with libPd and Juce, to make VST plug-ins with Pd and stand-alone applications https://github.com/logsol/Pd-Pulp
don't know how it works, but it looks super!
Yes, I heard of this, but I don't find it very convincing.
It's limited to about 10 automatable parameters and can only load one instance...that doesn't really fit my needs. AND it's not for Win, so I couldn't use it, what disqualifies it as an option...
Thanks though
Hi Elden,
I'm working on it. The goal of my project is to create a dynamic VST plugin where the interface is created with the GUIs of the Cream library. The VST would be able to retrieve the parameters of each GUI and to load multiple instance of PD. I started this project two weeks ago so it is still in development. The graphical part, the multiple instances are set up but I still have to create the parameters part. I'm working on Mac but the Windows and Linux versions should be easy to make. Here what it looks like :
[https://dl.dropboxusercontent.com/u/21891549/Camo.png](link url)
That sound amazing ! Running pd patches as vst would be quite an achievement, keep up the good work !
@Pierre-Guillot
That's really cool, Pierre! I'm looking forward to get hands on this!
What exactly do you mean with "dynamic" VST plugin? Will it detect the number of automatable parameters and adjust the GUI to it? Will it be able to distinguish between switches, buttons or faders? Will it be able to save parameter states as presets?
Will it work even as pd progresses to new versions in the future?
I know this might be too far away for the moment, but do you think about this?
(What I would find really cool as well is a VST wrapper made in pd to be used within a DAW, that can evolve and morph presets like a combination of "morf" http://sourceforge.net/projects/morf-wrapper/ and my "Ewolverine" patch.)
When a patch is loaded, the plugin redraws the interface and creates the buttons, toggles, sliders, etc... that are in the patch. The GUIs must be the ones of the Cream library (there are a lot of GUIs : https://github.com/CICM/CreamLibrary/releases). I made a wrapper that translates the graphical layers of the Cream library into graphical layers for Juce so I don't have to recreate all the GUIs. And you can use externals objects without recompiling the VST.
Then the VST detects all the objects that have "preset" attribute activate and I create the parameters for Juce.
There are 2 problems for the moment :
Most of the DAW are not compatible with the VST3 so the number of parameters is fixe. The solution for the moment is to use a large number of parameters by default (I use 64) then when a new patch is loaded the VST changes their names and values.
The 2nd problem is that some parameters can't be represented with a number value so I'm thinking about an alternative with a preset system inside the VST like in your example or the plugins of the GRM.
I try to document my code and I use libpd without their wrapper (that why I can already have several instances running at the same time in a thread context) so there are no reason of future incompatibility (and if someone want to take it and recompile there's no problem, everything is open source).
Sounds pretty straight forward!
My DAW cannot load VST3, too and it doesn't seem to me that the VST3 format is really common, so that should not bother the most musicians, I think.
To me a limited number of 64 parameters seem a bit too few, to be honest. That's just half of the MIDI standard! I think complicated synthesizers or effect machines could easily reach 200 or 300 automatable parameters.
And don't forget possibilities to input and output MIDI and Audio for every pdpatch-VST!
Apart from that, your project sounds really amazing!
I waited so long for this to happen! Quite a little dream comming true!
FYI, JuceLibPd is going to be imported to Windows too, in the (near?) future..
Oops! Looks like something went wrong!