There is a mistake that follows Scott Hansen everywhere he goes. You can find it in forum threads, in casual interview write-ups, in comment sections under gear-review videos. People assume that because Tycho sounds like it was made in Ableton Live — because the music is electronic, textured, and loop-informed — Ableton must be the instrument at the center of it. The assumption is so persistent that Hansen has spent more than a decade correcting it in interviews, on his ISO50 blog, and in technical feature coverage, and still it resurfaces. He makes Tycho records in Cockos REAPER. He has made them in REAPER since 2011. He has never recorded an album in Ableton Live, and the distinction matters far more than a simple software preference.

Understanding why Hansen chose REAPER, and why he has stayed there across six full albums and more than a decade of evolving workflow, is to understand something fundamental about how his music is made — and, by extension, how it sounds.

The Misconception and Why It Persists

The conflation of electronic music production with Ableton Live is one of the defining assumptions of the modern era. Ableton has been the default recommendation for producers of electronic music since the early 2000s, and its rise has been so thorough that for many listeners and observers, “makes electronic music” and “uses Ableton” have become effectively synonymous. The company’s marketing, community infrastructure, and educational ecosystem have reinforced this assumption at every level. Its interface, with the iconic Session View grid of clips and scenes, has become so familiar that it reads as a kind of genre signifier — you hear loop-based, textured, beat-forward music and you picture the screen it was made on.

Tycho’s music fits the listener’s profile: layered synthesizers, evolving pads, carefully crafted rhythmic loops, a dense spatial depth built from reverb and delay. It sounds like something that emerged from that familiar grid. It did not. It emerged from a timeline.

The distinction is not cosmetic. It represents a fundamentally different compositional philosophy, and the choice of REAPER over Ableton is both a symptom and a cause of what makes Tycho’s music structurally distinct from the wave of loop-based electronic production that surrounded it. To understand the gap, you need to understand what REAPER actually is, where it came from, and why a producer like Hansen found it indispensable when the software world was crowded with more famous alternatives.

What REAPER Is

Cockos REAPER — the acronym stands for Rapid Environment for Audio Production, Engineering, and Recording — was first released in 2006 by Justin Frankel, the software engineer who had previously created Gnutella and Winamp, two pieces of software that defined the early digital music landscape. Frankel built REAPER essentially as the DAW he wanted to use himself: lightweight, deeply customizable, platform-agnostic, and unburdened by the legacy code and corporate bloat that had accumulated in older DAWs.

REAPER is, by almost any measure, the most customizable digital audio workstation available to consumers. Its interface can be reshaped from the ground up using a combination of themes, scripts, and macros. Its routing architecture allows signal to flow in configurations that would require a large-format console in the analog domain — any track can send to any other track in any combination, with no preset hierarchy forcing the user into a particular workflow model. It supports virtually every plugin format: VST, VST3, AU, CLAP, and more. It runs efficiently on modest hardware. Its project file sizes are small. It updates frequently without charging upgrade fees.

REAPER is not glamorous. It does not have celebrity artist endorsements plastered across its homepage. Its default interface, before customization, looks utilitarian by the standards of competing products. The company that makes it, Cockos, has fewer than ten employees. REAPER’s marketing is essentially nonexistent compared to competitors like Ableton, Pro Tools, or Logic. Its user community has grown organically, through word of mouth and technical forums, populated largely by engineers, post-production professionals, audio researchers, composers for games and film, and a smaller but committed contingent of musicians who need more routing and scripting capability than mainstream DAWs provide.

Electronic music producers are underrepresented in that community, which is part of why Hansen’s name carries particular weight within it. When The REAPER Blog — the software’s primary community-run documentation resource — identified Hansen as “among the biggest artists using REAPER,” the distinction reflected a genuine scarcity. Most electronic musicians of Hansen’s stature work in Ableton, Logic, or FL Studio. His presence in the REAPER ecosystem is anomalous enough to be notable.

The license cost is $60 for individuals. A perpetual license for Pro Tools Studio runs nearly $800, and Logic Pro requires macOS at $199. Ableton Live Suite, the full-featured version most professional producers use, retails at over $700. REAPER offers a fully functional 60-day evaluation period before requesting payment, and it continues to function after that period with nothing but a reminder dialog. The economics of this model reflect a genuine philosophical position from Cockos: they believe in making professional-grade tools accessible regardless of budget.

That $60 price point aligns precisely with Hansen’s documented values. He has described himself as drawn to practical, anti-hype tools, and has consistently expressed skepticism of gear culture’s tendency to equate price with quality. The same man who prefers to work in a home studio rather than renting a commercial facility, who sampled his vintage Minimoog to avoid the cost and fragility of touring with it, and who eventually sold over $160,000 of studio equipment because software had reached parity with hardware — this man gravitates toward a $60 DAW with a utility-first philosophy. The alignment is not incidental.

The Migration Story: From Sonar to REAPER

To understand why Hansen moved to REAPER, you have to understand what he moved away from — and why the two most obvious alternatives, Logic Pro and Pro Tools, did not capture him along the way.

The Sonar Years

In the years before REAPER, Hansen worked in Cakewalk Sonar, the Windows-based DAW that had been part of his toolkit through the early and mid-2000s. He ran Sonar 6.2 on Windows XP, a configuration he maintained even after the rest of his setup had migrated to Mac, in part because several of his VST plugins were Windows-only and incompatible with Apple’s ecosystem.

