Yeah.  It's going to be a long time between releases but that's because 0.9 is going to drop a bunch of things.

6 months, haha no.  More like 6 weeks but probably less than that, especially since the mac mini turned up 2 weeks early.

Thanx a lot for making this audio library cross platform. The more platforms, the better. I think you've hit about all the possible computer platforms for now haha

@458
Yeah.  Part of the 0.9 release is pushing the sponsorship thing harder.  There's good points and bad points at which to push that as the author and "Hi I haven't done anything at all public-facing in a month or two" is not it.

@457
I mean I think it probably also works on FreeBSD, so there.  Haven't tried it and not going to, but Miniaudio supports it and the changes for mac turned out to be less than 10 lines, all places where I was violating the C++ standard and none specific to mac.  The most expensive less than 10 lines I've ever coded for a personal project being as I bought a computer for it.  But still.

Yeah.  miniaudio of all things might slowly become a competitor, but it's public domain so I can and totally will just grab and copy/paste his code if it comes to it, lol.

I'm not actually doing downtime, but there's nothing left in terms of issues that I don't know how to handle, save maybe surround sound which might require buying more hardware.  But 0.9 is supposed to be the last release with an API breakage before 1.0, so instead of releasing early and often I'm going nuts doing that.  But the upshot is that short of watching GitHub's commit logs and stuff it looks like nothing is going on.

Ok, sadly not the 0.9 announcement.  Instead it's the "yes 0.9 will have libsndfile support" announcement, so everyone waiting for ogg can stop waiting, provided that you're willing to distribute that dll and enable it.  We aren't going to get better than this until dr_vorbis is stable, so the answer to anyone who asks for an alternative to distributing libsndfile is "sorry, but no".

That sounds like you don't have HRTF enabled and you also aren't using the library in a realistic fashion.  I'm going to guess that you're trying to get Source3D to work for something that's not a first person viewpoint.  You probably want to switch to PannedSource and drive it yourself with panning_scalar if that's the case.

Otherwise no, therere's nothing you can do, and to the best of my knowledge there is nothing you can do in other libraries either.  This is a simulation of the real world, and if you move the sound through the center of the listener's head it's going to break down for that reason.

I mean yeah, but that starts at "how to use trigonometry and vectors properly" which is the problem.  At the end of the day Source3D is only useful for first-person games.  And either you know how to do that right already or you don't.  getting the people who don't to the point of being able to do so is probably a lot of work.

Yeah, so firstly if you're not using HRTF in first person you're missing out by a lot.  It matters less for non-first-person stuff.

Secondly, I bet your first person game modeled players as a point and still let the sound go through the head.  If not maybe there's more of a problem than I think.  There's improvements that I want to make for things close to the head, though.

And yeah, things that aren't first person are on their own.  I can't make a one size fits all model for sidescrollers or whatever else.  Maybe in the future if everyone converges on one specific thing, but not now.  Encoding something we might all hate in SYnthizer isn't something I would want to do.

Yes, I know, I know.  I've been silent for a while.  but as I said on Twitter it's code complete.  I'm rewriting the manual now.  Should only be a week or two depending on how this weekend goes--if I'm not busy and the record heatwave isn't boiling my apartment then maybe I'll get that done.

it will come with support for loading and streaming from anything you might want to load or stream from, at least to the extent possible if you're not going to write your own audio library with custom internals.  The story around being able to mathematically generate samples or whatever and throw them in post-decoding is still weak but no one here has ever asked me for that except maybe one person.

Got a 3.5 day weekend and most of the new manual is done so hopefully it will also be relatively quick.