Maschine4Bitwig Studio, MK2, MikroMK2 and MK1

[TeotiGraphix]

Note: There is an existing bug in Bitwig where you add a device and its not actually selected(through the API to controller), I think this is what you may have run into. It's an annoying little bug for sure.

Ahhh, good to know... this is probably what I've run into a couple of times with Push & Maschine scripts and been confused with (compared to how Push works with Live Devices, i.e.: always being able to select Devices from the controller)... the whole 'please select a device' message (and then having to select it from BW UI)?

I take it this bug has been reported and is on the radar for sorting?

Exactly... It has been on the radar from me since the beginning of the beta, if they don't fix it, i will be very sad.

But yes, it's known, don't actually know why its not fixed yet but, Volker said he fixed some things with the Channel selection and Device is a Channel do we will see.

Also, they have added a lot more selection type methods in 1.1 API, so we might actually have to update how we are handling selections to get them to work the way they should, patients daniel son.

Dom... this is an important one for usability for sure.

Mike

[dom@bitwig]

Adding devices with the + button, dragging devices to existing tracks etc. all leaves you with a valid selection, afaik.
The only case i know of where you end up with a selected track but a device chain without any selection at all is if you drag and drop a device from the browser into the project so that a new tack gets created automatically.
Do you know of more cases?

Good night!

[taoyoyo]

The only case i know of where you end up with a selected track but a device chain without any selection at all is if you drag and drop a device from the browser into the project so that a new tack gets created automatically.

... Ahh, that explains a lot... as it is my most used (i.e.: currently quickest/easiest) method of loading 3P VST instruments!

Is this method 'fixable' for avoiding this non-selected device scenario?

[TeotiGraphix]

The only case i know of where you end up with a selected track but a device chain without any selection at all is if you drag and drop a device from the browser into the project so that a new tack gets created automatically.

... Ahh, that explains a lot... as it is my most used (i.e.: currently quickest/easiest) method of loading 3P VST instruments!

Is this method 'fixable' for avoiding this non-selected device scenario?

This is what i was specifically talking about since dnd with presets is a fairly common thing, thus the usability issue I brought up.

Fixable; It should be, or at least something in their code needs to say, after dnd, create track, add device chain, select first device in the chain. So from that perspective, its a bug.

Mike

[dom@bitwig]

Not exactly a bug, but more or less an undefined state.
Whatever, i filed it as an improvement, i would like the device chain having a sensible focus selection at any time so we don't have to take care about that from the scripting side of things.

[TeotiGraphix]

Not exactly a bug, but more or less an undefined state.
Whatever, i filed it as an improvement, i would like the device chain having a sensible focus selection at any time so we don't have to take care about that from the scripting side of things.

I won't debate but if I was programming the UI, since the track was just created AND a device was just added, the first device should be selected.

In my mind, it wouldn't be a "bug" if you didn't select the track, but the track is selected, so to me the undefined state is the bug. If we can never really get into that undefined state on purpose, then it causes confusion.

So yeah, not a bug but more of a usability concern regarding consistency of the UI.

Mike

[ThomasHelzle]

I would call it a bug too since there isn't anything the script can do about it if it doesn't even know that there is something going on
The only moment where it should be possible that there is no primary device on a cursor track is when there actually is no device on the cursor track.

Now we just have to fix the "new device mapping page not being available to the controller right away" and we're mostly there.

Cheers,

Tom

[dom@bitwig]

Nah, c'mon, the definition of "bug" is not that the script can't do anything about it.
There are lot of things the scripts can't do anything about which are obviously not bugs.

That first... but does not even apply here, since the scripts can do something about it. I already did work around it when i started my little maschine script a few months ago.
Try hitting next device in Mike's script on a channel with no selection, and booom, selection there!
I think there's even selectFirstInChannel available now.
But who cares how we name it, bug, flaw, missing feature, horst or dieter... all it comes down to is that the app should feel absolutely right (i wanna do music in there!!) and it has to obey
And a device i just drag and dropped from the browser not being selected feels wrong and has to be improved!

[TeotiGraphix]

Nah, c'mon, the definition of "bug" is not that the script can't do anything about it.
There are lot of things the scripts can't do anything about which are obviously not bugs.

That first... but does not even apply here, since the scripts can do something about it. I already did work around it when i started my little maschine script a few months ago.
Try hitting next device in Mike's script on a channel with no selection, and booom, selection there!
I think there's even selectFirstInChannel available now.
But who cares how we name it, bug, flaw, missing feature, horst or dieter... all it comes down to is that the app should feel absolutely right (i wanna do music in there!!) and it has to obey
And a device i just drag and dropped from the browser not being selected feels wrong and has to be improved!

