Maschine4Bitwig Studio, MK2, MikroMK2 and MK1

[TeotiGraphix]

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!)

... Just checking the script using Studio and the 'Enter' button feels a lot more natural with the < > jogwheel buttons. (Noticed that Shift- < > currently moves the selected track in increments of 4.)

There does seem to be an issue with the Metronome function, where the expected jogwheel behavior is reversed (i.e.: Twisting it left increases and moving it right decreases the volume ).

Metro volume; Yeah that was a bug from when I switched the increase value, its fixed in GIT.

The enter button: Yeah I know, its on the right side. I wish NI would let us use the real Shift button, the MK2 and Enter was the best I could do.

Don't forget to update the editor template on the Studio, the Scene and Pattern buttons had the same cc, that is why you get that odd double light behavior.

I am working on the scales and session view today. Session clip colors for Bitwig colored clips, key, scale, octave, chromatic modes in display. This stuff set by the function buttons.

Mike

[TeotiGraphix]

> Noticed that Shift- < > currently moves the selected track in increments of 4.)

This is due to the base framework only having 1 track bank and it uses it for the Scene view, which the maschine can only have 4 tracks (4 pads) in a bank at a time.

I have to figure out how to use a second track bank to page 8 tracks that are synced to the display columns, on the list.

So what you are seeing is the default behavior configured, this Maschine project use the same core framework as Push4Bitwig.

Mike

[taoyoyo]

Metro volume; Yeah that was a bug from when I switched the increase value, its fixed in GIT.

... Cool, downloading now. (Yup, Metro Vol direction is good now! )

The enter button: Yeah I know, its on the right side. I wish NI would let us use the real Shift button, the MK2 and Enter was the best I could do.

... I understand, it's a tricky one when the ideal button (i.e.: the real shift) is already taken. 'Enter' is better with Studio (over Mk2) but it makes sense to keep 'em consistent.

Don't forget to update the editor template on the Studio, the Scene and Pattern buttons had the same cc, that is why you get that odd double light behavior.

... Will updating of the CE templates be necessary for every build?

I am working on the scales and session view today. Session clip colors for Bitwig colored clips, key, scale, octave, chromatic modes in display. This stuff set by the function buttons.

... Very cool. Looking forward to seeing these in action when they're ready

[TeotiGraphix]

> Will updating of the CE templates be necessary for every build?

No, but I say it in the docs(for now) because I might have a bug in the CCs which I did with the Studio, I must have accidentally changed it, since that was working months ago.

I "might" also be changing the knobs to cc values and the top 8 buttons to MCU buttons, I read some info and I will test this, If this happens I will say it and nothing would work right until the CE was updated.

All controllers share the same editor templates, so once it's clear they are "really" bug free, they will never change.

Mike

[TeotiGraphix]

BTW taoyoyo, are you on Windows or a Mac, Linux?

It kills me this Windows pad light bug, but the Mac lights them perfectly.

Mike

[Magneson]

This is why its taken me a lot longer to do these scripts, because I have had to think about of to launch/lock modes that change the screen display and function buttons but still maintain the correct view for the controller, IE Pad mode, Scnen/clip, Pattern/sequencer etc.

Thanks though, i will read it to see if I missed anything else.

Mike

Np. Couldn't this be sorted by stuffing all controls into an array with write from an offset set by a page button/knob (Maschine writes to the array, BW reads from it)? Or would that be a drain resource-wise? I'm on a mk1 though, don't know how much of a difference the mk2 makes.

[taoyoyo]

BTW taoyoyo, are you on Windows or a Mac, Linux?

It kills me this Windows pad light bug, but the Mac lights them perfectly.

Mike

I'm afraid I'm on Mac, (10.10) so can't check out this issue.

Those quirks between OS can be a pain (remember there being a Mac issue with NativeKontrol's original version of their Machine script that couldn't be solved and had to be postponed for a while).

[TeotiGraphix]

BTW taoyoyo, are you on Windows or a Mac, Linux?

It kills me this Windows pad light bug, but the Mac lights them perfectly.

Mike

I'm afraid I'm on Mac, (10.10) so can't check out this issue.

Those quirks between OS can be a pain (remember there being a Mac issue with NativeKontrol's original version of their Machine script that couldn't be solved and had to be postponed for a while).

Ah no worries, Volker at Bitwig knows about it and has been in contact with Native Instruments, so its out of my hands. He could reproduce it on his Windows machine so that verified it wasn't my setup or code.

Mike

[TeotiGraphix]

This is why its taken me a lot longer to do these scripts, because I have had to think about of to launch/lock modes that change the screen display and function buttons but still maintain the correct view for the controller, IE Pad mode, Scnen/clip, Pattern/sequencer etc.

Thanks though, i will read it to see if I missed anything else.

Mike

