Timeline – Richard Cabot

Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
OMF-Files.zip 107 KB Zip - Click to view

Options

Copy Download Link
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
adl_demo.txt 2 KB Text File - Click to view

Options

Copy Download Link

ADL Demo software - Readme NT/95 and MAC versions of "SSL List Courier" with OMF to ADL conversion and ADL input. These files are: SETUPSSL.EXE - WIN NT/95 SSLADL20.HQX - Macintosh Power PC The purpose in writing the programs was to: A) Get my head around the ADL specification as we refine it. B) Provide working examples for examination. C) Demonstrate the feasibility of the whole idea. Notes: The Macintosh version does not include the standard help files due to last minute compli cations with the MAC installation. The demonstration handles OMF Version 1.x only. It will work best if the OMF has been output from the Composer with the "SD2D" switch turned on so the OMF contains file locators. In the event of missing locators the OMF MobID or tapename will be used instead. One sample OMF has been placed on the AES site: BUGSMZ.OMF. Not all OMF to ADL data conversions are completed. For instance, Pans and Gains are not being extracted from the OMF. Use - OMF to ADL: A ) Open an OMF B) In the OMF import dialog, select "For SSL / ADL" (upper right corner of dialog, under "EDL Format"). C) Hit "Process" - The OMF will be converted to EDLMAX (List Courier) internal data and displayed as an EDL. D) In File, select "SaveAs ADL (Level 1 or 2)" - the internal data will be converted to ADL internal data, saved to disk, and displayed. Reading ADLs: A) Open an ADL - the data will be read into the ADL internal data structures and displayed. This can also be saved. ADL to OMF and ADL to EDL conversions are not implemented. May the force be with you. -Brooks

Expand
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
adl_6.pdf 45 KB PDF - Click to view

Options

Copy Download Link
edml_6.pdf 21 KB PDF - Click to view

Options

Copy Download Link
ppa_5.pdf 19 KB PDF - Click to view

Options

Copy Download Link
tcf_6.pdf 40 KB PDF - Click to view

Options

Copy Download Link
tcf_c_6.pdf 29 KB PDF - Click to view

Options

Copy Download Link
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
x67ssladl20.zip 1 MB Zip - Click to view

Options

Copy Download Link
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
x67setupssl.zip 2 MB Zip - Click to view

Options

Copy Download Link
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
x67-adl_9x3b-990407.pdf 50 KB PDF - Click to view

Options

Copy Download Link
x67-adl_9x3b-990407.rtf 102 KB Rich Text Format - Click to view

Options

Copy Download Link
x67-adl_9x4-990413.pdf 137 KB PDF - Click to view

Options

Copy Download Link
x67-edml_9x4-990413.pdf 87 KB PDF - Click to view

Options

Copy Download Link
x67-harris9x3b-990407.pdf 8 KB PDF - Click to view

Options

Copy Download Link
x67-harris9x3b-990407.rtf 11 KB Rich Text Format - Click to view

Options

Copy Download Link
x67-tcf_9x4-990413.pdf 106 KB PDF - Click to view

Options

Copy Download Link
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
x066-draft-my-051201.doc 131 KB Word Document - Click to view

Options

Copy Download Link
x66-draft-050419-copy.doc 147 KB Word Document - Click to view

Options

Copy Download Link
x066-ptd-my-060223.pdf 853 KB PDF - Click to view

Options

Copy Download Link
x66-draft-050419_copy_r1.doc 176 KB Word Document - Click to view

Options

Copy Download Link
x66-draft-050530.doc 384 KB Word Document - Click to view

Options

Copy Download Link
X66-ea-iff-85.html 81 KB HTML - Click to view

Options

Copy Download Link

