Bitwig

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 05, 2014 8:35 pm

EDIT 09-10-2015

The code in GitHub master is ONLY compatible with 1.2 - 7+ beta. For the 1.1.x branch use the zip from my web site below.

Hi,

It has been a long road of bugs and other various setbacks for these scripts.

I have spent the day refactoring and getting the basic transport and pad work in for all 3 controllers.

Some notes right now, the pad section is under construction as we speak and you can play on the pads but, things are in flux.

I am announcing this right now since all the features listed in the wiki are tested and stable and the list will only be added to. As is stands you can control most of Bitwig's transport and such, take a look at the wiki.

I have a lot more implemented under the covers in code, but since i actually have the controllers to test with, I am not releasing this as alpha for those that want to use their Maschine to control whats listed.

The displays on the Studio and MK2 work, along with the encoder knobs.

Native Instruments made it really hard for me to transition a lot of the code from the Push4Bitwig script, so I have been inventing new ways to set modes and views etc.

Notes as of now and I will update this as I go;
- Beta 1.1 required on 1.0.15
- Windows it seems has a bug in the driver for pad lighting, this has been a pain in the ass, NI is looking at it.
- Mikro pad lights don't really work right now but play notes.

I have scales and other things working but I am creating a way to toggle modes without using NI's knob pages, pain in the ass.

I will update this post as I add features, thanks!

Latest Stable release zip archive;
http://www.teotigraphix.com/bitwig/maschine

Here is the GITHub repo;
https://github.com/teotigraphix/Maschine4Bitwig

Here is the GITHub url for the always beta zip;
https://github.com/teotigraphix/Maschin ... master.zip

Here is the GITHub url for the wiki function list;
https://github.com/teotigraphix/Maschin ... ction-list

Peace,
Mike

c-wave · Post by **c-wave** » Wed Nov 05, 2014 8:41 pm

Thanks Mike,
Do you plan to produce a quick tour video?
C-Wave

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 05, 2014 8:48 pm

c-wave wrote:Thanks Mike,
Do you plan to produce a quick tour video?
C-Wave

Oh yeah definitely but these scripts are basic for what I have documented in the wiki.

I spent all day getting the basics of all 3 working perfectly. i will then get the Scene, Pattern and Pad mode working correctly and documented.

I purposely left a lot of what the Studio and MK2 can do right now because I am changing how modes and views work.

I will keep this thread updated as a go, its a lot of work. But, i have all 3 controllers abstracted so now its just implementing and re-enabling features that already exist

Mike

Ogopogo · Post by **Ogopogo** » Wed Nov 05, 2014 8:59 pm

Nice. Doesn't seem that long ago to me that you said you were starting work on these. I'd be interested in a demo video as well since I don't have Maschine but I'd still like to see what you can do.

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 05, 2014 9:04 pm

Ogopogo wrote:Nice. Doesn't seem that long ago to me that you said you were starting work on these. I'd be interested in a demo video as well since I don't have Maschine but I'd still like to see what you can do.

Well to be fair I think that was back in the summer.

This was extremely complicated in the the work I did on the Push didn't apply as far as modes and views because of the way Machine's Knob pages work.

On top of that I have the Studio and there is a Pad light bug on Windows, works perfect on Macs (another setback).

I have the MK2 and Mikro now so it all got going. Things will fly now because I have all three scripts working on the exact same code base with some minor teaks.

Right now I am creating the template for the MK1 for users to try, although I don't have one, the code I have written should work pretty much like the MK2 does right now. I will let them tell me what doesn't work.

Mike

Ogopogo · Post by **Ogopogo** » Wed Nov 05, 2014 9:12 pm

Oh, lol. Well that's my memory for you. Good thing we have you in the community.

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 05, 2014 9:59 pm

Ok, for those with the Maschine MK1, I put a template in the controller-editor directory and added a control.js file.

I DON NOT HAVE this controller so its shooting in the dark. If there are users out there that want this controller supported in this framework, you must test this script based on the wiki MK2 entries and tell me if things don't work.

As I add features to the rest of the controllers, the MK1 will get them automatically, so you would need to keep testing.

Other than that i can't help unless somebody ships me one.

Mike

taoyoyo · Post by **taoyoyo** » Wed Nov 05, 2014 10:01 pm

Hey Mike,

Just trying this out now (using the Mk2 controller at the moment).

