Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

When dealing with legacy code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

When dealing with legacy code

Subject: When dealing with legacy code
From: "R. Tyler Ballance" <email@hidden>
Date: Thu, 4 May 2006 03:33:42 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm dealing with some old legacy code that was once controlled by mpg123, and we're slowly moving it over to more modern, and mac specific APIs, but one of the problems is that the code that interfaces with this legacy code that currently is tied to mpg123 (which I want to change to Core Audio) uses raw audio that is written to stdout. (i'm not a big fan of the apporach, but who I am to judge :))

Anyways, I'm wondering if using some of the methods in AudioFile.h would be sufficient (like AudioFileWriteBytes or something similar)

Basically, we want to move this code away from mpg123, and use CoreAudio for decoding the mp3/4/wav files and write the audio data to stdout, so the rest of this code which already works on the platform will work.


Any tips? Or am I heading down the correct rabbit hole here?

Cheers,

- -R. Tyler Ballance
Lead Developer, bleep. LLC
http://www.bleepsoft.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFEWbxsqO6nEJfroRsRAqd2AJ9COwyGyJJoO9ptJ6mYtFVkwAGCHgCfV8Cd
ULL5m16PgMLFKdmlc/K8Ah0=
=qOaQ
-----END PGP SIGNATURE-----
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



Prev by Date:
Resource IDs for AU demo versions etc.

Next by Date:
(no subject)

Previous by thread:
Re: Resource IDs for AU demo versions etc.

Next by thread:
(no subject)

Index(es):

Date
Thread