Adobe Photoshop®
Asset transfer, versions and return of edited files.
Connectors link selected applications with assets, versions and workspaces in Orpheus. The Windows connector is available; further platforms will follow.
A catalogue entry describes the intended integration target. Where no released integration exists yet, the entry is explicitly marked as planned.
Asset transfer, versions and return of edited files.
Project-related media transfers and rendered results within the asset context.
Connect models, scenes and exports to their Orpheus assignment.
Link scenes and production files to assets in a controlled way.
Place working files, publishes and versions in project context.
Attach compositing projects and results to media in a traceable way.
Bring media, timelines and outputs into coordinated transfers.
Assign documents and revisions to workspaces and projects.
Bring Orpheus context and Lumiin integration together for interactive productions.
Keep vector files, derivatives and approvals in their asset context.
Bring layouts together with their linked media and versions.
Connect edit projects, deliveries and exports so they stay traceable.
Tie materials and textures to the model they belong to.
Place scenes, renders and project files within the project.
Link simulations and outputs to the job they belong to.
Store designs and model states alongside the media.
Connect projects and builds to assets and workspaces.
Open game engine with the same asset and version context.
Keep drafts and exports together with the project state.
Save drawings and layer states in their asset context.
Open image editing with hand-off and return of edited files.
Edit vector work in the open and return it versioned.
Keep audio projects, versions and mixes in their media context.
Connect analyses and lists to the records they come from.
Build presentations from approved media and versions.
Open document editing with the same storage and versions.
Collaborative document editing in the project context.
All names, word marks and logos shown here are the property of the respective manufacturers and are in part registered trademarks. They are named and displayed solely to describe the intended integration. This implies neither a partnership nor an endorsement or approval by the rights holders. ION.ADS claims no rights to these marks.
Assets remain connected with their workspace, project and task.
Transfers are intended to expose work states instead of anonymously duplicating files.
Connectors follow the intended role and permission context.
Tell us the platform, version and typical workflow. We will assess how the connector fits Orpheus.