Np. Couldn't this be sorted by stuffing all controls into an array with write from an offset set by a page button/knob (Maschine writes to the array, BW reads from it)? Or would that be a drain resource-wise? I'm on a mk1 though, don't know how much of a difference the mk2 makes.

I already have the model worked out, its just how to enable to modes on the controller, which I am working on right now.

Mike

[taoyoyo]

> Noticed that Shift- < > currently moves the selected track in increments of 4.)

This is due to the base framework only having 1 track bank and it uses it for the Scene view, which the maschine can only have 4 tracks (4 pads) in a bank at a time.

I have to figure out how to use a second track bank to page 8 tracks that are synced to the display columns, on the list.

So what you are seeing is the default behavior configured, this Maschine project use the same core framework as Push4Bitwig.

Mike

... Kind of off-topic but relevant to this post.

(Disclaimer I'm a complete novice with the API and this scripting stuff).

By the sounds of this, it should be possible within the API to toggle between two banks of 8 tracks?

I'm asking because I have a Livid Instruments Code2 and the existing script that Livid created only allows the user to move one track at a time. I would like to set up a single button on the Code that would allow me to toggle between 'Bank 1' (Tracks 1-8) and 'Bank 2' (Tracks 9-16) and ignore any tracks on Tracks 17 and after but keeping all the other assignments running parallel with the 2 banks (i.e.: Sends/Mutes/Clip triggers etc).

The idea is for Live performance, where the 2 x Bank of 8 tracks would be a 'song' and would allow for easy mixing between the two. (Any tracks after 16 would be routed via audio into the Bank tracks).

Not urgent at all but just wondered.

[Magneson]

This is why its taken me a lot longer to do these scripts, because I have had to think about of to launch/lock modes that change the screen display and function buttons but still maintain the correct view for the controller, IE Pad mode, Scnen/clip, Pattern/sequencer etc.

Thanks though, i will read it to see if I missed anything else.

Mike

Np. Couldn't this be sorted by stuffing all controls into an array with write from an offset set by a page button/knob (Maschine writes to the array, BW reads from it)? Or would that be a drain resource-wise? I'm on a mk1 though, don't know how much of a difference the mk2 makes.

I already have the model worked out, its just how to enable to modes on the controller, which I am working on right now.

Mike

Ah, obviously! There is also this by the way: http://www.native-instruments.com/forum ... io.219263/.

The interesting part is that where the first example (previous post) used FF 00 00 66 17 as the header, this one uses ...66 14 12 and ...66 15 12. It hints at Maschine having far more flexibility added from sysex messages, but I'm not sure that NI will ever let it get out. It's a pity though, I'm sure there would be a lot of interesting concepts.

[TeotiGraphix]

Yeah, I have the displays working perfectly right now.

There is an abstraction in the framework moss wrote for displays of multi-columns, I am using 8.

I only need to send an offset of 0 for the first row and 56 for the second, the Display class does the actual calcs of blocks and cells.

Moss rocked on that one.

Mike

[TeotiGraphix]

> Noticed that Shift- < > currently moves the selected track in increments of 4.)

This is due to the base framework only having 1 track bank and it uses it for the Scene view, which the maschine can only have 4 tracks (4 pads) in a bank at a time.

I have to figure out how to use a second track bank to page 8 tracks that are synced to the display columns, on the list.

So what you are seeing is the default behavior configured, this Maschine project use the same core framework as Push4Bitwig.

Mike

... Kind of off-topic but relevant to this post.

(Disclaimer I'm a complete novice with the API and this scripting stuff).

By the sounds of this, it should be possible within the API to toggle between two banks of 8 tracks?

I'm asking because I have a Livid Instruments Code2 and the existing script that Livid created only allows the user to move one track at a time. I would like to set up a single button on the Code that would allow me to toggle between 'Bank 1' (Tracks 1-8) and 'Bank 2' (Tracks 9-16) and ignore any tracks on Tracks 17 and after but keeping all the other assignments running parallel with the 2 banks (i.e.: Sends/Mutes/Clip triggers etc).

The idea is for Live performance, where the 2 x Bank of 8 tracks would be a 'song' and would allow for easy mixing between the two. (Any tracks after 16 would be routed via audio into the Bank tracks).

Not urgent at all but just wondered.

When i get this all working, any feature requests will be granted, I plan on using the Maschine + Push for live performances to myself.

I will put this as a feature request in GIT so it doesn't get lost.

Mike

[taoyoyo]

> Noticed that Shift- < > currently moves the selected track in increments of 4.)

This is due to the base framework only having 1 track bank and it uses it for the Scene view, which the maschine can only have 4 tracks (4 pads) in a bank at a time.

I have to figure out how to use a second track bank to page 8 tracks that are synced to the display columns, on the list.

So what you are seeing is the default behavior configured, this Maschine project use the same core framework as Push4Bitwig.

Mike

