![]() When cineSync runs a script, it calls it with arguments describing the current environment: the session key, saved frame folder and format. User data is propagated to all clients in the session. You can also attach user data to the session as a whole. When exporting from cineSync, an event handler script can use this to determine how to link everything back to the database. This is a custom string that can be attached to each file in the playlist. The script that starts the session can store this as user data. To link notes from cineSync back to the shot in the database, you need to know this shot ID. cineSync tracks the path to each QuickTime movie, whereas the database might use a shot ID. The production database typically refers to each file differently than cineSync does. Once the session is finished, any notes and annotations are saved back into the database and linked to the original shots. ![]() User DataĪ typical integration of cineSync into the production pipeline involves starting a session from shots in a database. From other languages, you can manipulate the XML structure directly. The cineSync API libraries (Ruby and Python) provide methods for manipulating and generating the session file format. ![]() This allows creating a session from an external tool, or adding notes from external sources. cineSync will then open this file and add its contents to the session. The script can examine the current playlist, notes, annotations, and so on, so it could save them to a shared production database, or access additional information about the active movie.Īdditionally, an external script can call a cinesync: URL, giving it the path to a session file on disk. When cineSync runs a command via an event, it serializes the current session and pipes it to the command. cineSync 3 can open sessions saved by older versions of cineSync, but will only write the v3 format. This is an XML-based file, with the goal to represent the session as it was seen on the local computer.īackward compatibility note: The session file format has changed significantly with cineSync 3. This is the same format that is generated when selecting "Save Session" from within cineSync. The cineSync session file format holds information about the contents of the session. Running event scripts from cineSync requires a cineSync Pro account. The triggered script has full access to the content of the session, along with some of the surrounding environment (the session key, etc.). You can always run these manually, or also choose to have them run automatically when certain things change in cineSync. These run commands, typically a Python or Ruby script. The syntax for these is described in the command reference.Įvents are triggered from within cineSync. Running a script configured in cineSync.Modifying the current session's content (adding new files, changing notes and annotations).A command is a URL with the cinesync: scheme, so they can be called from a web page or email, or sent by an application or script. This is achieved with two concepts: commands and events.Ĭommands are sent by other applications to cineSync. Integration Overview Commands and EventsĬineSync 3.0 introduced new features to integrate with the production pipeline. Please instead use see the downloads on the cineSync website. This repository is now deprecated and unsupported. CineSync RubyGem Notice: old and unsupported!
0 Comments
Leave a Reply. |