<title>EA IFF 85</title>  <table border="0" cellpadding="0" cellspacing="0" bgcolor="#d0d0d0"> <tr> <td width="120" align="left"><a href="fpbm.html"><img decoding="async" width="96" height="20" border="0" src="../images/navlt.gif" alt="Flexible Precision Images"></a></td> <td width="96" align="left"><a href="lwsc.html"><img decoding="async" width="64" height="20" border="0" src="../images/navrt.gif" alt="Scene Files"></a></td> <td width="96" align="left"><a href="../filefmts.html"><img loading="lazy" decoding="async" width="56" height="20" border="0" src="../images/navup.gif" alt="File Formats"></a></td> <td width="288" align="right"><a href="../index.html"><img loading="lazy" decoding="async" width="230" height="20" border="0" src="../images/proglw.gif" alt="Table of Contents"></a></td> </tr> </table> <table border="0" cellpadding="0" cellspacing="0"> <tr> <td width="600"> <h3 align="center">"EA IFF 85" Standard for Interchange Format Files </h3> <table> <tr> <th align="left">Document Date: From: Status of Standard: </th> <td> January 14, 1985 Jerry Morrison, Electronic Arts Released and in use </td> </tr> </table> <h3>1. Introduction</h3> Standards are Good for Software Developers As home computer hardware evolves to better and better media machines, the demand increases for higher quality, more detailed data. Data development gets more expensive, requires more expertise and better tools, and has to be shared across projects. Think about several ports of a product on one CD-ROM with 500M Bytes of common data! Development tools need standard interchange file formats. Imagine scanning in images of "player" shapes, moving them to a paint program for editing, then incorporating them into a game. Or writing a theme song with a Macintosh score editor and incorporating it into an Amiga game. The data must at times be transformed, clipped, filled out, and moved across machine kinds. Media projects will depend on data transfer from graphic, music, sound effect, animation, and script tools. Standards are Good for Software Users Customers should be able to move their own data between independently developed software products. And they should be able to buy data libraries usable across many such products. The types of data objects to exchange are open-ended and include plain and formatted text, raster and structured graphics, fonts, music, sound effects, musical instrument descriptions, and animation. The problem with expedient file formats typically memory dumps is that they're too provincial. By designing data for one particular use (e.g. a screen snapshot), they preclude future expansion (would you like a full page picture? a multi-page document?). In neglecting the possibility that other programs might read their data, they fail to save contextual information (how many bit planes? what resolution?). Ignoring that other programs might create such files, they're intolerant of extra data (texture palette for a picture editor), missing data (no color map), or minor variations (smaller image). In practice, a filed representation should rarely mirror an in-memory representation. The former should be designed for longevity; the latter to optimize the manipulations of a particular program. The same filed data will be read into different memory formats by different programs. The IFF philosophy: "A little behind-the-scenes conversion when programs read and write files is far better than NxM explicit conversion utilities for highly specialized formats." So we need some standardization for data interchange among development tools and products. The more developers that adopt a standard, the better for all of us and our customers. Here is "EA IFF 1985" Here is our offering: Electronic Arts' IFF standard for Interchange File Format. The full name is "EA IFF 1985". Alternatives and justifications are included for certain choices. Public domain subroutine packages and utility programs are available to make it easy to write and use IFF-compatible programs. Part 1 introduces the standard. Part 2 presents its requirements and background. Parts 3, 4, and 5 define the primitive data types, <tt>FORM</tt>s, and <tt>LIST</tt>s, respectively, and how to define new high level types. Part 6 specifies the top level file structure. Appendix A is included for quick reference and Appendix B names the committee responsible for this standard. References <cite>American National Standard Additional Control Codes for Use with ASCII, ANSI standard 3.64-1979 for an 8-bit character set.</cite> See also ISO standard 2022 and ISO/DIS standard 6429.2. Amiga™ is a trademark of Commodore-Amiga, Inc. <cite>C, A Reference Manual,</cite> Samuel P. Harbison and Guy L. Steele Jr., Tartan Laboratories. Prentice-Hall, Englewood Cliffs, NJ, 1984. <cite>Compiler Construction, An Advanced Course,</cite> edited by F. L. Bauer and J. Eickel (Springer-Verlag, 1976). This book is one of many sources for information on recursive descent parsing. <cite>DIF Technical Specification</cite> � 1981 by Software Arts, Inc. DIF™ is the format for spreadsheet data interchange developed by Software Arts, Inc. DIF™ is a trademark of Software Arts, Inc. Electronic Arts™ is a trademark of Electronic Arts. <cite>"<tt>FTXT</tt>" IFF Formatted Text,</cite> from Electronic Arts. IFF supplement document for a text format. <cite>Inside Macintosh</cite> � 1982, 1983, 1984, 1985 Apple Computer, Inc., a programmer's reference manual. Apple� is a trademark of Apple Computer, Inc. Macintosh™ is a trademark licensed to Apple Computer, Inc. <a href="ilbm.html"><cite>"ILBM" IFF Interleaved Bitmap</cite></a>, from Electronic Arts. IFF supplement document for a raster image format. <cite>M68000 16/32-Bit Microprocessor Programmer's Reference Manual</cite> � 1984, 1982, 1980, 1979 by Motorola, Inc. <cite>PostScript Language Manual</cite> � 1984 Adobe Systems Incorporated. PostScript™ is a trademark of Adobe Systems, Inc. Times and Helvetica� are trademarks of Allied Corporation. <cite>InterScript: A Proposal for a Standard for the Interchange of Editable Documents</cite> � 1984 Xerox Corporation. <cite>Introduction to InterScript</cite> � 1985 Xerox Corporation. <hr class="PAGE-BREAK"> <h3>2. Background for Designers</h3> Part 2 is about the background, requirements, and goals for the standard. It's geared for people who want to design new types of IFF objects. People just interested in using the standard may wish to skip this part. What Do We Need? A standard should be long on prescription and short on overhead. It should give lots of rules for designing programs and data files for synergy. But neither the programs nor the files should cost too much more than the expedient variety. While we're looking to a future with CD-ROMs and perpendicular recording, the standard must work well on floppy disks. For program portability, simplicity, and efficiency, formats should be designed with more than one implementation style in mind. (In practice, pure stream I/O is adequate although random access makes it easier to write files.) It ought to be possible to read one of many objects in a file without scanning all the preceding data. Some programs need to read and play out their data in real time, so we need good compromises between generality and efficiency. As much as we need standards, they can't hold up product schedules. So we also need a kind of decentralized extensibility where any software developer can define and refine new object types without some "standards authority" in the loop. Developers must be able to extend existing formats in a forward- and backward-compatible way. A central repository for design information and example programs can help us take full advantage of the standard. For convenience, data formats should heed the restrictions of various processors and environments. E.g. word-alignment greatly helps 68000 access at insignificant cost to 8088 programs. Other goals include the ability to share common elements over a list of objects and the ability to construct composite objects containing other data objects with structural information like directories. And finally, "Simple things should be simple and complex things should be possible." --Alan Kay. Think Ahead Let's think ahead and build programs that read and write files for each other and for programs yet to be designed. Build data formats to last for future computers so long as the overhead is acceptable. This extends the usefulness and life of today's programs and data. To maximize interconnectivity, the standard file structure and the specific object ...

