Maschine4Bitwig Studio, MK2, MikroMK2 and MK1

[TeotiGraphix]

Hey,

Thank you so much for your work on this script! I look forward to seeing it grow. I posted about it in Maschine forums to spread the word. hope that was cool.

http://www.native-instruments.com/forum ... pt.232830/

Cheers,
X

Yeah that's fine. It is still in active development, I just knew December-February was going to be really busy for me(business wise) thus, it hasn't got that much love atm.

But it does quite a bit right now.

Mike

[Esla]

TeotiGraphix,

Thank you for tackling this! I have a Mikro MK2 and eagerly await the script to be complete.

I did try to load the one from your Gethub. You said it was 3/4 complete earlier, does that mean it has any functionality beyond transport?

Right now all I got is 4 blue and one purple lit pads, all of the function buttons are lit but don't do anything beyond the transports.

Again, THANK YOU!!!! You are a King.

[TeotiGraphix]

TeotiGraphix,

Thank you for tackling this! I have a Mikro MK2 and eagerly await the script to be complete.

I did try to load the one from your Gethub. You said it was 3/4 complete earlier, does that mean it has any functionality beyond transport?

Right now all I got is 4 blue and one purple lit pads, all of the function buttons are lit but don't do anything beyond the transports.

Again, THANK YOU!!!! You are a King.

It has been awhile since I plugged the Mikro in. So I would just be guessing. the way it stands is the Mikro pretty much gets all the functionality as the other controllers automatically. It's just without the Group buttons, I have to override how the Mikro does things in a logical manner, which I haven't done yet.

So you can look here and try some stuff that would still apply to the Mikro, again, I am still looking at around March/April before I have time to really nail this project feature complete code wise.

https://github.com/teotigraphix/Maschin ... efinitions

Mike

[Reefius]

Is there any way to change the encoder speed? On my Maschine Studio when I assign an encoder to a macro, I need to keep turning the encoder while the parameter value only changes slowly. It's quite impossible to use that way.

[TeotiGraphix]

Is there any way to change the encoder speed? On my Maschine Studio when I assign an encoder to a macro, I need to keep turning the encoder while the parameter value only changes slowly. It's quite impossible to use that way.

Is it with encoder 1? I have the same problem on my Studio, all other 7 work fast and #1 takes 5 times more turns.

I am not impressed with the Studio's MIDI on Windows, which OS are you using?

Mike

[Reefius]

I'm on Windows 8.1, and it is indeed only encoder 1, the others work fine.

[Reefius]

I found the problem, it's in the MaschineStudio4Bitwig.ncmst file.

Code: Select all

        <knob id="EncoderKnob1">
          <name>Param 1</name>
          <mcu-vpot>16</mcu-vpot>
          <dec>127</dec>
          <range>3600</range>
          <steps>100</steps>
          <bipolar>off</bipolar>
        </knob>
        <knob id="EncoderKnob2">
          <name>Param 2</name>
          <mcu-vpot>17</mcu-vpot>
          <dec>127</dec>
          <range>360</range>
          <steps>100</steps>
          <bipolar>off</bipolar>
        </knob>

Notice the 'range' difference between EncoderKnob 1 and 2.

I changed the 3600 to 360 for encoder 1, reloaded the script in Controller Editor and now encoder 1 is working like it should

[TeotiGraphix]

I found the problem, it's in the MaschineStudio4Bitwig.ncmst file.

Code: Select all

        <knob id="EncoderKnob1">
          <name>Param 1</name>
          <mcu-vpot>16</mcu-vpot>
          <dec>127</dec>
          <range>3600</range>
          <steps>100</steps>
          <bipolar>off</bipolar>
        </knob>
        <knob id="EncoderKnob2">
          <name>Param 2</name>
          <mcu-vpot>17</mcu-vpot>
          <dec>127</dec>
          <range>360</range>
          <steps>100</steps>
          <bipolar>off</bipolar>
        </knob>

Notice the 'range' difference between EncoderKnob 1 and 2.

I changed the 3600 to 360 for encoder 1, reloaded the script in Controller Editor and now encoder 1 is working like it should

Wow, props to you!

I feel like an idiot, I swear I checked those values.

You get the gold star for today, that was killing me because a lot of the parameters had cutoff mapped to 1, and it was frustrating to say the least.

I will update that in GIT.

Thanks again, I was doing so much, having to eyes helped.

Mike

[TeotiGraphix]

Ok,

Now looking at the controller editor, no wonder I didn't catch this, it must be a bug in NI's controller implementation since there is no way to adjust that in the editor, thanks again. I didn't even think to look in the XML.