One question about the documentation...

Several of the commands say to use the 'Shift' button in conjunction with another button/knob... 'Shift' always brings up the Midi Mode menus so I'm wondering if 'Shift' in this case might be set to another button?

I was able to control tempo with just Tempo + Jog-wheel and Tap-tempo with just Note Repeat... (no 'Shift' needed ) but could not get Metronome working (or Toggle Clip Launch Overdub, Tracks with Step < >buttons)

Really looking forward to seeing how this one develops!

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 05, 2014 10:14 pm

HAHA,

Oh yeah I forgot that in the docs, Shift;

Studio = [ENTER]
MK2 = [ENTER]
Mikro = [MAIN]

Sorry about that!

Yeah I have the session and pads working, those will be turned on in the next couple days.

Mike

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 05, 2014 10:29 pm

taoyoyo wrote:Hey Mike,
I was able to control tempo with just Tempo + Jog-wheel and Tap-tempo with just Note Repeat... (no 'Shift' needed ) but could not get Metronome working (or Toggle Clip Launch Overdub, Tracks with Step < >buttons)

Really looking forward to seeing how this one develops!

Ok, I just fixed the Tap tempo and < > arrows for track nav, there were two bugs from when I switched things, I tested and they work per docs now. (latest git)

Let me know now if anything doesn't work as the docs say. It should.

Mike

taoyoyo · Post by **taoyoyo** » Wed Nov 05, 2014 10:51 pm

TeotiGraphix wrote:HAHA,

Oh yeah I forgot that in the docs, Shift;

Studio = [ENTER]
MK2 = [ENTER]
Mikro = [MAIN]

Sorry about that!

Yeah I have the session and pads working, those will be turned on in the next couple days.

Mike

No worries, I wondered about that 'Shift' thang!

Was wondering how set on using 'Enter' as the 'Shift alias'? It's a bit tricky to execute... do you think 'Grid' or 'Erase' might be an easier reach? (although you might already have plans for those!)

taoyoyo · Post by **taoyoyo** » Wed Nov 05, 2014 10:52 pm

TeotiGraphix wrote: Ok, I just fixed the Tap tempo and < > arrows for track nav, there were two bugs from when I switched things, I tested and they work per docs now. (latest git)

Working for me with the latest git too! Thanks.

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 05, 2014 11:35 pm

taoyoyo wrote:
TeotiGraphix wrote: Ok, I just fixed the Tap tempo and < > arrows for track nav, there were two bugs from when I switched things, I tested and they work per docs now. (latest git)
Working for me with the latest git too! Thanks.

- Fixed Encoder knob change and C, F, G and H group arrows now navigate as arrow keys. (were previously working)
- Scene button now shoes primitive clip view. I had RGB colors(clip colors) working for the pads but forgot to commit that code when I overwrote some stuff.
- TEMP for now [SHIFT + PAD MODE] Toggle chromatic mode.
- TEMP Long press [PAD_MODE] lets you select scales (in C until added functionality), press again to exit.
- TEMP [PAD_MODE + Step/Jog arrows Left/Right] change octave.

- [Navigate longpress] Shows the device param banks, select the bank with a pad.

I am only posting these temps, so you people can see scales selection/mode will be implemented correctly next. And that i will try hard to keep this controller implementation intuitive so memorizing things is minimal.

Basically all the TEMP stuff is going to be accessed with the F1-F8 buttons while holding a corresponding pad to set a certain mode.

Mike

powermat · Post by **powermat** » Wed Nov 05, 2014 11:37 pm

None of these would work for the Mikro, though, correct?

TeotiGraphix · Post by **TeotiGraphix** » Wed Nov 05, 2014 11:47 pm

powermat wrote:None of these would work for the Mikro, though, correct?

Well, the Mikro, I haven't yet got the display working in the miniature version yet.

But scales and such will work (but you can not see them scroll in the display to select). I need to have a notification on the screen in Bitwig until I get the display figured out. I will add that tomorrow.

But yeah, everything I have stated works on the Mikro except the function keys and display stuff.

Once I get the major impl in the Studio and MK2, I will figure out what I can get away with in the Mikro with views and modes.

The pad lighting is different as well as how I have to handle the group buttons. We will see.

Mike

Bitwig

KVR Audio

Maschine4Bitwig Studio, MK2, MikroMK2 and MK1