This is indeed the result of « history » : some scripts are more recent or revised versions of older ones. We could possibly deprecate some of them, and possibly move them in a « unsupported » folder. What I can say on the examples you gave :
- faust2msp was for Max/MSP 4/5 versions, faust2max6 came later for Max/MSP 6/7,: it is OK for Max/MSP users to deprecate faust2msp ? - faust2vst was developed first; faust2faustvst is Albert more complete version. Albert does faust2faustvst compelety supersede faust2vst? Could faust2vst be marked unsupported ? Could/should faust2faustvst be renamed faust2vst ? (for naming consistency purpose…) - faust2w32xx are cross-complation scripts - faust2sc / faust2supercollider don’t have exactly the same purpose AFAICS ? Any Supercollider guru to comment more ? - faust2pd/faust2puredata don’t have exactly the same purpose AFAICS ? Any PureData guru to comment more ? - faust2api does not aim to replace them : faust2api is meant to produce a Faust/Audio engine with an extended API, that could be monophonic or polyphonic, which User Interface (or any control interface BTW) will be developed later on, depending of the applications specific needs. faust2api aims to give developer more control on what UI they are going to branch over the generated Faust/Audio engine. - also some kind of global environment variable to enable/disable universal binaries on macOS, would be much appreciated ==> what precise use-case do you have in mind ? Stéphane > Le 27 oct. 2017 à 14:05, Oliver Larkin via Faudiostream-devel > <faudiostream-devel@lists.sourceforge.net> a écrit : > > hello all, > > IMHO there are too many faust2xxx scripts with similar functionality and > names, that regularly break > > faust2msp / faust2max6 / faust2pd / faust2puredata / faust2vst / > faust2faustvst / faust2w32* / faust2sc / faust2supercollider > > is the plan that faust2api replaces this? > > I think what is included with the distribution should rely as little as > possible on third party tools such as macports, and, although the “pure” > based scripts are great, it's probably a bit of a big dependency, I think the > distribution should include only one script for each target, which should > handle building on different platforms and have as few dependencies as > possible other than the sdks > > e.g. faust2vst / faust2pd / faust2max / faust2sc > > best > > oli > > > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Faudiostream-devel mailing list > Faudiostream-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/faudiostream-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Faudiostream-devel mailing list Faudiostream-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
