On January 2, 2013 09:00:49 AM Geoff Beasley wrote: > Tim could you just clarify what this really means? I'm currently re > building using the vstsdk2.3 ( should document 2.3 not 2.4 btw - 2.4 > won't work)
Yes true, only the 2.3 SDK works. I don't have the 2.4 SDK. But there is currently no benefit to using it until more advanced features are added, so you might want to just stick with the built-in Vestige header which should work just fine. I hope the cmake options for choosing the type of header and its location weren't too confusing, it's the best I could do given two types of headers. Be sure to examine them carefully. > - will muse host windows vst's or linux native vst's using > thisa framework? Only the Linux native VSTs. The upshot is that we could leverage this whole native code later to support Win VSTs. I think it was good for me to start with the native VSTs and get it right before proceeding. What I want to do is take Chris's DSSI-VST code and rip out the whole DSSI part and use the rest in MusE. Or modify FST for our use. With DSSI-VST we are seeing Win VSTs through the 'eyes' of DSSI, which presents some severe limitations and challenges. Far better to bypass the whole DSSI part and use the rest of it. Sort of, DSSI-VST without the DSSI part, replaced with a more MusE-friendly layer. Tim. > > g > ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
