this seems to be data fork / mac binary encoding related
refer to this 1998 article for more info re: preparing mac files for transfer over the net
http://tidbits.com/article/5066as u know mac files contain data forks + metadata that can be damaged by windows + unix filesystems
the only way to avoid this is to properly encode the files to be in macbinary (.bin) or binhex (.hqx) encoded format
which can be thought of as a container or wrapper that allows the files to be transfered onto windows + unix filesystems
and arrive 100% intact with file associations + icons + other mac os info intact in the file
f.e. a toast image that is properly binary encoded i believe will be able to be double clicked to launch toast within mac os 9
vs one that is downloaded without proper encode.. the os will not recognize the file on double click . but most likely u will be able to still open it
in toast.. and resave the file .. if u do this u will see the new copy u "Resave" will show the proper icon etc
we need to adopt the practice of encoding files for transfer by using stuffit deluxe and using the "Translate" menu to "Encode to Macbinary" or "encode to binhex"
im leaning more towards .bin macbinary as a standard.. this means that every file we transfer would have this .bin extension, so file extensions would appear as
.sit.bin or .img.bin or .toast.bin or smi.bin etc etc
the actual encoding doesnt take long, and creates a new copy/version of the file that will allow it to visit windows or unix filesystems while keeping data fork + mac filesystem resouces in tact
this is something that we will be preppign everyone on very shortly due to upcoming changes on the site.. stay tuned for more info re: this in the very near future
Topic: Native Instruments Kompakt (Read 15863 times)