Menu
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New media
New media comments
New resources
Latest activity
Media
New media
New comments
Search media
Resources
Latest reviews
Search resources
Misc
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
Labrish
Nalij
Jinaral kantent
Running a big analog desk inside a Pro Tools room
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Queen, post: 90549, member: 27"] O-Motion writes console moves straight into Pro Tools automation playlists or Logic Pro lanes, so the desk's automation now lives inside your session file. That sounds like a small plumbing detail. It is not. For forty years, console automation lived in the console, on its own storage, in its own format, with its own rules about what could be edited and how. Backing up the mix meant backing up two separate things and hoping they stayed married. Now a fader move made on the surface arrives as a playlist you can trim, copy, nudge, and undo with the same keystrokes you use on a plugin. Your archive strategy already covers it, because your archive strategy already covers the session. [HEADING=2]Console automation stops being a separate system[/HEADING] The practical gain is editing. Analog automation used to mean rehearsing a pass until it was right, because fixing one moment often meant redoing the region around it. Handing those moves to the DAW turns them into data you can shape after the fact. It also means one timeline. Plugin automation, volume rides, and console parameter changes all sit against the same bars and beats, so a tempo change or an arrangement edit drags everything with it rather than leaving your analog moves stranded three seconds late. The catch worth respecting is that only the control data moves. Audio still runs through the desk, so the DAW knows where the compressor threshold went, not what the compressor did to the sound. Committing a printed stem remains the only way to make an analog decision permanent, which is what people actually mean by [B]a hybrid setup that splits work between desk and DAW[/B]. [HEADING=2]A single bay of faders can leave the analog world[/HEADING] The FOCUS key hands any eight-channel bay over to DAW control while the rest of the surface stays analog. That is a more useful idea than a global mode switch, because the way you work rarely divides neatly. Picture a mix in progress. Forty channels of analog sitting exactly where you left them, and the bay under your right hand temporarily driving track volumes, sends, and transport for a vocal comp. You edit, you fly the chorus, you flip the bay back, and nothing about the analog path moved while you were away. Older hybrid rooms solved this with a separate control surface bolted to the side of the console, which meant two sets of faders, two sets of habits, and an argument about desk space. That was the compromise [B][URL='https://goldmidi.com/community/threads/ssl-crowned-odyssey-its-flagship-analog-console.75866/']SSL's latest inline flagship[/URL][/B] was built to remove. [HEADING=2]The prep happens before anyone walks in[/HEADING] SSL splits the software into three parts. O-Setup handles console configuration, O-Session holds projects, presets and snapshots, and O-Overview gives you channel visibility and metering. The important word is offline. You can build the routing, the labels, and the starting configuration away from the room, then load it when the session starts. On a comparable SSL surface, a full session recall lands in three to four seconds. Multiply that across a facility running three clients a day, and the argument stops being about sound quality at all. Snapshot filtering, added in the V2.0 software, decides which parts of the console a snapshot touches. That matters more than it sounds. A snapshot that restores everything is useless when you want the monitor mix to stay put while the record path changes, and filtering is what turns a blunt recall into a working tool. None of this removes the one decision the DAW cannot make for you. With 16-track busses feeding the recorder and returns landing back on channels, you still have to choose what goes to disk already shaped and what stays adjustable. Recall makes the desk repeatable, not reversible, and a printed track carries whatever the preamp and the compressor did to it. The engineers who get the most out of these rooms are the ones who decide that early, out loud, and then stop renegotiating it at two in the morning. [/QUOTE]
Insert quotes…
Name
Post reply
Home
Forums
Labrish
Nalij
Jinaral kantent
Running a big analog desk inside a Pro Tools room
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top