Maschine4Bitwig Studio, MK2, MikroMK2 and MK1

[TeotiGraphix]

Ok, so in order to get a chromatic scale are you saying that I need to hold down the "Navigate" button and then hit "Pad 7"? I did but I still get 4+5, 7+8, 12+13. I am running the latest from Github at this moment.

If I am reading your question right, you don't want chromatic mode, you want scales that cover the whole 16 pads without repeats.

> Fixed ScalesLayoutMode(NAVIGATE + PAD7), [F5] will correctly use sequential layout of all 16 pads.

What the above means is, press [NAVIGATE + PAD7], then once in scale layout mode, Press [F5] function button to put the layout in sequential scale.

Mike

I have (on my MIKRO MKII) a NAV button and then I have pads numbered from 1-16. When I hold down the NAV button and then strike pad 7, it does nothing. After that, there is no F5 button, only F1 - F3.

Hi,

I havn't worked on this script in a month+ due to my business and some other things(really busy).

the Mikro is not fully tested since I could not get the screen working and never heard back from Bitwig about it. NI is impossible to get any information from.

The pads are weird to for group selection but I have to test this specifically. I stated earlier in the thread that when i get the Mikro tested, I will post an update here.

For now, there doesn't seem to be much interest in these scripts (the last 1+ months) so I have taken a sabbatical from them.

Mike

[TeotiGraphix]

Oh yeah, and since I own the Maschine Studio and its pad lights are crippled on Windows in Bitwig, I can't even use the damn thing for my own music.

This was a huge bummer for me that NI and Bitwig couldn't get this problem fixed, another reason i lost temporary interest.

[taoyoyo]

Hey Mike... I just wanted to say that the work you've been doing on these scripts has been great (and appreciated).

My main stumbling block personally (and it's nothing to do with your work) has been the problems with using multiple controller scripts in Bitwig...

I could not get the M4B, Moss's Push4Bitwig and Thomas' Komplete Kontrol scripts all working together nicely without weirdness... also there were problems with using M4B and instances of Maschine with the controller at the same time. As I use Maschine HW constantly I just scaled it down to using P4B.

I'm pretty sure that you and Moss had mentioned that some these problems could not be solved at your end, that they were Bitwig-specific?

[TeotiGraphix]

Hey Mike... I just wanted to say that the work you've been doing on these scripts has been great (and appreciated).

My main stumbling block personally (and it's nothing to do with your work) has been the problems with using multiple controller scripts in Bitwig...

I could not get the M4B, Moss's Push4Bitwig and Thomas' Komplete Kontrol scripts all working together nicely without weirdness... also there were problems with using M4B and instances of Maschine with the controller at the same time. As I use Maschine HW constantly I just scaled it down to using P4B.

I'm pretty sure that you and Moss had mentioned that some these problems could not be solved at your end, that they were Bitwig-specific?

Yes, that is pretty much where we are at. I talked to Volker last month about the performance issues and he had said he is pretty sure our framework isn't the problem. So that is where it stands, I think they need some type of reproduction case on their end. It seems pretty simple, hook a Push and Maschine up at the same time.

As far as the VST to MIDI controller issues, I had experienced those to and have no idea how to combat them. The Push fortunately doesn't suffer since it's not also a VST controller.

I' am trying to light some business fires on my end so I should be getting back to these in a month or so, and hopefully talking to Volker about some outstanding issues.

Mike (thanks for the support)

[jaytwoeight]

Michael,

First, thanks for putting all this work to make Maschine control Bitwig. I'm really excited to try your template, but when I install it I run into the following problems.

Problems:

I loaded the template in Bitwig and the Controller editor. I enabled Host Transport Control. When I am in Bitwig and the template is loaded I run into the following two problems:

1) Pressing NAVIGATE + a pad button does not do anything. The first pad remains highlighted and the template does not change modes. :(

2) The template appears to be stuck in PAD MODE. The symptoms are:

- PAD MODE button is always lit up. The only times when it's not lit up are A) when STEP is on/lit up and B) while I am holding NAVIGATE.

- no matter where I am in the template if I have an instrument track selected in the Bitwig UI when I press any of the pads I see that a midi note signal is sent to Bitwig. This is most easily seen if I add a drum machine to the track, because then I can see the software pads light up and hear the sounds from the drum machine. :)


Setup:

Latest stable ver of template http://www.teotigraphix.com/assets/bitw ... Bitwig.zip
Bitwig 1.1.4
Maschine MK2
Controller Editor 1.7.4
MBP Core i7
OS X 10.9.5


Let me know what if there is anything that I can do to get this working.

Thanks!

[TeotiGraphix]

I will reread this when i have the proper time but, there is no need to enable host transport since I have all the transport buttons hooked up to Bitwig transport;

