Maschine4Bitwig Studio, MK2, MikroMK2 and MK1

[TeotiGraphix]

Just playing around with it, great stuff!
Function buttons in device mode currently don't work (e.g. switching to macros), right?

Cheers,
Dom

Hah, i don't know why but I had commented that out in the code.

it works again;

* ReAdded: [`Select`] In Devicemode, selects the parameter banks.

Mike

Updated in GIT master

[dom@bitwig]

Woha, that was quick! Re-Downloading...
BTW: In your current controller editor preset pad 16 is currently in toggle instead of gate mode...

[TeotiGraphix]

Woha, that was quick! Re-Downloading...
BTW: In your current controller editor preset pad 16 is currently in toggle instead of gate mode...

OMG I can't believe this, that was the problem with my MK2 controller I received last week! I will have to confirm it's not nutty elsewhere, I can't believe I didn't check that.

I will email Placidus about this if all is well.

Mike

* Fix: MK2 controller template pad 16 was in Toggle instead of Gate.

Updated in GIT master

[dom@bitwig]

Ha, that's my support karma... i'm a bug magnet.
Sorry that i only now found time to check it out, i only heard from Volker there was some kind of pad problem?
Was it that?

And regarding the select-page in device mode, maybe you commented it out when adding

Added [SELECT + <] In DeviceMode, pages parameter page previous.
Added [SELECT + >] In DeviceMode, pages parameter page next.
Added [SELECT press] In DeviceMode, displays the selected parameter page notification.

as they clash a bit?

[TeotiGraphix]

Ha, that's my support karma... i'm a bug magnet.
Sorry that i only now found time to check it out, i only heard from Volker there was some kind of pad problem?
Was it that?

And regarding the select-page in device mode, maybe you commented it out when adding

Added [SELECT + <] In DeviceMode, pages parameter page previous.
Added [SELECT + >] In DeviceMode, pages parameter page next.
Added [SELECT press] In DeviceMode, displays the selected parameter page notification.

as they clash a bit?

Actually, probably was. I didn't look at the code well enough, I didn't realize I had just axed a full fledged mode.

YES! The MK2 seems to be working correctly from what I told Volker, so all good until I realize I don't know what I am talking about.

there is still a NI problem on Windows, the Studio has crappy pad lighting, definitely a bug in their driver, the MK2 shows it intermittently.

I hope its not a Bitwig issue. but I swear i tried the Ableton template NI provides in Abelton 9.1 and the pads are screwed up lighting on the Stuido as well.

I noticed device selection is not activated in ParamBankSelectMode, I am only checking if it's Device or Preset mode, i will fix that.

Mike

[TeotiGraphix]

Added [SELECT + <] In DeviceMode, pages parameter page previous.
Added [SELECT + >] In DeviceMode, pages parameter page next.
Added [SELECT press] In DeviceMode, displays the selected parameter page notification.

as they clash a bit?

Not really, I have checks for current mode and pressed, so these work fine, unless you find a bug in that they don't work as the documentation says.

I am having fun testing it now.

I think I got Maschines pretty usable in Bitwig, just as fun as the Push for me! :0

Mike

[mrfrenkie]

MK1 - "SAMPLING" Button must be gate or trigger (LED On For MIDI Out). Now is toggle. And when i press "D" maschine freeze. But big up for your work!!!

[TeotiGraphix]

MK1 - "SAMPLING" Button must be trigger. Now is toggle. And when i press "D" maschine freeze. But big up for your work!!!

Sorry about that! Yeah, i don't have an MK1, but I will update the controller template with all gates, doing to much stuff at once.

BTW, You are using the MK1, can you use it? Or is the D key always crashing it, really the scripts should just work together because its just MIDI messages and I have them all parallel.

Let me know.

Mike

PS You are the first to say you are trying the MK1, there are things that might now work since I haven't mapped some of the latest jogwheel etc. stuff to it.

[dom@bitwig]

It is really great to play with in its current state already! Love it!
Have to dig into the scripts to see how i might modify a few minor things for me personally, like device mode being in macro control mode when entering it by default instead the first parameter page, because i use it more often, adding a device on/off button to the macro page.
For my workflow i guess i'll try to restructure the track mode a bit, too, removing the crossfader parameter to get one more send in and adding a rec arm to the F-buttons, when not using auto arm in the app for audio tracks...

[dom@bitwig]

Confirmed, "D" (controller 47) freezes the script also for the MK2, just never pressed it before as it should have no function yet But there's nothing in the console...

[TeotiGraphix]

It is really great to play with in its current state already! Love it!
Have to dig into the scripts to see how i might modify a few minor things for me personally, like device mode being in macro control mode when entering it by default instead the first parameter page, because i use it more often, adding a device on/off button to the macro page.
For my workflow i guess i'll try to restructure the track mode a bit, too, removing the crossfader parameter to get one more send in and adding a rec arm to the F-buttons, when not using auto arm in the app for audio tracks...

Dom, this script is still really raw, I am up for any changes. i have only really been working on this about 5 days, so I haven't thought everything out, just trying to test the features not really into the usability testing yet.

Please, list out any features or changes in the GIT issues if you have time. Odds are my workflow is close to yours and if not, i could always add options in the Controller config in Bitwig.

The rec arm button definitely was going in Track Mode next to mute/solo, i just started implementing the Function buttons so i probably have missed a lto.

Mike

[TeotiGraphix]

Confirmed, "D" (controller 47) freezes the script also for the MK2, just never pressed it before as it should have no function yet But there's nothing in the console...

Hah, damn I thought he was talking about the G, ok that is something in the script, i will check it and disable it. (it shouldn't have any functionality right now)

Mike

[TeotiGraphix]

Confirmed, "D" (controller 47) freezes the script also for the MK2, just never pressed it before as it should have no function yet But there's nothing in the console...

That was a bug where i was testing an EditView but it wasn't loaded, FIXED!

* Fix: D Group button crashed controller because it was accessing a view that doesn't exist.

Mike

Updated GIT in master.

[dom@bitwig]

Dom, this script is still really raw, I am up for any changes. i have only really been working on this about 5 days, so I haven't thought everything out, just trying to test the features not really into the usability testing yet.

Amazing, the whole work for the push scripts really pays off now!

Please, list out any features or changes in the GIT issues if you have time. Odds are my workflow is close to yours and if not, i could always add options in the Controller config in Bitwig.

Some things are just taste sometimes, but i'll be more than happy to add my suggestions to the git issues, as it is personally my favourite controller weapon.

The rec arm button definitely was going in Track Mode next to mute/solo, i just started implementing the Function buttons so i probably have missed a lto.

Mike

Great, and no hurry! This comes together nicely...

[mrfrenkie]

BTW, You are using the MK1, can you use it? Or is the D key always crashing it, really the scripts should just work together because its just MIDI messages and I have them all parallel.


PS You are the first to say you are trying the MK1, there are things that might now work since I haven't mapped some of the latest jogwheel etc. stuff to it.

Yes, I have the MK1 but I am not have english.

And yes - where is SHIFT on MK1?

PS: "AUTO WRITE" must be gate (Sorry. maybe toggle, but at now for switching i double push it). And when press (hold) MUTE or SOLO there is something strange. Specifically with LED.