Mk3 user here. Console quits working since updating to OS Sequoia. Latest softube firmware and software. Softube customer service totally useless. Sent ticket w/sreenshots and detailed info couple of times, no response. Hate this product.

And Sequoia is listed by Softube as a supported OS?

from System Requirements for Console 1 and Console 1 Fader

There is no 15 Sequoia seen there.

User error.

Thought so.

To be fair though, for such an expensive and high-end product, it's kind of meh to still not support Sequoia. It's not like it was released yesterday...

Double checked - yes, I overlooked the system requirement. My fault. But the customer support did not even mention this in his reply. All my other gear, interface, sound card, midi keyboard plus all my plugins work. Only my 800 € controller collects dust. Sequoia was released 5 months ago btw.

In the audio world the autumn is indeed yesterday. Who making audio updates the OS before 6 months in (unless they buy a brand new machine released after, in which case there are no options)?

It's soon 4 months.

Yeah. It's not like anybody ever has to buy a new computer...

I think the audio software industry in general, with a few notable exceptions, is very bad at supporting new hardware/OS:es in reasonable time. But I guess that's where you end up with the "new product sales is supposed to cover support of old products forever" model.

It's not that I don't like working on the Mac Studios we have in the studio, but having OS, DAW of choice and plugins I paid for work together at all times is a real PITA which is why personally I would choose a Win PC everytime. The amount of trouble we had just waiting for everything to be flawlessly Silicon compatible was unbearable. On my PC at home, I never had any second where something audio related wouldn't work the way I want to.

You do you. I chose mac for the exact same reasons. Nothing audio related ever work really well on Windoze i m h o. (Also, audio under Rosetta2 still ran much better than on any of my windoze machines, even though they were both newer and possibly in theory faster than my M1 Air). I really thought windoze would have caught up a bit, but stuff like hot-swapping USB audio/midi interfaces with software running still had me reboot the computer to get windoze to find the interfaces again. Or, trying and failing to have daw + utility programs access the same audio and midi ports at the same time. So, done with that.

This also doesn't make me change my mind. Even if windoze did actually work as well, I STILL think the audio software industry, and the business model of having new products pay for all support on an increasing number of older products, is bad at staying up-to-date and supporting changes and improvements in hardware/OS etc. It's not just limited to new OSX releases.

I had started to trace the problems that I've been having with Console 1 OSD that I'd mentioned recently here. Softube got back to me, but still can't diagnose the issue. I'm still having the problem after updating to the latest version of software, and without fail, the OSD shuts off when I close out Studio One. It never did this before the update. Has anyone else had this issue, and if so, how did you solve it?

Well, every ecosystem is different and there's many variables involved. I'm not arguing against Mac. They are wonderfully designed and immensely powerful. I just shared my personal experience of having had zero audio related trouble on my Win PC the last couple years compared to loads of headaches and problems on the studio Macs - including Console 1.

Mac seems to swing from being absolutely rock solid and perfect to then being really fussy, then perfect again. I don’t have any desire to use windows because I just don’t like the “feel” of it, but I do wish Apple would stop their constant “widgetization” of their OS! I do love how my iPhone, iPad, and Mac all work together, but I still try to keep my interface on all of them as basic as I can.

I do love what digico did with windows (still windows xp!)- it barely has anything running, and boots right into their console software. I remember back in my windows xp days that you could download very stripped back OS versions, or do it yourself.

At the end of the day of course, whatever works for someone is the best choice, and I don’t know anyone who liked or didn’t like a song, commercial, movie, or whatever other end product due to the computer and apps used to create it.

I’m quoting your post, but this isn’t directed at you in any way specifically.

I can safely say though that console 1 and fader were the biggest game changers for computer audio for me. My Apollo rack is up there as well in terms of sound and I/O, but in terms of workflow console 1 makes mixing on a computer so much more fun and I feel much more connected to the things on which I’m working. I’m still on channel mk2 and fader mk1, and am very happy with them, but at some point I’ll move to the newer ones, at least for channel at first, to take advantage of the better feeling knobs and encoders.

Oh, and I don’t know why, but I only just discovered a few days ago that I can control unison devices in UA Console when in Apollo Central mode. I’m late to that party, but that’s REALLY nice!

