Hi all,
For a music production I had to compile vst~ for OSX in Flext. I noticed that there is already code in "vsthost.cpp" that seems to try to load vst plug-ins in the form of "carbon" code resources (search for FSPathMakeFSSpec) but I found no compiled vst~ in Pd-extended, nor does anyone on the list seem to think this exists.
I adapted the code so that it loads macho vst plug-ins. It seems to work, except that, in the help patch, when I try to open the editing window nothing comes up. I suspect this has to do with something other than vst~ proper but haven't looked into it since I don't know how the editor stuff is supposed to work.
Before I go on and submit this as a formal patch, I'd like to know if anyone knows whether the carbon code should be kept around (do there still exist vst plugins in carbon taht are worth trying to support?) and whether I should look harder to figure out why the editing window in the help file doesn't open. For anyone curious, grab the patch (vst-OSX.patch) and/or the cmopiled extern (vst~.pd_darwin) from http://crca.ucsd.edu/~msp/tmp/ .
cheers Miller
Am 07.07.2008 um 22:17 schrieb Miller Puckette:
Hi all,
For a music production I had to compile vst~ for OSX in Flext. I noticed that there is already code in "vsthost.cpp" that seems to try to load vst plug-ins in the form of "carbon" code resources (search for FSPathMakeFSSpec) but I found no compiled vst~ in Pd-extended, nor does anyone on the list seem to think this exists.
Thats absolutely right....
And very good to hear
I adapted the code so that it loads macho vst plug-ins. It seems to work, except that, in the help patch, when I try to open the editing window nothing comes up. I suspect this has to do with something other than vst~ proper but haven't looked into it since I don't know how the editor stuff is supposed to work.
Before I go on and submit this as a formal patch, I'd like to know if anyone knows whether the carbon code should be kept around (do there still exist vst plugins in carbon taht are worth trying to support?) and whether I should look harder to figure out why the editing window in the help file doesn't open. For anyone curious, grab the patch (vst-OSX.patch) and/or the cmopiled extern (vst~.pd_darwin) from http://crca.ucsd.edu/~msp/tmp/ .
Is it Intel Mac - compatible ???
best luigi
cheers Miller
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
---------------------------------------<
Luigi Rensinghoff luigi.rensinghoff@freenet.de skype:gigischinke ichat:gigicarlo
Yep, I've only tried it in intel mac so far. On Tue, Jul 08, 2008 at 10:09:47AM +0200, Luigi Rensinghoff wrote:
Am 07.07.2008 um 22:17 schrieb Miller Puckette:
Hi all,
For a music production I had to compile vst~ for OSX in Flext. I noticed that there is already code in "vsthost.cpp" that seems to try to load vst plug-ins in the form of "carbon" code resources (search for FSPathMakeFSSpec) but I found no compiled vst~ in Pd-extended, nor does anyone on the list seem to think this exists.
Thats absolutely right....
And very good to hear
I adapted the code so that it loads macho vst plug-ins. It seems to work, except that, in the help patch, when I try to open the editing window nothing comes up. I suspect this has to do with something other than vst~ proper but haven't looked into it since I don't know how the editor stuff is supposed to work.
Before I go on and submit this as a formal patch, I'd like to know if anyone knows whether the carbon code should be kept around (do there still exist vst plugins in carbon taht are worth trying to support?) and whether I should look harder to figure out why the editing window in the help file doesn't open. For anyone curious, grab the patch (vst-OSX.patch) and/or the cmopiled extern (vst~.pd_darwin) from http://crca.ucsd.edu/~msp/tmp/ .
Is it Intel Mac - compatible ???
best luigi
cheers Miller
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
---------------------------------------<
Luigi Rensinghoff luigi.rensinghoff@freenet.de skype:gigischinke ichat:gigicarlo
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Hi Miller, many thanks for the contribution - I think that a lot of people will be happy about it. I can't say if it makes sense to "keep" compatibility with Carbon plugins - considering that they have never really worked with vst~. Also when i was working on the Mac code of vst~ the main problem was the editor window - i can't really remember but there must still be some code missing to actually handle user interaction (in editormac.hpp). all the best, Thomas
Am 07.07.2008 um 22:17 schrieb Miller Puckette:
Hi all,
For a music production I had to compile vst~ for OSX in Flext. I noticed that there is already code in "vsthost.cpp" that seems to try to load vst plug-ins in the form of "carbon" code resources (search for FSPathMakeFSSpec) but I found no compiled vst~ in Pd-extended, nor does anyone on the list seem to think this exists.
I adapted the code so that it loads macho vst plug-ins. It seems to work, except that, in the help patch, when I try to open the editing window nothing comes up. I suspect this has to do with something other than vst~ proper but haven't looked into it since I don't know how the editor stuff is supposed to work.
Before I go on and submit this as a formal patch, I'd like to know if anyone knows whether the carbon code should be kept around (do there still exist vst plugins in carbon taht are worth trying to support?) and whether I should look harder to figure out why the editing window in the help file doesn't open. For anyone curious, grab the patch (vst-OSX.patch) and/or the cmopiled extern (vst~.pd_darwin) from http://crca.ucsd.edu/~msp/tmp/ .
cheers Miller
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Thomas Grill http://grrrr.org
OK, I looked at the editor window stuff and it looks like it needs to be filled out as an interface to the OSX window creation and management code... also, I presume somewhere, someone is drawing stuff on the window, but I couldn't figure out where and how that should happen. I think my next step should be to look at vst~ on a windows machine and try to trace function calls around to see what's happening... yuck!
Miller
On Tue, Jul 08, 2008 at 11:15:39AM +0200, Thomas Grill wrote:
Hi Miller, many thanks for the contribution - I think that a lot of people will be happy about it. I can't say if it makes sense to "keep" compatibility with Carbon plugins - considering that they have never really worked with vst~. Also when i was working on the Mac code of vst~ the main problem was the editor window - i can't really remember but there must still be some code missing to actually handle user interaction (in editormac.hpp). all the best, Thomas
Am 07.07.2008 um 22:17 schrieb Miller Puckette:
Hi all,
For a music production I had to compile vst~ for OSX in Flext. I noticed that there is already code in "vsthost.cpp" that seems to try to load vst plug-ins in the form of "carbon" code resources (search for FSPathMakeFSSpec) but I found no compiled vst~ in Pd-extended, nor does anyone on the list seem to think this exists.
I adapted the code so that it loads macho vst plug-ins. It seems to work, except that, in the help patch, when I try to open the editing window nothing comes up. I suspect this has to do with something other than vst~ proper but haven't looked into it since I don't know how the editor stuff is supposed to work.
Before I go on and submit this as a formal patch, I'd like to know if anyone knows whether the carbon code should be kept around (do there still exist vst plugins in carbon taht are worth trying to support?) and whether I should look harder to figure out why the editing window in the help file doesn't open. For anyone curious, grab the patch (vst-OSX.patch) and/or the cmopiled extern (vst~.pd_darwin) from http://crca.ucsd.edu/~msp/tmp/ .
cheers Miller
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Thomas Grill http://grrrr.org
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Am 08.07.2008 um 22:20 schrieb Miller Puckette:
I think my next step should be to look at vst~ on a windows machine and try to trace function calls around to see what's happening...
You could also compare with the windows version of the code (editor_win.hpp) which is pretty self-explaining. I'm not sure if the design of the editor class works well with the MacOS way of things though... all the best, Thomas
-
Luigi Rensinghoff -
Miller Puckette -
Thomas Grill