On his ISO50 blog, in posts from the San Francisco apartment years when he was working corporate design jobs by day and making music at night, Hansen documented his setup with the specificity of a dedicated home recordist: the MOTU 828mk2 interface, the Roland RE-201 Space Echo, the expanding synthesizer collection, the Sonar sessions open on the screen. He defended Sonar at the time as his preference over Logic and Pro Tools, positions that now read as the views of someone who was not yet aware that his true preference had not yet been released.

The relationship with Sonar was always contentious. Hansen described it later as a prolonged struggle: “I had always struggled with that program, so many bugs and broken features. But it was all I knew.” He was not describing a technical tool that was failing him in the aggregate — he was describing software that occasionally worked well enough to complete projects, but that never settled into a reliable creative partnership.

The breaking point arrived with Sonar X1, a major update that Cakewalk released in 2010. X1 was an interface overhaul that changed the software’s workflow substantially. For users like Hansen who had built their entire production methodology around Sonar’s particular logic, the update was destabilizing. The problems he had lived with became unlivable when combined with an unfamiliar interface. “Sonar is out,” he wrote on the ISO50 blog. “X1 was the nail in the coffin for me.”

The REAPER Discovery

What happened next was not a methodical evaluation of competing DAWs. Hansen tried REAPER on impulse and was converted almost immediately. “I tried Reaper and after about 30 mins I never looked back,” he wrote. That immediacy is revealing. REAPER did not win him over through feature lists or marketing claims. It won him over through feel — through a workflow logic that matched how he already thought about audio.

The specific quality Hansen seized on was REAPER’s conception of the arrangement space. Where Sonar’s timeline was a fixed, hierarchical structure, REAPER offered what Hansen described as treating the software “as a multi-track tape player.” That framing is important. A multi-track tape player is the simplest possible conception of a DAW: you record material onto tracks, you arrange those tracks against each other in time, and the result is a mix. There is no secondary Session View for clip launching. There are no scenes or patterns that need to be mapped onto a timeline. There is only the tape and what’s on it.

This linear mental model appealed to someone whose musical instincts were formed by working with hardware sequencers and samplers rather than software grid-launchers. The Ensoniq ASR-X Pro that had defined his earliest production years, the analog effects chains he had been building since Sacramento — these were all linear instruments. Sound entered them, was transformed, and exited. The timeline metaphor was native to Hansen’s thinking in a way that the session view grid was not.

He immediately saw advantages that extended beyond the basic layout. REAPER’s free item positioning feature allowed audio clips to be placed anywhere on the timeline, overlapping freely, with multiple clips coexisting on a single track. This enabled what Hansen called “a hybrid sampler/multi-track workflow” that he had always envisioned but never been able to fully realize in Sonar. He could treat audio clips the way he had once treated samples in the ASR-X Pro — moving them freely, layering them, treating the arrangement as a collage. The track was not a container with a single audio file; it was a space where multiple pieces of audio could live simultaneously, interacting and overlapping.

Why Not Ableton?

The question of why Hansen did not simply move to Ableton Live — which was already the dominant software in his musical territory by 2010 — is the question that most illuminates his approach. He has answered it directly, on multiple occasions, without equivocation.

“Was never happy with Ableton,” he wrote on the ISO50 blog in 2011. “It’s a great app but it just didn’t fit my specific needs / workflow.” In a subsequent interview with MusicTech, he elaborated: “Reaper is the most efficient way to do the live show but it’s hard to find people to run it and maintain it on tour. Ableton Live is kind of the universal language everyone speaks.” The second sentence explains why he later incorporated Ableton into his live rig. The first explains why it never became his studio tool.

Ableton’s core identity is built around its Session View — the clip-launching grid that allows producers to assemble music from loops, trigger patterns in real time, and work in a non-linear, performance-oriented mode. This is an extraordinarily powerful tool for certain kinds of music and certain kinds of producers. For Hansen, it was the wrong model at the fundamental level. He told Prefix Magazine that he prefers to work linearly and thinks of his DAW as a multi-track tape player rather than a clip-launching environment. His compositions unfold as continuous narratives with careful attention to arc, dynamic development, and internal structure. The loop-launching model, which by design treats musical content as modular and interchangeable, works against the kind of compositional intentionality Hansen pursues.

This is not a criticism of Ableton or of the production approach it enables. It is an observation about fit. A hammer is not a better or worse tool than a screwdriver; both are indispensable and both fail when applied to the wrong task. Ableton’s session view is the right tool for a large portion of modern electronic music. For Hansen’s specific compositional practice, it was the wrong tool — and he was self-aware enough to recognize that.

Why Not Pro Tools or Logic?

Pro Tools was never a serious contender. It is the industry-standard DAW for professional recording studios, built for multitrack recording of live instruments and mixing, and optimized for a workflow that centers on audio rather than MIDI and software instruments. For a producer working primarily with synthesizers and effects in a home studio environment, Pro Tools’ advantages — compatibility with external facilities, the ability to hand sessions to professional mix engineers — come at a significant cost in terms of workflow flexibility and expense. At nearly $800 for a perpetual license, it is also priced for commercial studios rather than home producers. That the software Hansen uses to make records that have been Grammy-nominated costs 1.3% of the price of the industry-standard alternative is a data point that says something about Hansen’s practical, anti-hype orientation.

Logic Pro was a more natural alternative, given that Hansen had migrated to Mac for his design work and the two platforms coexisted in his creative life. But Logic, despite its integration with the Apple ecosystem and its comprehensive feature set, did not capture him. Logic has its own organizational logic, its own routing philosophy, its own conception of the project structure — and none of it matched the model Hansen found in REAPER’s thirty-minute trial.

