Maschine4Bitwig Studio, MK2, MikroMK2 and MK1

[TeotiGraphix]

still no luck hacking the Studio screens with 1.1's new apis?

Sorry but Native Instruments does not give access to the full screens. We have to use MCU mode which gives me two lines to work with just like the MK2.

Trust me, if I knew I had a way to use those screens I would do it in a heart beat. So to answer your question, this limitation has to do with NI not Bitwig.

Mike

[Magneson]

I've been researching running on linux for a bit this morning, and just stumbled across a post somewhere that said ALSA has gotten all the driver info from NI. This was in relation to screens not working on linux, and blame was put on ALSA for not having incorporated it. If NI is stubborn about the screen communication, maybe you could check with ALSA to see if they can provide additional driver info? I poked around on their site to see if I could find anything, but there was only a list of devices that were somewhat supported. You might have luck contacting Takashi Iwai as he seems to at least have something to do with the implementation of NI stuff (http://mailman.alsa-project.org/piperma ... 84385.html).

[TeotiGraphix]

I've been researching running on linux for a bit this morning, and just stumbled across a post somewhere that said ALSA has gotten all the driver info from NI. This was in relation to screens not working on linux, and blame was put on ALSA for not having incorporated it. If NI is stubborn about the screen communication, maybe you could check with ALSA to see if they can provide additional driver info? I poked around on their site to see if I could find anything, but there was only a list of devices that were somewhat supported. You might have luck contacting Takashi Iwai as he seems to at least have something to do with the implementation of NI stuff (http://mailman.alsa-project.org/piperma ... 84385.html).

Hi, I said I could not use the "rich" screens the Studio has. The MCU 2 row screens work just fine. I think the OP was asking about if we are able to use the screens the Studio uses in Maschine 2, which is a No.

Other than that, the Maschine Studio screen works as well as the MK2.

Mike

[Magneson]

Aha, ok! I only have the mk1, and that seems to work fine, so that explains a bit

[M-Prod]

Great work! What an amazing template. Thanks for all the effort. And thanks for working on the MK1 despite the fact you don't have one.

I tried this on the MK1 and noticed a few things
navigate-pad1 selects macro, not device.
Solo PAD1-4 selects solo of channel 5-8
Solo PAD5-8 selects solo of channel 1-4
Same for mute. Is this as designed to match the screens?
It works different in drum mode (pad1 = channel 1)
Also different in Select mode. Select+PAD1-8 works according to the pad numbers (selects channel 1-8).
So Pad 1 selects channel 1 but it solo's channel 5.
Select pad 16 selects the next bank. Then Pad 1 selects channel 9. But the second time i press pad 1 it selects channel 5, the third time it's back to 1, and all pads select the first bank. The bank selection seems to 'jump' back.
Mute - F1-F8 mutes the channels.
Solo - F1-F8 also mutes the channels.




cheers

Mike

[TeotiGraphix]

Great work! What an amazing template. Thanks for all the effort. And thanks for working on the MK1 despite the fact you don't have one.

I tried this on the MK1 and noticed a few things
navigate-pad1 selects macro, not device.
Solo PAD1-4 selects solo of channel 5-8
Solo PAD5-8 selects solo of channel 1-4
Same for mute. Is this as designed to match the screens?
It works different in drum mode (pad1 = channel 1)
Also different in Select mode. Select+PAD1-8 works according to the pad numbers (selects channel 1-8).
So Pad 1 selects channel 1 but it solo's channel 5.
Select pad 16 selects the next bank. Then Pad 1 selects channel 9. But the second time i press pad 1 it selects channel 5, the third time it's back to 1, and all pads select the first bank. The bank selection seems to 'jump' back.
Mute - F1-F8 mutes the channels.
Solo - F1-F8 also mutes the channels.

navigate-pad1 selects macro, not device.

Yes that is the default "Device bank" see video.

Solo PAD1-4 selects solo of channel 5-8
Solo PAD5-8 selects solo of channel 1-4
Same for mute. Is this as designed to match the screens?

I screwed this up! This was from the very beginning where I wasn't matching it to the bottom to top Maschine layout. I will fix this in Mute and Solo.

Also different in Select mode. Select+PAD1-8 works according to the pad numbers (selects channel 1-8).
So Pad 1 selects channel 1 but it solo's channel 5.
Select pad 16 selects the next bank. Then Pad 1 selects channel 9. But the second time i press pad 1 it selects channel 5, the third time it's back to 1, and all pads select the first bank. The bank selection seems to 'jump' back.
Mute - F1-F8 mutes the channels.
Solo - F1-F8 also mutes the channels.

There is a little bug in how the track banks work, yes this is a little"jump bug" in their and I am aware. i will try to fix that sooner than later, it has to do with How long it takes Bitwig to page the bank and the script needs to wait like 100 milliseconds be fore it can actually switch tracks. I think I am going to talk to Volker about this and try to get it natively fixed.

Did you see my little intro video? I explain Device bank modes, you should "get it" after watching.

See this thread; http://www.kvraudio.com/forum/viewtopic ... 9&t=425343

Thanks for testing the MK1!! Anything I can do to fix your end is great.

Mike

[lp]

Hey, sorry if I´m repeating someone who already asked about this, but is there a chance to get the mikro mk2 script working for mikro mk1?

I really would love to appreciate your work as much as all the others do

[powermat]

