DrivenByMoss: Bitwig extension for many hardware controllers (version 26.6.2)

[sj1]

Hi,

Is there a way inside of Bitwig to see what the currently deployed version of DBM is?

DBM in Bitwig 4.0b6.jpg

My apologies if it is there but I don't see it!

If there is no-such, then I suggest that version display as a future addition.

Thanks.

[sj1]

Using DBM with Launchpad Pro Mk3 in Bitwig 4.0b6 -

I am noticiing a strangeness/inconsistency in the Session Overview display wrt. my actual session orientation.

Example: I see on the LPP each track as a column (just like Bitwig clip launcher display itself). I use the arrow (or click in Bitwig) to move to the 2nd set of 8 (i.e columns 9-16).

What I expect to see then in the Session Overview (when I hold down the Session button) is for the top row, 2nd pad to be highlighted - to match what I was just looking at prior to going into the Session Overview.

Instead, I see the 2nd row, first pad highlighted. which might make sense if I had been in the alternate orientation (but I was not).

Then, when I leave Session Overview my orientation is reversed from where I entered it.

So, it seems the long-press which takes me into Session Overview is -also- (undesirably) acting as a short-press which is used to change orientation.

The way it is behaving, I cannot achieve stable navigation.

Is there any way I can prevent a long-press from changing the orientation? Or is this something you could perhaps fix Jürgen?

Thanks.

[moss]

Hi,

Is there a way inside of Bitwig to see what the currently deployed version of DBM is?

My apologies if it is there but I don't see it!

If there is no-such, then I suggest that version display as a future addition.

Thanks.

It was there in the past but it was removed, no idea why. Please send a request to Bitwig.

However, there are 2 workarounds:

1) Click on the "?" to open the DrivenByMoss manual. In the manual check the Changes list at the end for the latest version number.
2) Right click on the controller header and select "Reveal file". Unzip DrivenByMoss.bwextension and check the file META-INF\MANIFEST.MF for the Implementation-Version.

[sj1]

Thanks. (Time for me to update!)

Inquiry to Bitwig Beta sent.

[sj1]

OK, I'll note that after the update to DBM 12.3.1 the comments on Session Overview still apply.

Instead of getting a Session Overview display matching the actual Session view of where I came from, I get the opposite (orientation) Session Overview display.

[moss]

Using DBM with Launchpad Pro Mk3 in Bitwig 4.0b6 -

I am noticiing a strangeness/inconsistency in the Session Overview display wrt. my actual session orientation.

Example: I see on the LPP each track as a column (just like Bitwig clip launcher display itself). I use the arrow (or click in Bitwig) to move to the 2nd set of 8 (i.e columns 9-16).

What I expect to see then in the Session Overview (when I hold down the Session button) is for the top row, 2nd pad to be highlighted - to match what I was just looking at prior to going into the Session Overview.

Instead, I see the 2nd row, first pad highlighted. which might make sense if I had been in the alternate orientation (but I was not).

Then, when I leave Session Overview my orientation is reversed from where I entered it.

So, it seems the long-press which takes me into Session Overview is -also- (undesirably) acting as a short-press which is used to change orientation.

The way it is behaving, I cannot achieve stable navigation.

Is there any way I can prevent a long-press from changing the orientation? Or is this something you could perhaps fix Jürgen?

Thanks.

Thanks for reporting! Will be fixed in the next update!

[sj1]

Wonderful! Thanks Jürgen!

[questionaire]

I'm using Novation SL MKIII keyboard. The monitor buttons do nothing. I would expect that pressing the monitor button would change the monitor state in a sequential way from auto/on/off. Is my assumption right?
I have the latest version script. 12.3.1

[Trancer]

Hello Moss,

I just bought the latest version of Bitwig 3 and have a Push 2 / Komplet kontrol S61 mk2 and a Maschine Mikro mk3.

Can you tell me what script version I need to download to make these three Machines work in Bitwig 3?

The most important is Push 2 and the Komplet Kontrol S61 mk2.

These scripts will also be compatible with version 4 of Bitwig?

Thank you in advance for your reply.

I am a bit confused and not used to handling this stuff at all.

[ozias_leduc]

Hi there! I'm using Push 2 - is there a way to get the play button to behave the same as the space bar?

The manual says : "Play - Start/Stop playback. Double click to move play cursor to start of song. You can configure the behavior on stop in the preferences."

But when I press play twice - ie to stop and start again - it counts this as a double click unless I consciously go very slow. Is there a way to disable this behaviour ?

[moss]

I'm using Novation SL MKIII keyboard. The monitor buttons do nothing. I would expect that pressing the monitor button would change the monitor state in a sequential way from auto/on/off. Is my assumption right?
I have the latest version script. 12.3.1

On the right hand side, press the up or down button to toggle to monitor/rec arm. The upper 8 buttons (lit in green) toggle now monitor between on/off. Note that this only works if an input is selected for the track.

[moss]

Hello Moss,

I just bought the latest version of Bitwig 3 and have a Push 2 / Komplet kontrol S61 mk2 and a Maschine Mikro mk3.

Can you tell me what script version I need to download to make these three Machines work in Bitwig 3?

The most important is Push 2 and the Komplet Kontrol S61 mk2.

These scripts will also be compatible with version 4 of Bitwig?

Thank you in advance for your reply.

I am a bit confused and not used to handling this stuff at all.

Step 1: Don't be afraid

Simply download the latest version (currently 12.3.1) from my homepage: http://www.mossgrabers.de/Software/Bitwig/Bitwig.html

Watch the video for the basic installation, which is linked on the page as well. Also note the included manual and read the chapters for your devices.

[moss]

Hi there! I'm using Push 2 - is there a way to get the play button to behave the same as the space bar?

The manual says : "Play - Start/Stop playback. Double click to move play cursor to start of song. You can configure the behavior on stop in the preferences."

But when I press play twice - ie to stop and start again - it counts this as a double click unless I consciously go very slow. Is there a way to disable this behaviour ?

Changing the "Behavour on stop" setting to "Pause" should do the trick.

[moss]

DrivenByMoss 12.3.2 is online!

Get it from http://mossgrabers.de

• Fire
  • New: Scene 3+Pad in Drum 64 mode soloes the drum sound.
  • New: Scene 4+Pad in Drum 64 mode mutes the drum sound.
  • Fixed: Pattern up/down button did trigger twice.
• Launchkey Mini Mk3
  • Fixed: Navigation with Shift+Track left / right was broken.
• Launchpad
  • Fixed: Exiting birds-eye view did also toggle session flip.
• Launchpad Pro Mk3
  • New: Fixed Length + Track buttons creates new clips of different lengths.
• Maschine (except Mikro)
  • New: Mk2: Step-left+Select: Toggle note edit (reload the template!).
  • New: Select + Pattern: Select the clip without starting it.
  • New: Select + Scene: Select the scene without starting it.
  • New: Select + Drum Pad: Select the drum without playing it.
• Push 1/2
  • New: Select+Pad in session mode displays the name of the selected clip (if it has one).

Enjoy!

[questionaire]

I'm using Novation SL MKIII keyboard. The monitor buttons do nothing. I would expect that pressing the monitor button would change the monitor state in a sequential way from auto/on/off. Is my assumption right?
I have the latest version script. 12.3.1

On the right hand side, press the up or down button to toggle to monitor/rec arm. The upper 8 buttons (lit in green) toggle now monitor between on/off. Note that this only works if an input is selected for the track.

That is the thing it does not work at my system. I use windows 10 and bitwig 4 beta 7, could it be that it does not work with version 4?