Sascha Franck wrote: > Would be nice if some of the folks being more experienced with such > file conversions could post like a guideline containing the most > basic information (snip) Sascha, Here's my thoughts on Mac->PC file transfers... Two approaches could be taken: 1. The lowest common denominator approach: - MS-DOS-formatted disks - MS-DOS 8.3 file naming conventions - No illegal characters... \/:*"?<>| ...or spaces in file name - No usual characters like ¡£¢?<sum> (the characters you get when you use the option or alt key modifier) - Use .wav files (beware: I think there are some non-standard .wav files out there). Unfortunately, the result of of all this dumbing-down is an ugly, non-descriptive and confusing filename! 2. A more flexible approach: - 32 character file name limit, including file extension - Always use a file extension - No illegal characters... \/:*"?<>| (spaces should be okay) - Don't start file names with a period (eg: ".file.wav") - No unusual characters like ?£¢?<sum> (the characters you get when you use the option or alt key modifier) - Always use .wav files (unless agreed otherwise) - Don't use Sound Designer II files (.sd2) - Use .zip files for compression (unless agreed otherwise) - When burning CDs on a Mac, create Mac/Joliet (Win9x) dual-formatted CDRs (using Disk Burner, Toast, etc) - When burning CDs on a PC, create a standard Joliet CD (Note: if the PC user wanted to cover all bases, a utility like MacDrive could be installed to allow the PC to mount a Mac-formatted disk - http://www.mediafour.com/products/macdrive/) - On the Mac, install a freeware extension called "Joliet Volume Access" to allow Joliet volumes to mount on the desktop. The latest version can be found via Version Tracker - http://www.versiontracker.com/ - Unless agreed otherwise, send text notes as a plain text file (.txt), not formatted text - eg: a Word .doc file - Unless agreed otherwise, no floppies! :-) Have I missed anything? Darrel
Message
Re: [exs] EXS24 Strings
2002-04-28 by dna_studios
Attachments
- No local attachments were found for this message.