Why not figure out what the bitrate of the chunk is by doing what people normally do: encode the entire track.
How about using iTunes 128kb/s CVBR (default quality, available even on Windows), loop each sample, check the bit rates, and take the loop giving the lowest bit rate (as the above plot shows, there obviously is a clear lower bit rate border)?
Should be the middle bitrate choosen as it has highest probability (mean value)?
3. Apple --cvbr 124 128 --highest .
It won't be right to choose the chunk with minimal bitrate. I propose to choose average bitrate ( the chunk with 140 kbps in this case).
... CVBR bitrate distribution for looped x16 samples: I've tried fatboy_30sec sample. h*tp://www.mediafire.com/?nz1cmjoj1y51st chunk: 133 kbps.from 2d to 16th chunks: 140 kbps.It won't be right to choose the chunk with minimal bitrate. I propose to choose average bitrate ( the chunk with 140 kbps in this case).
ORIGINAL Left RightMin Sample Value: -32768 -32768Max Sample Value: 32718 32766Peak Amplitude: 0 dB 0 dBPossibly Clipped: 1 4DC Offset: -.016 -.004 Minimum RMS Power: -73.09 dB -84.87 dBMaximum RMS Power: -5.45 dB -7.44 dBAverage RMS Power: -17.05 dB -16.79 dBTotal RMS Power: -16.12 dB -15.8 dBActual Bit Depth: 16 Bits 16 BitsUsing RMS Window of 50 msCVBR Left RightMin Sample Value: -31040 -32768Max Sample Value: 32767 32767Peak Amplitude: 0 dB 0 dBPossibly Clipped: 1 9DC Offset: -.009 -.004 Minimum RMS Power: -77.87 dB -84.53 dBMaximum RMS Power: -5.95 dB -8 dBAverage RMS Power: -17.34 dB -17.11 dBTotal RMS Power: -16.45 dB -16.18 dBActual Bit Depth: 16 Bits 16 BitsUsing RMS Window of 50 ms
Regarding using a looped sample, I think it would be difficult to cut it accurately without first decoding it. Perhaps the sample should be decoded and the wave file cut in order to get it right. Then that sample should be provided in a lossless format.
Add 4 samples (one millisecond), and we get exactly 646.
Alex or Igor (or both), can you [...] loop it, encode it with iTunes CVBR, then split the looped MP4 encode into 15-second chunks, and report on the file size of each chunk? That would be interesting.