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-explainin
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 "
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
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 prob
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
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
