On the other hand, the developer-friendly version just has Csound and
then users figure out on their own how to interface with it.
Seems the reality is somewhere in the middle.
-Chuckk
On Wed, Jul 8, 2009 at 7:02 PM, Jacob Joaquin<
jacobjoaquin@...> wrote:
>
> What if?
>
> Csound only comes in one variety, Csound Core. Csound Core is designed with
> an interface layer. Developers design plugins/add-ons to Csound Core using
> this interface layer. Users download and use Csound Core. When a
> particular user needs something more than Csound Core has to offer, they go
> to the Csound Plugin page, find what they are looking for, download, and
> install. After the installation, Csound Core automatically recognizes the
> plugin. Csound Core does not need to be compiled, it just works.
>
> Plugins include: Python, Java, VST, CsoundAC, Audio Units, TclCsound, FLTK
> Widgets, Virtual MIDI Keyboard, LADSPA, Plugin Manager (allows users to turn
> on/off installed plugins), etc. Third party software also uses this same
> interface layer to use Csound as an audio engine.
>
> To me, this is nearly the ideal situation. Is this possible. Absolutely!
> Plausible, maybe?
>
> Best,
> Jake
>
> --
> View this message in context:
http://www.nabble.com/The-%27User-Friendly%27-Alternate-Reality-of-Csound-tp24393267p24393267.html> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email
sympa@... with body "unsubscribe csound"
>
--
http://www.badmuthahubbard.comSend bugs reports to this list.
To unsubscribe, send email
sympa@... with body "unsubscribe csound"
