Proximate Help

How Proximate Works

Proximate automates a three-stage pipeline:

1. Source monitoring — watches your source folders for new camera files (BRAW, CRM, R3D, NEV)
2. Encoder distribution — creates symlinks in each encoder's watch folder so the encoder transcodes a reference to your original file without copying it
3. Proxy delivery — monitors encoder output folders for completed proxies and moves them to the configured destination, matching the naming and folder structure your NLE expects

This lets you distribute encoding work across multiple instances of Adobe Media Encoder, Blackmagic Proxy Generator, or any other watchfolder-capable encoder — on the same machine or across your network.

Getting Started

Quick Start

1. Add one or more source folders containing your camera media
2. Add at least one encoder with its watch folder and output folder
3. Configure the destination — where proxies should be placed and how they should be named
4. Click Start to begin processing
5. Monitor progress in the Assets tab

The Automation tab shows the full pipeline: source folders at the top, encoder instances in the middle, and destination configuration at the bottom with a live path preview.

Source Folders

Multiple source folders can monitor different volumes or directory trees simultaneously.

Source folders are monitored for media files that match the file extensions specified in your encoders. You can add multiple source folders spanning local drives and network volumes.

• Processing must be stopped before adding, editing, or removing source folders
• Files are monitored for changes and only processed after they've settled (file size stops changing)
• Offline folders are preserved and automatically resume monitoring when the volume becomes available again
• Badge counts next to each folder show pending and processed file totals

Encoders

Three AME encoder instances, each with its own watch folder and output folder. File extensions are configured per encoder.

Encoder Types

Configuring an Encoder

• Name — a label for your reference (e.g. "AME1", "BM Proxy Suite A")
• Type — determines default extensions and output naming pattern detection
• Watch Folder — where Proximate creates symlinks for the encoder to pick up
• Output Folder — where the encoder writes completed proxies
• File Extensions — which source file types this encoder handles (add or remove as needed)

Scaling with Multiple Encoders

Add as many encoder instances as you have available. Each instance needs its own watch folder and output folder. Proximate distributes incoming files across all enabled encoders. You can mix encoder types — for example, route BRAW files to Blackmagic Proxy Generator and R3D files to Adobe Media Encoder.

Destination Modes

The destination configuration controls where completed proxies are placed and how they are named. Proximate offers three output modes, each suited to different NLE and MAM workflows:

Same as Source

Proxies are placed relative to the source file's location. You can specify a proxy subfolder (e.g. "Proxies"), a proxy suffix (e.g. "_Proxy"), or both. At least one must be specified to distinguish proxies from source files.

Alternate Root

The full source directory structure is mirrored under a different root folder. This preserves the relative path hierarchy while placing proxies on a different volume or in a different location. Useful for MAM systems that expect proxies in a parallel tree.

Fixed Output Folder

All proxies are placed into a single flat folder regardless of where the source files are located. Simplest configuration, but risks filename collisions if source files in different directories share the same name.

Path Preview

The destination section includes a live path preview showing exactly where a proxy will be placed based on your current settings. This updates as you change the output mode, proxy folder, and suffix.

Workflow Examples

The following examples show how to configure Proximate's destination settings for common production tools. In each case, the source file is /Volumes/medianas/Subdir/Camera_A.r3d.

Iconik Edit Proxy Creation

Iconik expects edit proxies alongside source media with an _editproxy suffix and no subfolder.

Iconik configuration — Same as source mode, no proxy folder, _editproxy suffix. Result: Camera_A_editproxy.mov next to source.

• Output Mode: Same as source media
• Proxy Folder: (empty)
• Proxy Suffix: _editproxy

CatDV Alternate Root Standard

CatDV typically expects proxies in a parallel directory tree under a different root, with the same filename as the source (no suffix).

CatDV configuration — Alternate root mode mirroring the source tree under /Volumes/medianas/Proxies, no suffix. Result: /Volumes/medianas/Proxies/medianas/Subdir/Camera_A.mov

• Output Mode: Alternate root
• Output Location: /Volumes/medianas/Proxies
• Proxy Suffix: (empty)

Premiere Pro Proxy Workflow

