Review before applying
Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
AI coding workspace
RIFF chunk boundary walking
RiffMeadow is a Windows AI coding client for inspecting RIFF chunk traversal. Open a project folder and discuss declared lengths, padding and unknown chunk handling with a compatible model before reviewing the proposed parser changes.
● ● ●RiffMeadow●
A concrete starting point · RIFF chunk boundary walking ×
def riff_chunks(wire):
if type(wire) is not bytes or not 12 <= len(wire) <= 1048576:
raise ValueError("riff.input")
if wire[:4] != b"RIFF" or wire[8:12] != b"WAVE" or int.from_bytes(wire[4:8], "little")+8 != len(wire):
raise ValueError("riff.header")
chunks, pos = [], 12
while pos < len(wire):
if len(chunks) == 128 or pos+8 > len(wire):
raise ValueError("riff.chunk")
tag = wire[pos:pos+4]
size = int.from_bytes(wire[pos+4:pos+8], "little")
start, stop = pos+8, pos+8+size
next_pos = stop+(size & 1)
if next_pos > len(wire):
raise ValueError("riff.truncated")
chunks.append((tag, wire[start:stop]))
pos = next_pos
return chunks
✳RIFF chunk boundary walking
✓ ChangesReview before applying ↗
Illustrative workspace
Connection
Base URL, credentials and a reachable server.
Project
Test unknown chunks and odd-length padding, rejecting truncated headers or payloads without decoding audio.
A concrete starting point
def riff_chunks(wire):
if type(wire) is not bytes or not 12 <= len(wire) <= 1048576:
raise ValueError("riff.input")
if wire[:4] != b"RIFF" or wire[8:12] != b"WAVE" or int.from_bytes(wire[4:8], "little")+8 != len(wire):
raise ValueError("riff.header")
chunks, pos = [], 12
while pos < len(wire):
if len(chunks) == 128 or pos+8 > len(wire):
raise ValueError("riff.chunk")
tag = wire[pos:pos+4]
size = int.from_bytes(wire[pos+4:pos+8], "little")
start, stop = pos+8, pos+8+size
next_pos = stop+(size & 1)
if next_pos > len(wire):
raise ValueError("riff.truncated")
chunks.append((tag, wire[start:stop]))
pos = next_pos
return chunks
Review a file import from its header to its final chunk
RiffMeadow brings file-format maintenance into a Windows coding workspace with your project source and a connected model conversation. Start from the import behavior you need to change and identify what the application does with parsed chunks. Ask the model to inspect that path before suggesting edits to an individual length calculation.
A task using riff_chunks.py could investigate a RIFF file whose odd-sized chunk needs a padding byte before the next header. Provide a small byte fixture and the expected chunk boundaries. Review the declared container length and truncation behavior together, so the proposal explains why the next read starts where it does.
After inspecting the change, run valid and truncated fixtures in your own development environment and check the import result through its consumer. Include an unfamiliar chunk tag if the application must preserve or skip it. Keep format traversal and application interpretation distinct: locating chunk bytes does not establish that their contents are suitable for every later operation.
For model assistance, configure a supported OpenAI-compatible or Anthropic endpoint and credentials when required. An abliterated AI model can be selected where available, with restrictions determined by its provider. Tools and context capacity depend on the model and server; the fixture and expected import behavior provide the concrete basis for accepting the code.
Before changing a chunked-file reader
Why does an odd chunk length need its own fixture?
Padding affects where the following header begins, so an even-length example can miss an offset defect. Provide a file with another chunk after the padded one. Check the returned boundaries and final position, not only that the first chunk was found.
Should unknown tags make an import fail?
Decide according to the format subset and application behavior you intend to support. Traversal and interpretation can use different policies. Ask the model to inspect the consumer before changing tag handling, and include an unfamiliar tag in the fixtures if it is accepted.
What does a truncated-file test need to show?
Identify which declared boundary exceeds the supplied bytes and the rejection behavior expected by the caller. Include a shortened header or payload as appropriate. Review the import path so a partial parse cannot be mistaken for a successfully loaded file by the interface.
Does successful chunk traversal prove the audio is valid?
No. It establishes only the boundary checks covered by that code and its tests. Interpreting audio metadata or sample data belongs to additional logic. Focus the review on the requested parser change and verify later stages when the application depends on them.
RiffMeadow · Updated 2026-10-25