Editor Documentation
Follow this guide end-to-end to onboard into the editor, ship your first draft quickly, and troubleshoot export issues with confidence.
How to use this page
1) Overview
Action: Open the editor and identify the layout: project library, timeline, preview surface, AI settings, and export actions.
Expected result:
- You can point to where media uploads, timeline edits, and export actions happen.
- You can explain the difference between draft iterations and final export.
Action: Follow the standard workflow: create project → edit timeline → tune AI settings → review with collaborators → export.
Expected result:
- You know which stage to move to next without guesswork.
- You can estimate where feedback and approvals should happen.
2) Prerequisites
Action: Sign in with a RunAsh account that has editor access and collaboration permissions.
Expected result:
- You can open the editor dashboard without permission errors.
- Project creation and sharing controls are visible.
Action: Gather source files in supported formats (video, audio, and image assets) and use clear file names.
Expected result:
- Uploads complete and appear in the project library.
- Assets are easy to identify while building timeline segments.
Action: Use an updated Chromium-based desktop browser and a stable connection for rendering and playback.
Expected result:
- Timeline scrubbing and preview remain responsive.
- Generation and export jobs start reliably.
3) Quick Start
Action: Open the editor dashboard, start a new project, and add a short goal/brief.
Expected result:
- A project workspace opens with autosave and a default timeline.
- The project appears in your recent projects list.
Action: Add clips, audio tracks, images, or references from the input panel.
Expected result:
- All validated assets are available for drag-and-drop on the timeline.
- Asset previews show correct durations and names.
Action: Select an initial model and set prompt + output constraints for your first pass.
Expected result:
- The project uses your selected default generation profile.
- A first generation run starts without validation errors.
Action: Generate a draft output, inspect pacing in preview, and capture revision notes.
Expected result:
- A first draft returns to your project history.
- You have concrete adjustment notes for the next pass.
4) Timeline Editing
Action: Reorder clips, trim edges, and split long segments to match narrative flow.
Expected result:
- Playback follows your intended story order.
- Segment boundaries align with key beats.
Action: Scrub frame-by-frame to place accurate cuts and transition points.
Expected result:
- Cut points land where expected in preview.
- Audio/visual sync improves on repeated playback.
Action: Duplicate, mute, lock, or remove segments to clean up your sequence.
Expected result:
- Timeline complexity is reduced without losing intended content.
- The sequence is easier for collaborators to review.
5) AI Generation Settings
Action: Write a concise prompt covering subject, style, motion, and camera intent, then add constraints as needed.
Expected result:
- Draft outputs align more closely with the intended direction.
- Fewer random artifacts appear across iterations.
Action: Specify elements to avoid (styles, artifacts, text noise, or objects).
Expected result:
- Undesired patterns are reduced in subsequent generations.
- Iteration count drops because fewer corrections are needed.
Action: Choose aspect ratio, resolution, and duration based on destination channel requirements.
Expected result:
- Output fits publishing constraints without additional reformatting.
- Final render settings are reusable for similar projects.
6) Collaboration
Action: Share project access with teammates and clarify who edits versus who reviews.
Expected result:
- Invited collaborators can open the project with expected permissions.
- Ownership boundaries reduce conflicting edits.
Action: Share draft checkpoints, collect comments, and apply agreed revisions in batches.
Expected result:
- Feedback is centralized and easier to action.
- Revision history remains understandable for the team.
7) Export + Troubleshooting
Action: Confirm target settings and metadata before launching final export.
Expected result:
- A final render job starts with publish-ready settings.
- The exported file matches expected ratio, quality, and duration.
Action: If generation/export fails, simplify settings, verify inputs, and retry with a clean rerun.
Expected result:
- Most failures are resolved after correcting invalid combinations.
- You can identify whether the issue is input, settings, or environment related.