I used I/O bit uninstalled. Wiped all things Softube.

Restart.

Re installed the older version. Then installed the latest over it.

NOW this crap is working.

Some great news-- with version 2.5.98 being just released, I updated to that one, and Console 1's OSD (on screen display) is no longer closing out where it shuts off for no real reason, and can only be re-activated by re-starting the computer. I have mentioned this to Softube; so far, so good.

If this can help anyone (now, or in the future when searching), this is the change log:

"Fixed an issue that could cause the On-Screen Display to crash in Compact mode when removing a Console 1 plug-in instance (for instance by removing a track).

Changed so that the MIDI CC modules are not possible to load unless a Mk III HW unit (either Console 1 Channel Mk III or Console 1 Fader Mk III) is connected since modules will not work otherwise."

I think that my issue was related to the first "on-screen display to crash in Compact mode when removing a Console 1 plug-in instance". My OSD was closing out randomly, as mentioned, when removing some plugins/ tracks, but I couldn't diagnose it. When I close Studio One, perhaps it was being perceived as the same as removing a track for whatever reason?

Do the midi mappings get saved on the device or just in the daw session?

On C1C mk3, they are just like any other device loaded in C1. The setup is saved per channel/plugin in the daw, and they gets saved with the preset, if saving as a C1 preset. Pretty much how you would expect it to work, given how the C1 in general works.

Hoping to get some help from the forum since Softube support has unfortunately been unresponsive. I've been using Console 1 MkII for years with Reason. Everything has worked very well.

Fast forward to last week. I bought a new beefed up laptop and migrated everything over.
Windows 11 fully updated
Softube central fully updated
Reason 13 fully updated
Console 1 OSD running and connected

On the new laptop, Console 1 is auto detected by Reason as usual. I can load the plugin to multiple tracks but none of them assign to a track on the hardware. I can open the OSD by clicking the button on the controller and navigate through settings from the hardware. There seems to be a disconnect between the hardware and software. I see there's an option to manually assign tracks. Nothing happens when I try to do so. I can use the plugin within the DAW which defeats the purpose of the hardware.

I've got a new project that's moving at a slower pace since I can't mix with Console 1. Really hoping for some assistance if anyone has ideas. Aside from the OS difference, I've matched every setting in Reason between the two laptops and still no luck. Unsure what I could be missing or if the problem is unfortunately that the new laptop is running the latest version of everything.

Have you installed the vst2 or vst3 plugin on your new machine?

VST3 is installed for all of my Softube plugins, including Console 1.

EDIT: Double checked and found VST2 was auto-installed from Softube Central. In Reason, I disabled Console 1 VST2, left Console 1 VST3 enabled and we're back in business. Huge thanks to you! I should have posted here rather than getting the silent treatment from Softube support for a week.

Yes softube installers sadly install all kinds of unwanted formats...

Is there a way to uninstall only VST2 while keeping VST3 in place or is it all or nothing with Softube's installers? I tried uninstalling to reinstall and it doesn't give any option to specify which format(s) you want to install/uninstall.

I think you could just delete the vst2 files in the vst2 folder.

copy them to a backupfolder if you want to be safe

So guys, where are we now at here in 2025 with all the complaints about phase smearing and aliasing?

I work at 48Khz.

I really like the workflow of Console 1 - it's great but I don't want to hurt my audio - it sounds ok to me but perhaps younger ears than mine are hearing stuff higher up?

I can't really hear anymore 14Khz +

Thanks

14khz...lucky duck. 12.5khz for me

I'm working at 88khz because Console 1 doesn't seem to use that much more cpu at that high of a sample rate. Probably due to the oversampling etc....

Not noticing any aliasing or smearing compared to the first console 1 version I used to have, I'm quite sensitive to it, if it's there it's not a problem this time around

Great - thank you for that feedback.

Does anyone know when softube typically releases updates?

still waiting (hoping?) for them to support the UAD SSL EQ on the new console one before I grab one and sell my UF8

cheers

ps. good to know the aliasing/smearing issues ive read about are not an issue anymore on the new one

It was only an issue for those who preferred to play video games with plugin doctor instead of making actual music.