Angstrom wrote:
Nathan , although the 'programming community' for such a thing is tiny , the end-user base is massive.
In the same way that most NI Reaktor users buy it for the library, the LiveAPI is a similar way of producing new fun out of existing functions.
I would expect most 'users' of LiveAPI to be simply
using things built by a small group of creators.
I can think of a lot of uses for LiveAPI and solutions which many many thousands of people would enjoy, even though they would hate to create them!
well, the future is big.
Very well put. So far I've only seen a couple uses of the API, but mostly because I think people didn't "get it", though the couple uses out there were really impressive. The tragedy is that after doing it, I got super busy with work and never got the impetus to expand on it.
There's actually another issue, since the Live API inside is somewhat limited, it kind of was discouraging for me. Since 7 has come out and there's no push whatsoever to enhance it's capabilities (even unoffically), it kind of seems like why bother?
With the emphesas on new instruments and bug fixes, while 7 is a nice update and I appreciate the work they've done (Hell, I'll even be upgrading at least the basic suite), the addition of new instruments is kinda ho-hum, I've been a Reaktor user since 2.3, so additional VST-style things are kind of valueless to me, that library provides everything and a kitchen sink as far as noise makers.
But they've decided to take the FruityLoops marketing stance, once you've got a good central editing system, you make more money by providing tools with the same UI components that plug in tightly, can't blame them at all for that..
Kinda meandering, guess who doesn't want to finish installing these cluster machines?
I think at the end of the day my time would probably be better spent writing Python code on top of a DSP that provides the option, but I like Live too much. So, tilting at windmills a bit longer.
-n