Well hopefully I don't have any more bugs in the template or I will have to manually change that each time.

Mike

[Esla]

It has been awhile since I plugged the Mikro in. So I would just be guessing. the way it stands is the Mikro pretty much gets all the functionality as the other controllers automatically. It's just without the Group buttons, I have to override how the Mikro does things in a logical manner, which I haven't done yet.

So you can look here and try some stuff that would still apply to the Mikro, again, I am still looking at around March/April before I have time to really nail this project feature complete code wise.

https://github.com/teotigraphix/Maschin ... efinitions

Mike

Thanks! It is much appreciated. I can get some functionality out of it but it's hard with no visual feedback (aside from what is going on on the Bitwig GUI that is). It's great to have access to the pads though, this is a huge plus for me!

Is there a way to move up or down octaves?

Anyone know how to adjust the colors of the pads without getting into the script?

Right now I just have Pad 11,12,14,15,16 lit different brightnesses of blue for no apparent reason.

[TeotiGraphix]

It has been awhile since I plugged the Mikro in. So I would just be guessing. the way it stands is the Mikro pretty much gets all the functionality as the other controllers automatically. It's just without the Group buttons, I have to override how the Mikro does things in a logical manner, which I haven't done yet.

So you can look here and try some stuff that would still apply to the Mikro, again, I am still looking at around March/April before I have time to really nail this project feature complete code wise.

https://github.com/teotigraphix/Maschin ... efinitions

Mike

Thanks! It is much appreciated. I can get some functionality out of it but it's hard with no visual feedback (aside from what is going on on the Bitwig GUI that is). It's great to have access to the pads though, this is a huge plus for me!

Is there a way to move up or down octaves?

Anyone know how to adjust the colors of the pads without getting into the script?

Right now I just have Pad 11,12,14,15,16 lit different brightnesses of blue for no apparent reason.

The lit pads are actually the groups being lit from the script, C, D, F, G, H.

The Mikro seems to have different MIDI message protocol then the other models and another reason it's not finished.

So my script is telling the Mikro to light the group buttons and it's actually lighting the pads instead. It doesn't make since to me since I am sending CC messages to light the Group buttons on Studio, MK but Mikro is using them as note messages, go figure.

I know there is about 4 people that have tagged onto this saying they would love the Mikro support, I just don't have the time to spend a couple days right now trying to get it working.

So the unknowns for me are Group assignment, pad lighting and how to send text to the display.

Mike

[powermat]

Mike, it's cool. I use it as generic midi (like I always have, since I bought the mikro second hand ... I know, stupid move on my part) and it's good 'nuff. I've created a profile with custom scales and with Bitwig's note mods, it's good for what I need. I figured that if I truly wanted its workflow benefits, I just need to shell out the full price for a new Maschine.

[Esla]

I know there is about 4 people that have tagged onto this saying they would love the Mikro support, I just don't have the time to spend a couple days right now trying to get it working.

So the unknowns for me are Group assignment, pad lighting and how to send text to the display.

Mike

I wish i knew what to learn so I can help but fear it is WAY over my head.

Color feedback in the pads and transpose control would be the most helpful. Colors seem arbitrary or unimportant but they really help me when I adjust the transposition to keep track of scale and root note. And they look cool

[TeotiGraphix]

I know there is about 4 people that have tagged onto this saying they would love the Mikro support, I just don't have the time to spend a couple days right now trying to get it working.

So the unknowns for me are Group assignment, pad lighting and how to send text to the display.

Mike

I wish i knew what to learn so I can help but fear it is WAY over my head.

Color feedback in the pads and transpose control would be the most helpful. Colors seem arbitrary or unimportant but they really help me when I adjust the transposition to keep track of scale and root note. And they look cool

I know this sounds crazy but what DOES work for you right now? I am asking since you are a user and that script is huge since it covers all Maschine controllers, so I have been out of the loop.

I don't have mine plugged in right now(I have all the controllers except MK1).

Mike

[oivivio]

Dear Mike,

Thank you for all your hard work on this maschine script. I am currently running a MK1 have ran into a few problems, mainly in the scale mode.

When I am in chromatic major scale for example, the first note in the second pad bank, pad 5 on maschine, goes a whole tone above pad 4. Same goes for pads 9 & 13. When C is the root note in the major scale, pad 5 plays "F" rather than "E". This happens regardless of the root note, so pads 5, 9 & 13 always play a tone above the previous pad. Also, when changing the root note, the LED's do not properly show a correct chromatic scale.

I'm not sure if many people have been testing MK1 and I believe you do not even have one in your arsenal, so I thought this might help in some debugging

Thanks again,

Brad