For those of us who waited for UAD SSL being mapped to C1:
Nothing good happened unfortunately .As was mentioned earlier - each section is like adding an instance of UAD ssl. The result - you’re going to have overheated signal (imagine this happening on 30-40 tracks) By turning the drive knob fully to 0 it’s a bit better.
But the worst part is - when you adding filters too - you are going to have phase problems as I could hear from my test with the drums multitrack. Eq section by UAD also have low end roll off. When combined with Softube filter it’s ok. But when UAD ssl filter engaged there’s double hi pass I guess. (SOLVED) So there’s just 1 or 2 sections that could be used if you want to be as close to UAD ssl sound but Softube’s drive should be used more carefully then. Tested in 96khz.
The plugin UAD on its own sounds better definitely. And I know “better” is very subjective but I can hear more headroom and less hyped highs and a better transient smack in a pleasant way.
Don’t know what’s the issue to properly map sections. Like say ssl 360 link does (besides metering data)
Maybe the c1 itself brings the problem when used like container for different sections. Don’t know. So I hope that helps for someone.
Anyway - love how ssl9000k sounds by Softube

Is anyone else experiencing an issue where the hardware volume control suddenly locks at 100% down on the Console 1 MK3?

When using the hardware Volume control:

1. The indicator lights stop working.
2. Although the DAW fader initially moves as expected, when I release or touch the hardware control, the fader abruptly jumps to 100% down.

The pan control exhibits similar issues:

1. The pan indicator lights remain stuck at 50% (center).
2. When I interact with the hardware pan control, the DAW pan immediately jumps to hard left.

Restarting the system, or replacing the plugin - does sweet F.A to solve this. I’ve reinstalled the (latest) software four times so far, but regardless of the software or firmware version, I continue encountering issues with the unit not functioning smoothly.

I guess you're using the Softube's SSL 4000E drive along with the UADx SSL 4000E sections. If that's the case then I would suggest to turn it off because it will change the sound of the UADx SSL 4000E quite a lot, even at zero.

I haven't heard any phase problems with multi-tracks but the SSL 4KE filters are known for having a strong color and behavior. Right now I'm mixing a song with a few percussion sets that were mic'ed and maybe it's because the SSL filters are working on all of them that I'm not hearing anything wrong.

After mixing 5 songs with the UADx filters, EQ and comp ( and gate on a couple of tracks), turned on and working, I'm very happy with the results and the clients love the songs. In fact, since I know the UADx SSL 4000E actually sounds way better when driving its preamps I am cranking the C1 input close to 0dBFS, something I don't do with any other plug-in because it sounds bad.

Maybe it's because I know that channel strip too well and I've been using it since UA released it like 10 years ago or so that I'm really enjoying it in C1.

By the way, the line preamp is not so "colored" as the mic preamp so you can abuse it a bit more.

Thanks for sharing! Yes, the drive knob doesn’t fit with UAD ssl I’m trying to figure out what sections to load to fully satisfy my ears! The idea of cracking the input - I’ll try that, thanks)

If I just use UADx SSL E eq in my console 1 eq section and have the drive at the end of my chain, that would still affect the sound? On the preamp, I usually use the UAD Studer on alot of things, its first in the chain, would that change the sound of the SSL alot?

Yes. The drive section from Softube will affect the sound drastically. But if you turn it off as was said before it will be the closest as possible but still a bit more coloured than the UAD ssl on its own. Depends on how many sections you’re using from UAD SSL.
By using the Studer it’s typically like running your signal through out of tape recorder to the desk. It’s pretty much like it was back in the days. LUNA is replicating that kind of approach too. It’s ok.

Yes, the sound will change but that's not bad at all because when mixing you just have to put the pieces together to get the sound you're after. Don't overthink it, do whatever it takes to get the mix done.

soo can someone confirm, is the UADx SSL plugin doing weird stuff with C1 or not?

