iplug 2 vs Juce technical differences?
Hi folks, I'm trying to find some information on the technical differences between iPlug 2 and JUCE, especially for a non-plugin app. I'm working on music pedagogy tools, building prototypes in S7 Scheme hosted in Max/MSP, with the intention of building release versions in S7 + some C++ layer. My main worry about JUCE is that I trust Roli not at all given they are acquisition driven (I earn my bread in technical merger acquisition consulting, so I know rather a lot about what goes on behind the scenes in acquired/acquiring companies) So I'm leaning to iPlug 2, *but* it seems like iPlug's focus is more plugins. If any experienced developers can weigh in on concrete differences or their subjective experiences with regard to developing a stand alone app that will need a gui, scheduler, midi/io, and would possibly be build for multiple targets, that would be awesome. Much appreciated. Also, mad props to the iPlug devs if they see this. :-)
|