A Hidden Parameter in Softube Console 1?

I found a (somewhat) hidden parameter in Softube Console 1 and I'd like to share it with you.

[@RasSparrowOfficial]

Nice! Thanks for the tip!

[@vdub4216]

Wow! Great find! Wondering if this is available in Live also? Hmmm... will wait until I get my console 1 to try. Thanks :)

[@SupaMarioJCS]

WOOOWWW! Thats crazy will add that parameter to my template thanks for that!!

[@G_handle]

Weeellllll. I'll do you one better! (Maybe one and a half) So first, that WIDTH control is the same as on Console 1 Fader, and what that means is that it isn't merely the bonus feature of making stereo tracks wider than they are. When the knob is Centered, there's no effect, normal "STEREO". Turn to the Right, and the value goes up from 1-100% then "WIDE". Turn to the Left though, and the value shows Frequencies from 5Hz to 24,500Hz then "MONO" What that means is that you can use the knob one of two ways: A) To artificially widen stereo tracks, beyond the speakers using MS Voodoo. (Spreading say a pair of overheads wider than the actual drum room.) B) To make any frequencies below the value shown, Monoized. As the Hz value goes up, everything below it will come equally from the left and right speakers, from the dead center. It's a bit counterintuitive at first, but makes perfect sense after a minute. Both of these 'Tricks' are old Mastering Techniques, and discovering them there, hidden behind "Invisible Knob #1" is a sweet thing. Thank you for poking around and finding it!

[@thomas-mavian]

Yeah, I'd actually rather use DrMS for widening, tons more control and you get more "center" left when you collapse the listening to mono. Going down on the other hand is very handy, used to have bx_control V2 for controlling the low end width but having it in Console 1 is one less plugin to add. Good one, if you're in Reaper. Isn't that "wet" thing standard for all plugins you add in Reaper? There is no parameter in Studio One with that name, not that I can find anyway.

[@G_handle]

@@thomas-mavian That's the Mathew Lane one? Haven't used it, but heard its great. There are plenty of options out there, but this ones baked in and within arms reach when I need it. And it's free, kinda. The Free bx_control is what I used also, though not enough. It's always one more step for me, exactly as you say. But it definitely tightens up a mix when you go through all your stereo tracks and give em all a V shape. So yeah, having the collapse to mono, on a Console 1 knob, is something I think I'd use more often with C1 Fader, which I'm still considering. But I'm glad I can play with it now.

[@G_handle]

So upon further inspection, you are correct. Reaper is adding the [Bypass] and [Wet] from Reaper's plugin header to the plugins list of parameters. Never noticed it there before. Always used it from the Header. So not an "Invisible Knob #2". Just the usual Reaper bonus feature. Still love it though. Console 1 IS however adding a second "Bypass" control in addition to the "Bypass Console 1" that is triggered by Shift+Phase Invert. It behaves differently, cutting off the processing, but not like the other OR like the Reaper Bypass. The Reaper Bypass pops in and out, the other two do not. Still sussing that out.

[@thomas-mavian]

@@G_handle You are correct, Mathew Lane DrMS, love it!

[@thomas-mavian]

@@G_handle Thanks for confirming my suspicion, that is one of Reapers strength, dry/wet control on everything! Gotta look at that second bypass as well.

[@G_handle]

Good Find!

[@thehitchslap]

Great job!!!!

[@carlosp.1846]

Great find ! You have to assign the knob on each track? or it keeps its functionality when you change track?

[@thomas-mavian]

I actually have it mapped as a "user mapping" on my Faderport (you can let it map out the parameters automatically or you can set up your own) so I have it available even though I haven't mapped it to a knob in Studio One. I should have mentioned that in the video. To answer your question: yes, you would need to map it to every single track. However, you could make an Instrument+FX preset and just map it once.

[@carlosp.1846]

Thomas Mavian ah yes good idea loading the preset instead of the plugin itself as I don’t have faderport. Thanks

[@NoQualmsTheArtist]

Hold shift and turn the input knob to adjust width. You may need to upgrade your software to see it.

[@thomas-mavian]

Yeah, but believe me, almost 18 months ago it was hidden 😎

[@NoQualmsTheArtist]

@@thomas-mavian that makes sense.

[@hansdorenstouter3813]

Was it described in the update info? I downloaded the manual yesterday but that wasn't updated...

[@NoQualmsTheArtist]

@@hansdorenstouter3813 here. kzbin.info/www/bejne/oKi4no2NepmBY5o

[@RadiAsian]

thanks excellent. I will try and implement this in Nuendo

[@darkmaer]

I don have console 1 or a fader port, but an looking to expand my hardware and console 1 is going to be a must, but how do you like it in conjunction with the fader port. Trying to decide if fader port would be more logical. Being as I am a studio one user, or if the softube fader would be better being that it will be more integrated with console 1. I'm liking the idea of fader port having the ability to map it's faders to instrument parameters. Anyway, thoughts?

[@thomas-mavian]

