Most importantly, you guys fixed inconsistent metering on percussive sources bug! I've been waiting for 6 months and started losing hope, but you guys did it! Love you!
For those asking how to save the mappings, rather than having to remap manually each time. On bitwig and ableton, and other daws, you can save your console 1 as a preset. Better still, you can save it as a group preset combined with your fave eq and distortion plugins pre mapped. Then you can load the whole group at once. The thing is, I'm not sure how this is going to work with mulitiple instances on different tracks in your project?
for Reaper users you can use ReaLearn / Helgobox extension to dynamically map controllers to specific plugins. For instance you can say "(x) midi message from (x) controller input / midi port are mapped to (x) parameters if a plugin exists on the selected track named (x). For example, if there is a plugin named "Pro-Q3" on the selected track the controls will automatically pick up whatever parameters you mapped. you can also transform the input and feedback for the controller to make it behave as needed in case it is not specifically designed to control a particular type of parameter (for example a knob controlling a set of switches). super powerful and really nice to be able to now do this with C1OSD running.
Total game changer...these are the best controllers on the market...hands down...loving mine :) I am not interested in 3rd party plugs though as i dread the remapping.
@@ToneChaser-13 Afraid it looks like a 'no' for now at least. I just updated and tried what is shown in the video - no 'midi CC' option appears, and then saw Todd's comment on his own channel today where he says: "As of now, the MIDI Fader mode and the mapping to midi modules is for Mk III units. But the change[log] you are referring to is that I believe you can put your Mk I or II units into a MIDI mode as long as a Mk III unit is running."
Thank you for the info@@synthshedmkIII came out a few months after I bought Mkii. If I knew I would have waited a few months and get the MkIII. I really hope they keep providing support and updates for mkii as well and that the unit does not become obsolete with time.
@@ToneChaser-13 I feel you brother, we're in similar boats - believe it or not, my mk2 console and fader arrived in the post literally the same day they announced the launch of mk3 console (facepalm)... but then I realised I couldn't justify the cost of the newer models, so stuck with it and so far pretty happy with the way updates have continued - although I'm sure I'll upgrade eventually.
@@synthshed it’s all on purpose, as they kept midi CC out of the picture as long as they could. Until SSL took the lead, suddenly MidiCC is available. But indeed they try to push mkI and MKII users to upgrade. I didn’t buy any Softube plugin since ages and will not , this is the result as a consumer.
Hi, has anyone gotten the new MIDI-CC feature to work in the latest Windows Bitwig Studio? In my case the knob does not map to the one in the plugin...
Can we actually have some DAW based tutorials. Becuase I can't get plugin mapping to work in Cubase or Studio One. However CC learn functions for controlling synths and sampler controls, works fine.
@@alanevansmusic-yt In Pro Tools, as far as I know, the individual plug-in must allow for MIDI mapping. Certain products such as the Model Series products or FabFilter products do allow for this.
Only thing i've managed to get working in Cubase is mapping QC (quick controls) but not for plugins. MIDI learn works, but mappings are lost if you change patches. As for plugins with MIDI learn (like Pro Q4) the plugins don't seem to receive the input from the MK3. Seems a bit pointless atm. Be more useful to have full DAW integration and be able to map all controls to what ever daw functions you desire. So far pan and volume are only things it can control in DAW (without console one plugin) even these two controls are mot re-mappable. Finally, be better if we could drag and drop to reorder the CC mappings in the Console software. To organise them how we want.
How do you save the midi map after you’ve done it on logic cause I just did it on logic saved my session save the preset and reopen my project and I had to re-map all over again
Interesting - Nektar cs12 for a half of the price of Console1 can do almost anything.... So Softube, is it possible to do something similar? I bought Console1 mk3 and Fader MK3 3months ago, but i cant use it as it should, just because of software... pretty strange thing for that price.
I have the same question, because if you have to do this from scratch every time it seems a less attractive option. Maybe you can save each configuration as a custom preset....
When i started Cubase 12-14 it shows a message in MIDI Remote Script Console (about Console 1 and Fader) - TypeError:cannot read property 'bintTo' of undefined (line319)(for Cons1) (line 234)(fo Fader) What it could be?
A bit of an unfortunate way of implementing MIDI on Console 1 mk3. Why not a global mode where we wouldn't loose complete sections of console when we want MIDI control over things? Now instead we have to keep juggling sections and presets. You basically created a clunkier worse solution than a single button toggle for a global midi mode with hard coded CC's. Still, the MIDI mode is very much appreciated as we've been asking for this almost a decade.
They keep adding features to mk3 users and leave mk 1 and 2 users hanging, even if it’s technically no problem to give these features to all CUSTOMERS. I think this is very disappointing and invaluable behavior. Why do you expect people to buy every new iteration of a product you come up with? I’m done with softube
It’s been 8 years since the last iteration was released. If you want gear that stays relevant for longer than that, digital controllers aren’t for you. It’s not as if they have made the controller unusable as some other companies would have done. They just aren’t going to spend their time providing more features for older model because that would be terrible for business and the company would seize to exist. I think you should recalibrate your expectations for what is essentially a software company.
@@astrofishtix see I would keep buying their plugins if features are also available for mkII. now, I will not only stay on MKII but I’m not buying anything from them. I don’t see how you can call that suitable for business. Just the form factor of mkIII bothers me
@ sorry I am the client and end user , not my job , my job is to choose to spend my money or not. Seems you know nothing about the end user, that’s why many businesses end up failing.
It is worst than that, you can use it now in OSD if you have Core Suite but they will remove it. So you will have to get new update and Core Suite and then never update it again.
Took 10 years but it’s finally here! Thanks for MKII users! so nice from you! No i‘m kidding.
I hope this is the start of a trend. There are SO many plugs that I *really* wanted to get working on Console 1. This could be MASSIVE
Most importantly, you guys fixed inconsistent metering on percussive sources bug! I've been waiting for 6 months and started losing hope, but you guys did it! Love you!
However, still no frequency analyzer when DAW control features are turned OFF - please fix this too! :)
Bro, You make the best software now your hardware is exemplar. Keep up the good work. My Console 1 is the most memorable thing my parents ever got me.
For those asking how to save the mappings, rather than having to remap manually each time.
On bitwig and ableton, and other daws, you can save your console 1 as a preset. Better still, you can save it as a group preset combined with your fave eq and distortion plugins pre mapped. Then you can load the whole group at once. The thing is, I'm not sure how this is going to work with mulitiple instances on different tracks in your project?
Would be cool to see a video tutorial of this, especially if we get an answer to that question at the end.
for Reaper users you can use ReaLearn / Helgobox extension to dynamically map controllers to specific plugins. For instance you can say "(x) midi message from (x) controller input / midi port are mapped to (x) parameters if a plugin exists on the selected track named (x). For example, if there is a plugin named "Pro-Q3" on the selected track the controls will automatically pick up whatever parameters you mapped. you can also transform the input and feedback for the controller to make it behave as needed in case it is not specifically designed to control a particular type of parameter (for example a knob controlling a set of switches). super powerful and really nice to be able to now do this with C1OSD running.
.. which is exactly why a simple one button GLOBAL MIDI controller mode would have been a lot better in my opinion.
Think Softube just buried the competition. Great job on listening to users and continuing to develop the system! ❤
In Studio One you can use the MIDI Learn function. There you can assign all of the MIDI CC's to each plugin and Studio One saves it globally. Perfect
Total game changer...these are the best controllers on the market...hands down...loving mine :)
I am not interested in 3rd party plugs though as i dread the remapping.
It doesn’t get any better! Thx Softube ❤
Can we name the parameters on the hardware display, and save mappings for later? (I’m on Ableton Live)
Ya but can I save them and reload them in different projects use later.
Save it inside your project template, pre-routed.
Using this with synth instruments are going to be fun too
Sold... ordering one now.
will the title of the knob also be shown on the screen? for complex plugins this might be essential to remember which knob does what.
Is there shortcut to toggle betwen Console 1 mode and Midi Mode??? Pressing Shift-Settings and then dial and click "ok" everytime feels to slow...
Holy cow. Softube you’re smashing it. Still rocking my mk2 console/fader combo though - does the update work for the older units too?
I really hope they haven't forgotten about their loyal mkii users.
@@ToneChaser-13 Afraid it looks like a 'no' for now at least. I just updated and tried what is shown in the video - no 'midi CC' option appears, and then saw Todd's comment on his own channel today where he says: "As of now, the MIDI Fader mode and the mapping to midi modules is for Mk III units. But the change[log] you are referring to is that I believe you can put your Mk I or II units into a MIDI mode as long as a Mk III unit is running."
Thank you for the info@@synthshedmkIII came out a few months after I bought Mkii. If I knew I would have waited a few months and get the MkIII. I really hope they keep providing support and updates for mkii as well and that the unit does not become obsolete with time.
@@ToneChaser-13 I feel you brother, we're in similar boats - believe it or not, my mk2 console and fader arrived in the post literally the same day they announced the launch of mk3 console (facepalm)... but then I realised I couldn't justify the cost of the newer models, so stuck with it and so far pretty happy with the way updates have continued - although I'm sure I'll upgrade eventually.
@@synthshed it’s all on purpose, as they kept midi CC out of the picture as long as they could. Until SSL took the lead, suddenly MidiCC is available. But indeed they try to push mkI and MKII users to upgrade. I didn’t buy any Softube plugin since ages and will not , this is the result as a consumer.
Does it remember the settings? It would be great to have the plug-ins already mapped to start with.
How can this be implemented in Cubase? What settings are necessary in Cubase and in the console software?
Can't figure it out in Ableton either?🙃
Please tell us, which DAW was used in this Video. Can I realise this in Logic Pro?
Hi, has anyone gotten the new MIDI-CC feature to work in the latest Windows Bitwig Studio? In my case the knob does not map to the one in the plugin...
To see the plugin as with Todd is that plugin in the same slot?
Can we actually have some DAW based tutorials. Becuase I can't get plugin mapping to work in Cubase or Studio One. However CC learn functions for controlling synths and sampler controls, works fine.
Agreed!! I just tried it in Pro Tools with no luck. It's a great idea though if it works across all DAWs.
@@alanevansmusic-yt In Pro Tools, as far as I know, the individual plug-in must allow for MIDI mapping. Certain products such as the Model Series products or FabFilter products do allow for this.
@@ToddUrban Thanks Todd. I now remember seeing a midi map selector on some plugins in PT. It's been a long time since I've used that feature.
Same thing in Cubase!
Only thing i've managed to get working in Cubase is mapping QC (quick controls) but not for plugins. MIDI learn works, but mappings are lost if you change patches. As for plugins with MIDI learn (like Pro Q4) the plugins don't seem to receive the input from the MK3.
Seems a bit pointless atm. Be more useful to have full DAW integration and be able to map all controls to what ever daw functions you desire.
So far pan and volume are only things it can control in DAW (without console one plugin) even these two controls are mot re-mappable.
Finally, be better if we could drag and drop to reorder the CC mappings in the Console software. To organise them how we want.
Do you put the plugin in the same slot as the console plugin?
I can't get the MIDI CC to work with Cubase. Am I missing something? How do I make the exact settings in the settings? Softube
We are all waiting!)
How do you save the midi map after you’ve done it on logic cause I just did it on logic saved my session save the preset and reopen my project and I had to re-map all over again
More of an “unlock” than an update seeing C1 always used midi info, but a welcome unlocking nonetheless.
Nice you can kinda make things into modules.
Excellent!
How to use Midi CC Feature with Console 1 in Bitwig ?
Interesting - Nektar cs12 for a half of the price of Console1 can do almost anything.... So Softube, is it possible to do something similar? I bought Console1 mk3 and Fader MK3 3months ago, but i cant use it as it should, just because of software... pretty strange thing for that price.
Does the midi mapping also remain saved?
I have the same question, because if you have to do this from scratch every time it seems a less attractive option. Maybe you can save each configuration as a custom preset....
Can I change the MIDI CC number as my own preference?
When i started Cubase 12-14 it shows a message in MIDI Remote Script Console (about Console 1 and Fader) - TypeError:cannot read property 'bintTo' of undefined (line319)(for Cons1) (line 234)(fo Fader) What it could be?
Does it work on Console 1 mkII?
Yeah!!! Does this work on MKii ?
Gonna have a play later on a MK2 and test it out - I’ll feedback later
@@Jeff_Brannon Please:)
Not sure it works for now. they definitely will update it for MKii
i tried to activate it trough the main plugin and it asks me to buy Core Suite LOL
I sort of got it working for MK2 but i had to demo the Core Mixing Suite. My next issue how to get it actually working in Studio One
I tried and can't seem to get it to work in this way in Reaper.
Does the fader mk3 support Mackie control universal, in other words, can it be used as a generic DAW mixer controller?
ex) Reason
I think I saw the word MCU in the function list on the fader side, if I'm right, please make a video about this!
Thank you
Do you need the Console 1 Core mixing suit for this to work?
You need MKIII unit. Won't work on mk1/2 even with core suite.
How do we save a particular mapping to every plugin?
Your DAW should be able to memorize the mappings (didn’t try) and in Console one plugin as presets
@@carlosp.1846 Got it now and it's awesome!
Nice, but it do not work in Logic Pro...????
Panning to the Right on Fader MK3 still panning to infinity value (Cubase). Cool update, but its not working, until Softube show us how)))
Why isn't it working in Pro Tools?
Not working in Cubase
A bit of an unfortunate way of implementing MIDI on Console 1 mk3. Why not a global mode where we wouldn't loose complete sections of console when we want MIDI control over things? Now instead we have to keep juggling sections and presets. You basically created a clunkier worse solution than a single button toggle for a global midi mode with hard coded CC's.
Still, the MIDI mode is very much appreciated as we've been asking for this almost a decade.
J’avais demandé ça il y 5 ans sur la console one mk1 je m’étais fais envoyé … par le sac de softube…
Je détestes ces versions mkiii
They keep adding features to mk3 users and leave mk 1 and 2 users hanging, even if it’s technically no problem to give these features to all CUSTOMERS. I think this is very disappointing and invaluable behavior. Why do you expect people to buy every new iteration of a product you come up with? I’m done with softube
It’s been 8 years since the last iteration was released. If you want gear that stays relevant for longer than that, digital controllers aren’t for you. It’s not as if they have made the controller unusable as some other companies would have done. They just aren’t going to spend their time providing more features for older model because that would be terrible for business and the company would seize to exist. I think you should recalibrate your expectations for what is essentially a software company.
@@astrofishtix see I would keep buying their plugins if features are also available for mkII. now, I will not only stay on MKII but I’m not buying anything from them. I don’t see how you can call that suitable for business. Just the form factor of mkIII bothers me
Sorry, if you think it’s trivial, you know nothing about software development!
@ sorry I am the client and end user , not my job , my job is to choose to spend my money or not. Seems you know nothing about the end user, that’s why many businesses end up failing.
It is worst than that, you can use it now in OSD if you have Core Suite but they will remove it. So you will have to get new update and Core Suite and then never update it again.