Projects and Recovery

Projects And Recovery

Creating And Opening Projects

New asks for a parent directory, creates a sanitized child folder from the project name, creates clips, and immediately saves project.edi.json.

Open expects the directory that directly contains project.edi.json.

The Studio stores up to ten recent project paths per Windows user and attempts to reopen the newest valid project on startup.

Save Versus Save Scene

These are separate operations:

• Save and Ctrl+S persist project-level state, including the project name, game target, simulator layout, preset, and trigger mappings.
• Save scene validates and commits the scene editor fields, tracks, and current review clip.
• Save + lock saves the scene and prevents accidental definition, trim, curve, overwrite, and deletion changes until it is unlocked.

Project-level save does not commit an unsaved scene editor. There is currently no unsaved-change prompt when switching projects or exiting.

Project Contents

Project Name/
|-- project.edi.json
|-- .history/
`-- clips/
    `-- <revisioned>.ediclip

An .ediclip is a ZIP package containing JPEG review frames and clip metadata. It is not a standard video and contains no audio.

History And Recovery

Before replacing an existing project.edi.json, the Studio copies it into .history. At most 25 JSON backups are retained.

Important limitations:

• History is metadata-only, not full project version control.
• There is no history browser or automatic restore command.
• Clip assets are not copied into each history revision.
• Replacing or deleting a scene can delete its prior current clip, so an old JSON may reference a clip that no longer exists.

For important integrations, back up the complete project directory rather than relying only on .history.