-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 24 Aug 2003 16:56:52 -0600, Rodolfo J. Paiz wrote:
> > The problem with your WAV files is not that they contain sparse > > blocks. If they did, they would not sound good, because you would hear > > every blank block. And since they are listed as 20 times the original > > size, you would hear a lot of "silence", and each of them would play > > for several hours. ;) But as you've mentioned, two arbitrary "1GB > > songs" still sound good. > > > > Just out of curiousity, what do you get when you gzip such a huge > > file, transfer it to another machine and gunzip it? > > Sorry to take so long to respond. > > Didn't have another Linux machine at hand, so I gzipped it (took all of six > seconds) and transferred the compressed file (down from 1.18GB to an > expected 53MB) to another drive. Gunzipping the file resulted again in a > 1.18GB file. > > Color me baffled. Okay. What else can you report about the integrity of the WAV files? When you load them into a somewhat capable audio player, is the displayed playtime correct? In that case, the internal file size in the WAV header would be correct. What do you see at the end of the files when you display them in a hex-editor (e.g. khexedit)? Could it be that they have ~1 GiB of zeroes at the end? - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/SUvB0iMVcrivHFQRAhlSAJ9FIS00i9KH3cvVz9vh8epIVZJs2ACfWwOL xNCSPF7sT38/eLKzrQRhHbc= =xfuZ -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
