WAVE file format oddness -Sound Forge - PC - MAGIX Community Forums Archive

Subject:WAVE file format oddness Posted by: mcgeedo Date:3/21/2007 1:21:40 PM Sound Forge seems to be doing something odd with the wave file format, when it embeds metadata. It seems to be adding an occassional extra byte just before the tag, e.g. it puts a 0x03 byte in front of the ICMT tag. Does anyone have a clue?
Subject:RE: WAVE file format oddness Reply by: ForumAdmin Date:3/22/2007 9:08:30 AM RIFF file chunks must be WORD (2-byte) aligned, so this is probably filler for an odd-length ASCII string, though I would have expected it to be 0x00. If you wish to detail how the files are generated and what you are doing with them, I can investigate further. J. Message last edited on3/22/2007 9:09:06 AM byForumAdmin.
Subject:RE: WAVE file format oddness Reply by: mcgeedo Date:3/30/2007 11:23:28 AM Thanks, but I finally found a complete spec that defined how this was organized. FYI, it was indeed an extra byte to byte-align an ASCII string of odd length. Sound Forge includes this byte when needed, but doesn't always use 0x00. It will start with 0x00 and increment for each tag, whether the byte is actually used or not. In one file, I saw it use 0x01 (skipping 0x00 for the first tag which didn't need a fill), then 0x03, 0x07 and 0x08. The skipped ones were, again, where they would have been used for a tag but weren't needed.

Subject:WAVE file format oddness

Posted by: mcgeedo

Date:3/21/2007 1:21:40 PM

Sound Forge seems to be doing something odd with the wave file format, when it embeds metadata. It seems to be adding an occassional extra byte just before the tag, e.g. it puts a 0x03 byte in front of the ICMT tag. Does anyone have a clue?

Subject:RE: WAVE file format oddness

Reply by: ForumAdmin

Date:3/22/2007 9:08:30 AM

RIFF file chunks must be WORD (2-byte) aligned, so this is probably filler for an odd-length ASCII string, though I would have expected it to be 0x00. If you wish to detail how the files are generated and what you are doing with them, I can investigate further.

J.

Message last edited on3/22/2007 9:09:06 AM byForumAdmin.

Subject:RE: WAVE file format oddness

Reply by: mcgeedo

Date:3/30/2007 11:23:28 AM

Thanks, but I finally found a complete spec that defined how this was organized.

FYI, it was indeed an extra byte to byte-align an ASCII string of odd length. Sound Forge includes this byte when needed, but doesn't always use 0x00. It will start with 0x00 and increment for each tag, whether the byte is actually used or not. In one file, I saw it use 0x01 (skipping 0x00 for the first tag which didn't need a fill), then 0x03, 0x07 and 0x08. The skipped ones were, again, where they would have been used for a tag but weren't needed.