Expand

This file was truncated for preview. Please download to view the full file.
x66-riffmci.pdf 550 KB PDF - Click to view

Options

Copy Download Link
x66-smpte-330m-umid.pdf 55 KB PDF - Click to view

Options

Copy Download Link
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
ebu-rf64_ext-bwfv1_6.pdf 98 KB PDF - Click to view

Options

Copy Download Link
mixauto-ultan-030816.pdf 116 KB PDF - Click to view

Options

Copy Download Link
mixauto-ultan-040503.pdf 137 KB PDF - Click to view

Options

Copy Download Link
mix-00-01.pdf 3 MB PDF - Click to view

Options

Copy Download Link
mixauto-ultan-040511.pdf 137 KB PDF - Click to view

Options

Copy Download Link
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
aes31-3bextIntl_Rev1.pdf 84 KB PDF - Click to view

Options

Copy Download Link
aes31-3-r-041018.pdf 221 KB PDF - Click to view

Options

Copy Download Link
aes31-3-r-050515.doc 438 KB Word Document - Click to view

Options

Copy Download Link
aes31-3-r-pwd-060504c.pdf 2 MB PDF - Click to view

Options

Copy Download Link
aes31-3-r-pwd-060710.doc 485 KB Word Document - Click to view

Options

Copy Download Link
aes31-3-r-pwd-060722-ex.pdf 85 KB PDF - Click to view

Options

Copy Download Link
aes31-3-r-pwd-060912.pdf 2 MB PDF - Click to view

Options

Copy Download Link
aes31-3-r-pwd-071219.pdf 2 MB PDF - Click to view

Options

Copy Download Link
AES31-3-bextIntl_Rev1.doc 74 KB Word Document - Click to view

Options

Copy Download Link
aes31-3-xxxx-pcfc-080121cc.pdf 2 MB PDF - Click to view

Options

Copy Download Link
0 Comments
Richard Cabot posted an update 4 weeks ago

4 weeks ago
Documents

Folder Title Following special characters are not supported: \ / ? % * : | " < >

Privacy

Cancel Create

Create new folder Cancel Move
x66ebuusid990104.rtf 14 KB Rich Text Format - Click to view

Options

Copy Download Link
0 Comments
Load More