nice project! and works fine (it is a pity that pd starts without additional libraries). seems i (we) have to spend much more time with pd for creating special vst patches now : )
notes: i have found out, that when i close vst window or apply on an audio track, pd does not unload from the memory. thus, after a few times of loading pd like vst plugin the memory is overfilled by N pd.exes Гµ 6MB.
all the best
----- Original Message ----- From: "Joseph A. Sarlo" jsarlo@ucsd.edu To: "PD Announce List" pd-announce@iem.kug.ac.at Sent: Tuesday, September 23, 2003 3:39 AM Subject: [PD-announce] PdVst: Pd as a VST plugin v0.0.1
Hi all,
I've just finished the first version of PdVst. It allows you to run Pd patches as VST plugins (Win32 only). It's still pretty alpha, but for any brave souls out there who want to give it a try...
http://crca.ucsd.edu/~jsarlo/pdvst/
Joe jsarlo@ucsd.edu
PD-announce mailing list PD-announce@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-announce
nice project! and works fine (it is a pity that pd starts without
additional
libraries).
If your patch requires an external library, you can put the .dll file in the pdvst directory and Pd should find it automatically. Oh, but I just realized that will only work for objects that have the same name as the library. I guess this is first on my TODO list for the next version.
notes: i have found out, that when i close vst window or apply on an audio track, pd does not unload from the memory. thus, after a few times of loading pd like vst plugin the memory is overfilled by N pd.exes х 6MB.
What VST host application are you running? pd.exe is supposed to exit when either the instance of the plugin unloads (i.e. the destructor is called) or the application that opened Pd is no longer running.
Thanks for the bug report.
Joe jsarlo@ucsd.edu
i was using Sound Forge 6 and VST-DX Wrapper v1.0 and forgot to say that gripd window also does not close after applying/closing.
best
What VST host application are you running? pd.exe is supposed to exit when either the instance of the plugin unloads (i.e. the destructor is called)
or
the application that opened Pd is no longer running.
Thanks for the bug report.
Joe jsarlo@ucsd.edu
hi Joe, Miller, everybody,
this reminds me of an old ``patch dependency'' theme...
So, is the idea of either Pd magically putting in a patch file (1st line) anything of the ``#N require gem zexy...'' sort, or of a Pd user explicitly putting in a patch an object [require gem zexy], simply a bad idea?
Krzysztof
Joseph A. Sarlo wrote: ...
If your patch requires an external library, you can put the .dll file in the pdvst directory and Pd should find it automatically. Oh, but I just realized that will only work for objects that have the same name as the library. I guess this is first on my TODO list for the next version.
On Wed, 24 Sep 2003, Krzysztof Czaja wrote:
this reminds me of an old ``patch dependency'' theme...
So, is the idea of either Pd magically putting in a patch file (1st line) anything of the ``#N require gem zexy...'' sort, or of a Pd user explicitly putting in a patch an object [require gem zexy], simply a bad idea?
Putting a [Gem] and [zexy] as first objects in your patch will load Gem and zexy ... its not super clean, but it works.
Guenter
Joseph A. Sarlo wrote: ...
If your patch requires an external library, you can put the .dll file in the pdvst directory and Pd should find it automatically. Oh, but I just realized that will only work for objects that have the same name as the library. I guess this is first on my TODO list for the next version.
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Nice!!!! I think this is a great step ahead in the pd integration with other software!!! Joseph you are doin' a really great work!!! ...Is it possible to route midi messages to and from pdvst?
lalo ----- Original Message ----- From: "guenter geiger" geiger@xdv.org To: "Krzysztof Czaja" czaja@chopin.edu.pl Cc: "Joseph A. Sarlo" jsarlo@ucsd.edu; pd-list@iem.kug.ac.at Sent: Thursday, September 25, 2003 4:26 PM Subject: Re: [PD] Re: [PD-announce] PdVst: Pd as a VST plugin v0.0.1
On Wed, 24 Sep 2003, Krzysztof Czaja wrote:
this reminds me of an old ``patch dependency'' theme...
So, is the idea of either Pd magically putting in a patch file (1st line) anything of the ``#N require gem zexy...'' sort, or of a Pd user explicitly putting in a patch an object [require gem zexy], simply a bad idea?
Putting a [Gem] and [zexy] as first objects in your patch will load Gem and zexy ... its not super clean, but it works.
Guenter
Joseph A. Sarlo wrote: ...
If your patch requires an external library, you can put the .dll file
in the
pdvst directory and Pd should find it automatically. Oh, but I just
realized
that will only work for objects that have the same name as the
library. I
guess this is first on my TODO list for the next version.
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Nice!!!! I think this is a great step ahead in the pd integration with other software!!! Joseph you are doin' a really great work!!! ...Is it possible to route midi messages to and from pdvst?
In my thinking, the VST host should be handling all MIDI I/O. So you can use the host application's normal method of routing MIDI data to VST plugin parameters, and in your Pd patch receive the parameter value with a "receive rvstparameter<n>" object, where <n> is the integer index of the parameter.
Joe jsarlo@ucsd.edu
-
Andrey Savitsky -
guenter geiger -
Joseph A. Sarlo -
Krzysztof Czaja -
lalo