I’ve tested once again and hopefully there’s no issue with phase. So , I guess I srewed something up when first did it (maybe I hit the phase flip button and didn’t noticed) And I have to apologise.
The main problem stays the same - cpu usage.
I loaded up 15 instances of c1 with filters, Eq and compression of UADx SSL in LUNA and I’ve had pops and clicks right after. Something around 60-70 % of usage.
Did the same with C1 Softube ssl and there’s barely 10 % hitting. But the UADx SSL itself doesn’t eat so much cpu.
So at least in LUNA I have to pass on C1 with all the sections of UAD engaged. Maybe 2 or 1 section will be okay.
But if it works for you - great 👍

My LFC is achieved with

Console 1
Faderport 16
Monogram Creative Console
X - Touch Mini
Stream Deck XL

It took me a few months of tweaking, programming Cubase MIDI Remote Manager (that idea by Steinberg was a game changer for me)

If you saw me operate these controllers as sngle intergrated system I’m sure you’d be impressed.

It’s a very slick smooth work flow. Each controller is used to it’s strength and then any weakness is taken up by the next controller.

The sidedhowfx profile for Cubase Pro 14 on a Stream Deck XL is genius imho.

Have not seen any comments about the fader parameter spill. Appreciate Softube adding this. I like the idea but feel it would be faster if we could hold Param+ section buttons on the Channel to spill sections to the fader.

The current implementation seems fiddley to navigate since you have to toggle the Param button again. If you want to target another section you have to shift+page and jump the faders repeatedly to get to where you want. Not saying to remove the current combos but adding Param+ Section would make it better.

Also, using the spills brings to light how loud the faders are when going to 0. Seems like they could be tuned to not slam against the stopping point so hard.

I recently moved from my older Windows 10 computer to a new Windows 11 computer. Resolved the first C1 issue a couple weeks ago with the help of this forum. There's one more lingering issue Softube's turtle-paced support has yet to provide anything useful beyond asking to update the software, which I previously told them everything was already up to date. Instead of wasting more time with their support, I'll pick everyone's brain here.

Quick rundown:
OS: Windows 11
Latest version of Softube Central and Console 1
Console 1 MkII
DAW: Reason 13
Problem: Say I have 15 tracks and load C1 onto each track, the C1 hardware only reflects a fraction of those tracks. They're also not in order. If I save the project, exit Reason, re-open Reason and re-open the project the C1 hardware again randomizes which tracks it sees in no logical order.

I experienced this same problem a few years ago after a Console 1 update. Rolling back to a prior version fixed it. Unfortunately, I don't recall which version I rolled back to at that time. I'm lucky if I get one response per week from Softube support, although it doesn't seem like they're comprehending the problem.

Any thoughts or suggestions? My current workaround is to load C1 to every track as normal, deal with whichever tracks assign to the hardware, mix what I can, print those changes to new tracks, remove the old, re-apply C1 to the remaining tracks until they show up on the hardware, rinse and repeat. Not very efficient but I don't want to stall on these projects.

This is the same issue I had when I got my Console 1 Mk2 a few months ago and was also using Reason 13. I can have a song open and all the C1 channels are working correctly and then when I reopen the song later only some of the C1 tracks will be activated. I usually have to save the settings in the plugin and keep reopening the plugin til it registers and then choose the preset I had saved.

I ended up switching to Cubase Elements and use all my Reason Extensions as a Reason Rack Plugin. The issue still happens here and there on Cubase but not as much and only a track or 2 unlike Reason where it could be half or more of the C1 tracks inactivated. I'm enjoying Cubase but I've been a Reason user since v4 but when I got the Console 1 I knew this was gonna be a main piece to my studio. If Reason ever fully supports Console 1 then I may go back but it seems like they dgaf about it cuz it's been out forever now.

I've been using use Console 1 and Cubase for quite some years now and never ever had a quirk like that. Not to say there's no quirks, but those are different.

Just wanted to share my experience. I hate that some people are having issues, but I’ve had console/fader Mk2 and now Mk3 versions. No issues with either.

