This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author seebk
Recipients jcea, seebk
Date 2012-11-24.12:50:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353761443.38.0.858399026842.issue16525@psf.upfronthosting.co.za>
In-reply-to
Content
Write support is no problem, I will add this.

From reading the spec in the link you provided I think the implementation in general is OK.

Everything apart WAVE_FORMAT_PCM should have an extension size cbSize, that's right. But only WAVE_FORMAT_EXTENSIBLE sets cbSize=22.
So for read access it is not mandatory to check the value when WAVE_FORMAT_IEEE_FLOAT, but for writing files I would set this to zero.

There are several other wave formats which also use float data, but most important is WAVE_FORMAT_IEEE_FLOAT, and that can be suppoted quite easily without many changes.
History
Date User Action Args
2012-11-24 12:50:43seebksetrecipients: + seebk, jcea
2012-11-24 12:50:43seebksetmessageid: <1353761443.38.0.858399026842.issue16525@psf.upfronthosting.co.za>
2012-11-24 12:50:43seebklinkissue16525 messages
2012-11-24 12:50:42seebkcreate