PC or MAC
-
- KVRian
- 886 posts since 2 Jun, 2005 from Hawaii
-
- KVRAF
- 12615 posts since 7 Dec, 2004
if you're questioning as to which side you should get into when coding for vst, the answer is definitely windows. windows plugins work on linux already, and with recent advancements in wine running on intel mac, they soon will run on mac as well.
unless you already own a mac or a very fast pc and a copy of osx, it will cost you much more to develop on the mac platform than pc, while you'll have a smaller user base and less sales on mac. it just doesnt make sense to start development of any new software on the Gx mac systems right now. assuming worst case, windows vst plugins never run on x86 osx, it will not be too difficult to port them anyway.
i've been looking into providing a version of xhip for mac. there is no way to create an automated system to propagate source tree changes to binaries on all platforms at once. i would need completely seperate build enviroments, seperate compiles, seperate libraries and i would have to do everything manually. not only that, but i would have to own a mac and osx or alternatively own a copy of osx and a very fast pc to use an emulator with, and own a commercial compiler on the platform.
minimum cost for me, and if i'm wrong here please god somebody tell me about an easier way, is around $1500 USD (including tax) for a mac which seems to include what i would need.
based upon that, my current position regarding a mac port is that apple can get stuffed.
all the tools i require, including the os (i can successfully compile windows vst plugins using mingw on linux) are free for me using a pc and coding for vst on windows. since the popularity of mingw has forced microsoft to release a free version of their compiler for windows, you can alternatively use that if you like.
unless you already own a mac or a very fast pc and a copy of osx, it will cost you much more to develop on the mac platform than pc, while you'll have a smaller user base and less sales on mac. it just doesnt make sense to start development of any new software on the Gx mac systems right now. assuming worst case, windows vst plugins never run on x86 osx, it will not be too difficult to port them anyway.
i've been looking into providing a version of xhip for mac. there is no way to create an automated system to propagate source tree changes to binaries on all platforms at once. i would need completely seperate build enviroments, seperate compiles, seperate libraries and i would have to do everything manually. not only that, but i would have to own a mac and osx or alternatively own a copy of osx and a very fast pc to use an emulator with, and own a commercial compiler on the platform.
minimum cost for me, and if i'm wrong here please god somebody tell me about an easier way, is around $1500 USD (including tax) for a mac which seems to include what i would need.
based upon that, my current position regarding a mac port is that apple can get stuffed.
all the tools i require, including the os (i can successfully compile windows vst plugins using mingw on linux) are free for me using a pc and coding for vst on windows. since the popularity of mingw has forced microsoft to release a free version of their compiler for windows, you can alternatively use that if you like.
Last edited by aciddose on Wed Sep 06, 2006 5:29 am, edited 1 time in total.
-
- KVRer
- 11 posts since 17 Nov, 2005 from Berkeley/Hollywood
mac