Premiere Pro's proxy workflow expects proxies in a subfolder named "Proxies" with a _Proxy suffix, relative to the source media.

Premiere configuration — Same as source mode, "Proxies" subfolder, _Proxy suffix. Result: /Volumes/medianas/Subdir/Proxies/Camera_A_Proxy.mov

• Output Mode: Same as source media
• Proxy Folder: Proxies
• Proxy Suffix: _Proxy

Collect from Distributed Watch Folders

When collecting proxies from multiple distributed source locations into a single centralized folder — for example, coalescing proxies from several camera offload points into one shared proxy library.

Collect configuration — Fixed output folder mode, all proxies collected into /Volumes/medianas/Proxies. Add a suffix if your workflow requires it.

• Output Mode: Fixed output folder
• Output Location: /Volumes/medianas/Proxies
• Proxy Suffix: per workflow requirements (e.g. _Proxy or empty)

Duplicate File Handling

When the same source content exists in multiple locations, Proximate detects duplicates using content-based hashing — not just filenames. The same file with different names in different folders is correctly identified as a duplicate.

Settings

Preferences panel with file discovery methods, timing configuration, duplicate handling mode, and application behavior options.

File Discovery Methods

Both methods can be enabled simultaneously (recommended for mixed local/network workflows). At least one method must be enabled.

Timing

• Scan Interval — how often to check source folders for new files. Lower values (30–60s) for near-real-time detection; higher values (hours) for batch processing
• Scheduled Start Time — optionally begin scans at a specific time of day (e.g. midnight for overnight processing)
• Settle Interval — how long to wait after a file stops changing before processing. Prevents encoding files that are still being copied. Recommended: 30–60 seconds

Application Behavior

Automatically resume processing when app starts: when enabled, Proximate restarts the processing pipeline on launch if it was running when the app was last closed.

Assets & Activity Log

The Assets tab shows a real-time activity feed of processing events and a searchable asset database with codec details and proxy status.

Activity Log

The top section shows a live feed of processing events: new assets created, files submitted to encoders, proxies found and moved to destination, and any processing errors. Each entry includes the filename, event type, and timestamp. Use the time filter to narrow the view to recent activity.

Asset Database

The bottom section lists all tracked assets with their name, source location, file size, and proxy status. Assets with confirmed proxies show a green indicator; pending assets show orange. Duplicates detected across multiple locations are grouped under the same asset entry.

The database is disposable — it tracks processing state but your original files are never affected. Use Reset Database in Settings to clear all history and force reprocessing on the next scan.

Troubleshooting

Encoder Not Picking Up Files

• Verify the watch folder path in Proximate matches the folder your encoder is actually monitoring
• Check that the encoder application is running and its watch folder is active
• Confirm the source file extension is listed in the encoder's file extensions list
• Check the activity log for error messages

Proxies Not Appearing at Destination

• Verify the output folder path matches where the encoder actually writes its output
• Check that the encoder has finished transcoding — Proximate waits for the output file to settle before moving it
• If using "Same as source" mode, ensure at least a proxy suffix or proxy folder is specified

AME Encoding Fails or Produces Silent Output

The most common cause is an audio channel mismatch between the AME preset and the source media. If your preset expects stereo audio but the source has 4 or 8 channels (or vice versa), AME may fail silently or produce a proxy with no audio. Check the AME preset's audio channel configuration and ensure it matches the source media format.

Files Being Reprocessed

Proximate tracks processed files in its database. If files are being reprocessed unexpectedly:

• The database may have been reset — a full rescan reprocesses all source files
• The file may have been modified since it was last processed (Proximate detects content changes via hashing)
• Files with the configured proxy suffix in their name are automatically excluded from source scanning

Network Volume Issues

• FSEvents may not fire reliably on network volumes — enable Periodic Scanning as a fallback
• Offline volumes are detected automatically and resume when remounted
• Increase the settle interval for network volumes where file copies take longer to complete

Debug Logging

Enable Debug level logging in Settings for verbose diagnostic output covering file discovery, hash calculations, encoder submissions, and proxy delivery. Logs are written to ~/Library/Logs/daveco/proximate.log.