chunk.py can't handle >2GB chunks

[wingel]

BPO	1373643
Nosy	@birkenfeld
Files	chunk.diff: Patch to chunk.py

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2006-02-18.21:11:15.000>
created_at = <Date 2005-12-05.16:42:45.000>
labels = ['library']
title = "chunk.py can't handle >2GB chunks"
updated_at = <Date 2006-02-18.21:11:15.000>
user = 'https://bugs.python.org/wingel'

bugs.python.org fields:

activity = <Date 2006-02-18.21:11:15.000>
actor = 'georg.brandl'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2005-12-05.16:42:45.000>
creator = 'wingel'
dependencies = []
files = ['6906']
hgrepos = []
issue_num = 1373643
keywords = ['patch']
message_count = 2.0
messages = ['49167', '49168']
nosy_count = 2.0
nosy_names = ['georg.brandl', 'wingel']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1373643'
versions = ['Python 2.4']

[wingel]

chunk.py unpacks the chunk size as a signed long 'l'
not as unsigned long 'L' which is what it ought to do
according to the WAV specs. Additionally, since field
contains a byte count it makes no sense for it to be
signed.

What I want to do is to read a wave file generated by
madplay on the fly. Since madplay doesn't know the
size of the WAVE chunk when it is written, it sets the
chunk size to 0xffff which is inpreted as -1 by
chunk.py . Changing chunk.py to read it as an unsigned
long makes this work.

Example code:

import wave
import os

f = os.popen('madplay -o wave:- foo.mp3')
wf = wave.open(f, 'rb')

Without a patch, this will raise an error:

wave.Error: not a WAVE file

[birkenfeld]

Logged In: YES
user_id=1188172

Thanks for the report. Committed revisions 42464, 42465 (2.4).