Softube Console 1 Total Integration
-
- KVRist
- 270 posts since 10 Sep, 2008
I sent a feature request to Softube, who told me they would like to see this happen as well, but it's in Bitwig's hands and recommended sending them a feature request as well. I sent the request and got a thank you reply from Bitwig. I suggest you do the same.
The Console 1 would make an awesome controller for Bitwig's mixer. Fingers crossed for DAW integration.
The Console 1 would make an awesome controller for Bitwig's mixer. Fingers crossed for DAW integration.
- KVRist
- 459 posts since 28 Mar, 2014 from Los Angeles, CA
+1 I'm very interested in this too.
As a somewhat related note, does anyone know of any similar channel-strip focused controllers? I would love a hardware controller with common channel-strip operations (gain/gate, hi/low cuts, EQ, compression, etc) that would be more open (not limited to Softube's included plugin).
As a somewhat related note, does anyone know of any similar channel-strip focused controllers? I would love a hardware controller with common channel-strip operations (gain/gate, hi/low cuts, EQ, compression, etc) that would be more open (not limited to Softube's included plugin).
-
- KVRian
- 844 posts since 6 Nov, 2004 from UK
shadiradio wrote:+1 I'm very interested in this too.
As a somewhat related note, does anyone know of any similar channel-strip focused controllers? I would love a hardware controller with common channel-strip operations (gain/gate, hi/low cuts, EQ, compression, etc) that would be more open (not limited to Softube's included plugin).
Yes, Thomas Helzle and myself have been working on a awesome system just for this purpose - built around an Icon Platform M motorised controller unit and totally built for bitwig. You can assign any plugins to it, it has multiple modes (and submodes within those modes). It takes full advantage of Bitwigs macros system so one knob can be assigned to very clever processes (whatever you can imagine) for example I have one knob that is called "De-Stabilise" which gently randomises all the EQ on the track
It's as basic or deep as you need it to be. [personally i have it set to do EQ, compression, saturation-drive, transient, pan, autopan, sends, air, gating, sidechain 'pumping' and a few other mixing tools]. You can also store multiple versions of it (as each one will simply be a bitwig preset) so you could have a mixing version and also a mastering one.
Here is a short and very rough/bad video showing the basic workflow: https://drive.google.com/open?id=0B3D1h ... jNOUmJNekE
When i have a little more time i'll type up a proper description of how it works, a much better video, and a link to the script once completed so that if anybody is interested they can try it.
but to summarise, for me personally - it's a total console1 killer.
Best
Dale
-
- KVRist
- 146 posts since 4 Apr, 2005
Nice tune!askewd wrote:shadiradio wrote: Here is a short and very rough/bad video showing the basic workflow: https://drive.google.com/open?id=0B3D1h ... jNOUmJNekE
Best
Dale
- KVRist
- 459 posts since 28 Mar, 2014 from Los Angeles, CA
That definitely looks very interesting, nice work! I do have an MCU Pro, which works well for basic mixer tasks, but is a little cumbersome (slower than mouse + keyboard) in my opinion for drilling down to things (plugin settings, and basically anything other than solo/arm/mute/fader/pan/transport). What draws me to Console 1 is the 1-to-1 no-nonsense mapping. I think getting used to the script you guys are working on is probably awesome though, and once you have it down, very fast and flexible. The way you've mapped the faders to EQ frequencies is clever.askewd wrote:Yes, Thomas Helzle and myself have been working on a awesome system just for this purpose - built around an Icon Platform M motorised controller unit and totally built for bitwig.
I'm thinking of getting a MIDI Fighter Twister and writing a script for it, or prototyping something with Touch OSC, or something along those lines. It would be nice if Bitwig allowed for track defaults, so a custom channel strip preset could be placed in every newly-created track.
-
- KVRist
- 270 posts since 10 Sep, 2008
Awesome. Thanks for stepping up and doing this.askewd wrote:shadiradio wrote:+1 I'm very interested in this too.
As a somewhat related note, does anyone know of any similar channel-strip focused controllers? I would love a hardware controller with common channel-strip operations (gain/gate, hi/low cuts, EQ, compression, etc) that would be more open (not limited to Softube's included plugin).
Yes, Thomas Helzle and myself have been working on a awesome system just for this purpose - built around an Icon Platform M motorised controller unit and totally built for bitwig. You can assign any plugins to it, it has multiple modes (and submodes within those modes). It takes full advantage of Bitwigs macros system so one knob can be assigned to very clever processes (whatever you can imagine) for example I have one knob that is called "De-Stabilise" which gently randomises all the EQ on the track![]()
It's as basic or deep as you need it to be. [personally i have it set to do EQ, compression, saturation-drive, transient, pan, autopan, sends, air, gating, sidechain 'pumping' and a few other mixing tools]. You can also store multiple versions of it (as each one will simply be a bitwig preset) so you could have a mixing version and also a mastering one.
Here is a short and very rough/bad video showing the basic workflow: https://drive.google.com/open?id=0B3D1h ... jNOUmJNekE
When i have a little more time i'll type up a proper description of how it works, a much better video, and a link to the script once completed so that if anybody is interested they can try it.
but to summarise, for me personally - it's a total console1 killer.![]()
Best
Dale
-
- KVRist
- 215 posts since 27 Sep, 2004
Really cool! Could you create a new topic for this to keep us updated please?askewd wrote: Here is a short and very rough/bad video showing the basic workflow: https://drive.google.com/open?id=0B3D1h ... jNOUmJNekE
-
- KVRian
- 844 posts since 6 Nov, 2004 from UK
Cheers for the positive feedback so far ! yes would be very happy to create a new topic for this. Will do so soon.Really cool! Could you create a new topic for this to keep us updated please?
Best
DALE
-
- KVRist
- 105 posts since 8 Jan, 2017
Regarding Console One, does anyone here actually own it and use it with Bitwig? If so, can you explain a bit about the limitations presently presented by the DAW in its integration? I am gassing hard for one and have even considered moving to Studio One for the built in integration, but the reported CPU inefficiency of that DAW scares me away.
-
- KVRer
- 2 posts since 19 Apr, 2017
i'm also interested to this! I ordered my Console 1 last week. Should be in my setup really soon.totheatom wrote:Regarding Console One, does anyone here actually own it and use it with Bitwig? If so, can you explain a bit about the limitations presently presented by the DAW in its integration? I am gassing hard for one and have even considered moving to Studio One for the built in integration, but the reported CPU inefficiency of that DAW scares me away.
- KVRist
- 459 posts since 28 Mar, 2014 from Los Angeles, CA
Is there a trick to getting device selection to work - or perhaps is something broken in the 2.0 API and working 2.1? I've tried so many different avenues regarding cursorDevice and can't get it to work reliably (if using a named custom cursorDevice independent of the editor selection). selectFirst(), selectLast(), selectLastInChannel(), etc - they just don't do what they say and are unpredictable - especially selectNext() and selectPrevious(). Same with the CursorDeviceFollowMode enum... it *sort* of works, but also doesn't. I know this isn't a good explanation, and maybe the wrong thread for this - just wondering if there are some recent API fixes I'm not aware of.askewd wrote:Yes, Thomas Helzle and myself have been working on a awesome system just for this purpose
