Skip to content

WAVE hul Messages

David A. Russo edited this page Oct 16, 2019 · 2 revisions

WAVE-HUL-1

Message

File does not start with RIFF header

Details

The first four bytes of the file did not spell "RIFF" or "RF64". A Wave file should begin with a RIFF chunk header.

Impact

In many cases the lack of a RIFF header at the beginning of a file indicates that the file does not belong to the RIFF family of file formats and so is not actually a Wave file. If the file format has been misnamed or misidentified as a Wave file, its content could still be accessible after its true format has been correctly identified.

In other cases, it could mean the beginning of the file has been corrupted or had extra data appended to it. If extra data has been appended to the beginning, it may still be possible to recover the content of the original Wave as long as none of its content was also modified.

Remediation

Correct identification of the file format can be attempted using a format identification tool or manual binary inspection.

If extra data has been added to the beginning of the file, manual binary inspection could be used to discover the new location of the RIFF header by searching for the "RIFF" or "RF64" header ID, and then using the appropriate size field to extract the Wave's contents.

WAVE-HUL-2

Message

Form type in RIFF header is not WAVE

Details

The form type specified in the RIFF header was not "WAVE". RIFF-format files may be of types other than WAVE, such as AVI.

Impact

In most cases this signifies the file is not a Wave file but instead some other RIFF format, such as AVI or MIDI.

Remediation

Correct identification of the file format can be attempted using a format identification tool or manual binary inspection.

WAVE-HUL-3

Message

Unexpected end of file: ...

Details

The file size is less than the Wave's own reported size, indicating that some amount of data is missing from the file. This can occur when file creation is interrupted, such as during loss of power or when transferring over an unreliable network.

Impact

The impact will depend on how much of the file is missing and specifically which data was lost. If the Wave still contains a Format chunk, a Fact chunk where applicable, and at least some of a Data chunk, then some audio content may still be recoverable.

Remediation

When possible, the best option is to attempt retrieval of a complete copy of the file from the original source or an equivalent backup. When not possible, manual repair of the file can allow what data remains to still be accessible.

WAVE-HUL-4

Message

Exception reading file: ...

Details

An unexpected error occurred while trying to read the file.

Impact

The module was unable to complete file characterization or validation.

Remediation

Please report the issue and circumstances to the project for investigation.

WAVE-HUL-5

Message

No Format chunk found

Details

A Format chunk was not found in the file. All Wave files must have a Format ("fmt ") chunk, which contains the information required to decode their audio data.

Impact

Without a Format chunk software will be unable to render any audio data the file may contain.

Remediation

Needs review

WAVE-HUL-6

Message

Invalid chunk size

Details

The chunk size reported in a chunk's header exceeds the file's remaining size. The file's remaining size is calculated based on the size reported in the RIFF header, which may not be the same as the file's actual size.

Impact

Needs review

Remediation

Needs review

WAVE-HUL-7

Message

Ignored unrecognized chunk: ...

Details

A chunk with the given ID was found but ignored because the module is currently unaware of how to interpret the chunk's data.

Impact

The module is unable to inspect the contents of the chunk.

Remediation

To request support for an unrecognized chunk type, please report it to the project.

WAVE-HUL-8

Message

Duplicate chunks found for type: ...

Details

A chunk of the given type was found multiple times where it is expected only once.

Impact

If the repeated chunks contain different data then rendering software could act unpredictably depending on which chunk the software decides to use.

Remediation

Remove all but one of the repeated chunks. If the data contained in each chunk is both different and deemed valuable, copies of the file could be created differing only in which of the chunks they keep.

WAVE-HUL-9

Message

Unknown list type in Associated Data List chunk

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-10

Message

Ignored Associated Data chunk of type: ...

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-11

Message

Exif User Comment chunk is too short

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-12

Message

Incorrect length for Exif Version chunk

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-13

Message

SAXException in reading Link chunk

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-14

Message

ParserConfigurationException in reading Link chunk

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-15

Message

List chunk contains unknown type: ...

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-16

Message

Ignored Info List chunk of type: ...

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-17

Message

Ignored Associated Data chunk of type: ...

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-18

Message

Ignored Associated Data chunk of type: ...

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-19

Message

Ignored Info List chunk of type: ...

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-20

Message

Invalid format value in Peak Envelope chunk

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-21

Message

Invalid pointsPerValue in Peak Envelope chunk

Details

Needs review

Impact

Needs review

Remediation

Needs review

WAVE-HUL-22

Message

File too large to validate

Details

The RIFF size exceeded what the module can currently handle, approximately 9.22 exabytes.

Impact

Needs review

Remediation

Needs review

WAVE-HUL-23

Message

Data Size 64 chunk not in required location

Details

The first chunk following an RF64 header was not a Data Size 64 chunk. The Data Size 64 ("ds64") chunk must be the first chunk in an RF64 file because it may contain extended size values required to interpret the remainder of the file.

Impact

Needs review

Remediation

Needs review

WAVE-HUL-24

Message

No Data chunk found

Details

A Data chunk was not found in the file. All Wave files must have a Data ("data") chunk, which contains the audio data to decode.

Impact

Needs review

Remediation

Needs review

WAVE-HUL-25

Message

Data chunk appears before Format chunk

Details

A Data chunk was found before any Format chunks. Data chunks should only appear after the Format chunks that specify how to interpret them.

Impact

Needs review

Remediation

Needs review

WAVE-HUL-26

Message

Ignored unrecognized data in chunk: ...

Details

A chunk with the given ID contained more data than the module expected. The chunk may contain non-standard data or the module may have an incomplete understanding of the chunk's format.

Impact

Needs review

Remediation

Needs review

Clone this wiki locally