Source code for Audio Tools v0.8

Generally we're not updating source code anymore, simply because it takes a large amount of time to clean up/prepare for release, and 99% of our users don't care at all if we provide it or not. I'm not sure if the "latest" audiotools source is even possible for us, because we've got a huge number of changes internally that we're working on for the next release (and I'm terrible about actually branching the svn repository for formal releases of non-commercial software).

I would love to see the source code for Audio Tools as well! I have found any and all CoreAudio example code to be insanely cryptic... oooh, and MidiTools as well... I've got a strong need for Program Control message support and I figured I could just add it myself. :)

you probably don't want to learn CA from AudioTools :) CA's complicated because it's a rather powerful but necessarily low-level API. Most of the audiotools CA code hasn't changed, we've just modified how we actually handle the data we receive.

Regarding midi stuff -- I think you mentioned that before? (holy cow I'm so far behind) -- adding PC support wouldn't be too difficult, I'm sure we'll get around to it when we have a moment to revisit midi (midi tools is in dire need of some SL love first..)

just to clarify :

Midi tools DOES NOT work under SL ?

I have no idea -- I have no midi devices to do a useful test, and I've not heard either way. so it's essentially "use at your own risk". I think it's compiled for 64bit, so it should load on SL without needing to drop to 32bit mode, but that's about all that I know.

yeah the midi got changed its called core midi as well as video is core video now, but the interesting thing is that core video supports rendering to opengl context like qc so you can add glsl shaders to quads. you might want to have a look at the spatial audio developer examples for snow leopard they are pretty cool. qc has 3d spatial audio player from openAL but its lacking all the reverbs and stuff that the application build has but it might be cool to throw in some of that to a qc plugin.

as far as analyzing the spectrum it appears apple still has a inherent resonant frequency at bands 14 and 15, kind of weird all ghost in the machine. i like the safe audio patch haven't seen if that works yet. i'm in gl es land today almost got a osc controller built in cocoa, im negating tuio because it doesn't work in sl so im parsing out multi-touch and accelerometer osc. i was using open frameworks which is way cool c++ on the iphone but the frameworks addons are limited in comparison to apples examples so im back to cocoa touch. i spent 3 hours trying to figure out why multi touch events where not woking in my view when i realized you have to be using a opengl es renderer even though they have an option to turn on mutli touch for window and regular views. man if only qc had a build for the iphone. the context look entirely similar as that of a consumer patch. i bet in the future it will when the iphone is a as fast as the computers of today. although it seems i can use fragment and vertex shaders in gl es not sure if that is just for the new phone or not.

i often wondered the same question my self as kineme being an open source community why the plugin sources where not to available but i don't care.

CoreMIDI and CoreVideo existed on Leopard (and on Tiger, for that matter) -- current MIDITools uses CoreMIDI, and QuartzBuilder uses CoreVideo today.

The spatial audio thing is powered by OpenAL -- I know next to nothing about openal, but I personally see CoreAudio as the way to go on this (I'll have to check out OpenAL in more detail to know for sure though) -- OpenAL also exists on Leopard. So we're batting 0/3 on "new" technologies thus far ;)

Safe* should work (as long as they're 64bit compiled), since the safe/unsafe mechanism is the same on Snow Leopard. We're planning on obsoleting all those plugins, and just making KinemeCore handle Safe/unsafe trickery though, for convenience/flexibility.

As for opensource/no source -- like I mentioned above, it's a lot of effort to package it up nicely (and make sure it builds properly -- we use esoteric build settings that break non-bleeding-edge Xcode installations; many of our internal testers had severe problems building/testing our software before we forced them all to upgrade), and the last thing we want to deal with is a zillion questions on why we did things various ways. Not that it's bad to ask, etc, it's just that we don't have a lot of time to deal with that. :/ And once apple released the official API, we somewhat want to encourage people to use that instead (as it's supported, whereas the skanky sdk is not), to minimize problems in the future. It's a razor-thin line we get to walk....

mmm.... i'll have to check this (just ordered a new SL computer) and PM you if anything goes wrong

thanks chris it just dawned on me that i was building the tuio plugin for 32bit not 64bit thats why it wasn't working in snow leopard great thanks you.

I'm not sure if that new audio patch really does anything with the y/z ports on the renderer... I asked about this and was told that they don't do anything, but I haven't tested.

The pitch shift is BADASS. That is one thing I forgot to mention in my summary of QC4 stuff.

Okay, going back to the beginning of the discussion, I chose to ask about Audio Tools, because we wanted to request feature in Audio Input, namely the possibility of tuning the gain; but I rather wanted to play with it myself first rather than posting in requests, as a good chance to learn about and practice the framework.

I see that Kineme is offering a lot of pretty useful tools, and for future developments it would be really useful to understand how these ones are done.

What is your suggestion, should we just play with the older releases? I think it would be very cool at least to make some major releases public.