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

[Sekops]

Might it be possible to remap the pots to control the volume / gain on a tool device on each track, or to a different parameter such as the “In” value of Kclip to push the volume into a clipper? I prefer to automate these, rather than record automation on the track volume. After all, recording analog automation is the killer feature of Roto Control.

All instances of a plugin will have the same configuration.

How does it handle hidden tracks in Bitwig? Are these ‘counted’ within the 64 track limit? How does it handle projects with more than 64 tracks? Is it just the first 64 that are usable?

Hidden tracks are not counted. So, if you hide the first 64, you will see 64 more
You can access only 8 pages (8x8 = 64)

On the first point. Is the Controller script customisable such as when using Roto-Control in Mix mode, rather than adjusting the channel volume, it could adjust a plugin parameter, e.g. Tool's volume or KClip's "In"?

On the 64 track limit point. If, inside my Bitwig Project I enter a group that has less than 64 tracks, but the main project has more than 64 tracks total, will Roto Control see all tracks within the group?

[moss]

On the first point. Is the Controller script customisable such as when using Roto-Control in Mix mode, rather than adjusting the channel volume, it could adjust a plugin parameter, e.g. Tool's volume or KClip's "In"?

I cannot change anything. Everything is implemented in the Roto-Control itself. I can only fill in data. That is the big issue with this approach. Real changes can only be done by Melbourne Instruments.

On the 64 track limit point. If, inside my Bitwig Project I enter a group that has less than 64 tracks, but the main project has more than 64 tracks total, will Roto Control see all tracks within the group?

There is no hierarchical track navigation on the device. All tracks are always shown, except when a group is closed.

[Sekops]

Thanks for the help understanding this, much appreciated.

Does closing a group help with the 64 track limitation in any way?

[moss]

Thanks for the help understanding this, much appreciated.

Does closing a group help with the 64 track limitation in any way?

Yes. If you close it, only the group track will be shown.

[Unconformed]

It is probably user error, hoping you can help?

I have placed focus on the clip. added a clip with push and via GUI.

I have used push 1 with Ableton no issues in the past.

Here is an example image.

https://imgur.com/a/mJoTy0g

Please show me a screenshot of Bitwig as well.
It is hard to tell from your picture but it might be that the 1st page of the sequence is not selected.
The 4x4 square right to the drum pads select the loop and edit page. Try to press left/upper pad.

Hi

I got it working, selecting the bottom highlighted item in the push.

https://imgur.com/a/aMJPS0k

Are the options (drum, drum64 etc) supposed to be aligned like that?

Screen as requested (noting I got it working).

https://imgur.com/a/KQVkoi4

It does seem like something in not just right, but perhaps it is fine?

Ty either way!

[Unconformed]

Also
Is there anything particularly special going on here with Richie Hawtin's set-up that can't be done with the Push 1? did you write thee script for him:)

[moss]

Also
Is there anything particularly special going on here with Richie Hawtin's set-up that can't be done with the Push 1? did you write thee script for him:)

No and No

[Attuned]

Hey Moss. Firstly, thanks for such a great script! What you've done for the community with this is simply amazing.

I posted a bit earlier about the way to replace a drum pad with another device. I've been through all the documentation and rewatched your videos but I can't find any info about it.

If I press 'Browse' and then press the pad, I'm shown on the Push 2 screen "Replace: HH Closed". However when I select a new device it adds this device before the current one. I can of course simply delete the other devices after the new one has been added, so it's not a big deal - I just want to check if this is the correct behaviour or if I'm doing something wrong?

I'm also experiencing something else that seems to be a bug - when I'm browsing and I filter through any of the filters using the knobs or the buttons on Push 2, selecting 'AnyCat' does not remove the category filter. The last one selected stays active. This seems to happen for all of the browser filters. Holding 'Delete' and touching the knob also doesn't remove the filter selection.

Here's a video of it happening: https://share.icloud.com/photos/01c0Clz ... cROEHmrGoA