What REAPER Gives Hansen: A Technical Account

Hansen’s enthusiasm for REAPER across more than a decade of interviews is not the generic praise of someone endorsing a product. It is the specific appreciation of a power user who has customized the software to fit his exact working style and can articulate precisely why each customization matters.

Routing Flexibility

The single most often-cited advantage of REAPER in Hansen’s interviews is its routing architecture. He has described the nesting capabilities in particular: on any given track in REAPER, you can have infinite other tracks nested within it, essentially creating a whole sub-project inside a single track of the master arrangement. For a producer who constructs compositions from elaborate signal chains — synthesizers running through reverb, through distortion, through another reverb, through delay, through compression, all before reaching the final mix — this nesting capability is not a convenience. It is a creative necessity.

In conventional DAWs, complex signal routing requires either a fixed channel-strip architecture (Pro Tools, Logic) or a clip-based model (Ableton) that imposes structural assumptions on how audio moves through the system. REAPER imposes almost nothing. Any output can be sent to any input. You can create feedback loops, parallel processing paths, and multi-stage effects chains that would require a hardware patch bay to replicate in the analog domain. For Hansen, who has spoken extensively about treating effects processing as composition rather than post-production — who stacks reverb on reverb, runs signals through distortion and back into further reverb, who creates chords from reverb tails rather than played notes — this routing freedom is fundamental to what Tycho sounds like.

CPU Efficiency and Stability

REAPER’s reputation as a low-overhead DAW comes from the engineering decisions Frankel made at its foundation. The software is written with exceptional efficiency, and it has been consistently updated to take advantage of modern multicore processors without the legacy code that burdens more established DAWs. For Hansen, who runs dense sessions with dozens of plugin instances across hundreds of tracks, this efficiency has practical consequences.

The tab feature is especially significant: REAPER allows multiple projects to be open simultaneously in separate tabs, with plugins in inactive tabs disabled so they draw no CPU resources. For the live show, where a two-hour setlist might contain forty or fifty songs each loaded with their own plugin chains, this tabbed architecture is the difference between a reliable performance rig and a crash risk. Hansen has described using this feature both in the studio — keeping several projects open and moving between them — and on stage, where each song in the setlist lives in its own REAPER tab and becomes active only when needed.

He made the switch to REAPER during the Dive sessions in part because Sonar was hitting stability limits at exactly the moment when his arrangements were growing more complex. REAPER’s ability to handle that complexity without degrading was a revelation.

Deep Customization: Macros, Scripts, and Extensions

In his MusicTech interview, Hansen described REAPER’s customization potential in practical terms: “Reaper’s efficiency is number-one. It’s a very visual programme, very extensible, very flexible.” He praised the depth of the customization available through “macros and shortcuts to scripting,” noting that these time-saving tools compound over thousands of hours of studio work.

This is the observation of a software engineer speaking to another software engineer. Hansen studied computer science before his career took its creative turn, and his relationship with software has always been more technical than most musicians’. He builds macros. He writes scripts. He configures the interface to match his workflow rather than learning to adapt his workflow to a fixed interface. For someone with that background, REAPER’s openness to scripting and customization is not a bonus feature. It is the entire point.

The practical result of this customization over time is a version of REAPER that is not quite the same software any other producer uses. Hansen’s REAPER instance reflects more than a decade of accumulated workflow decisions, keyboard shortcuts, track templates, routing presets, and plugin configurations. When he opens a new project, he is not starting from scratch in a generic environment. He is starting from a finely tuned instrument that has been calibrated to his exact creative habits.

Super8 and the Loop-Based Workflow

REAPER’s built-in looping tool, Super8, became an integral part of Hansen’s process. He demonstrated its use for The REAPER Blog in 2021, describing how he uses it both for songwriting and live performance. Super8 is a software looper — it records audio in real time, stacks loops on top of each other, and allows the user to manipulate those loops with controls that mirror hardware loop pedals. Hansen routes everything through Super8, controlling record and play functions via MIDI footswitch and using an expression pedal for reverb send levels during live looping passages.

The significance of this is that it keeps Hansen’s entire compositional chain within REAPER rather than distributing it across multiple applications. Where a producer using a hardware looper would have a physical device in the signal chain — creating a division between the hardware looping world and the software recording world — Hansen’s Super8 implementation keeps everything in one place. The loop feeds into the arrangement. The arrangement can reference the loop. The session stays coherent.

Super8 is also part of how Hansen maintains the spontaneous, improvised quality that runs through his music despite the dense layering and careful production. He builds compositions by playing and looping rather than by drawing MIDI notes into a grid. The loop is captured in real time, with the micro-timing variations and performance energy of a live take. REAPER hosts it, archives it, and integrates it into the arrangement without any translation step.

ReaLearn and Hardware Integration

In 2023, Hansen demonstrated his ReaLearn configuration for The REAPER Blog, revealing the depth to which he has integrated physical hardware controllers into REAPER through scripting. ReaLearn is a REAPER extension that enables deep, customizable MIDI mapping — essentially a programming environment for building exactly the control surface you want rather than accepting whatever a hardware controller’s factory mapping provides.

Hansen’s configuration maps a Softube Console 1 hardware controller to REAPER functions, to PSP InfiniStrip, and to additional devices through multiple instances of ReaLearn. Each controller button or knob can handle multiple functions, and entirely separate control mapping profiles can be swapped in and out during a session. The result is a mixing experience where physical knobs and faders replace the mouse for critical operations — where reaching for a compressor threshold feels different from reaching for a reverb tail length, because each has its own dedicated physical control.

