<h1>Cinezoid Wiki</h1> __TOC__ ==About Cinezoid == Cinezoid is a modular, platform-independent application for data-management of camerafiles, generated by file-based motion picture cameras. An example of such a camera is the [http://red.com RED ONE Digital Cinema Camera]. Cinezoid manages and tracks the data flow from the camera media to the storage systems of the postproduction facility. All copy operations are done within the application. All data transfers are check-summed. There is no possibility to delete camera data within Cinezoid. All functionality in Cinezoid is provided through modules. The application itself and the basic modules are open source. The basic modules will cover local management of the data, preview and local render. Enterprise users will be able to download modules with advanced functions like distributed rendering over network. Those modules will not be open source and not free. Cinezoid and all its modules are updateable via a software update central. Cinezoid is currently developed by Michael Mocnak and [http://jonasrejman.com Jonas Rejman]. ===Features=== *pragmatic, secure and repeatable workflow and handling of camera data *project-management with fixed human-readable directory structure, supporting shooting day and camera number *main storage and backup storage management *automatic detection of inserted media *checksum verification of all copy transfers *re-verification of checksums possible anytime *database-independent metadata in xml file format *no possibility of erasing data *data remains on media, till re-insertion into camera, which forces media format *64bit application ===Planned Features=== *using of JHOVE for format-specific identification, validation, and characterization of digital objects *local render via redline with presets to current format, all redline options supported *offline media management *R3D playback via ffmpeg implementation ===Planned Features For Enterprise edition=== *automatic background render of offline data after checksum verification *network render ability via Elzoido API ==Installation== On a mac, you download the zip, unpack and place it into your application folder. You should use Leopard 10.5.6 and have the latest Java for MAC update installed. ===System Requirenments=== *MAC ** Java 1.6 ** on a 32 bit system (CoreDuo, NOT Core2Duo), please read this [http://www.netbeans.org/kb/61/java/javafx-jdk6-on-32-bit-mac.html tutorial] to install 32bit JAVA 1.6 on your system *LINUX **Java 1.6 ==How Cinezoid works== Most DITs are using a MAC based station, to backup and secure the data on the set. This may be either a small setup with a Mac Book Pro and external harddrives, or a mac pro, attached to a RAID5 storage system. In any case, Cinezoid should assist you in copying data into pre-defined storages, while keeping a simple directory structure based on project, shooting day and camera unit (A,B, ...) The idea is to remove the usage of the finder, except for deleting operations, in order to reduce errors during the copy and distribution process of the camera data. In the hectic environment of a film set, procedures need to be repeatable, simple and precise. ===Setting up storages=== Before you start to work, you setup paths to your main storages and backup storages. ===Setting up projects=== Next, you create a project and assign a main storage and a backup storage to it. You activate the project. If it is the first time for this day, Cinezoid will ask you about the current shooting day. ===Insert Media=== From that point you are ready to start the insertion of the camera media you might add one or more, depending on your ingest path. You might have 2 firewire readers daisy-chained to gether, for example, so you might populate both of them with a CF card. A dialogue appears, in which you can launch the copy process. '''!!! ATTENTION !!!''' ''During test, we found a very strange bug, causing kernel panics. It seems, that there is a problem in the firewire bus, when commands to it are sent ,while a device is transferring data. This error is random, but shuts down the computer entirely. The only workaround is to insert the media first, start the copy process, and remove them only after the copy is finished. Any physical activity on the bus, even on previously unmounted media might result in a kernel panic and system freeze.<br/> You may have never experienced this bug, using the finder, because the kernel panic is random and appears only when you unmount a media and/or try to physically remove it during the copy process.'' After the copy process is finished (on all media, that were inserted simultaneously), the media are removed from the system, and you can physically eject the CF Cards/ RED DRIVES. Cinezoid automatically starts with the checksum generation and checksum verification. This process is interrupted only by inserting another media, where the copy of new media has priority over checksum generation. The checksums are created only from the first copy onto the harddrive, not directly from the CF/REDRAM media itself. The reason is the following: If an error occurs during the copy from the camera medias to the harddrive.