Note: You are reading this message either because you can not see our css files, or because you do not have a standards-compliant browser (such as Mozilla Firebird (all platforms), Safari (Mac OS X), iCab (Mac OS 9), or Explorer 5 or above). You would enjoy our site a lot more if you did, but that is up to you.

AATON


» back to the web version

Why is aaton using the wave format?


Next Page: John Bowring on Aatoncode »

Since it can be read by any MAC/OS or WINTEL machine, the MS-Wave format is the standard in the PC digital-audio world.

A basic Wave file holds two headers or "chunks" only: one contains the audio data itself and the other the description of sample rate, bit rate etc., but the format specifications allow for other chunks to be added and make it tailored for professional needs.

For example, the EBU Broadcast Wave Format (BWF) adds a chunk that contains the sequence description and the date & time of recording. It will not be a daunting task for established DAW manufacturers to handle Wave files even though they may be alien to their own native audio files format.

At IBC 96 Aaton disclosed a new chunk - called FilmChunk - used for instant syncing of film and audio during the telecine session or right after it. (FilmChunk contains field timecode, field and post media identifiers, telecine timecode and many other production information).

In 1997 Aaton further extends the system with some other chunks that handle scene and take data, playback levels and phase corrections, multi-track shuffling etc. BWF chunk, FilmChunk, AatonChunks... they all contribute to make the Wave format at ease in the film/video environment, and one can expect to see more chunks to be added in the future to extend its use into audio editing and mixing applications.

Important notice: as of Sept. 97, IndawPass-recorded disks (e.g. JAZ or CDR) containing AatonChunks can directly be imported into Avid Composers where a plug-in internally converts them into OMF files; this saves hours and hours of audio-program transfer time.


Next Page: John Bowring on Aatoncode »


=end=

^ back to top