Bitwig is mind boggling stupid with Controller scripts.

[jeffb01]

I bought a popular midi controller (Arturia Minilab mkII) and it's incredible how bad it works with Bitwig. They have a preset for it, but the stuff that's supposed to control Analog Lab it seems also controls bitwig so there's no way to use it to control analog lab without also changing volume and stuff like that. I'm trying generic keyboard and it's okay, but when I turn a knob it changes the value but doesn't change the knob on the screen.

Now I plug it into Live lite or Logic and it works much better. I don't understand - is this very hard stuff? What I love about bitwig is it's simplicity and intuitiveness, but basic knob controller fail undermines that perception.

[abique]

You need to tell Arturia, and ask them to provide an integration with Bitwig Studio.

[jeffb01]

Well, someone made a script and it wasn't Arturia. I'm not going to contact Arturia. I like knobs, but I like using my mouse, too - so I won't use the keyboard knobs for a while. I'm just saying the implementation was soooo poor. A lot of people love their midi controllers and I understand why they leave bitwig.

[abique]

The main issue with controllers is that manufacturer don't take the time to do the integration with Bitwig.
Contacting Arturia is about making sure that Arturia understands that there is a certain amount of people using their controller with Bitwig and it would make sense spending more time into the Bitwig Studio integration.
Cheers,
Alex

[aMUSEd]

I think the real issue is the Bitwig implementation needs to be more accessible to real people rather than just developers and script gurus. The way it is currently you’re always having to beg others to help you with scripts or beholden to manufacturers who too often can’t be bothered.

[pdxindy]

I think the real issue is the Bitwig implementation needs to be more accessible to real people rather than just developers and script gurus. The way it is currently you’re always having to beg others to help you with scripts or beholden to manufacturers who too often can’t be bothered.

There is General Flexi from Moss...

[aMUSEd]

Yes, that’s the sort of way Bitwig should handle things. Something more like a list of functions with options regarding CC numbers and behaviour for each, not scripts that many of us mere mortals can’t even understand or read, let alone write.

[brownerthanu]

The Akai MPK script is very good. You might not want to hear this but I recommend selling yours and getting an MPK2*.

[pdxindy]

Yes, that’s the sort of way Bitwig should handle things. Something more like a list of functions with options regarding CC numbers and behaviour for each, not scripts that many of us mere mortals can’t even understand or read, let alone write.

Yeah, that would be sweet if all included scripts could be edited in such a user friendly manner.

So far in my 2 limited uses, Flexi works well enough that I was able to fulfill my needs without a learning curve or needing to seek help. Using Flexi, someone should be able to make their own script for whatever controller they have without needing to know some arcane scripting language.

[x.iso]

When it comes to Arturia controllers and their software, it get's quite weird in terms of midi routing. It forces you to disable some of the Arturia's controller midi port features for it to work with it's plugin properly. I'm guessing that well known DAWs have luxury of making control scripts with help of Arturia's devs.

Just recently seen one user asking how to get Spark LE working in another DAW, where there's no scripts to help. It just doesn't work out of the box unless the DAW have official specialised script

[JHernandez]

The Akai MPK script is very good. You might not want to hear this but I recommend selling yours and getting an MPK2*.

I'm using a modified version of Akai's script that I found on the web because sustain pedal didn't work among other issues. The script adds sustain pedal support, metronome toggle, and clip launcher overdub mode toggle. Still I'm not totally happy with it because of some other issues, like there's something strange/glitchy going on with the pad lights in "Drum Rack" mode for example. The idea is cool (the pads light up to show which have samples on them, color coded/on/off) and could be very useful imo, it just doesn't work right therefor it's useless and more of an annoyance. That said, it does work pretty good otherwise, plus It was made back in 2015 (If I remember right) so maybe that has something to do with the bugs, idk.

I did contact Akai, a few times, to try and get them to update the script (add some stuff, fix others) and they didn't give me much beyond a scripted response which included that if they make any changes in the future I can find it at their site in the download section. They're really good at executing that script, ad nauseam Speaking of, I should check back, but I doubt anything has changed.

I've tried to get my head around this stuff, at least just enough to fix it myself, but it's like learning another language from the ground up. That's a lot of extra work that would take away from other duties I consider priorities. Akai should supply an up to date script if they're going to continue to sell a controller with Bitwig support imo.

It would be awesome if Bitwig could (if possible) simplify this (beyond the basics like Generic Flexi offers) for us non-programmer types but given that they're a small team I'd rather see them roll out other, imo, more useful updates/features right now. It's a time/resource/priority thing, and I get that. For now we have to bitch to the controller manufactures. If they're going to offer Bitwig support, then do it right.

[jeffb01]

sigh... thanks for the responses. I would be happy just to control the Arturia software from within Bitwig. Maschine can at least do that (control maschine software, not much else). I am giving up on the dream of knobs. I would return the controller to GC, but I registered the software so I probably can't. It works well in stand alone, but hmmm. well, thanks.

[brownerthanu]

The Akai MPK script is very good. You might not want to hear this but I recommend selling yours and getting an MPK2*.

I'm using a modified version of Akai's script that I found on the web because sustain pedal didn't work among other issues. The script adds sustain pedal support, metronome toggle, and clip launcher overdub mode toggle. Still I'm not totally happy with it because of some other issues, like there's something strange/glitchy going on with the pad lights in "Drum Rack" mode for example. The idea is cool (the pads light up to show which have samples on them, color coded/on/off) and could be very useful imo, it just doesn't work right therefor it's useless and more of an annoyance. That said, it does work pretty good otherwise, plus It was made back in 2015 (If I remember right) so maybe that has something to do with the bugs, idk.

I did contact Akai, a few times, to try and get them to update the script (add some stuff, fix others) and they didn't give me much beyond a scripted response which included that if they make any changes in the future I can find it at their site in the download section. They're really good at executing that script, ad nauseam Speaking of, I should check back, but I doubt anything has changed.

I've tried to get my head around this stuff, at least just enough to fix it myself, but it's like learning another language from the ground up. That's a lot of extra work that would take away from other duties I consider priorities. Akai should supply an up to date script if they're going to continue to sell a controller with Bitwig support imo.

It would be awesome if Bitwig could (if possible) simplify this (beyond the basics like Generic Flexi offers) for us non-programmer types but given that they're a small team I'd rather see them roll out other, imo, more useful updates/features right now. It's a time/resource/priority thing, and I get that. For now we have to bitch to the controller manufactures. If they're going to offer Bitwig support, then do it right.

Hmm. Let’s work together on this. I can possibly fix it if the script is faulty. PM me.

[Alchemedia]

I believe Thomas Helzle wrote a controller script for Arturia's MiniLab which is no longer supported however he surely has insight into this issue. I have written Arturia about it also, but have yet to receive a response.

[machinesworking]

This is one of the main reasons I never switched from Live to Bitwig. So much about Bitwig I like, but the whole "roll your own scripts for even the main controllers out there" deal they have going on is off-putting. I doubt that every controller out there spends all their time on making sure Live, Cubase and Logic all have good support, I'm sure it's a two way street, and it's frustrating to me that the other companies out there are not as interested in ponying up.

Möss proves that you can do amazing things with Bitwig and Reaper etc. with his scripts for various controllers, (his Reaper script for Push 2 is amazing!) but a part of me just hates that anyone needs to do it at all.

--- Side note, I also use DP10 and they have a huge problem with this, control surface support is limited to Mackie and HUI and that's it...