“It’s just really helpful to be able to multitask with each controller, and have each controller have multiple functions,” Hansen explained. The underlying insight is that tactile engagement changes the quality of decision-making. When he is mixing through physical controls rather than a mouse, the decisions feel more like performing than programming. The Minimoog plugin sounds different — not because the audio is different but because the act of adjusting it is different. This is a position Hansen has articulated in various forms across multiple interviews: that how you interact with a tool shapes what you do with it.

This level of customization is not possible in most DAWs at the level REAPER enables it. Ableton Live offers controller mapping, but within a structure that the user cannot fundamentally reconfigure. Pro Tools and Logic are similarly constrained in how deeply a user can script custom behavior. REAPER, by contrast, exposes its API through Lua and EEL2 scripting languages, allowing users to build custom interfaces, custom behaviors, and custom integrations that are indistinguishable from native functionality once deployed.

The Hybrid Workflow: Live Instruments in a Software-First Environment

One of the persistent assumptions about REAPER — and about software-first production environments in general — is that they are best suited to purely electronic music, where synthesizers, samples, and programmed rhythms need no interface with the physical world. Hansen’s workflow refutes this assumption directly. REAPER is where he records live guitar, live bass, live drums, and the synthesizers that are played rather than sequenced. It is a multitrack recorder in the original sense of the term, and its capabilities in that domain are central to what makes Tycho sound the way it does.

Recording the Band

Since drummer Rory O’Connor and bassist/guitarist Zac Brown joined the project for Dive, the Tycho sessions have been genuinely collaborative recording endeavors rather than solo production projects with musicians added as an afterthought. Hansen tracks guitar in his Oakland home studio through a signal chain that runs from the instrument through Origin Effects pedals — the RevivalDRIVE for guitar, the BASSRIG for bass — through the analog front-end of Neve 1076 preamps and Lynx Aurora converters, and into REAPER. Drums are tracked at external facilities and brought into the REAPER sessions. The software handles all of this with the same architecture it uses for synthesizers and samples, treating recorded audio clips as items that can be moved freely against a timeline.

REAPER’s stable multitrack recording capabilities have been significant here. The early Dive sessions, which marked the transition from Sonar to REAPER, were recorded as Hansen was simultaneously learning the new software and completing a complex album. The fact that he adopted REAPER in the middle of a major project and never looked back suggests that its multitrack recording functionality was immediately and obviously superior to what he had been using.

Synthesizers and Samples Alongside Live Instruments

The challenge of a hybrid workflow — combining live instrument recordings with software synthesizers, sample libraries, and programmed drums — is that the two worlds have different technical requirements. Live instrument recording benefits from low-latency monitoring, stable multitrack handling, and reliable punch-in/punch-out capability. Software synthesis benefits from flexible MIDI routing, plugin hosting, and the ability to manipulate playback in real time. Ableton Live is optimized for the latter; Pro Tools is optimized for the former. REAPER, by design, handles both with equal competence, which is a significant part of its appeal for a producer whose music sits at exactly the intersection of the two.

Hansen has described keeping multiple projects open simultaneously in REAPER tabs — a synthesizer sketch in one tab, a completed arrangement in another, a drum session in a third. Moving between these contexts happens without closing and reopening sessions, without waiting for plugins to load, and without the kind of context-switching friction that multiplies cognitive load over long studio days. For someone who has described his composition process as iterative and exploratory — spending time with sounds, returning to them days later, building arrangements that emerge from extended engagement with raw material — this fluid navigation between projects enables the kind of patient, revisionist approach that defines how Tycho albums are made.

The Signal Chain From Instrument to Session

The physical recording path in Hansen’s studio runs from the analog instrument through an extensive analog front-end — preamps, dynamics, EQ — before reaching the converter and entering REAPER. A synthesizer signal might pass through a Neve 1076 preamp before hitting the Lynx Aurora converter on its way in. A guitar might go through the RevivalDRIVE pedal into the preamp and then the converter. Effects processing — particularly in the earlier years of the studio — might happen partially in hardware (Roland Space Echo, Strymon pedals, Ursa Major Space Station) before the converter and partially in REAPER plugins after it.

REAPER receives this material without prejudice, treating a guitar audio file and a VST synthesizer output as functionally equivalent items that can be arranged, processed, routed, and mixed by the same system. The DAW does not care whether the sound source is forty years old or a plugin installed last week. That neutrality is philosophically aligned with Hansen’s approach, which has never treated hardware and software as morally different categories but simply as tools with different practical characteristics at different points in time.

Ableton in the Picture: Division of Labor

Hansen’s current setup uses both REAPER and Ableton Live, but the division of labor between them is absolute and clearly defined, and the roles of the two pieces of software illuminate exactly why Hansen would not reverse them.

The Live Show Architecture

The critical piece of context is that Ableton entered Hansen’s workflow through the back door: as a touring solution rather than a creative one. He explained the reasoning to MusicTech directly: “Reaper is the most efficient way to do the live show but it’s hard to find people to run it and maintain it on tour. Ableton Live is kind of the universal language everyone speaks.”

This is a pragmatic observation about the ecosystem, not an endorsement of Ableton’s suitability. On a touring rig, the software must be operated by a technical team that may include personnel Hansen has not trained himself. When a touring technician needs to troubleshoot a problem at soundcheck, or when a rental company provides a replacement laptop, the software needs to be something that qualified engineers can work with without extensive onboarding. REAPER’s power is inseparable from its depth, and its depth creates a learning curve that becomes a liability in the touring environment. Ableton’s ubiquity solves that problem.

In the current two-machine live setup, Ableton Live runs on the secondary computer and functions as master show automation — coordinating the setlist timeline, synchronizing REAPER’s audio machine, driving the visual projections, and syncing stage lighting via MIDI-to-DMX protocols. It is the conductor’s score, coordinating all the other performers without generating much of its own content. Hansen has described it as functioning “essentially as a software-based pedalboard with effects chains, clip-launching and automation to perform entire shows.” Critically, Ableton’s clip-launching capability — the feature that defines its creative identity — is being used here for show control rather than music composition. The clips being launched are not songs or loops; they are cues in an automation sequence.

REAPER handles the audio. Three Apollo x8p interfaces and a UAD-2 Live Rack form the backbone of the live processing system on the REAPER machine. All backing stems, virtual instrument hosting, and soft-synth tone generation live there. The tab system ensures that only the current song’s plugins are active at any time, keeping CPU load manageable across a two-hour set. When the Ableton machine advances the setlist, the REAPER machine switches to the corresponding tab, and all plugin states recall instantly.

The Clean Conceptual Separation

What this architecture reveals is a clean conceptual separation: REAPER is Hansen’s creative environment, the place where musical decisions happen. Ableton is the deployment infrastructure that gets those decisions from the studio to the audience. He builds the music in REAPER. He delivers it through Ableton. The two applications do not compete or overlap in any meaningful way within his workflow.

The early dual-REAPER configuration — which predated the Ableton integration — actually ran REAPER on both machines during the Dive touring cycle. The migration to Ableton on the secondary machine was driven entirely by personnel logistics, not by any creative dissatisfaction with REAPER or any creative advantage offered by Ableton. This clarity matters because it corrects the implication that Hansen uses both DAWs for different creative purposes. He uses one for creation and one for deployment. The creative tool is and has always been REAPER.

REAPER as Mixing Environment

The mixing stage of Tycho’s production happens predominantly in REAPER, with Hansen’s longtime collaborator Count (Mikael Eldridge) as the primary mix engineer. The integration of Count’s mixing work into Hansen’s REAPER sessions has evolved from an initially rocky start into one of the more interesting examples of DAW-native mixing collaboration documented in contemporary music.

The Pro Tools Detour

When Count first joined the project for Dive and Hansen raised the possibility of working in a different DAW at the mixing stage — Pro Tools being the professional standard for external mix engineers — the experiment ran into immediate obstacles. The complex routing relationships that Hansen had built in REAPER did not transfer cleanly to Pro Tools’ different session structure. What made sense within REAPER’s routing architecture became ambiguous or meaningless when translated into Pro Tools’ fixed channel strip model. The sessions came back to REAPER.

As Hansen told Tape Op: “At this point it’s become a really smooth process.” Count now visits Hansen’s Oakland home studio every few weeks to mix newly recorded material directly in the REAPER sessions, without translation to any other environment. The acoustic treatment of the studio was designed by Count specifically so that Hansen could mix in the same space where he composed and recorded — eliminating the logistical friction of transporting sessions to a separate mixing facility and ensuring that the sonic character of the room is familiar to both the producer and the mixing engineer.

This is an unusual arrangement. Most professional mix engineers have their own studios, their own Pro Tools rigs, their own carefully calibrated monitoring chains. Working in the producer’s REAPER session requires Count to operate in a software environment that most of his peers would consider unfamiliar territory. The fact that this collaboration has persisted across six albums — and that it produced a Grammy nomination for Epoch — suggests that the arrangement’s advantages outweigh any friction.

The Plugin Architecture in the Mix

REAPER’s plugin hosting is protocol-agnostic and technically straightforward: any VST, VST3, or AU plugin can be loaded on any track and the routing between plugins can be configured with the same freedom as the routing between tracks. For Hansen, who is a documented “plugin junkie” with an extensive and carefully curated plugin collection, this means that the mixing stage can draw on the same tools he uses during production without any translation overhead.

The Soundtoys suite — EchoBoy, Decapitator, FilterFreak, MicroShift — lives natively in REAPER and can be applied during mixing with the same behavior it has during recording. The Valhalla DSP reverbs — VintageVerb and Shimmer — appear on mixing tracks with the same parameter settings Hansen established during production. The UAD plugin collection — 1176, Studer A800, Ampex ATR-102 — integrates through the Apollo interfaces that Hansen uses for both conversion and DSP processing.

REAPER’s automation system handles the dynamic adjustments that bring a mix to life: volume rides, filter sweeps, reverb tail manipulation, and the subtle parameter changes that translate a static balance into a performance. Hansen has described his approach to automation as tactile — using the Console 1 hardware controller mapped through ReaLearn to adjust parameters in real time during playback, then committing those moves to automation lanes. The physical act of turning a knob while the music plays produces different results than drawing automation curves with a mouse, and REAPER’s flexible recording of those physical gestures into automation data reflects his philosophy of treating the mixing process as performance.

The Cost Philosophy and Practical Anti-Hype

The $60 REAPER license is not a trivial detail in the context of Hansen’s documented approach to gear and tools. It is a data point in a consistent pattern.

Hansen built his reputation as an analog devotee — someone who owned thirty vintage synthesizers, racks of Neve preamps, Distressors, La-2As, and effects hardware worth well over a hundred thousand dollars in aggregate. The acquisition of that hardware was always defended on sonic grounds: analog equipment sounds different from digital, and the difference matters. When he eventually sold the majority of that hardware in 2023 — listing nearly 100 pieces through Reverb for a total exceeding $160,000 — it was because he had concluded that the sonic argument was settled. “If there’s a software equivalent of a tool or an instrument, I’m going to use that instead of the hardware, no matter what,” he told MusicTech.

The willingness to make that reversal — to abandon significant financial and reputational investment in hardware when the practical argument for it weakened — reflects the same sensibility that attracted him to REAPER in the first place. Hansen is not a gear romantic. He does not keep tools for sentimental reasons or for the status they confer. He keeps tools that serve his work. When the work changes or the tools improve, the collection changes with it.

REAPER’s pricing reflects a philosophy that Hansen has never articulated but consistently demonstrates: the tool should serve the work, and charging more than necessary for a tool is a form of gate-keeping that does not make the music better. The software engineering community has a tradition of high-quality, low-cost or open-source tools built by practitioners for practitioners, and REAPER sits in that tradition — made by a developer (Frankel) who wanted the software he could not otherwise find and priced for the people who needed it rather than for the market it could bear.

That Hansen’s Grammy-nominated, critically acclaimed records were produced in $60 software running on standard computers is not a counterintuitive fact about the modern production landscape. It is a confirmation of something Hansen has said explicitly: “The most basic DAWs have enough tools to make 90 percent of all music ever created.” REAPER is not a basic DAW. It is an extraordinarily capable one. The point is that the capability gap between REAPER and its more expensive competitors is not 90 percent larger for the additional cost. The returns diminish sharply. And Hansen, as someone who thinks carefully about the relationship between tools and work, made the practical calculation accordingly.

The Plugin Ecosystem Within REAPER

While REAPER provides the architecture, the sonic character of Tycho’s productions comes from the plugin ecosystem that Hansen has assembled and refined within it. Understanding which plugins Hansen relies on — and why — is inseparable from understanding what REAPER’s flexible hosting environment makes possible.

Soundtoys as First-Call Tools

No plugin developer has a deeper documented relationship with Hansen than Soundtoys. He has appeared in their official “Process” video series and described their tools in terms that go beyond recommendation: “Every single project I work on has at least one of the Soundtoys plugins being used.” More specifically: “I can’t do a track without using EchoBoy and FilterFreak… they’re equal to finding drums or a pad.”

EchoBoy functions as his primary delay and his primary reverb-tail processor simultaneously. He layers it after other reverbs, using it to sample and further process reverb tails rather than dry signals — a technique that creates the cascading, self-referential spatial textures that define so much of Tycho’s sound. He has cited EchoBoy’s Memory Man emulation mode as a particular favorite, and has described EchoBoy and PrimalTap as the most-used plugins he owns, present on every record without exception.

Decapitator handles saturation and harmonic distortion. It appears on virtually every track in some form, providing the analog warmth and gentle crunch that previously required committing to hardware distortion at the tracking stage. “I can’t do a track without using EchoBoy and FilterFreak,” Hansen has said, and Decapitator appears alongside them as a near-mandatory insert. Hansen has described EchoBoy and Decapitator as having been on every mix he has done over the past fifteen-plus years — “mandatory in a session.”

These tools run inside REAPER without any special configuration requirement. They behave the same there as they would in any other DAW. But REAPER’s routing flexibility allows Hansen to insert them at unusual points in the signal chain — after reverb rather than before it, nested inside a track folder that represents a complex multi-stage processing chain, configured as a parallel processor alongside a dry signal rather than in series. The plugin’s character is the same; the creative possibilities of its placement are expanded by the environment.

Valhalla DSP: The Reverb Foundation

Sean Costello’s Valhalla DSP plugins — particularly VintageVerb and Shimmer — form the backbone of Hansen’s reverb architecture. He runs two instances of VintageVerb as inserts on synth chains: the first a simple plate reverb with the mix level pulled to around 15% for subtle spatial context, the second a long, modulated reverb using the 1970s color mode with modulation amount and depth emphasized. The dual-reverb approach creates the layered spatial depth that is structural to Tycho’s sound — one reverb for presence, one for immersion.

Valhalla’s reputation in the plugin community rests on an unusual combination: extremely competitive pricing (individual plugins cost $50, the same order of magnitude as REAPER itself) and exceptional sound quality. Sean Costello, who writes and maintains the plugins, operates from a similar philosophy to Cockos’ Frankel — quality software, accessible pricing, constant updates, no marketing hype. The alignment of values between the tools Hansen chooses is consistent enough to suggest it is not accidental.

UAD: Emulation as Recall

Hansen’s Universal Audio plugin collection functions partly as sound-quality processing and partly as a bridge between his analog and digital worlds. The UAD 1176 Classic Limiter emulates the behavior of the hardware 1176 units that have appeared in his studio for years; the Studer A800 and Ampex ATR-102 provide tape saturation and compression that approximates what his actual tape machine would do. In an important sense, the UAD plugins are not replacements for hardware. They are archived performances of that hardware — a way of accessing the sonic character of equipment even when the physical objects are not in the rack.

Within REAPER, the UAD plugins run through Hansen’s Apollo interfaces, which provide the DSP processing that UAD’s platform requires. The integration is invisible at the user level: UAD plugins appear alongside native REAPER plugins and third-party VSTs in the same interface, behave the same way in terms of routing and automation, and participate in the same session structure. The Apollo interfaces serve as both audio conversion hardware and DSP acceleration, a dual role that makes the UAD ecosystem a practical choice for a REAPER-based workflow.

The Template and Session Architecture

Hansen’s REAPER sessions reflect a working method that he has described as beginning from loop structures rather than from completed compositions. A new session typically starts with a 16-measure loop — a synthesizer or guitar idea — to which bass is added immediately, followed eventually by strings and percussion. He mutes and unmutes elements while developing arrangement and energy flow. The session grows from this loop outward.

REAPER’s track templates allow him to have pre-configured track structures available from the beginning of a new project: tracks with routing already established, plugins already loaded, common instruments and effects chains already in place. The Soundtoys and Valhalla plugins appear on template tracks because they appear on every session; the UAD processing chain is pre-built because it is consistent across projects. Starting a new Tycho session in REAPER is not starting from zero. It is starting from a familiar instrument already tuned to play.

Project organization within REAPER reflects the same sensibility as Hansen’s physical studio organization. He has described the importance of “ergonomics” repeatedly in the context of both his hardware setup and his software workflow. In the studio, this means the most-used synthesizers are at arm’s reach, the effects pedals are arranged by function, the signal path flows logically from left to right. In REAPER, this translates to track organization where related elements are grouped in folders, track colors reflect function rather than arbitrary assignment, and the timeline is structured so that navigating between sections of an arrangement is immediate rather than involving significant scrolling or searching.

This is the practice of someone whose background in interface architecture and user experience design — his corporate career before music became full-time — informs how he thinks about any workspace, whether physical or digital.

REAPER’s Community and Hansen’s Place in It

The REAPER community is not large by the standards of Ableton’s ecosystem, but it is exceptionally deep and technically sophisticated. The primary online gathering points — KVR Audio’s REAPER forum, the Cockos forums, the REAPER Blog — are populated primarily by professionals: post-production engineers, film and game composers, researchers, and power users who have chosen REAPER specifically because they need capabilities that mainstream DAWs do not provide.

Hansen’s place in this community is unusual. He is one of the very few artists of genuine mainstream recognition who uses REAPER as a primary creative tool. The REAPER Blog’s decision to feature him twice — in 2021 for the Super8 looping demonstration and in 2023 for the ReaLearn and Console 1 configuration — reflected both the rarity of his presence in the community and the genuine technical substance he brought to each appearance. He was not there to endorse the software in a superficial way. He was there to demonstrate specific, advanced uses that illuminated capabilities even experienced REAPER users might not have considered.

The influence of this visibility on other electronic music producers is difficult to quantify but not negligible. When a Grammy-nominated artist with a fully developed sonic identity describes REAPER as “the Swiss Army knife for audio” and demonstrates a working professional’s use of it, it carries a different weight than a technical user praising the software’s feature set. It answers the question that many producers ask before committing to REAPER: can this make music that sounds like the music I want to make, at the level I want to make it? Hansen’s catalog, produced entirely in REAPER, is the answer.

The broader effect on the electronic music production conversation has been modest but real. REAPER remains underrepresented in the mainstream electronic music world, and it is unlikely to challenge Ableton’s dominance in that space in any near-term horizon. But producers who follow Hansen’s documented workflow — who read his ISO50 blog posts about the switch from Sonar, who watch the REAPER Blog demonstrations, who read his MusicTech and Tape Op interviews — have a fully documented case for why REAPER might serve their specific needs better than the default recommendation.

Hansen Among His Peers: The Outlier Position

Most electronic music producers of Hansen’s generation and profile use one of three DAWs: Ableton Live, Logic Pro, or FL Studio. These three have colonized the space with near-totality. Ableton dominates among DJs, live performers, and producers who work in loops and patterns. Logic dominates among Mac-centric producers who integrate its bundled instruments and effects into their sound. FL Studio has an exceptionally loyal community, particularly in hip-hop and bass music. The DAW landscape for mainstream electronic music is, in practice, a three-horse race.

Hansen falls outside this frame entirely. He does not use Ableton for production. He has explicitly said he was never happy with it. He does not use Logic, despite working entirely on Mac hardware. He does not use FL Studio. The software he has used for every record since 2011 is not the first recommendation that any forum post, YouTube tutorial, or production course would offer to someone making music in Hansen’s sonic territory.

This outlier position is consistent with how Hansen approaches his entire creative practice. He has never positioned himself as a participant in trends; his music has always reflected personal aesthetic concerns rather than market responsiveness. He uses a vintage 1972 Minimoog not because Moogs are fashionable but because that specific instrument has a character that serves his music. He uses Neve preamps not because they are the most technically neutral option but because their color is the color he wants. He uses REAPER not because it is the expected choice but because its specific capabilities match his specific needs.

The contrast with peers is instructive. Artists who use Ableton as their primary creative tool typically work in ways that leverage its specific strengths: clip launching, complex MIDI manipulation, real-time performance. Artists who produce primarily in Logic tend to integrate its bundled instruments heavily into their sound. FL Studio’s devotees often build from its step sequencer and Pattern mode. Each DAW shapes the music made in it, not through determinism but through the nudges and friction of its interface — the things it makes easy, the things it makes harder.

REAPER makes continuous, narrative, timeline-based composition easy. It makes complex routing easy. It makes deep customization and scripting easy. It makes the linear tape-machine workflow that Hansen has described as natural to his thinking easy. The music that emerges from these capabilities — patient, developmental, non-looping in its fundamental structure even when loops are present in its production — reflects the capabilities of the environment in which it was made.

The Evolution of DAW Use Across the Catalog

The arc from GarageBand and Cakewalk Sonar to REAPER as Hansen’s settled tool is not just a story about software preferences. It is a story about a producer finding his environment — the digital equivalent of the acoustic treatment in his studio, the ergonomic organization of his synthesizers, the calibrated monitoring chain that lets him hear exactly what he wants to hear.

The Early Years: Constraint and Experimentation

The very earliest Tycho recordings — the material that became The Science of Patterns EP in 2002 — emerged from a setup that predated any serious DAW involvement. The Ensoniq ASR-X Pro handled sequencing and sampling. MiniDisc handled archiving. The computation involved was minimal, and the compositional process was physically constrained by hardware that could hold about six minutes of audio.

When DAW software entered the picture, it was Cakewalk Sonar — chosen not for its creative fit but for its practical availability on Windows, where Hansen was working. For nearly a decade, Sonar was simply what he used: functional enough to complete projects, frustrating enough to generate consistent complaints. The records from this period — The Science of Patterns, Sunrise Projector, Past Is Prologue — were made in software that was technically adequate but never creatively aligned.

The REAPER Transition as Creative Catalyst

The switch to REAPER during Dive was contemporaneous with other significant changes: the expansion to a full band, the signing to Ghostly International, the adoption of live guitar as a central compositional element. It would be overly deterministic to say that REAPER caused any of these changes. But it is accurate to say that REAPER enabled all of them. The routing flexibility allowed Hansen to integrate live instruments and synthesizers in a single environment without compromise. The stability supported the complex plugin chains his expanding sonic ambitions required. The linear timeline model mapped onto the compositional approach he was developing.

Dive was the first Tycho album to fully realize the sound that Hansen had been working toward since Sacramento. That it was also the first album made in REAPER is not a coincidence, though it would be wrong to claim simple causation. REAPER did not make Dive sound the way it does. Hansen made Dive sound the way it does, in REAPER, because REAPER was the environment where he could finally work without fighting his tools.

Maturity and Deepening: Awake Through Infinite Health

By Awake, Hansen’s REAPER sessions had accumulated years of templates, custom routing configurations, and plugin presets. The workflow had matured from a producer learning a new environment to a producer operating in a highly calibrated instrument. The ReaLearn configurations that Hansen would eventually demonstrate publicly were already developing. The Super8 looping workflow was being refined. The tab-per-song architecture for live performance was established.

Epoch received a Grammy nomination. Weather introduced vocals and expanded the production scope. Simulcast turned the live show into a studio artifact. Infinite Health took the final step of declaring software primary over hardware. Through all of it, REAPER remained the constant — not because Hansen is sentimental about his tools but because the tool continued to serve the work. As the work evolved, the REAPER sessions evolved with it, adding new plugins, new scripts, new hardware controller mappings. The underlying environment remained stable. The music grew within it.

The stability of REAPER as a platform through this period is itself significant. Cockos has not made major changes to REAPER’s fundamental workflow philosophy across more than a decade of updates. The software has added features, improved performance, and expanded its plugin format compatibility, but the basic experience of working in REAPER in 2011 and working in REAPER in 2025 is continuous in a way that significant platform overhauls — like Sonar X1 — interrupt. For Hansen, who has invested years of accumulated workflow into REAPER’s environment, that continuity is worth more than any feature update from a competing product.

What REAPER Reveals About Hansen’s Philosophy

The choice of REAPER over more obvious alternatives is not a quirk in Hansen’s biography. It is a precise expression of his creative values, and understanding it illuminates how he thinks about making music at a level that purely discussing the music itself cannot reach.

Hansen is drawn to tools that do not constrain his thinking through their design assumptions. Ableton’s Session View is a genuinely brilliant tool — but it is a tool with an embedded opinion about how music is made, and that opinion (music is modular, music is loop-based, music is assembled from interchangeable pieces) is an opinion Hansen does not hold about the music he makes. REAPER has almost no embedded opinion about how music should be made. It is a surface on which any approach can be realized, provided the user is willing to invest in understanding it deeply.

That investment — learning a software thoroughly enough to extend it through scripts and macros, to configure hardware controllers through custom mapping, to build templates that reflect a specific and personal workflow — is itself a reflection of Hansen’s background as a software engineer and interface designer. He thinks about tools at the level of their design, not just their outputs. When he chose REAPER, he chose a tool whose design principles he could respect and extend rather than merely accept.

The anti-hype position that REAPER represents — a $60 license, a ten-person company, no celebrity endorsements, no mainstream marketing — aligns with the position Hansen has consistently held toward gear culture in general. The Tycho sound was not built by expensive tools. It was built by specific tools chosen for specific reasons, used with deep familiarity and precise intent over a long period of time. REAPER is the foundation of that approach: not the most expensive option, not the most famous option, not the option that any peer review or industry recommendation would have suggested. The option that fit, discovered through thirty minutes of trying it, and never abandoned.

“I play synths and guitar, but I’m not virtuosic at either of those things,” Hansen told Grammy.com in 2024. “The thing I’ve spent the 10,000 hours at is working in Reaper on a computer. That inspires me the most.” The sentence is the clearest account he has offered of where the music really comes from. Not from the synthesizers, which are also present in countless other studios. Not from the guitars or the reverbs or the Neve preamps. From fifteen years of accumulated expertise in a specific digital environment, shaped to his specific compositional needs, running under a $60 license that has never needed to be renewed.

That is what REAPER reveals about the production philosophy of Tycho: that the creative center of one of the most warmly regarded sonic catalogs of the past two decades is not hardware, not expensive software, not a prestigious studio facility. It is deep, patient, disciplined mastery of a tool chosen for fit rather than fame — and a refusal to mistake the price of a tool for its value.

Sources