|
osdir.com mailing list archive |
|
Subject: Re: New AL 1.1 Spec and Beta Windows Implementation - msg#00049List: lib.openal.develCould we get rid of the 343.3 factor from the Doppler? Alex Thread at a glance:
Previous Message by Date: click to view message previewRe: New AL 1.1 Spec and Beta Windows ImplementationThe 1.1 draft on the site is rev 1.6 from march 2005, is there some sort of sync period before it site updates? Where are you finding the old document? Downloading off the site in the Documents section, I'm getting rev 1.9 (as documented after the TOC in the revision history). I've re-downloaded the SDK and it seems to contain the correct rev as well. Garin Next Message by Date: click to view message previewAL_MSEC_OFFSETTwo suggestions regarding AL_MSEC_OFFSET: 1. Perhaps restrict the signature of AL_MSEC_OFFSET from "i,f" to just "f"? AL_SAMPLE_OFFSET and AL_BYTE_OFFSET are of course naturally integers but AL_MSEC_OFFSET is more naturally a float (especially since sample rate is not guaranteed to be a multiple of 1000 Hz). 2. Change AL_MSEC_OFFSET to AL_SEC_OFFSET (or, even better, just call it AL_TIME_OFFSET) and have the time expressed in seconds instead of milliseconds. I think it is nicer to have a uniform time unit for everything. Also, having time expressed in seconds would be more useful than milliseconds in calculations since frequency is already expressed in Hz. Previous Message by Thread: click to view message previewRe: New AL 1.1 Spec and Beta Windows ImplementationJason Daly wrote: James Tomaschke wrote: Everything is okay, I think I tried too soon yesterday. This mornin' I grabbed it just fine, thanks! Just fyi, I had to manually clear my cache to get the latest version. --"J" Heh. Too bad browsers don't have ESP technology where they can know exactly when you want to fetch new data versus cached data on the fly. -- James Tomaschke Snr. Software Engineer InfoSemiconductor, Inc. Next Message by Thread: click to view message previewRe: New AL 1.1 Spec and Beta Windows ImplementationCould we get rid of the 343.3 factor from the Doppler? Why? If we set it to 1.0, then the only situation where the value would be appropriate by default would be in a world where the units were such that "1" is the distance that sound travels in one second. The decision is arbitrary, so we picked 343.3 for the convenience of those few potential people who may have built an AL app around Creative's 1.0 definition of Doppler. It also makes the "1.0 implementor's note" section work. Garin Loading Comments...
|
|
