How to convert file BWF into wave or mp3 ?

Archived from groups: rec.audio.tech (More info?)

k34 wrote:
> I do not can convert files .bwf into wave or mp3 format. How to do?
> Thank you!

BWF files ARE wave files. There is no need to convert them.
What makes a BWF special is simply the addition of extra
meta information in the file for such information as originator
name and time and such. But the file format is exactly the same
as a wave file already.

Any well-behaved application that can read WAVE files can also
read BWF files equally well. If it can't, then the application
is defective.

As to converting them to MP3, if you have an application that
can convert WAVE toi MP3, it should alos be able to convert
BWF to MP3.

Archived from groups: rec.audio.tech (More info?)

On Thu, 19 May 2005 21:23:00 +0200, "k34" <k34@wanadoo.fr> wrote:

>I do not can convert files .bwf into wave or mp3 format. How to do?

BWF or EBU Broadcast Wavefile Format is basically encapsulated .wav or .mp2
streams.

Numerous conversion utilities exist. Check for instance Awave Audio v9.2.

Archived from groups: rec.audio.tech (More info?)

Then Windows Media Player 9 is broken, because BWF files ARE wave
files. Thus the problem lies with Microsoft. This is hardly the first
time they have not met their own "standards."

A WAVE file, at its minimum, is a RIFF file which must contain two data
containers called "chunks". One chunk is the 'fmt" chunk which contains
information about the data format type (linear PCM, MPEG, AC-3,
whatever), the sample size, sample rate, number of channels, and so
forth. The second is the "data" chunk which simply contains the
encoded audio sample data in the format described in the "fmt" chunk.

A BWF file has the standard "fmt" and "data" chunk and, in addition,
has at least one other chunk, the "bext" chunk, which, as I mentioned
earlier, contains meta information such as a 256-character description,
32-character originator, 32 character originator reference, originator
date and time, coding history and others. NONE of this information is
required for reading the file and since it is contained in a
self-describing chunk, if the consumming application doesn't know what
to do with it, it simply skips over it and moves to the next chunk it
can read.

The presence of this chunk is the ONLY thing that makes a WAVE file
into a BWF file. If, in fact, what you have IS a real BWF file, and
Windows Media PLayer can't handle it, then shame on Microsoft for
failing to make what THEY define as a "well behaved RIFF application."

It's also possible that the file is corrupted or is not, as claimed, a
BWF file.