Hey, sorry if I´m repeating someone who already asked about this, but is there a chance to get the mikro mk2 script working for mikro mk1?

I really would love to appreciate your work as much as all the others do

As far as I know, they're just working out the kinks in the display. I'm waiting, too!

[TeotiGraphix]

Yes, I haven't heard anything from Bitwig about NI contacting them so I am stuck.

I will also have to spend a couple days with just the Mikro in front of me testing things as 1/3 of the functionality doesn't migrate 1 to 1 and there will have to be some special key combinations.

As I said earlier, I will update this thread when I hear something.

Mike

[lp]

Great, thank you so much!

[TommyMotion]

Hey Mike
The script is great. Thanks for taking the time to develop MK1 too, it's nice not to feel redundant.

I've a question about the scales, my pads (4 and 5, 8 and 9, 12 and 13) play the same note when in INKEY mode (obviously to keep the notes in the right key). Is it possible to set it up so each pad plays a unique note of the scale, giving me an extra 3 notes of the scale?

Forgive me if this has been covered, I did check over the last 13 pages and couldn't find this discussion but I could've missed it.

Thanks again -great functional script .

[TommyMotion]

Actually after looking at your Intro clip, the pads work fine. It must be my controller, or a MK1 thing?

[TeotiGraphix]

Hey Mike
The script is great. Thanks for taking the time to develop MK1 too, it's nice not to feel redundant.

I've a question about the scales, my pads (4 and 5, 8 and 9, 12 and 13) play the same note when in INKEY mode (obviously to keep the notes in the right key). Is it possible to set it up so each pad plays a unique note of the scale, giving me an extra 3 notes of the scale?

Forgive me if this has been covered, I did check over the last 13 pages and couldn't find this discussion but I could've missed it.

Thanks again -great functional script .

Yes, there was a bug in the ScaleLayoutMode this is what you want.

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

Let me know if that works for you (get the latest code from GITHub).

Mike

[TeotiGraphix]

Hi,

Just released stable version 0.1.5 with Bitwig 1.1 and above;

* Fixed ScalesLayoutMode(NAVIGATE + PAD7) [`F5`] will correctly use sequential layout of all 16 pads.
* Fixed Realign pads for [`Solo`]/[`Mute`] and display Issue #47
* Change Blue Monitor to Orange
* Change Green Mute to Orange
* Change mute behavior to mirror Bitwig mute button selection
* Fixed Scales mode, use knobs to switch between keys Issue #43
* Slowed down scales knob paging
* Added MK1 [`JOG2 turn`] Tempo 1 beat increments, [`A + JOG2 turn`] Temp in 100th increments.
* Added Fixed length project config Issue #34
* Clips created with [`PATTERN + PAD1-16`] will use this value for clip length.
* Change restart and stop to [`D + PLAY`].
* Added [`ERASE + PAD1-16`] In ClipTriggerMode, removes the selected clip from the scene.
* Added [`PATTERN + PAD1-16`] In ClipTriggerMode, creates a new clip without playing or recording.
* Added DrumChannelMode in DrumView [`MUTE`], [`SOLO`] press to display channel names on controller(current bank of 16) when muting or soloing drum channels.
* Added Maschine style [`SOLO`]color/display for DrumView.
* Added Maschine style [`MUTE`]color/off for DrumView.
* Fixed colors in Play and Drum views.
* Fixed DrumView playing notes don't light pads Issue #25
* Fixed DrumView selection when changing tracks.
* Added [`SAMPLING longpress`] Active's FrameMode to toggle Edit, Automation, Device and Mixer panels.
* [`STEP/_MODE`] improvements, arrow keys [`F`], [`G`] now page the edit grid in the clip.
* Added Coming from [`STEP/_MODE`], pressing [`PAD_MODE`] automatically activates DrumView.
* Added Auto button to be aware of panel layout Issue #23
* Added Create temp Mode for Tempo display as editing Issue #20
* Fixed DrumView mute/solo views need cleared not mappings Issue #17

Stable 0.1.5 download: http://www.teotigraphix.com/bitwig/maschine

Note; I have about 20 issues in GIT for enhancements of step sequencer and other things, so the script will get a lot better. Moss is trudging the way for sub device navigation and the Push using our framework, there are still Bitwig API bugs preventing a correct impl.

Git ZIP; https://github.com/teotigraphix/Maschin ... master.zip
GIT Changes; hhttps://github.com/teotigraphix/Maschine4Bitwig/wiki/Changes

Thanks,
Mike

[TommyMotion]

What I meant is, for now the only thing that the JogWheel turn affects is when you are in PresetMode or DeviceMode.

In PresetMode, the jogwheel scrolls through presets of the device.
In Devicemode, the jogwheel scrolls through the device pages. You cannot be in Macro, Common etc, they don't have pages, only Device [SELECT + F1].

You get to PresetMode by [NAVIGATE + PAD1], [SELECT + F1], [BROWSE]

Mike

I've tried it many times, including in previously video. No reaction...

OK I think I finally nailed down the missing line!

this.onJogWheelInternal (increase);

Forgot to add that in the MK1ViewExtensions file, this should really work now. If it doesn't or the scrolling seems weird I will need to work on how the increment is set in the template.

Let me know.

Update in GIT.

Mike

Sorry one other thing Mike: The scrolling of the jog (volume) still seems weird. It's responding but jumping around the pages without any control on where it ends up?