STSZ entry becoming zero for one particular sample for a particular AAC Audio track while muxing 1 H.264 video Track with 4 AAC Audio Tracks.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use mp4v2 library for muxing 1 H.264 video track and 4 AAC audio tracks to 
create QT compatible MP4/MOV file.
2. Continue muxing for more than 8 hours. Print the entries in the function 
UpdateSampleSizes() present in mp4track.cpp file.
3. Check the finally written MP4/MOV file in atomic browser or MP4 Explorer.

What is the expected output? What do you see instead?
1. Expected output should be that all the values of "STSZ" property in the 
final "MOOV" box should be updated correctly for all the AAC audio tracks with 
same values at that instant of time. 
2. But however observed behavior is that after 2000 samples or so one value of 
"STSZ" value for one of the AAC audio track is entered zero while other entries 
are correct for that audio track and when that sample size is entered 
incorrectly for that track, the other tracks have correct entries of "STSZ" for 
that particular sample.
3. When checked in UpdateSampleSizes() function the size which has gone zero in 
the final "MOOV" created has also been updated correctly. 
4. This problem only occurs for "SOUN"(audio) track and not for "VIDE"(video) 
track.
5. Also any one sample size entry of any of the audio tracks can go zero which 
means it happens randomly. 
5. Please find attachment of such a file opened in MP4Explorer where size is 
zero.
6. "Sample size expected to be written in 171 but is shown as zero."

What version of the product are you using? On what operating system?
This bug is observed with all versions of mp4v2 library ie mp4v2 library 
present in mpeg4ip library version 1.5 to the latest mp4v2 library version 2.0.

Operating System is Fedora 6(Linux).

Please provide any additional information below.
When we check for "MDAT" when that sample size is entered as zero, that "MDAT" 
is present. This can be seen if the file is opened in Atomic Browser.  

Original issue reported on code.google.com by [email protected] on 27 Apr 2013 at 7:24

Attachments:

• Screenshot.png