Using Object Mount with Digital Audio Workstations (DAWs)

Object Mount works well alongside many industry-standard audio tools by offering high-performance access to cloud-based sample libraries, project archives, and media assets. This guide offers high-level advice for working with Pro Tools, Logic Pro X, Ableton Live, Cubase, FL Studio, Reaper, Studio One, and Adobe Audition.

While Object Mount behaves like a local drive, most DAWs perform best when:

  • Project/session files are saved to a local SSD
  • Media and asset libraries (e.g. sample packs, stems, field recordings) are stored on Object Mount
  • Render/export targets are local, then archived to cloud storage after completion

In all cases, placing scratch/cache folders on fast internal drives is strongly recommended.

Tool-Specific Tips

  • Store .ptx session files and audio files on local volumes
  • Use Object Mount for archived session material, bounced stems, or loop/sample libraries
  • Avoid using cloud storage for active playback/editing unless the session is fully loaded into RAM

Summary

DAWs are highly sensitive to disk latency. For best results:

  • Store active sessions and renders locally
  • Use Object Mount for assets, libraries, and archives
  • Enable caching in Preferences for faster access to large sample sets
  • Avoid real-time recording or playback to Object Mount volumes

Looking to integrate Object Mount into a studio or broadcast pipeline? Contact support for advice on multi-user and high-throughput setups.

Previous
Object Mount with DaVinci Resolve
Next
Object Mount with Final Cut Pro