Broadcast Wave Files -Sound Forge - Scripting - MAGIX Community Forums Archive

Subject:Broadcast Wave Files Posted by: kb420 Date:6/27/2006 7:52:48 PM Is it possible to export a .wav file as a Broadcast Wave File in Sound Forge?
Subject:RE: Broadcast Wave Files Reply by: StyleSupportMIDI Date:6/28/2006 5:32:43 PM I dont see broadcast. BUT From "Save As" choose "Wave(microsoft)(*wav)" from the drop-down. This is the same as Broadcast. Hope this helps. Gary Michael Reed StyleSupportMIDI
Subject:RE: Broadcast Wave Files Reply by: ForumAdmin Date:6/30/2006 7:50:48 AM Well, to be precise, they are not exactly the same. Broadcast Wave is a .wav with specific additional metadata (the "bext" chunk). Data may be MPEG Layer 2, but, like regular .wav files, is typically uncompressed (and usually 16-bit, 48 kHz). As for exporting one from Sound Forge, the short answer is no. The long answer is that Sound Forge does not currently expose the Broadcast Wave metadata, though it will preserve it should you choose to edit an existing file that contains it. A proficient script author with some insight into the RIFF structure and the contents of the bext chunk could, perhaps, read or write the necessary metadata by operating directly on a file, but it really has nothing to do with the Forge scripting API. Just might be a convenient place to try it. J. Message last edited on6/30/2006 8:00:19 AM byForumAdmin.
Subject:RE: Broadcast Wave Files Reply by: kb420 Date:6/30/2006 4:04:52 PM "The long answer is that Sound Forge does not currently expose the Broadcast Wave metadata, though it will preserve it should you choose to edit an existing file that contains it." Sonar does export in Broadcast Wave, so from what you are saying, I can export from Sonar, and edit in Sound Forge, save the edited data, and it will remain a Broadcast Wave file. Am I correct? I recently ran into someone who has access to a full blown Pro Tools HD studio, and he said that it would be best if I took each of my tracks in Sonar and converted them into Broadcast Wave files so that he could open them in PT to mix. I would like to be able to make the sound the best that I can in Sound Forge before I do that. If what you say is true, then I shouldn't have a problem.
Subject:RE: Broadcast Wave Files Reply by: ForumAdmin Date:7/5/2006 7:45:03 AM Yes, with two small caveats. 1) There's currently a bug that may delete unrecognized (e.g. bext) data depending on where it occurs in the file and on the complexity of the editing. But there is a simple workaround to avoid this case described in this post. 2) if you adjust the length at the beginning of the file, the information in the bext chunk (e.g. the start time) may differ from what is intended. This is more of an issue if you are exporting some kind of edl project with individual rendered events. If you are rendering entire tracks, this shouldn't be much of a concern. J.

Subject:Broadcast Wave Files

Posted by: kb420

Date:6/27/2006 7:52:48 PM

Is it possible to export a .wav file as a Broadcast Wave File in Sound Forge?

Subject:RE: Broadcast Wave Files

Date:6/28/2006 5:32:43 PM

I dont see broadcast. BUT
From "Save As" choose "Wave(microsoft)(*wav)" from the drop-down.
This is the same as Broadcast.
Hope this helps.
Gary Michael Reed
StyleSupportMIDI

Subject:RE: Broadcast Wave Files

Reply by: ForumAdmin

Date:6/30/2006 7:50:48 AM

Well, to be precise, they are not exactly the same. Broadcast Wave is a .wav with specific additional metadata (the "bext" chunk). Data may be MPEG Layer 2, but, like regular .wav files, is typically uncompressed (and usually 16-bit, 48 kHz).

As for exporting one from Sound Forge, the short answer is no.

The long answer is that Sound Forge does not currently expose the Broadcast Wave metadata, though it will preserve it should you choose to edit an existing file that contains it.

A proficient script author with some insight into the RIFF structure and the contents of the bext chunk could, perhaps, read or write the necessary metadata by operating directly on a file, but it really has nothing to do with the Forge scripting API. Just might be a convenient place to try it.

J.

Message last edited on6/30/2006 8:00:19 AM byForumAdmin.

Subject:RE: Broadcast Wave Files

Reply by: kb420

Date:6/30/2006 4:04:52 PM

"The long answer is that Sound Forge does not currently expose the Broadcast Wave metadata, though it will preserve it should you choose to edit an existing file that contains it."

Sonar does export in Broadcast Wave, so from what you are saying, I can export from Sonar, and edit in Sound Forge, save the edited data, and it will remain a Broadcast Wave file.

Am I correct?

I recently ran into someone who has access to a full blown Pro Tools HD studio, and he said that it would be best if I took each of my tracks in Sonar and converted them into Broadcast Wave files so that he could open them in PT to mix. I would like to be able to make the sound the best that I can in Sound Forge before I do that. If what you say is true, then I shouldn't have a problem.

Subject:RE: Broadcast Wave Files

Reply by: ForumAdmin

Date:7/5/2006 7:45:03 AM

Yes, with two small caveats.

1) There's currently a bug that may delete unrecognized (e.g. bext) data depending on where it occurs in the file and on the complexity of the editing. But there is a simple workaround to avoid this case described in this post.

2) if you adjust the length at the beginning of the file, the information in the bext chunk (e.g. the start time) may differ from what is intended. This is more of an issue if you are exporting some kind of edl project with individual rendered events. If you are rendering entire tracks, this shouldn't be much of a concern.

J.