Did you see this documentation?

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

I haven't heard of any problems with this script and Mac and the MK2, so I will need to think about it and see if there is anything obvious.

Mike

[WXLF]

For now, there doesn't seem to be much interest in these scripts (the last 1+ months) so I have taken a sabbatical from them.

I am very interested as a Maschine Mikro MKII owner. I was assuming since it was not uploaded to the community on Bitwig's site that it was not completely finished yet. And was waiting for that

[TeotiGraphix]

For now, there doesn't seem to be much interest in these scripts (the last 1+ months) so I have taken a sabbatical from them.

I am very interested as a Maschine Mikro MKII owner. I was assuming since it was not uploaded to the community on Bitwig's site that it was not completely finished yet. And was waiting for that

Yeah well, I kind of meant that but its more about 3/4 finished and I knew that the beginning of the year was going to be busy for myself.

I still can't use my Studio on Windows which REALLY sucks. Honestly that is one of the major reasons I lost steam.

And with the Mikro, I have said it about 3 times, I don't know how or if it's even possible to access the screen with MIDI, I asked Bitwig months ago and NI isn't helpful at all.

The Mikro works but the problem is I have to spend a couple days reworking the Group buttons since it doesn't have any.

Mike

[WXLF]

Well I appreciate your work, Mike

Sorry to hear about your Maschine Studio issue. When you installed the driver, was Maschine Studio plugged in?
If so, try reinstalling without it plugged in. Hopefully that will help.

I'm not sure if I know what you mean by "access the screen with MIDI" on the Mikro. So I'm assuming you cannot.
The only MIDI function I know of on the Mikro is hitting "Shift + F1" to go into MIDI mode.

Thanks again for your hard work!

[TeotiGraphix]

Well I appreciate your work, Mike

Sorry to hear about your Maschine Studio issue. When you installed the driver, was Maschine Studio plugged in?
If so, try reinstalling without it plugged in. Hopefully that will help.

I'm not sure if I know what you mean by "access the screen with MIDI" on the Mikro. So I'm assuming you cannot.
The only MIDI function I know of on the Mikro is hitting "Shift + F1" to go into MIDI mode.

Thanks again for your hard work!

No, the Studio issue has to do with the Windows driver and pad lights not lighting correctly. Volker actually tested another Studio at his office and the same thing happened. I think most people use Mac, because this hasn't come up once with other users.

I just mean using the display, sending Sysex messages to the Mikro display.

Mike

[jaytwoeight]

I will reread this when i have the proper time but, there is no need to enable host transport since I have all the transport buttons hooked up to Bitwig transport;

Did you see this documentation?

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

I haven't heard of any problems with this script and Mac and the MK2, so I will need to think about it and see if there is anything obvious.

Hey Mike,

I disabled Host Transport Control and the issue persists.

The template stays in either of the two states below when you press the PAD MODE button. In both states Bitwig is receiving note input (seen in a drum machine) when I press the pad buttons.

http://drive.j28.us/temp/bitwig/pad-mode-state-1.JPG
http://drive.j28.us/temp/bitwig/pad-mode-state-2.JPG

I had not seen the docs. I just checked them out... unfortunately the template does not work as described in the docs due to the issues which I mentioned. ;((

Thanks!

[TeotiGraphix]

Ok, thanks for the screenshots, this is really weird because the pads are lit correctly meaning that the controller is talking to Bitwig correctly.

Are you sure you have record arm on? For the track you want to play?

Does pressing and holding the NAVIGATE button change the display contents?

Can you post a screenshot of your Bitwig controller preferences where it shows the MIDI connection in/out from the controller?

Mike

[TeotiGraphix]

Ah man, I needed to reread your post.

> 1) Pressing NAVIGATE + a pad button does not do anything.

It is supposed to stay lit, you are putting it in a mode, it's in Pad Mode when all pads are lit with the octaves being darker. Did you check out this video I did a couple months ago?

Mike

[jaytwoeight]

Ah man, I needed to reread your post.

> 1) Pressing NAVIGATE + a pad button does not do anything.

It is supposed to stay lit, you are putting it in a mode, it's in Pad Mode when all pads are lit with the octaves being darker. Did you check out this video I did a couple months ago?

Mike

Hey,

I just realized what the problem was... I had installed another Maschine template in the Controller Scripts folder about a year ago (made by "Emerah") and didn't even notice it when I was installing yours. The two templates were clashing. I removed the old one, restarted Bitwig, detected the controller again, and your template appears to work normal now.

Digging into the controller functionality now.

Thanks for suggesting that I look into the MIDI settings! I had to delete everything in there (TouchOSC etc) to see that BWS was loading two different templates when detecting the controller.

[Xminus1]

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