Shockwave (Director)
m (I don't understand the previous commit) |
(Adding more information to the "Identifiers" section) |
||
| Line 19: | Line 19: | ||
== Identifiers == | == Identifiers == | ||
File extensions: | File extensions: | ||
| − | * .DIR = Director file | + | * .DIR = Director file (holds an editable project) |
| − | * .DXR = Protected Director file | + | * .DXR = Protected (i.e., read-only) Director file |
| − | * .DCR = Shockwave version of DIR | + | * .DCR = Shockwave (compiled/published) version of DIR; the normal format for distribution of Shockwave applications outside of the organization where they were made. |
| − | * .CST = | + | One major element of Shockwave is "cast members", objects that can have scripts and other resources attached to them. These can be bundled together into a "cast" file for modularity. |
| − | * .CXT = Protected Director cast | + | |
| − | * .CCT = Shockwave cast | + | File extensions: |
| + | * .CST = Editable director cast | ||
| + | * .CXT = Protected (read-only) Director cast | ||
| + | * .CCT = Shockwave (compiled/published) cast; to be loaded after a reference by (presumably) a DCR file | ||
| + | Sources: [https://helpx.adobe.com/director/kb/common-questions-director.html] [https://forum.ragezone.com/f338/help-extracting-cct-files-280268/] [https://help.adobe.com/archive/en_US/director/UsingScripting/director_reference.pdf] | ||
== Sample files == | == Sample files == | ||
Revision as of 11:44, 30 April 2020
- For Shockwave Flash, see SWF.'
Shockwave is a platform and format for multimedia applications, video games, etc. It was owned by Macromedia during most of its formative years, and is now owned by Adobe. It has many names, most of which involve permutations of the words "Macromedia", "Adobe", "Shockwave", and "Director". Director is the application usually used to develop it. It is distinct from SWF (Flash).
The format seems to be based on the RIFX metaformat, though some DCR files are not[1] actually valid RIFX files.
It might be that the DCR files don't work as valid RIFX files due to DEFLATE compression being used on some sections of the file using an undetermined scheme. Presumably a correct application of INFLATE would yield a valid file. AN old oreilly[2] book reveals that this compression and decompression step used to be done by a Director Xtra plugin called "afterburner" before it was a built in feature. Afterburner is available on some mac abandonware sites.
Shockwave also has a plugin system called "xtras" which may complicate the correct interpretation of some files in the future.
Contents |
Identifiers
File extensions:
- .DIR = Director file (holds an editable project)
- .DXR = Protected (i.e., read-only) Director file
- .DCR = Shockwave (compiled/published) version of DIR; the normal format for distribution of Shockwave applications outside of the organization where they were made.
One major element of Shockwave is "cast members", objects that can have scripts and other resources attached to them. These can be bundled together into a "cast" file for modularity.
File extensions:
- .CST = Editable director cast
- .CXT = Protected (read-only) Director cast
- .CCT = Shockwave (compiled/published) cast; to be loaded after a reference by (presumably) a DCR file
Sample files
Links
- Wikipedia:Adobe Shockwave
- Wikipedia:Adobe Director
- Wikipedia:Adobe Shockwave Player
- Xtras installed with Adobe Shockwave Player - Adobe's list of default extras installed with shockwave
- Schockabsorber - Has some very rudimentary reverse engineering of the Director format.
- Adobe Shockwave - A case study on memory disclosure - This contains some useful specifics on the format, specifically for the purposes of building a security exploit.
- https://zenhax.com/viewtopic.php?t=252 - A thread on a game reverse engineering forum discussing the DCR format
- http://aluigi.org/papers/bms/shockwave.bms - (direct download) A script for QuickBMS roughly describing how to apply decompression to a DCR file.
Editors' notes
The PRONOM database claims that the PC version of Director creates files that begin with "RIFX" (i.e. big-endian), and the Macintosh version creates files that begin with "XFIR" (little-endian). This seems backwards. Either PRONOM is wrong, or something else is going on here.
