Two Editors, One exFAT Drive, Three Days
Priya is cutting a 12-minute brand film on a MacBook Pro (M2 Pro, 16 GB) running Premiere Pro 2024. All media and the .prproj live on a 2 TB USB-C SSD formatted exFAT, because a Windows-based editor will review cuts later. Footage: 90 minutes of 4K 60fps HEVC from an iPhone 15 Pro, 40 minutes of Sony FX3 10-bit 4:2:2 XAVC, and 30 GB of JPEG stills. Symptoms: timeline playback stutters even at 1/4 resolution, "Media Pending" appears when scrubbing, two clips went offline after the drive was unmounted and remounted, and the Media Cache folder on the internal drive has grown to 180 GB, leaving only 12 GB free. The producer wants a first cut in three days.
1. What is actually causing the offline clips and the playback problems, and what would you change before cutting a single frame?
Read the worked answer
Two separate faults are being conflated.
- Offline clips: exFAT has no journaling, and macOS and Windows mount the same volume under different paths. Premiere stores absolute paths, so a remount that changes the mount point or a Windows drive letter breaks the links. exFAT also has weaker error recovery, which is a genuine risk when it holds the only copy of the media.
- Playback and Media Pending: 4K60 HEVC decode plus a nearly full internal drive. With 12 GB free, macOS and Premiere compete for scratch space, and a 180 GB cache buys you nothing while costing you the disk.
Before cutting: copy all media to an APFS (or NTFS) working volume and keep the exFAT drive as a shuttle copy only; relink the project to the new paths; move Media Cache to the external SSD with automatic deletion enabled; keep at least 15–20% of every drive free; and ingest through the Media Browser rather than Finder drag-and-drop so paths stay consistent.
2. Design the proxy workflow: which clips, what settings, where stored, and how do you guarantee the final export uses originals?
Read the worked answer
Which clips: only the 90 minutes of 4K60 HEVC. The FX3 XAVC 10-bit already plays at 1/2 resolution; proxying it burns a day you do not have.
Settings: ProRes Proxy at 1280x720, or H.264 at 8–10 Mbps if space is tight. Match the source frame rate - do not let an ingest preset turn 59.94 into 29.97, because the proxy inherits its timecode behaviour and you will get odd conforms on any clip you later re-time.
Where: the same external SSD as the media, in a sibling Proxy folder, generated through the Media Browser Ingest Settings so the attach dialog finds them predictably.
Guaranteeing originals: proxies are only ever attached, never relinked as media. Verify by toggling Proxies on the timeline and confirming the proxy badge on the clips, then confirm at export that the source resolution shown in the summary is the original, not 720p. If you ever see a 720p source in the export summary, the proxy was added as media by mistake - fix the link, do not just raise the bitrate.
3. The Windows editor needs to open the project with media online. What do you do about the drive format and the file paths?
Read the worked answer
The real requirement is not "exFAT" but "the other editor opens the project with media online." Solve the path problem, not the filesystem problem.
- Consolidate: File > Project Manager > Copy to a new location, include all media, 50-frame handles. You get one self-contained folder.
- Put that folder on a filesystem both machines read. APFS locks out Windows; use NTFS with a third-party driver, or keep exFAT strictly as a transfer volume, never as the working volume.
- Keep the top-level folder name identical on both machines and mount it at the same drive letter (Windows) or volume name (macOS). Premiere resolves paths relative to the project when the structure matches, so identical structure means no relinking at all.
- Send the .prproj plus a short note: sequence settings, which clips are proxied, and which version is master. Otherwise the editor will "fix" the proxies and hand you back a 720p timeline.