Skip to content Skip to footer

Switch DAW: Logic to Pro Tools to REAPER (Pt 3)

In 12 months I’ve managed to revolutionize my workflow, twice. Part 3 of why I migrated to REAPER is about open architecture, development cycle, efficiency.

Simone Silvestroni's avatar

Part 1

  1. Cost
  2. Multi-platform
  3. A different workflow

Part 2

  1. Customization
  2. Community
  3. Stock plug-ins

Part 3

  1. Open architecture & development cycle
  2. Efficiency

Benefit 7: Open architecture & development cycle

Updates and fixes are relased regularly. Dan Worrall’s video series also confirmed the agile way the software is maintained, with maximum attention to its community.

In a video about ReaComp (stock compressor plug-in), he pointed out a slight defect in the range of a slider. This is what happened, just a week later:

Screenshot from a YouTube comment section showing people praising Dan Worrall and Cockos for a prompt update after a minor defect was pointed out by a user REAPER compressor received a prompt update after a minor defect was pointed out on YouTube

Benefit 8: Efficiency

The last point would need a whole other slew of posts to be properly explained. I’m going to make a simple list of the main aspects, explaining the major improvements that REAPER brought to my personal workflow.

The newest version opens in about 4.5 seconds on my 6-year-old laptop. Rendering, editing and pretty much everything I do in REAPER is lightning fast.
The installer is around 15 megabytes, while the single executable application on macOS is 130 megabytes. Logic is 2 gigabytes, while Pro Tools is around 3.5 gigabytes.
A project can include entire other projects, allowing to divide big sessions in chunks.
Render Matrix
Add many regions to a render queue, which can be taken care of later. Also: render presets, great for exporting mono/stereo versions with a multitude of different customizations.
Powerful batch editor
Together with the previous two points, it adds to the reasons why REAPER is the go-to DAW for game sound designers.
Save different mix versions and recall each one with the stroke of a key.
Region-based non-destructive FX processing
In addition to the “normal” track-based one.
Record FX on the way IN
This feature translates to an early commit to a sound, if someone wishes so.
Tabbed sessions
Open multiple full-on sessions, each in its tab, and switch back and forth. Copy and paste regions, tracks and more from one to another.
Quick built-in edits
Reverse, peak normalize, loudness normalize, you name it.
Actions list
Open it with the keystroke ? then filter by typing in the search box and find anything in seconds. The list includes Cockos’ own scripts, third-party add-ons and all the personal custom-created ones.
Markers and regions
Jump to sections, move entire blocks around, make selections, split, loop certain areas, export and render. Super flexible and powerful.
Automatic colors
It might sound minor, however to me this is a godsend. I always color-code everything: tracks, items, markers and regions. I used to do the same in Logic and Pro Tools, but in REAPER it’s a different world. An SWS extension allows to set rules for automatic colour-coding of everything, based on several patterns. Now, whenever I name a track with a specific pattern, the track (and its items) get the colour I want. Same for markers and regions. Huge timesaver.
Integrated support for writing and reading advanced metadata. Also useful when it comes to importing markers from other sessions or from other DAWs.
Pretty much every single window in REAPER can be docked. The position on the screen can be customized too. Coupled with the amazing screenset functionality, this allows the software to morph into whatever is the best interface for the task.


Working with others

Switching DAW is a dreadful task for many. If you work within a team of people where the flow is based on Pro Tools, that’s something to consider. I’m flexible on this topic, and love to learn and improve my skill set. I currently work by myself, and a majority of my current collaborators uses Logic. Nonetheless, I managed to get a relatively old and cheap Pro Tools 12.5, which I had to install on Windows 10, as that version isn’t supported after macOS High Sierra. I decided to keep it for session legacy and compatibility with clients.

My current setup

I currently use REAPER for almost everything, writing music, producing, editing audio, batch processing, mixing, stem rendering, mastering.

It’s an unbelieavably powerful, fast and flexible piece of software, I regret not having tried it sooner.

Bonus: other software

I do plan to try REAPER and Logic, or Reason, in sync: if the ventilation system of my machine doesn’t catch fire, I’d like to have the opportunity. For anything related to restoration, advanced audio editing and clean-up I set iZotope RX as my default external editor. In this case, the workflow is:

  • right-click on an audio region
  • edit in external editor
  • fix it in RX
  • save it and go back to REAPER
  • done

Thanks for reading. I leave you with a video by American composer, producer and sound designer Nick Peck, who explains in 18 minutes his 11 reasons to switch from Pro Tools to REAPER:

Related topics