I'm gonna suspect (one of) the error(s) being related to the unknown error in the positional audio module shown for the 3d positioning enabled state, which needs to be queried from the db as it's not part of the API.
I guess it's either that the devs are actually doing something there in the alpha or it's an osx thing (which it ofc shouldn't).
I'm not sure if it's still small, or if it has become small as I wasn't there from the beginning.
For me, the missing link to florish is actually not the sdk, but having a plugin installer/updater in the client.
If a plugin is only a click away, that's a whole different story compared to being driven enough to go to the addons page, find, download and install for the common user. I'm suspecting one of those beautiful circles here, you know, the plugin ecosystem would need it to lift off (while still not guaranteed), while the devs don't deem it a priority as it is too small. Hence, it's not really getting anywhere. I'd even (attempt to) code that if I had hope it'd get distributed with it. Heck, even devs seem to not know the features provided by the couple of working plugins for their product on occasion, how would the end user.
The outsourcing is a great idea, with the added benefit of disabling or interaction. You know, you cannot really use a part of the API responsibly especially in the areas you mentioned due to interaction with client modules. Try naively using setClientVolumeModifier for a temporary volume change, soon after you're dealing with the clients own modules catching and saving those in the contact list etc. You wouldn't have guessed that and just wasted a lot of time.
I actually started with the test plugin and was pretty much getting nowhere, however I'm not at a senior many-digits $$ level of c++ programmer, but what plugin dev is. We gotta blame Jules open sourcing G-Key for me hanging in there ;D
Speaking of which, the sheer amount of closed-source plugins didn't help either. I gotta admit I had my doubts as I had bad experiences with that, but it actually seems to work out this time and it's really for the greater good if I'd drop of the earth or sth. Giving LUA a space at the addons page might help actually. It's fast enough for anything not dealing with audio directly, is cross-plattform per se, open source, doesn't need to be recompiled...
[Insert reduced mojo comment about the plugins/miscellaneous section still missing on the temporary download page]
Hu, let's take this as a blog entry
Reply With Quote
Originally Posted by Philosound