I must be stupid but I dragged a drum machine in, made sure it was in device mode pressed `>` and no dice, is that what you were talking about? (you must be talking about in general, its the cursor device working it's majic)

> And a device i just drag and dropped from the browser not being selected feels wrong and has to be improved!

Yes, it feels absolutely wrong...

Mike

[dom@bitwig]

Hm, should work, at least it did... Can't check it, still at the office and my MK2 is at home.
Whatever, device selection after create-new-track-while-dragging is decided on and filed... stuff that feels wrong gets kicked out

[TeotiGraphix]

Updates 0.1.4 alpha

# 0.1.4 [alpha]
* Added [`F1-F8`] In VolumeMode, toggles track mute.
* Added [`SELECT + F1-F8`] In VolumeMode, selects the track.
* Added [`F4`] In TrackMode, toggles monitor.
* Added [`F8`] In TrackMode, Enhanced with dual top row display toggle to switch between button and knob labels.
- Fixed StepSequencerView step layout to mirror Maschine's bottom to top layout.
- Added [`SCENE + PAD1-16`] In SceneView, creates an empty clip, buggy, need to get index of selected clip (acts like New right now).
* Fixed pressing [`SCENE`] in SceneView now consistently stops/plays slots regardless of the track's RecArm, will not start recording.
* Added [`D + NAVIGATE`] initial prototype of second shift and Navigate view.
* 1 > Undo, 2 > Redo, 5 > Quantize, 9 > Clear/Delete (just prototyping for now)
* Fixed AccentMode, [`ENCODER9`] sets fixed accent value and [`F8`] toggles fixed accent on/off.
* Fixed MK1 JogWheel, confirmed. Missing internal jogwheel call.
* Added Studio [`STEP_MODE`], MK1, MK2 [`STEP`] StepSequencerView first prototype.
* Added [`SELECT press`] In StepSequencerView, will select that drum channel that is being edited in the step sequencer.

I am going through all the modes and tidying, tightening, refactoring and making them pretty extensible for the future.

Adding more ways to select tracks in different modes, example VolumeMode you can now press [SELECT + F1-F8] to select the track in that mode.

TrackMode got some enhancements as well, the [F8] button now toggles between button and knob label display for the top row display.

Also in TrackMode add monitor toggle so [F1-F4] is Mute, Solo, RecArm and Monitor.

Also a little prototype code with a new 2nd Shift Button [D], this will work great for massive additional navigation. So [D + NAVIGATE] takes you do a new action view. Pad 1 > Undo, Pad 2 > Redo, 5 > Pad Quantize, 9 > Pad Clear/Delete, I haven't yet made a mode display for this yet.

Mike

GIT Zip: https://github.com/teotigraphix/Maschin ... master.zip
Changes: https://github.com/teotigraphix/Maschin ... ki/Changes

[dom@bitwig]

Wow, even more additons!
Say, shouldn't the browse mode work regardless of the chosen parameter page in device mode?
Currently it only works for the first, but i could swear it also was working while being on the macro page or somewhere else?

[TeotiGraphix]

Wow, even more additons!
Say, shouldn't the browse mode work regardless of the chosen parameter page in device mode?
Currently it only works for the first, but i could swear it also was working while being on the macro page or somewhere else?

The Browse is a bug, it should work in all device bank modes, I haven't got to that yet. And yes currently it should work in PresetMode.

I did make a new view and mode. TrackView! [D + SELECT] makes it to where you can choose Pad1-8 to select a track in the track bank, they are colored with track colors and the display lists the track names.

Then Pad 15,16 page the track bank up/down, really fast track navigation now.

I have a question, now that I have implemented a second shift with [D], I am using [D + SELECT] to get the the TrackView, but now it seems like [SELECT] should be the TrackView since its a fast way to navigate and now [D +SELECT] should be device bank selection.

What do you think?

Mike

[dom@bitwig]

Ah, but that's not committed yet, right?
Changing it like you suggested sounds like the better way 'round.

Myself i'm not a big user of the "bank of 8 style" navigation on such "smaller" controllers that are not actually mixing desk replacements.
But i would definetly keep it in, sometimes it comes in handy, like hitting several mutes at once when doing live gigs and stuff.
But yes, most of the time on something like machine i like just cursoring around with a cursor track.
Mainly i scroll up and down, do a volume change here, solo or mute something there, enter device view to tweak a device or hit record to record something new. That's like 90% of what i do on a controller.

I was thinking about how it would fit both workflows and merge the "bank of 8 modes" with having cursor track navigation available regardless of the mode you're in: track up and down always works globally, jog dial is always volume and solo and mute on the controller are always solo and mute of the current track. Shift-solo and Shift-mute would then do the bank solo and mute you already implemented, but besides that i can't see anything bigger clashing at the moment...

[TeotiGraphix]

Ah, but that's not committed yet, right?
Changing it like you suggested sounds like the better way 'round.

Myself i'm not a big user of the "bank of 8 style" navigation on such "smaller" controllers that are not actually mixing desk replacements.
But i would definetly keep it in, sometimes it comes in handy, like hitting several mutes at once when doing live gigs and stuff.
But yes, most of the time on something like machine i like just cursoring around with a cursor track.
Mainly i scroll up and down, do a volume change here, solo or mute something there, enter device view to tweak a device or hit record to record something new. That's like 90% of what i do on a controller.

I was thinking about how it would fit both workflows and merge the "bank of 8 modes" with having cursor track navigation available regardless of the mode you're in: track up and down always works globally, jog dial is always volume and solo and mute on the controller are always solo and mute of the current track. Shift-solo and Shift-mute would then do the bank solo and mute you already implemented, but besides that i can't see anything bigger clashing at the moment...

Yes, I was thinking about live stuff, i do a lot live with the Push and Maschine, so call me self centered.

* Added [D + SELECT] TrackView and TrackViewMode to select, prototype idea.

I haven't changed the [SELECT] right now though.

Updated Git so you could check it out.

I like your idea about the global cursor track paradigm. I will have to see how that fits in with the current code.

I think I am at a state now where I will sit back, refactor a bit and write documentation of what I have. I do change tracks a lot so I added this feature.

Mike