Opened 13 years ago
Closed 13 years ago
#32828 closed defect (worksforme)
SOX Outputs invalid headers with 24bit wav files when using OS 10.6.8
| Reported by: | michael@… | Owned by: | janstary (Jan Starý) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | Cc: | ||
| Port: | sox |
Description
With either an updated macports and SOX (to Macports 2.0.3 and SOX 14.3.2), or on a cleanly installed system running OS 10.6.8 there is an error with SOX outputting 24bit wav files.
The error is that the file has padding, this can easily be seen by using the BWF MetaEdit software which shows the error as follows:
"An odd byte length chunks exists that is not immediately followed by a NULL byte. This could cause problems in reading subsequent chunks in some systems."
This does not happen for every single file, but at least 50% of files tested.
This bug does not occur on a system running OS 10.6.7 and macports 2.0.3 with SOX 14.3.2
This bug can make the files incompatible with some other audio software.
Please note this bug has been seen on a number of machines.
Change History (8)
comment:1 Changed 13 years ago by mf2k (Frank Schima)
| Keywords: | SOX removed |
|---|---|
| Owner: | changed from macports-tickets@… to david@… |
| Port: | sox added; SOX removed |
comment:2 Changed 13 years ago by michael@…
comment:3 Changed 13 years ago by jmroot (Joshua Root)
| Owner: | changed from david@… to hans@… |
|---|
comment:4 Changed 13 years ago by janstary (Jan Starý)
Can you please try with the new 14.4.0, and if your problem persists, could you please upload a small file that exemplifies the problem?
comment:5 follow-up: 6 Changed 13 years ago by janstary (Jan Starý)
With 14.4.0 on 10.5.8, a 24bit file produced with
sox -n -b 24 file.wav trim 0 10
is just fine. Can you please show how exactly did you produce the 'faulty' file with SoX?
comment:6 Changed 13 years ago by michael@…
Replying to hans@…:
With 14.4.0 on 10.5.8, a 24bit file produced with
sox -n -b 24 file.wav trim 0 10is just fine. Can you please show how exactly did you produce the 'faulty' file with SoX?
This appears to be fixed in the new version of SOX, in the SOX homepage the latest build has the following fix "Pad WAV data chunks to an even number of bytes."
WIth the latest version installed I've tested it with
sox -n -b 24 file.wav trim 0s 9s
After which the Pad WAV data chunk is now present, in the previous version(s) the Pad WAV data chunk was missing.
comment:8 Changed 13 years ago by mf2k (Frank Schima)
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Update.
Please note that this has now been tested fully and the bug occurs on OS 10.6.8, and OS 10.6.7. Both tested with clean installs.
The previous statement that it did not occur on OS 10.6.7 was incorrect as the application BWF MetaEdit which the files were tested with was set to Accept files if the padding byte was missing.