[ sox-Bugs-3539474 ] WAV --ignore-length reads past end of WAVE chunk

[ sox-Bugs-3539474 ] WAV --ignore-length reads past end of WAVE chunk

[SourceForge.net]

Bugs item #3539474, was opened at 2012-07-02 08:05
Message generated for change (Tracker Item Submitted) made by ccaz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=3539474&group_id=10706

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Charles (ccaz)
Assigned to: Nobody/Anonymous (nobody)
Summary: WAV --ignore-length reads past end of WAVE chunk

Initial Comment:
Some WAV files contain extra RIFF chunks with metadata or other data in them (iXML is an example: http://www.gallery.co.uk/ixml/ ; for a list of software generating this chunk, see http://www.gallery.co.uk/ixml/compatible.html).  Extra trailing RIFF chunks interact badly with the --ignore-length sox parameter, because sox reads past the end of the WAVE chunk containing the audio data and interprets the contents of the extra chunk(s) as audio data.

So I can't use --ignore-length to fix WAVE files which contain bogus lengths (or 0 lengths) in the WAVE header if these files also contain extra chunks, as that results in random glitches on the end of the audio.

Ideally --ignore-length would indeed ignore the length specifiec in the WAVE header, but would only read to the end of the WAVE audio chunk in the file.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=3539474&group_id=10706

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ sox-Bugs-3539474 ] WAV --ignore-length reads past end of WAVE chunk

[SourceForge.net]

Bugs item #3539474, was opened at 2012-07-02 08:05
Message generated for change (Comment added) made by uklauer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=3539474&group_id=10706

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Charles (ccaz)
Assigned to: Nobody/Anonymous (nobody)
Summary: WAV --ignore-length reads past end of WAVE chunk

Initial Comment:
Some WAV files contain extra RIFF chunks with metadata or other data in them (iXML is an example: http://www.gallery.co.uk/ixml/ ; for a list of software generating this chunk, see http://www.gallery.co.uk/ixml/compatible.html).  Extra trailing RIFF chunks interact badly with the --ignore-length sox parameter, because sox reads past the end of the WAVE chunk containing the audio data and interprets the contents of the extra chunk(s) as audio data.

So I can't use --ignore-length to fix WAVE files which contain bogus lengths (or 0 lengths) in the WAVE header if these files also contain extra chunks, as that results in random glitches on the end of the audio.

Ideally --ignore-length would indeed ignore the length specifiec in the WAVE header, but would only read to the end of the WAVE audio chunk in the file.


----------------------------------------------------------------------

>Comment By: Ulrich Klauer (uklauer)
Date: 2012-08-30 08:32

Message:
> Ideally --ignore-length would indeed ignore the length specifiec in the
WAVE header, but would only read to the end of the WAVE audio chunk in the
file.

Ideally, yes, but unfortunately SoX isn't clairvoyant. :) There is simply
no way to tell where the data chunk ends other than the chunk length, and
if that isn't correct, you are out of luck.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=3539474&group_id=10706

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ sox-Bugs-3539474 ] WAV --ignore-length reads past end of WAVE chunk

[SourceForge.net]

Bugs item #3539474, was opened at 2012-07-02 08:05
Message generated for change (Comment added) made by ccaz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=3539474&group_id=10706

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Charles (ccaz)
Assigned to: Nobody/Anonymous (nobody)
Summary: WAV --ignore-length reads past end of WAVE chunk

Initial Comment:
Some WAV files contain extra RIFF chunks with metadata or other data in them (iXML is an example: http://www.gallery.co.uk/ixml/ ; for a list of software generating this chunk, see http://www.gallery.co.uk/ixml/compatible.html).  Extra trailing RIFF chunks interact badly with the --ignore-length sox parameter, because sox reads past the end of the WAVE chunk containing the audio data and interprets the contents of the extra chunk(s) as audio data.

So I can't use --ignore-length to fix WAVE files which contain bogus lengths (or 0 lengths) in the WAVE header if these files also contain extra chunks, as that results in random glitches on the end of the audio.

Ideally --ignore-length would indeed ignore the length specifiec in the WAVE header, but would only read to the end of the WAVE audio chunk in the file.


----------------------------------------------------------------------

Comment By: Charles (ccaz)
Date: 2012-08-30 09:08

Message:
Ah, my mistake.  I thought the WAVE chunk contained a length/# of samples
field, and was hoping sox could read to the end of the WAVE chunk instead
of obeying that field.  I see now there isn't such a field, and it's the
chunk size that's used to find the length of the audio.

Thanks.


----------------------------------------------------------------------

Comment By: Ulrich Klauer (uklauer)
Date: 2012-08-30 08:32

Message:
> Ideally --ignore-length would indeed ignore the length specifiec in the
WAVE header, but would only read to the end of the WAVE audio chunk in the
file.

Ideally, yes, but unfortunately SoX isn't clairvoyant. :) There is simply
no way to tell where the data chunk ends other than the chunk length, and
if that isn't correct, you are out of luck.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110706&aid=3539474&group_id=10706

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/