... Kind of off-topic but relevant to this post.

(Disclaimer I'm a complete novice with the API and this scripting stuff).

By the sounds of this, it should be possible within the API to toggle between two banks of 8 tracks?

I'm asking because I have a Livid Instruments Code2 and the existing script that Livid created only allows the user to move one track at a time. I would like to set up a single button on the Code that would allow me to toggle between 'Bank 1' (Tracks 1-8) and 'Bank 2' (Tracks 9-16) and ignore any tracks on Tracks 17 and after but keeping all the other assignments running parallel with the 2 banks (i.e.: Sends/Mutes/Clip triggers etc).

The idea is for Live performance, where the 2 x Bank of 8 tracks would be a 'song' and would allow for easy mixing between the two. (Any tracks after 16 would be routed via audio into the Bank tracks).

Not urgent at all but just wondered.

When i get this all working, any feature requests will be granted, I plan on using the Maschine + Push for live performances to myself.

I will put this as a feature request in GIT so it doesn't get lost.

Mike

Hey Mike,

My long-winded question was more to do with whether this was possible theoretically with the API, I wanted to see if it was possible to alter the script for Livid Instruments Code 2 to make this happen.

When I do eventually go out Live I will definitely be taking out the Maschine Mk2 controller (possibly a Mikro Mk2 as well) but Push is just too weighty (lugged that to Berlin last year! ) so am thinking about the Code 2 instead (using the 2 x Banks of 8 idea if possible).

Apologies for the confusion, I just thought you might know the answer to this (as you'd just mentioned 'banking' in the post I replied to).

Cheers,

Alan

[TeotiGraphix]

Major update;

The last two days I spent getting all 16 modes working correctly for the Maschines.

I have a brain storm about just holding down the Navigate button which then shows you 16 modes to choose from, well in practice it worked out way better than I hoped.

- 16 new Modes by pressing [Navigate] and hold, select the Pad to select the mode;
Modes
- Device - Uses the 8 encoders for parameter values.
- Track - Adjust the selected Track Volume, Pane, CrossFader.
- Volume - Adjust the current bank's 8 track volumes.
- Pan - Adjust the current bank's 8 track pans.
- Send 1 - Adjust the current bank's 8 track send 1.
- Send 2 - Adjust the current bank's 8 track send 2.
- Send 3 - Adjust the current bank's 8 track send 3.
- Send 4 - Adjust the current bank's 8 track send 4.
- Scales - Adjust the current Scale, current Key, whether chromatic or inkey (F8)
- to change top key (C, G, D, A, E, B) press (F2 - F7) for the bottom keys, press [SHIFT + F2-F7]
* NOTE I need to hook up the knobs for these changes, coming soon.
- Scale Layout Change to 4th, 3rd layouts etc (Push like)
- Clip - Adjust the currently selected clip's Play start, Play end, Loop start, Loop end, Loop on/off, shuffle and eccent percentage.
- Cross Fade Switch from A, Both, B settings.
- Master - Adjust Master track's Volume and Pan
- Groove - Adjust Global Groove Shuffle rate, Shuffle amount, Accent rate, Accent amount, Global percentage, enable/disable global groove.
- Frame - Switch between Bitwig's UI elements Arrange, Mix, Edit, Note edit, Automation, Device, Mixer, Full screen; Toggles - Markers, Sequencer follow, Track height, Clip Launcher, Crossfade, FX, I/O and Large meters
- Accent - Set the accent of the pads.

Also in the Preferences > Controllers > Maschine gears you get settings like the Push that persist;



For what was added;

# Mode Controls

Allows the 16 pads to be used in selecting the current mode.
* The current mode's pad is blue and has a '>' in front of the bank name.

* Studio [`NAVIGATE longpress`]
* MK2 [`NAVIGATE longpress`]
* MikroMK2 [`NAVIGATE longpress`]

# Parameter Controls

## Parameter Banks

When in Device Mode allows the selection of the **Device**, **Common**, **Envelope**, **Direct**, **Macro**, **Modulation** and **User** parameter banks using the top **F** function buttons (1-7).

When in this selection mode, **F8** will enable/disable the current device.

* Studio [`SELECT`]
* MK2 [`SELECT`]
* MikroMK2 [`SELECT`]

## Parameter Pages

When in Device Mode changes parameter pages (next/previous) of the current parameter bank. This display updates with the name of the current page as the jog wheel scrolls through each page.

* Studio [`SHIFT + JogWheel`]
* MK2 [`SHIFT + JogWheel`]
* MikroMK2 [`SHIFT + JogWheel`]

You can download the 0.1.1 version from;

http://www.teotigraphix.com/bitwig/maschine

Or get the code at;

https://github.com/teotigraphix/Maschine4Bitwig

Wiki;

https://github.com/teotigraphix/Maschine4Bitwig/wiki

Mike