murphy@gibbs.physics.purdue.edu (William J. Murphy) (06/17/91)
In article <1736@toaster.SFSU.EDU> eps@cs.SFSU.EDU (Eric P. Scott) writes: >In article <1991Jun15.170228.2479@shaman.com> jiro@shaman.com > (Jiro Nakamura) writes: >> Many many *NIX compression methods can handle NeXT sound >>files? > >No one forces you to use BSD compress on everything. >Every 2.0/2.1 NeXT does come with a "sndcompress" utility, >y'know. > > -=EPS=- 14M%sndcompress junk.snd junk.snd.cmp 15M%sndcompress junk.snd.cmp junk1.snd 16M%ls -l junk*snd* -rw-r--r-- 1 murphy 524208 Jun 17 09:17 junk.snd -rw-rw-r-- 1 murphy 315830 Jun 17 09:21 junk.snd.cmp -rw-rw-r-- 1 murphy 523804 Jun 17 09:21 junk1.snd I don't know whether I would want to trust sndcompress for archiving my .snd files. I just ran a quick test to see whether I would get back the same size file if I compressed and then uncompressed a .snd file. As you can see, they are not the same size which makes me suspicious. Can anyone explain why this happened? Can anyone confirm this? I will check to see whether the header could have changed in size. Bill Murphy murphy@physics.purdue.edu