[Python-Dev] Expanding max chunk size to 4GB. (original) (raw)
Guido van Rossum gvanrossum at gmail.com
Wed Jul 6 21:17:22 CEST 2005
- Previous message: [Python-Dev] Expanding max chunk size to 4GB.
- Next message: [Python-Dev] Expanding max chunk size to 4GB.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Looks ok to me, but have you tested this with other software that reads/writes wave files?
You seem to be speculating about the format where you should be reading the reference documentation for this file format (alas, I can't help you find it -- you can Google for it as well as I can :).
Also, patches, are best submitted to SourceForge. Read python.org/dev/.
On 7/6/05, Mark Rages <markrages at gmail.com> wrote:
The RIFF chunk size (used by the Python wave library) is 2GB, because the length is read as a signed 32-bit integer.
The attached patch to chunk.py raises the limit to 4GB by using a signed integer. Is this correct? Is there a more general solution to 32-bit addressing limitation in wave files? Multiple chunks? Set the length field to zero and let software assume we only have one chunk? Regards, Mark Rages markrages at gmail.com -- You think that it is a secret, but it never has been one. - fortune cookie
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] Expanding max chunk size to 4GB.
- Next message: [Python-Dev] Expanding max chunk size to 4GB.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]