-
Notifications
You must be signed in to change notification settings - Fork 79
WAVE hul Messages
File does not start with RIFF header
The first four bytes of the file did not spell "RIFF" or "RF64". A Wave file should begin with a RIFF chunk header.
- Type: ErrorMessage
- Source location: WaveModule.java L348
- Examples: Needed
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.
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.
Form type in RIFF header is not WAVE
The form type specified in the RIFF header was not "WAVE". RIFF-format files may be of types other than WAVE, such as AVI.
- Type: ErrorMessage
- Source location: WaveModule.java L364
- Examples: Needed
In most cases this signifies the file is not a Wave file but instead some other RIFF format, such as AVI or MIDI.
Correct identification of the file format can be attempted using a format identification tool or manual binary inspection.
Unexpected end of file: ...
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.
- Type: ErrorMessage
- Source location: WaveModule.java L414
- Examples: 1, 2
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.
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.
Exception reading file: ...
An unexpected error occurred while trying to read the file.
- Type: ErrorMessage
- Source location: WaveModule.java L420
- Examples: Needed
The module was unable to complete file characterization or validation.
Please report the issue and circumstances to the project for investigation.
No Format chunk found
A Format chunk was not found in the file. All Wave files must have a Format ("fmt ") chunk containing the information required to decode their audio data.
- Type: ErrorMessage
- Source location: WaveModule.java L452
- Examples: 1
Without a Format chunk software will be unable to render any audio data the file may contain, resulting in errors attempting to open or render the file in playback software.
This error may also appear if the module aborts processing a file due to format or module errors before it is able to reach the file's Format chunk.
Needs review
Invalid chunk size
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.
- Type: ErrorMessage
- Source location: WaveModule.java L759
- Examples: Needed
Needs review
Needs review
Ignored unrecognized chunk: ...
A chunk with the given ID was found but ignored because the module is currently unaware of how to interpret the chunk's data.
- Type: InfoMessage
- Source location: WaveModule.java L849
- Examples: Needed
The module is unable to inspect the contents of the chunk.
To request support for an unrecognized chunk type, please report it to the project.
Duplicate chunks found for type: ...
A chunk of the given type was found multiple times where it is expected only once.
- Type: ErrorMessage
- Source location: WaveModule.java L896
- Examples: 1
If the repeated chunks contain different data then rendering software could act unpredictably depending on which chunk the software decides to use.
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. To avoid invalidating offset values stored inside certain chunks, repeated chunks can be safely removed by replacing them with Junk ("JUNK") chunks of the same size.
Unknown list type in Associated Data List chunk
A non-standard list ("list") chunk with the given type was found but ignored because the module is currently unaware of how to interpret the chunk's data.
- Type: ErrorMessage
- Source location: AssocDataListChunk.java L58
- Examples: Needed
Needs review
Needs review
Ignored Associated Data chunk of type: ...
A chunk with the given ID in a non-standard Associated Data List ("list") was found but ignored because the module is currently unaware of how to interpret the chunk's data.
- Type: InfoMessage
- Source location: AssocDataListChunk.java L86
- Examples: Needed
Needs review
Needs review
Exif User Comment chunk is too short
Needs review
- Type: ErrorMessage
- Source location: ExifUserCommentChunk.java L56
- Examples: Needed
Needs review
Needs review
Incorrect length for Exif Version chunk
Needs review
- Type: ErrorMessage
- Source location: ExifVersionChunk.java L47
- Examples: Needed
Needs review
Needs review
SAXException in reading Link chunk
Needs review
- Type: ErrorMessage
- Source location: LinkChunk.java L96
- Examples: Needed
Needs review
Needs review
ParserConfigurationException in reading Link chunk
Needs review
- Type: ErrorMessage
- Source location: LinkChunk.java L102
- Examples: Needed
Needs review
Needs review
List chunk contains unknown type: ...
A list chunk with the given type was found but ignored because the module is currently unaware of how to interpret the chunk's data. List ("LIST") chunks consist of a type field followed by a series of chunks. The list's type dictates how the chunks contained in the list should be interpreted.
- Type: ErrorMessage
- Source location: ListInfoChunk.java L67
- Examples: Needed
The module is unable to inspect the contents of the list chunk.
To request support for an unrecognized list type, please report it to the project.
Ignored Info List chunk of type: ...
See WAVE-HUL-19.
- Type: InfoMessage
- Source location: ListInfoChunk.java L95
Ignored Associated Data chunk of type: ...
An Exif List chunk with the given ID was found but ignored because the module is currently unaware of how to interpret the chunk's data.
- Type: InfoMessage
- Source location: ListInfoChunk.java L148
- Examples: Needed
The module is unable to inspect the contents of the chunk.
To request support for an unrecognized chunk type, please report it to the project.
Ignored Associated Data chunk of type: ...
An Associated Data List chunk with the given ID was found but ignored because the module is currently unaware of how to interpret the chunk's data.
- Type: InfoMessage
- Source location: ListInfoChunk.java L194
- Examples: Needed
The module is unable to inspect the contents of the chunk.
To request support for an unrecognized chunk type, please report it to the project.
Ignored Info List chunk of type: ...
An Info List chunk with the given ID was found but ignored because the module is currently unaware of how to interpret the chunk's data.
- Type: InfoMessage
- Source location: ListInfoTextChunk.java L145
- Examples: Needed
The module is unable to inspect the contents of the chunk.
To request support for an unrecognized chunk type, please report it to the project.
Invalid format value in Peak Envelope chunk
Needs review
- Type: ErrorMessage
- Source location: PeakEnvelopeChunk.java L78
- Examples: Needed
Needs review
Needs review
Invalid pointsPerValue in Peak Envelope chunk
Needs review
- Type: ErrorMessage
- Source location: PeakEnvelopeChunk.java L89
- Examples: Needed
Needs review
Needs review
File too large to validate
The RIFF size exceeded what the module can currently handle, approximately 9.22 exabytes.
- Type: InfoMessage
- Source location: WaveModule.java L383
- Examples: Needed
The module is unable to process the file.
Consider switching to FLAC?
Data Size 64 chunk not in required location
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.
- Type: ErrorMessage
- Source location: WaveModule.java L395
- Examples: 1
Needs review
Needs review
No Data chunk found
A Data chunk was not found in the file. All Wave files must have a Data ("data") chunk containing the audio data to decode.
- Type: ErrorMessage
- Source location: WaveModule.java L457
- Examples: 1
Without a discoverable Data chunk there is no audio data to render, often resulting in errors attempting to open or render the file in playback software.
This error may also appear if the module aborts processing a file due to format or module errors before it is able to reach the file's Data chunk.
Needs review
Data chunk appears before Format chunk
A Data chunk was found before a Format chunk. Data chunks should only appear after the Format chunk that specifies how to interpret them.
- Type: ErrorMessage
- Source location: WaveModule.java L771
- Examples: 1
Software expecting the Format and Data chunks to be in the correct order can fail to open or render the file.
If both Format and Data chunks still exist in the file, they could be reordered manually, with some effort, into the correct order. Care would need to be taken to ensure any offset information stored in other chunks is not invalidated by the move. This may be impossible if there exist proprietary or unknown chunks in the file whose functions also need to be preserved but which can't be verified or updated due to a lack of knowledge about their content or format. For that reason this option may only be feasible for relatively simple Wave files.
Ignored unrecognized data in chunk: ...
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.
- Type: InfoMessage
- Source location: WaveModule.java L871
- Examples: Needed
The module is unable to process the unrecognized data.
The file could be submitted to the project for investigation into supporting the unrecognized data.