[issue32004] Allow specifying code packing order in audioop adpcm functions

2018-01-10 Thread Nick Coghlan
Nick Coghlan added the comment: Adjusting target versions, as even though the status quo leads to mishandling some input data, the fix is a feature request to make the behaviour configurable, which restricts the change to 3.7+. -- nosy: +ncoghlan versions:

[issue32004] Allow specifying code packing order in audioop adpcm functions

2017-12-13 Thread MosesofEgypt
MosesofEgypt added the comment: Added serhiy.storchaka to nosy list as the issue has been open for over a month without response(not sure if I should have done this in the first place). -- nosy: +serhiy.storchaka versions: +Python 2.7

[issue32004] Allow specifying code packing order in audioop adpcm functions

2017-11-18 Thread MosesofEgypt
MosesofEgypt added the comment: Changed type to behavior as this is more of a bug fix than an enhancement. -- type: enhancement -> behavior ___ Python tracker

[issue32004] Allow specifying code packing order in audioop adpcm functions

2017-11-10 Thread MosesofEgypt
New submission from MosesofEgypt : --- Issue --- audioop.adpcm2lin and audioop.lin2adpcm currently treat the high 4 bits of each byte as the first code and the low 4 as the second code. In practice this is often the opposite.