Maschine4Bitwig Studio, MK2, MikroMK2 and MK1

[powermat]

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

Question 2, do you accept donations?

[TeotiGraphix]

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

Question 2, do you accept donations?

Yeah, a pat on the back, that is it. Any tool maker just loves having their stuff used, plus knowing I can help all those Maschine users create in Bitwig is great.

These scripts (doing all three) was pretty complex and I had to learn a lot to get them where they are right now. The hard part is behind me minus the stupid Windows pad light bug.

So, get people to use them, tell others so I can get all the bugs out and I will get the most I can out of all 3 controllers and Bitwig Studio.

Mike

[reflex58]

I have not been able to get this working on OSX BWS 1.015
Installed all scripts/ controller editor templates per instructions.
BWS does auto detect Maschine Studio and assigns the Maschine virtual Midi port
Trying switching to port 2 per the github installation directions.
No response in BWS from any key presses (correct controller editor template loaded).
Had the original script from months ago working, pretty sure its not the installation
Any ideas?

[TeotiGraphix]

I have not been able to get this working on OSX BWS 1.015
Installed all scripts/ controller editor templates per instructions.
BWS does auto detect Maschine Studio and assigns the Maschine virtual Midi port
Trying switching to port 2 per the github installation directions.
No response in BWS from any key presses (correct controller editor template loaded).
Had the original script from months ago working, pretty sure its not the installation
Any ideas?

Sorry, in the original post, I said you have to use 1.1 beta due to the framework being written with 1.1 API.

Again sorry about that, I wish I could allow 1.0.15 users to test it but way to much changed in the controller API from 1.0.15 to 1.1.

Mike

[dom@bitwig]

... btw: a pat on the back from me, too! now it won't take long to switch over from my quick and dirty hack script for my mk2 to yours, which is a lot tidier in overall structure

Cheers,
Dom

[TeotiGraphix]

... btw: a pat on the back from me, too! now it won't take long to switch over from my quick and dirty hack script for my mk2 to yours, which is a lot tidier in overall structure

Cheers,
Dom

Well I still have the pads and modes, but it's rock solid for transport/tempo/rec for now, it can only get better.

I really tried to keep this intuitive with the button's names and functions. I looked at NI's impl in Ableton and decided, I do not want to do that because I wouldn't use it most of the time, it's to complex.

Maybe I will fall short, hehe we will see. Device mode, Scales and Session tweaks next.

Everything on the wiki Global-function-list page has been tested with all 3 controllers. As I add stuff and test, that page gets updated.

https://github.com/teotigraphix/Maschin ... ction-list

BTW, just like moss did with push, I have a dedicated page on my web site for a stable zip archive with version # and date.

http://www.teotigraphix.com/bitwig

Mike

[dom@bitwig]

Great! I didn't do much with mine, hacked some transport functionality, track navigation and a channel strip page, device navigation and device/macro control and i was more or less fine with it. Fun and useable.
Never dived into scales or the step sequencer Volker started... but i planned to, and i wanted to implement the "hold clear together with a pad to delete that one out of the running clip" that i like a lot from the maschine vst. But time flies and there's so much else to do here!

[TeotiGraphix]

Great! I didn't do much with mine, hacked some transport functionality, track navigation and a channel strip page, device navigation and device/macro control and i was more or less fine with it. Fun and useable.
Never dived into scales or the step sequencer Volker started... but i planned to, and i wanted to implement the "hold clear together with a pad to delete that one out of the running clip" that i like a lot from the maschine vst. But time flies and there's so much else to do here!

Yeah, this is still quite alpha but just wanted to have some people try it as I start to add the more complicated things like scales mode, page nav and such.

In the 0.1 its really only usable as a transport controller, the pads play but are stuck in the Key of C until I get the modes working.

NI sucks as far as not being able to control the knob pages which has made it 10 times harder to do this script.

Mike

[Magneson]

Digging around the NI forums for info about the numeric displays on the S4, I stumbled across this:

http://www.native-instruments.com/forum ... ost-873089

It is basically a way to address the Maschines LCDs through SYSEX instead of the controller editor. A few posts further down, he also posts an Excel conversion sheet to get the correct hex values for strings. Could this be used as a way to avoid the Controller Editors regime of doing things? It should in theory be able to cut out all of CE-specific template editing (apart from setting affected knobs to MCU-mode), and provide a way to program pages and knobs from the script rather than in the hardware.

[TeotiGraphix]

Digging around the NI forums for info about the numeric displays on the S4, I stumbled across this:

http://www.native-instruments.com/forum ... ost-873089

It is basically a way to address the Maschines LCDs through SYSEX instead of the controller editor. A few posts further down, he also posts an Excel conversion sheet to get the correct hex values for strings. Could this be used as a way to avoid the Controller Editors regime of doing things? It should in theory be able to cut out all of CE-specific template editing (apart from setting affected knobs to MCU-mode), and provide a way to program pages and knobs from the script rather than in the hardware.

Oh I am, everything is display. So I am only using 1 (generic)knob page setup with 8 function buttons(cc messages) and 8 mcu knobs(I have to use vpots because the display doesn't work if I use cc messages, that sucks!, should be an NI bug).

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

[powermat]

To all of you, my first generation Maschine Mikro sits in MIDI mode, awaiting your greatness! Thanks to you all, for your efforts!

[TeotiGraphix]

To all of you, my first generation Maschine Mikro sits in MIDI mode, awaiting your greatness! Thanks to you all, for your efforts!

I have to look at the layout, but I think I just need to make a template and control file and I can get it to work, I will post back when its in GIT. (First generation Mikro is the only template I haven't made yet).

Then you can tell me if it works or not.

Mike

[powermat]

To all of you, my first generation Maschine Mikro sits in MIDI mode, awaiting your greatness! Thanks to you all, for your efforts!

I have to look at the layout, but I think I just need to make a template and control file and I can get it to work, I will post back when its in GIT. (First generation Mikro is the only template I haven't made yet).

Then you can tell me if it works or not.

Mike

Will do! However, this is a 2nd hand Maschine Mikro 1st gen. No software from NI (except the controller editor). I'll hang on to it, for sure, to help test, but think I should just get rid of it in the end? Perhaps save up for the full Maschine or grab the Studio?

[TeotiGraphix]

To all of you, my first generation Maschine Mikro sits in MIDI mode, awaiting your greatness! Thanks to you all, for your efforts!

I have to look at the layout, but I think I just need to make a template and control file and I can get it to work, I will post back when its in GIT. (First generation Mikro is the only template I haven't made yet).

Then you can tell me if it works or not.

Mike

Will do! However, this is a 2nd hand Maschine Mikro 1st gen. No software from NI (except the controller editor). I'll hang on to it, for sure, to help test, but think I should just get rid of it in the end? Perhaps save up for the full Maschine or grab the Studio?

Well it would be kewl for you to test the initial, since if that works fine, the rest should work automatically.

I got the Studio first and absolutely love it but for some the added 500$ is to much for it's extras. The MK2 is nice and will work well with Bitwig for sure.

Mike

[taoyoyo]

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