Oh, good question! And a tough one to answer, but I'll try. I started with the Console 1 and it is a real workflow booster, one knob = one function. It takes almost no time to learn where the different knobs are and I would buy a new in an instant if it would break. After a while I added the Faderport16. Now, I could probably be without it and still go on but I really wouldn't like to be without it for a longer period of time either. And as you say the ability to map parameters from various plugins to whatever fader is great. I mostly map the parameters I really need so that I'm ok with just one page of faders so to speak. If I had to choose one or the other I honestly don't know. Since the Console 1 also gives me another choice of sounds (in a ver nice way!) I think I'd take the Console 1 before the Faderport16. And Console 1 gets another plus because it can control UAD-plugins as well. I really like to have both. Sorry :-P

[@adoniramlipton]

I'm sure the OP has already made a decision but for anyone else seeing this... I also use Console 1 and FP16 on Studio One and it's a killer combo.

[@BladesMusic]

Pretty interesting. Haven't played with it, but took a look and sure enough, there it is. Nice find. It's one of those things that poking around will lead you to and about which you have to wonder 1. How did I not see this before, 2. How come they didn't make it more available in their other product and 3. How can I use this? Thanks for posting!

[@carlosp.1846]

Blades Music point 2. I guess they hide it so you are prompted to buy Console 1 Fader which has the dedicated button for this feature. And they can’t take it out from the software as both console use the same. So they hide it.

[@BladesMusic]

@@carlosp.1846 It's always about the sale, right! :) Really, I don't know how or when I might use this, but it is nice to know that it is addressible anyway. I have a FaderPort 8, so it's pretty unlikely that I'll be getting the Console 1 Fader. Interesting that this feature is available, nonetheless.

[@G_handle]

@@BladesMusic Weeellllll. I'll do you one better! (Maybe one and a half) So first, that WIDTH control is the same as on Console 1 Fader, and what that means is that it isn't merely the bonus feature of making stereo tracks wider than they are. When the knob is Centered, there's no effect, normal "STEREO". Turn to the Right, and the value goes up from 1-100% then "WIDE". Turn to the Left though, and the value shows Frequencies from 5Hz to 24,500Hz then "MONO" What that means is that you can use the knob one of two ways: A) To artificially widen stereo tracks, beyond the speakers using MS Voodoo. (Spreading say a pair of overheads wider than the actual drum room.) B) To make any frequencies below the value shown, Monoized. As the Hz value goes up, everything below it will come equally from the left and right speakers, from the dead center. It's a bit counterintuitive at first, but makes perfect sense after a minute. Both of these 'Tricks' are old Mastering Techniques, and discovering them there, hidden behind "Invisible Knob #1" is a sweet thing. Thank you for poking around and finding it! Howeverrrrr...... Because you Did find it, I too dug around in Reaper, and found sitting right next to it "Secret Knob #2" That knob's name is WET. And he turns out to be a Wet/Dry knob for the entire Channel Strip! You already have a Parallel Dry/Wet for the Compressor module, allowing for easy Parallel Compression. This allows you to Parallel Process the entire Plugin. Can you say Parallel EQ? How about Parallel Saturation? Maybe take a Vocal, crank the Input gain, Take the Drive to 10, pull back on the Output Volume, get those vocal cords sounding like a ten pack a day smoker, then crank the knob all the way to Dry. Now blend in just a few % of that Grit, just enough to give it some edge and some bite. Oh yeah, and you can AUTOMATE that one knob for effect, crunching up just the lyrics that need it! So not only do you have a WIDTH control hiding in there... There's also a WET/DRY lurking beneath!

[@jeffmcbeff6084]

Yeah, i discovered this parameter like you, i work with Reaper, but it dont saves the Parameter Savestate. Means, when i save my Project in Reaper and open it again, the Width Parameter is in starting position again >> "Stereo" on all Instances. How to Fix this problem? is this in Studio One the same ?

[@thomas-mavian]

I noticed this as well after a while. The only way to get it to "stick" is if I put it in the automation lane and give it a value. But then I'll need to change the automation if I want to change it and it all became "not-so-easy-to-use" anymore.

[@jeffmcbeff6084]

​@@thomas-mavian With the VST3 version it dont savestate only the "Width" parameter, the rest works like a charm. With the VST2.4 it savestate the "Width" parameter but you dont have "Autonaming", full "Dawcontrol" anymore. Writing a Automation seems the best compromise, like you said. ;) Or using a 3rd Party Plugin for this. Softube want to force the customer to buy the console fader because of one little feature. Softube really pisses me off.

[@thomas-mavian]

@@jeffmcbeff6084 interesting, I need to check with the VST2 and AU versions as well. I went back to using other plugins for width control. I think Softube are one of the better companies and since they didn't say that this function exist I wouldn't hold it against them.

[@thomas-mavian]

@@jeffmcbeff6084 this works exactly like you describe on a Mac, both the VST2 and the AU version of Console 1 saves the width parameter in the project. But no automatic naming. Interesting...