When you had the same issue, it was wiping out your settings per track on top of it all? I haven't checked if that happens to mine yet. To get through existing projects, I've been mixing as much as I can for the tracks that load on C1, print to track and keep moving to avoid losing ground. Saving the settings per track to reload would be too annoying to deal with.

No plans to move to another DAW. I know C1 and Reason can work together since I've used C1 for years without issues. Might be a matter of finding the right combination of versions for this to work. My current ticket with Softube support is a month old at this point. Last week's request was to send them a project file which I did. They responded today ignoring their prior request to say a new update has been deployed and to try that. Not expecting any difference but we'll give it a go later. Years ago when this same situation happened, I had to roll back to an older version of Console 1, not use the latest and greatest.

Just read the Sound on Sound review of the new MkIII Fader.

It claims that you MUST have an instance of the C1 plugin on a DAW track for it to be controllable with a fader.

This can’t be true surely?!

I use my Fader MkII with zero instances of C1 in my sessions…

Direct DAW control (at least for Cubase) was a fairly recent new feature...maybe the review was written before that update.

This!

Arrived in the post yesterday…

You don’t need to have it on a track to control cubase with the latest update. Make sure to also update cubase.

Yep, this is great for the DAWs supported (Cubase, Logic and Pro Tools). Would like to see this for Studio One and Ableton Live. Sucks needing to insert on every track. Ableton in particular does not make this easy to do. Also, you don't get VCA fader control in Studio One. The manual says Cubase gets accurate DAW output metering instead of "approximated" output levels which is also important. On top of that, you can't use on Live Drum rack pads, you can only get one instance per track. It's a nice system but Fader is not so useful to me with the DAWs I use due to the limited features.

I am seeing so many mk2 for sale. It is worth getting one? The price diff between an mk2 and mk3 is 60% if not more.

I think the console-1 system is great. I think the new version has some features that are wonderful compared to the MK2, but the MK2 prices are super low compared to what we paid for them.


Hopefully this is ok, just in case. This is mine up for sale.

https://www.thegearpage.net/board/in...fader.2625331/

Hello, in case one of the faders get stuck , how do you recommend cleaning it? apart for moving it up and down a million times .... thanks

Yes it is a good price, I'm thinking about getting a mk2.

How is the integration of the mk2 with Pro Tools now? Has that also been updated? Or does Direct DAW mode only work with the mk3? It's been surprisingly hard to get a straight answer. Does HUI mode work with the old mk2, or only the mk3? In other words, can you control faders, track selection, mute, solo etc in Pro Tools with a mk2?...

This is my biggest concern. As an Ableton Live user, I really can't stand a clunky integration. The way its integrated into cubase now sounds excellent. If it was like this in ableton, I would have already bought a Fader MK3. I honestly kind of want to use the fader just as a standalone volume fader and not getting into the plugins or ecosystem at all. At the very least, I want that to be an option, and potentially upgrade to a full console one setup at a later date.

Is their any plans to offer this clean integration with ableton without needing a plugin on every track. Is this going to happen ? is ableton refusing it on their end for its own sell of push and their own controllers ? its so stupid if this is the case and I bet it probably is. I already own a push 3 standalone anyways.

Anyone know the status of softube and ableton and these controllers ?

And ….. now software is no longer working again. And before that can’t use c1 with protools before 10.24.

I throw my hands up. I’ll revisit some other time. Smh.

Unfortunately I wouldn't know. I have Logic Pro and Studio One. I will say that personally I haven't had any issues with Console-1using either logic or Studio-one.

Thank you. Yes I do use Logic quite a lot so that's good. I also want to use the old faders in Pro Tools though. The old form factor actually suits my set up far more. Like the poster above said, I really just want to use the faders and am not all that concerned with the ecosystem.

Does anyone else know about Fader mk2 integration with Pro Tools? Are all the new Direct DAW Pro Tools things only for mk3's?