How to inspect a Pro Tools project
A Pro Tools session file is encrypted, which is why most tools cannot read one. This one can, in your browser.
- Drop the session: Drop the .ptx, or the whole session folder so the inspector can check the Audio Files folder too.
- Read the report: Third-party plugins, Avid’s own, every track, clips, markers, tempo, sample rate, bit depth and the audio files the session uses.
- Decide: Install what is missing, ask for the audio that did not come with it, or convert the session to the DAW you use.
What the inspector tells you
Plugins, before the session opens
Pro Tools tells you a plugin is missing when the session is already loading. The inspector lists the session’s plugins first, with Avid’s own ones — Click II, Elastic Audio — set apart.
The Audio Files folder, checked
A session file points at audio in its Audio Files folder. Drop the whole session folder and anything the session needs that is not there is listed as missing.
Nothing leaves your computer
The session is decrypted and read by this page. Nothing is uploaded or stored.
Questions about the Pro Tools inspector?
We have answers.
Do I need Pro Tools to use this?
No. It runs in any modern browser. To play or edit the session you still need Pro Tools, or the session converted into a DAW you have.
Which Pro Tools versions does it read?
.ptx sessions — the format since Pro Tools 10. It is tested against Pro Tools 12 sessions; older .ptf and .pts files may read only in part.
Is my session uploaded?
No. The page reads the file on your device and nothing is sent anywhere.
Inspect a project from another DAW
The same report for every format — read in your browser, nothing uploaded.
Try these Doseedo tools
- Project inspectors
- From Logic
- From Ableton
- From FL Studio
- From REAPER
- From Pro Tools
- Session files