Funnily enough, that's what I thought, but Stuffit reduced the total size of the files from 577mb to around 268mb (though apparently corrupting them in the process). The compress function in Rev did just as well, and seems not no have corrupted anything. Filetypes was the problem, and thanks to Klaus Majors kindly email, I was able to sort it out. I actually made a standalone that creates a stack containing all the data, and it's directory structure (I suspect that someone, maybe Chipp, has already done this), and uploaded the data stack and the standalone...I wait 'til Monday to see if my colleague at the other end gets it all ok.

I still quite like the idea of a standalone that contains the actual data, sort of like a self-extracting archive, and in cases like these, the engines' 2.8mb overhead would hardly be a problem.

sd2 is, indeed out of date, but actually in quite common use still. I suppose because it was always the 'native' format for ProTools. The guy I'm working with seems to prefer them, for some reason. I've settled with WAVs, myself, but he hasn't.

Cheers,

Mark


On 14 May 2005, at 02:19, Steven Barncard wrote:

One thing you should know is that Stuffit and most data compression
will not save you any size with audio. There are special lossless
compression techniques for audio, but they are proprietary and
time-consuming, and the best you could do would be 2:1 with those.
Lemper-Ziv/ RLE encoding of audio will probably make the file BIGGER.

Also SD2 is an obsolete audio format, Apple-centric with resource
forks, and that's probably where the problems are. Try converting
source files to WAV files instead, which do not have resource forks,
and can probably survive the travel.

You shouldn't have to build a standalone as a carrier.

_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to