| Re: [AD] Audio code and endian-ness |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Elias,
There is the CoreAudio driver and the SoundManager driver. CoreAudio
was only added in OSX 10.2, before that, you had to use SM which is
the Carbon version of the MacOS classic SoundManager.
I think it could be deprecated in the next release; I doubt anyone has
OSX 10.1 now.
The same applies to the QuickTime midi driver; it's not needed since
CoreAudio does midi, too.
Chris,
Thanks, I'll do it.
Pete
On 6/9/06, Chris <chris.kcat@xxxxxxxxxx> wrote:
On Friday 09 June 2006 10:00, Peter Hull wrote:
> However this only makes sense if there's some other endian-switching
> code elsewhere, that was active in the PPC port and is not active in
> the i386 port. But, I can't find it.
The only place I could think of would be the sample loading code. Allegro
deals with native endianness (ie. with 8/16 bit integer types) and passes it
off to the driver as such. On PPC, this would mean it gets big-endian data,
and on i386 it gets little-endian data. Just setting or clearing that flag
depending on the CPU arch should be enough as far as Allegro itself is
concerned.
--
https://lists.sourceforge.net/lists/listinfo/alleg-developers