Hi all,
I know that there was some activity going on at some point with using VST plugins in Pd, and I got the impression that there were several unrelated objects, or legacy objects, and I was never really sure which the "current" VST object was for Pd (plugin~? vst~?). So…
Is it currently possible to host VST objects in OS X in Pd? Which object should I be using? CVS? Is compilation straightforward?
Thanks! David
ps. My question also goes for LADSPA, does the old plugin~ work for LADSPA in os x?
On Sat Feb 03, 2007 at 10:11:34PM -0500, David NG McCallum wrote:
Hi all,
I know that there was some activity going on at some point with using VST plugins in Pd, and I got the impression that there were several unrelated objects, or legacy objects, and I was never really sure which the "current" VST object was for Pd (plugin~? vst~?). So…
Is it currently possible to host VST objects in OS X in Pd? Which object should I be using? CVS? Is compilation straightforward?
Thanks! David
ps. My question also goes for LADSPA, does the old plugin~ work for LADSPA in os x?
both tgrill's vst~ and plugin~ should work on OSX with trivial modifications. i suggest you just try compiling them, after collecting the requisite SDKs.
-- __ _ _ _ __ _ http://sintheta.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Plugin~ compiles (Hans has it doing it somehow, I couldn't get it to work) but it doesn't actually work for me, just causes Pd to crash. Also, the difference between OS X vsts and Win32 vsts is a factor here, from what I understand. So unfortunately I don't think Mac OS X is doing too well right now as for plugins, but hopefully someone who knows C will be able to fix that? There are many who would be very, *very* happy to be able to use ladspa plugins!
An option I haven't tried is dssi~ - you may want to look into that.
Kevin
On 2/4/07, carmen _@whats-your.name wrote:
On Sat Feb 03, 2007 at 10:11:34PM -0500, David NG McCallum wrote:
Hi all,
I know that there was some activity going on at some point with using VST plugins in Pd, and I got the impression that there were several unrelated objects, or legacy objects, and I was never really sure which the "current" VST object was for Pd (plugin~? vst~?). So…
Is it currently possible to host VST objects in OS X in Pd? Which object should I be using? CVS? Is compilation straightforward?
Thanks! David
ps. My question also goes for LADSPA, does the old plugin~ work for LADSPA in os x?
both tgrill's vst~ and plugin~ should work on OSX with trivial modifications. i suggest you just try compiling them, after collecting the requisite SDKs.
-- __ _ _ _ __ _ http://sintheta.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Yeah, I just found out that plugin~ is included in pd-extended, but I can't seem to get it to recognise any of the ladspa plugins I have on my machine, and whenever I try to load the plugin~ help patch, my machine just crashes… sigh.
D
On 04/02/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Plugin~ compiles (Hans has it doing it somehow, I couldn't get it to work) but it doesn't actually work for me, just causes Pd to crash. Also, the difference between OS X vsts and Win32 vsts is a factor here, from what I understand. So unfortunately I don't think Mac OS X is doing too well right now as for plugins, but hopefully someone who knows C will be able to fix that? There are many who would be very, *very* happy to be able to use ladspa plugins!
An option I haven't tried is dssi~ - you may want to look into that.
Kevin
On 2/4/07, carmen <_@ whats-your.name> wrote:
On Sat Feb 03, 2007 at 10:11:34PM -0500, David NG McCallum wrote:
Hi all,
I know that there was some activity going on at some point with using VST plugins in Pd, and I got the impression that there were several unrelated objects, or legacy objects, and I was never really sure which the "current" VST object was for Pd (plugin~? vst~?). So…
Is it currently possible to host VST objects in OS X in Pd? Which object should I be using? CVS? Is compilation straightforward?
Thanks! David
ps. My question also goes for LADSPA, does the old plugin~ work for LADSPA in os x?
both tgrill's vst~ and plugin~ should work on OSX with trivial
modifications. i suggest you just try compiling them, after collecting the requisite SDKs.
-- __ _ _ _ __ _ http://sintheta.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
--
++++ http://pocketkm.blogspot.com _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Should also say that when I try to compile plugin~ I get the following error (that I saw mentioned on the list earlier, and the only solution I could find anyone give was to find a binary of plugin~ somewhere, which isn't that helpful):
gcc -dynamiclib -o plugin~.pd_linux jload.os jsearch.os plugin~.os ld: Undefined symbols: _class_addmethod _class_new _dsp_addv _gensym _inlet_free _inlet_new _nullfn _outlet_anything _outlet_free _outlet_new _pd_new _post _sys_getsr /usr/bin/libtool: internal link edit command failed scons: *** [plugin~.pd_linux] Error 1 scons: building terminated because of errors.
D!
On 04/02/07, David NG McCallum d@mentalfloss.ca wrote:
Yeah, I just found out that plugin~ is included in pd-extended, but I can't seem to get it to recognise any of the ladspa plugins I have on my machine, and whenever I try to load the plugin~ help patch, my machine just crashes… sigh.
D
On 04/02/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Plugin~ compiles (Hans has it doing it somehow, I couldn't get it to work) but it doesn't actually work for me, just causes Pd to crash. Also, the difference between OS X vsts and Win32 vsts is a factor here, from what I understand. So unfortunately I don't think Mac OS X is doing too well right now as for plugins, but hopefully someone who knows C will be able to fix that? There are many who would be very, *very* happy to be able to use ladspa plugins!
An option I haven't tried is dssi~ - you may want to look into that.
Kevin
On 2/4/07, carmen <_@ whats-your.name> wrote:
On Sat Feb 03, 2007 at 10:11:34PM -0500, David NG McCallum wrote:
Hi all,
I know that there was some activity going on at some point with using VST plugins in Pd, and I got the impression that there were several unrelated objects, or legacy objects, and I was never really sure which the "current" VST object was for Pd (plugin~? vst~?). So…
Is it currently possible to host VST objects in OS X in Pd? Which object should I be using? CVS? Is compilation straightforward?
Thanks! David
ps. My question also goes for LADSPA, does the old plugin~ work for LADSPA in os x?
both tgrill's vst~ and plugin~ should work on OSX with trivial
modifications. i suggest you just try compiling them, after collecting the requisite SDKs.
-- __ _ _ _ __ _ http://sintheta.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
--
++++ http://pocketkm.blogspot.com _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- __ _ _ _ __ _ http://sintheta.org
Exactly the same as what I was getting. See http://lists.puredata.info/pipermail/pd-list/2007-01/046124.html
Kevin
On 2/4/07, David NG McCallum d@mentalfloss.ca wrote:
Should also say that when I try to compile plugin~ I get the following error (that I saw mentioned on the list earlier, and the only solution I could find anyone give was to find a binary of plugin~ somewhere, which isn't that helpful):
gcc -dynamiclib -o plugin~.pd_linux jload.os jsearch.os plugin~.os ld: Undefined symbols: _class_addmethod _class_new _dsp_addv _gensym _inlet_free _inlet_new _nullfn _outlet_anything _outlet_free _outlet_new _pd_new _post _sys_getsr /usr/bin/libtool: internal link edit command failed scons: *** [plugin~.pd_linux] Error 1 scons: building terminated because of errors.
D!
On 04/02/07, David NG McCallum d@mentalfloss.ca wrote:
Yeah, I just found out that plugin~ is included in pd-extended, but I can't seem to get it to recognise any of the ladspa plugins I have on my machine, and whenever I try to load the plugin~ help patch, my machine just crashes… sigh.
D
On 04/02/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Plugin~ compiles (Hans has it doing it somehow, I couldn't get it to
work)
but it doesn't actually work for me, just causes Pd to crash. Also,
the
difference between OS X vsts and Win32 vsts is a factor here, from
what I
understand. So unfortunately I don't think Mac OS X is doing too well
right
now as for plugins, but hopefully someone who knows C will be able to
fix
that? There are many who would be very, *very* happy to be able to
use
ladspa plugins!
An option I haven't tried is dssi~ - you may want to look into that.
Kevin
On 2/4/07, carmen <_@ whats-your.name> wrote:
On Sat Feb 03, 2007 at 10:11:34PM -0500, David NG McCallum wrote:
Hi all,
I know that there was some activity going on at some point with
using
VST plugins in Pd, and I got the impression that there were
several
unrelated objects, or legacy objects, and I was never really sure which the "current" VST object was for Pd (plugin~? vst~?). So…
Is it currently possible to host VST objects in OS X in Pd? Which object should I be using? CVS? Is compilation straightforward?
Thanks! David
ps. My question also goes for LADSPA, does the old plugin~ work
for
LADSPA in os x?
both tgrill's vst~ and plugin~ should work on OSX with trivial
modifications. i suggest you just try compiling them, after collecting
the
requisite SDKs.
-- __ _ _ _ __ _ http://sintheta.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
--
++++ http://pocketkm.blogspot.com _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- __ _ _ _ __ _ http://sintheta.org
-- __ _ _ _ __ _ http://sintheta.org
dssi~ definitely works on OS X for both LADSPA and DSSI plugins. The official release can be found at: http://www.puredata.org/Members/jb/dssi%7E/view
There is a dependency on the liblo library. You will also need the LADSPA and DSSI SDK's if you want to compile from source. Let me know if you have any problems.
Alternatively if you let me know which platform you are on (powerpc, intel), and which version of PD, I could send you a binary.
best,
Jamie
On Sun, 2007-02-04 at 10:21 -0500, David NG McCallum wrote:
Yeah, I just found out that plugin~ is included in pd-extended, but I can't seem to get it to recognise any of the ladspa plugins I have on my machine, and whenever I try to load the plugin~ help patch, my machine just crashes… sigh.
D
On 04/02/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Plugin~ compiles (Hans has it doing it somehow, I couldn't get it to work) but it doesn't actually work for me, just causes Pd to crash. Also, the difference between OS X vsts and Win32 vsts is a factor here, from what I understand. So unfortunately I don't think Mac OS X is doing too well right now as for plugins, but hopefully someone who knows C will be able to fix that? There are many who would be very, *very* happy to be able to use ladspa plugins!
An option I haven't tried is dssi~ - you may want to look into that.
Kevin
On 2/4/07, carmen <_@ whats-your.name> wrote:
On Sat Feb 03, 2007 at 10:11:34PM -0500, David NG McCallum wrote:
Hi all,
I know that there was some activity going on at some point with using VST plugins in Pd, and I got the impression that there were several unrelated objects, or legacy objects, and I was never really sure which the "current" VST object was for Pd (plugin~? vst~?). So…
Is it currently possible to host VST objects in OS X in Pd? Which object should I be using? CVS? Is compilation straightforward?
Thanks! David
ps. My question also goes for LADSPA, does the old plugin~ work for LADSPA in os x?
both tgrill's vst~ and plugin~ should work on OSX with trivial
modifications. i suggest you just try compiling them, after collecting the requisite SDKs.
-- __ _ _ _ __ _ http://sintheta.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
--
++++ http://pocketkm.blogspot.com _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
If anyone's curious, I managed to compile dssi~ myself with only a minor headache and am now up and running with LADSPA effects in OS X intel.
After futzing with plugin~ and vst~ (which I now know doesn't work yet in os x), I'd definitely recommend that people take a look at dssi~ if they're hoping to play around with plugins.
D
On 04/02/07, Jamie Bullock jamie@postlude.co.uk wrote:
dssi~ definitely works on OS X for both LADSPA and DSSI plugins. The official release can be found at: http://www.puredata.org/Members/jb/dssi%7E/view
There is a dependency on the liblo library. You will also need the LADSPA and DSSI SDK's if you want to compile from source. Let me know if you have any problems.
Alternatively if you let me know which platform you are on (powerpc, intel), and which version of PD, I could send you a binary.
best,
Jamie
On Sun, 2007-02-04 at 10:21 -0500, David NG McCallum wrote:
Yeah, I just found out that plugin~ is included in pd-extended, but I can't seem to get it to recognise any of the ladspa plugins I have on my machine, and whenever I try to load the plugin~ help patch, my machine just crashes… sigh.
D
On 04/02/07, Kevin McCoy km.takewithyou@gmail.com wrote:
Plugin~ compiles (Hans has it doing it somehow, I couldn't get it to work) but it doesn't actually work for me, just causes Pd to crash. Also, the difference between OS X vsts and Win32 vsts is a factor here, from what I understand. So unfortunately I don't think Mac OS X is doing too well right now as for plugins, but hopefully someone who knows C will be able to fix that? There are many who would be very, *very* happy to be able to use ladspa plugins!
An option I haven't tried is dssi~ - you may want to look into that.
Kevin
On 2/4/07, carmen <_@ whats-your.name> wrote:
On Sat Feb 03, 2007 at 10:11:34PM -0500, David NG McCallum wrote:
Hi all,
I know that there was some activity going on at some point with using VST plugins in Pd, and I got the impression that there were several unrelated objects, or legacy objects, and I was never really sure which the "current" VST object was for Pd (plugin~? vst~?). So…
Is it currently possible to host VST objects in OS X in Pd? Which object should I be using? CVS? Is compilation straightforward?
Thanks! David
ps. My question also goes for LADSPA, does the old plugin~ work for LADSPA in os x?
both tgrill's vst~ and plugin~ should work on OSX with trivial
modifications. i suggest you just try compiling them, after collecting the requisite SDKs.
-- __ _ _ _ __ _ http://sintheta.org
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
--
++++ http://pocketkm.blogspot.com _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
both tgrill's vst~ and plugin~ should work on OSX with trivial
modifications. i suggest you just try compiling them, after
collecting the requisite SDKs.
I'm sorry, that's not true for vst~. It doesn't currently work for
OSX, since the windowing functions haven't been implemented yet.
greetings,
Thomas