Preview. mollusk isn’t released yet, and this page will change before it is.
DAW conversion tool
Pro Tools to REAPER
Your Pro Tools mix opens in REAPER. Sounding like it should.
Convert one of your sessions for free and get a preflight report for your whole library.
- Plug-ins arrive dialed in
- For every plug-in mollusk can read, the settings come across exactly as you left them — the EQ curve you drew, the synth patch you built. The report names the ones that cannot come, and what to do about them.
- Pro Tools not required
- mollusk opens the
.ptxdirectly. A lapsed subscription or an expired plug-in license does not stop a conversion. - Built on messy sessions
- Frozen tracks come back editable. Committed tracks do not play twice. Alternate playlists arrive as lanes, and only the one you had active plays.
- One session free
- Every track, every bus, every plug-in in it, with nothing held back. Reading the report stays free on everything, before and after.
Everything it carries
Every track in order, with names reordered tracks, plug-ins staying put split .L/.R recordings as one stereo track aux inputs as real tracks fader levels, mutes, solos and pan both knobs of a stereo panner the Master Fader on REAPER’s master Pan Depth as REAPER’s pan law solo-safe, as solo-defeated hidden tracks track heights inactive and voice-off tracks, muted as Pro Tools plays them frozen tracks, unfrozen with live plug-ins committed tracks, playing once empty tracks with their mixer settings mix groups and VCA masters track comments sends at the same level, on the tracks that fed them send pan pre-fader sends, tapped where Pro Tools taps them bus outputs into the aux that takes them one bus under two names, resolved to one sends carrying audio, never stray MIDI sidechain keys, off the same track as before the key taken ahead of the receiving aux’s fader key-only buses kept off the master multi-output instruments, output by output unused channels silenced at the end of a keyed chain every insert chain, in order bypassed plug-ins bypassed, inactive ones offline settings read from the session file, Pro Tools absent EQ curves and knob positions unknown plug-ins identified from REAPER’s own scan VST3 by default, VST2 on request settings held for a plug-in REAPER does not have unreadable plug-ins, still in the slot and named in the report two- and three-way switches instrument tracks with their instrument plug-in MIDI input off where Pro Tools sends none volume, pan and mute automation faders parked at unity under an envelope automation over a stale fader value stereo pan automation on both knobs trim automation send level and send mute automation Master Fader automation automation modes, Off included plug-in automation, on the control the plug-in recorded every clip at its position and length, to the sample clip names and mutes clip gain, fixed and drawn trimmed gain lines, at the gain Pro Tools plays fades and crossfades, on their own curves a crossfade across a boundary, its length kept each side overlapping clips, the later one on top zero-length slivers losing a contested spot fade-only clips written as fades Elastic Audio warp markers, sliced per clip pitched clips, still pitched sync points as snap offsets clip groups laid out as they play alternate playlists as lanes, the active one playing comps built from several playlists orphan playlists as their own muted track notes with pitch, velocity and length notes before a clip edge, kept and silent notes past the edge, ringing in full everything outside the edges, still in the take notes shorter than a tick, muted and not lost stacked MIDI clips, playing as in Pro Tools pitch bend, aftertouch and controllers every CC from 1 to 119 SysEx MIDI clip mutes MIDI fader and pan, as events at each clip Patch Select as a program change MIDI on the beat through tempo changes the tempo map, change by change tempo steps as Pro Tools plays them the opening time signature markers with their names and colors selection memory locations as regions marker positions musical through tempo changes track and clip colors set by hand default track colors, all five coding schemes Groups coding, by highest-lettered active group channel and device coding for MIDI tracks position colors, counting the lanes left open a hand-picked color never replaced by a default clip bodies in Pro Tools’ twelve shades uncolored clips in their row tint, all sixteen rows MIDI clips in Pro Tools’ light blue the .ptx read directly — no Pro Tools, no iLok, no AAX sessions whose plug-ins Pro Tools can no longer load the sample rate folder and user names in any language audio in Rendered Files and Bounced Files missing audio named in the report audio copied into the project, on request existing REAPER projects never overwritten sample-based and tick-based tracks, each in its own timebase sessions with no clips, mixer and all empty or damaged files reported as such
103 of them, each one checkable in a real session. What does not come across is named in the report.
mollusk began as one question: can a session arrive in another DAW exactly as it was left, rather than approximately? Pro Tools to REAPER is the first pair, because it is the one that had to be proven.
More pairs follow. Which ones depends on what people ask for. If there is a conversion you need, tell us which DAWs.
Launching soon. To hear the day it is out, write to us.
hello@mollusk.audio