Object Mount in Media Workflows
π₯ Object Mount in Media Workflows
Object Mount is designed to make working with cloud storage as seamless as possible β especially in media production environments where performance, compatibility, and simplicity matter.
This page gives a quick overview of how Object Mount fits into post-production workflows, and where it works well with tools like DaVinci Resolve and Adobe Premiere Pro.
π What is Object Mount?
Object Mount is a native S3 mount tool that lets you treat remote object storage like a local drive. It works with Storj, AWS S3, and other compatible providers, and is available on macOS and Windows.
Once mounted, your object storage behaves like any other drive β you can browse, preview, and edit media directly from it using your preferred creative software.
π¬ DaVinci Resolve
Object Mount integrates cleanly into DaVinci Resolve workflows:
- Media can be accessed directly from your Object Mount volume
- Stills, cache, and preview files are best kept on local SSD/NVMe to avoid bottlenecks
- Direct I/O should be disabled for the Object Mount path
- Optional settings like proxy mode and smart caching can improve playback on cloud-mounted media
See Using Object Mount with DaVinci Resolve for the full setup guide.
ποΈ Adobe Premiere Pro
Premiere Pro users can also benefit from Object Mount in similar ways:
- Projects and source footage can be stored remotely and edited directly
- Media can be linked and relinked to Object Mount volumes just like local storage
- Proxies and cache files are recommended to remain on local disks for speed
Tip: Object Mount volumes appear like regular drives in Finder or File Explorer, making them easy to integrate with Premiereβs media browser and import panels.
β‘ When to Use Object Mount
Object Mount is ideal for:
- Remote editing workflows
- Team environments where storage is centralised
- Archival footage access over cloud
- High-speed read access (e.g. proxy editing or frame review)
Itβs particularly well-suited for hybrid workflows where some assets live on fast local disks and others come in from the cloud β without needing clunky manual sync tools or complex workflows.
π§ Final Notes
Object Mount is not a replacement for all local workflows β cache files, renders, and scratch disks are still best kept local. But for accessing and working with cloud-hosted media, it bridges the gap between storage and usability beautifully.
For app-specific setup steps, visit: