Tag Archives: Ableton Push

Customizing The Music Studio Furniture & Hardware

A lot of updates have been happening to my music studio setup. Hardware’s been rearranged and devices have changed. One of the things I haven’t covered yet here is how I built my studio desk. So in this article, I’ll be talking about how I set the desk up, installed or removed music studio hardware and keep everything working together.

New audio interface, the FCA1616

I wrote before about replacing my M-Audio Oxygen49 with a Roland A-49. The original audio interface, the Tascam US-322, that used to sit to the Continue reading Customizing The Music Studio Furniture & Hardware

Reason: Using Ableton Push As A Universal Controller

This is gonna’ be the most detailed review / talking piece about using the Ableton Push with Reason you’ll ever find. So let’s start this by asking; what is a universal controller? A universal controller is a physical hardware device (“USB controller”) that allows you to control every aspect of a device. A universal controller typically won’t have as many buttons as the virtual device they’re controlling, they’ll have different “banks” of parameters and, if that isn’t enough, different “pages” of banks.

This is what the Ableton Push has. It can control eight things at a time per bank and has access to eight banks at a time, with additional (practically unlimited) pages of banks. So, using this method, a universal controller like the Push can control as many different buttons, knobs, sliders and whatever a device has.

In short, the purpose of Continue reading Reason: Using Ableton Push As A Universal Controller

Reason: Custom PusheR Remote Maps

(Updated 04/29/2019) I created some custom virtual rack device remote map code for RetouchControl’s PusheR and PusheR2 software, which allows the Ableton Push (versions 1 and 2) to be used as a universal controller in Reason.

In order to control a virtual device in Reason (i.e. Synchronous) with PusheR and the Ableton Push universal USB hardware controller, the remote map of PusheR needs to have code written for that virtual device.

There’s some devices RetouchControl didn’t include remote maps for (originally or still currently). I ended up creating some myself (i.e. Hydronexious) or I fixed / improved existing devices (i.e Thor). This page exists for Continue reading Reason: Custom PusheR Remote Maps