About Marcus Sullivan

I run LogicPros as a practical Logic Pro testing and guide desk: hands-on session builds, repeatable MIDI routing tests, mix chain breakdowns, and blunt notes about where Logic's workflow falls short of what Apple's documentation implies.

Who I am

I write the Logic Pro guides on this site under the name Marcus Sullivan. The work is deliberately methodical: open a blank session, build the signal chain from scratch, stress-test the MIDI routing, push the mix bus, and write down what collapsed. I do not use Apple-supplied benchmark numbers or studio folklore passed off as technique.

Born: September 7, 1985, Boston, Massachusetts.

Education

B.M. in Music Production & Engineering, Berklee College of Music, Boston, 2007. Concentration in recording technology and post-production workflow. Followed by a professional certificate in Audio Post-Production from the Berklee Online faculty, completed 2013, covering DAW-agnostic mix theory and stem delivery standards.

Work history

2007–2011 — Junior Recording Engineer, Dimension Sound Studios, Boston. Tracked live sessions — primarily indie rock, jazz, and spoken word — on a Pro Tools rig, with Logic used as the offline editing and MIDI mockup environment. First systematic exposure to the gap between what a DAW's manual describes and what actually happens during a multi-track overdub session.

2011–2015 — Staff Producer & Mix Engineer, Authentic Form & Function (music production agency), Boston. Delivered finished masters for podcast networks, advertising agencies, and independent artists. Standardised the studio's internal Logic Pro template library, cutting session setup time from forty minutes to under eight. Switched the studio's primary DAW from Pro Tools to Logic Pro X in 2013 after a six-month parallel-running evaluation.

2015–2020 — Freelance Producer, Mixer & Educator. Clients included independent musicians, podcast production companies, game audio studios, and a Boston-area film school where he ran a semester-long Logic Pro elective for undergraduate students. Began publishing workflow notes publicly in 2018 as an alternative to the tutorial content he found imprecise or untestable.

2020–present — Full-time writer and publisher, LogicPros.net.

What I do here

I write guides on recording, MIDI production, and mixing inside Logic Pro — currently covering nine workflow areas — against a consistent standard: every technique described on this site has been tested in a live Logic session with real audio or MIDI data before a word is published. Guides update when Apple ships a meaningful Logic version update.

The testing method

Every technique, setting, or plugin chain covered on this site is built inside a live Logic Pro session on a current-generation Mac Studio running the latest stable Logic release. Test sessions use real recorded audio — not stock loops — and MIDI sequences of at least 32 bars with multiple instrument tracks firing simultaneously to expose latency and routing issues that clean demo projects hide.

Where a guide covers a third-party plugin, I own a licensed copy. I do not review plugins from trial versions with watermarked output. If a technique only works cleanly above a certain buffer size, or breaks when a specific Smart Control is mapped, I say so in the guide with the exact setting.

How I make money

Some pages on this site carry affiliate links. If you purchase a plugin, course, or piece of gear through one, I receive a commission. That is the standard model, and it funds the work. What is less standard: guide rankings and recommendations are finalised before any affiliate relationship is established. No plugin developer sees a draft. No product has moved position in a roundup because of a commercial arrangement. If that changes, it will be disclosed on this page before it appears anywhere else on the site.

How I score

The LP Score used in roundups is a weighted average: 35% practical usability inside a real Logic session, 25% documentation and preset quality, 20% CPU and latency performance at 128-sample buffer, 10% value relative to Logic's built-in alternatives, 10% developer update cadence. A plugin with a beautiful UI that adds 12 ms of latency at tracking buffer sizes scores accordingly.

What I will not do

• Publish a guide on a technique I have not personally tested in the current Logic version.
• Quote developer-supplied benchmark numbers or latency figures. Those are marketing conditions, not session conditions.
• Move a plugin or course up a roundup because the developer offered a discount code or review copy.
• Fabricate reader results. Every quoted outcome on this site comes from a real forum thread, YouTube comment chain, or direct email, and the source is named or easy to locate.
• Write as if I am the kind of producer I am not.