Thanks!

[Invisble Man]

Not sure what you mean. In which mode does this happen? Tried with the normal play view and could not see an issue.

In Play mode. In fact, I have a 88 keys keyboard, and it seems that after C5, sometimes before (G4), the note is not recognized. I've tried with an Arturia minilab and then augmented OCT+, same problem.

[moss]

Hey Moss. Firstly, thanks for such a great script! What you've done for the community with this is simply amazing.

I posted a bit earlier about the way to replace a drum pad with another device. I've been through all the documentation and rewatched your videos but I can't find any info about it.

If I press 'Browse' and then press the pad, I'm shown on the Push 2 screen "Replace: HH Closed". However when I select a new device it adds this device before the current one. I can of course simply delete the other devices after the new one has been added, so it's not a big deal - I just want to check if this is the correct behaviour or if I'm doing something wrong?

I'm also experiencing something else that seems to be a bug - when I'm browsing and I filter through any of the filters using the knobs or the buttons on Push 2, selecting 'AnyCat' does not remove the category filter. The last one selected stays active. This seems to happen for all of the browser filters. Holding 'Delete' and touching the knob also doesn't remove the filter selection.

Here's a video of it happening: https://share.icloud.com/photos/01c0Clz ... cROEHmrGoA

Thanks!

The API is still not adapted to the new Bitwig 5 browser. I guess that is the reason for these issues.

[AndreasObermeier]

Hello Moss. I have a Question to you. I changed from Ableton to Bitwig. What Controller is in your Eyes the best Option for Direct Access to Actions and Properties? Push2 or Launchpad Pro MK3? I ask because i want buy a Controller for your fantastic Work! Thank you Best Regards aus Berchtesgaden, Andreas ( Ich würde mich auch sehr über eine PN in Deutsch freuen)

[moss]

Hello Moss. I have a Question to you. I changed from Ableton to Bitwig. What Controller is in your Eyes the best Option for Direct Access to Actions and Properties? Push2 or Launchpad Pro MK3? I ask because i want buy a Controller for your fantastic Work! Thank you Best Regards aus Berchtesgaden, Andreas ( Ich würde mich auch sehr über eine PN in Deutsch freuen)

It always depends on what you want to do with it. You can't go too wrong with one of the Push models.

[iowastate89]

DrivenByMoss 25.0 is online!

Get it from https://mossgrabers.de

• Requires Bitwig 5.2+
• New: Added support for Melbourne Instruments ROTO CONTROL.
• Akai Force
  • Fixed: Scrolling tracks by 8 did not work.
• Elektra One
  • Fixed: The Parameter Page Buttons 2 and 5 were flipped on the Devices page. Upload the updated template to fix this.
• Kontrol MkI
  • Fixed: Option to dis-/enable 'Notify play chords' was missing.

Enjoy!

Late response, but THANK YOU for roto-control support, it is such a fun controller!

[jtmoulia]

Hi Moss, I set up a Yaeltex Turn with your DrivenByMoss 25.0. But, there were some MIDI mapping issues where I needed to rearrange the MIDI signals using Kilowhat to get the buttons and knobs working in the same order that you demonstrated in you video. There must be some build differences between our two devices.

Just wanted to give you a heads up on the difference. If it's helpful I can share my yaeltex config.

And, I'm super impressed by the integration and your contribution. Thank you!

[moss]

Hi Moss, I set up a Yaeltex Turn with your DrivenByMoss 25.0. But, there were some MIDI mapping issues where I needed to rearrange the MIDI signals using Kilowhat to get the buttons and knobs working in the same order that you demonstrated in you video. There must be some build differences between our two devices.

Just wanted to give you a heads up on the difference. If it's helpful I can share my yaeltex config.

And, I'm super impressed by the integration and your contribution. Thank you!

Did you install the template "TURN.ytx" that comes with DrivenByMoss?