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

[moss]

Also a few feature requests to consider:
- In Drum Mode Sequencer View: Use the green up and down arrows to change "Edit Page 1,2,3 ect" instead of current Offset
- In Session Mode "Stop Solo Mute" menu maybe add New Clip Lenght selection on the 1st row

Noted.

Ok, thanks for you replies! One request more would be to have the possibility to focus Track and Project Remotes, for eg with the Device Select button menu as now with the normal devices. Cheers!

Will see what I can do.

[Kabob7358]

Hi!
I use your extension with launchpad X and work great but i have a question: in the drum sequencer mode, the button 1 of the addictional function (Keep pressed and select a drum pad to select it without sounding it.) is there a way to invert the function (press to select it and it will sound) or to change it in a "toggle" button?

[moss]

Hi!
I use your extension with launchpad X and work great but i have a question: in the drum sequencer mode, the button 1 of the addictional function (Keep pressed and select a drum pad to select it without sounding it.) is there a way to invert the function (press to select it and it will sound) or to change it in a "toggle" button?

Currently. not.

[nowiamone]

Hi Jürgen,
Am i wrongly expecting /eq/param addresses to be alive?
/eq/param/1-8/name
/eq/param/1-8/valueStr
/eq/param/1-8/value
etc, and /eq/page/selected/name seem to be dead?
I’m asking because i thought i could make a quick EQ control which is built exactly like the control for the /device, but it seems that’s impossible. It’s not that big of a deal, because for a nice EQ interface, it’s better anyway to have no switching around pages. So my main question is about the /eq specific additional adresses: /q,/gain:
In case of the reset-function, it doesn’t seem to work as expected.
/eq/gain/1 (0/127) is working properly, but /eq/gain/1/reset does just the same, not resetting. Also not working are /eq/gain/reset/1, and /eq/gain/1 reset[reset sent as string], and /eq/gain/1/value/reset
How do i reset parameters of the /eq, specifically the /gain? I was trying to make a reset button via /eq/gain/1 and sending a 63 or 64 value. But sadly, that translates to either -0.2 or +0.2db, which isn't a true reset to 0.0db. Maybe there's a hack to send 63.5 , haha, but it doesnt seem to work.
Thank you for your help!

Ah, seems I was answering too quick. The EQ has specific parameters, see the EQ section after /device in the manual.

so just to be sure: there's no "reset" (return to default) osc function for gain and q, right?
At least it's not part of the manual (but i was hoping it exists somehow, haha).

In case you've overlooked my other post: there's a new bug since drivenbymoss 21.2.0 with the Komplete Kontrol s49mk2 4-directional-knob, when moving the selection cursor in the cliplauncher with it. Selection gets stuck / jumps back, when trying to move from scene to scene in the cliplauncher, happening only after having switched from track to track in the cliplauncher. Thank you!

[moss]

so just to be sure: there's no "reset" (return to default) osc function for gain and q, right?
At least it's not part of the manual (but i was hoping it exists somehow, haha).

Makes sense to add them. Maybe I simply could add all the parameters...

In case you've overlooked my other post: there's a new bug since drivenbymoss 21.2.0 with the Komplete Kontrol s49mk2 4-directional-knob, when moving the selection cursor in the cliplauncher with it. Selection gets stuck / jumps back, when trying to move from scene to scene in the cliplauncher, happening only after having switched from track to track in the cliplauncher. Thank you!

Up to my knowledge that is a Bitwig bug.

[nowiamone]

so just to be sure: there's no "reset" (return to default) osc function for gain and q, right?
At least it's not part of the manual (but i was hoping it exists somehow, haha).

Makes sense to add them. Maybe I simply could add all the parameters...

In case you've overlooked my other post: there's a new bug since drivenbymoss 21.2.0 with the Komplete Kontrol s49mk2 4-directional-knob, when moving the selection cursor in the cliplauncher with it. Selection gets stuck / jumps back, when trying to move from scene to scene in the cliplauncher, happening only after having switched from track to track in the cliplauncher. Thank you!

Up to my knowledge that is a Bitwig bug.

Thanks!

The bug wasn't happening with My Bitwig 5.0.6 together with DrivenByMoss-20.3.2.
Now, with Bitwig 5.0.6 and DrivenByMoss-21.2.0 it's happening.
I haven't tested the Bitwig internal-script for the KompleteKontrolS49MK2 keyboard for quite some while, but now i did. I almost couldn't believe it: The movement in the cliplauncher is working properly now Even moving through groups!? That's a strange development of things, because many months ago, i permanently switched to using only your script, because it was working better (and it's still so much better designed, with customization in the controllerpanel.. would love it, if it would be restored to former greatness, )!

[luistro]

Hey moss last bitwig 5.0.4 not work fix accent in launchpad x

[lao974]

Hi, I've found some bugs with Push 2 on Bitwig 5.0.4.

1. The browse menu does not show Collection, and the configuration options for show/hide Browser elements are shifted. E.g. Collection controls Location, Location controls File Type, etc. Device Type and Device do nothing. I've found no way to make Collection appear.
2. In the browse menu, when scrolling through tags, the list changes as the selection is changed. This is very annoying, makes tag selection kind of useless from push.

Your Bitwig extension for Push is a lifesaver to have. Thanks very much for your work.

[Elkiwixmandalaz]

Elkiwixmandalaz wrote: ↑Thu Jun 29, 2023 7:14 pm
Hi Again, I just went ahead and try toggling through "NOTES" on Bitwig with the LaunchPad Pro and I am notable to toggle through either "NOTE" or "CHORD". I am currently trying to use the LaunchPad as a key board like I did in the past. I simple grabbed the sampler on Bitwig, and selected "Acoustic Piano". I hope that you can help me out. I also grabbed the latest version of DrivenByMoss and put it on my extensions folder.

Thanks in Advance!
What is your question?


Hi Mate,
My question is. How do I activate the piano roll on my launchpad pro? I mean there was a key board if you pressed CHORD in the past. Just wondering if it will still be available or not? I would like some keys, might buy myself a keyboard if you say you took that option away.

Thanks in Advance, Ricardo Fernandez or EL Kiwix Mandalaz

[Jed]

Moss for Push 3 please please please integrate the pad sensitivity as per Ableton (threshold, drive, compand, and range settings) so that the pads are as beautiful to use as they are in Ableton.

That would be super awesome

Thanks
Jed

[thepisiest]

Hi, I have a question. I have a Push 2 and have been trying your script which, by the way, is pretty awesome, and I've been looking for a function it has in ableton. In ableton, when you press the record button, it creates a new clip in a empty slot and stop when you press it again. I have been reading you manual and just have found two possibilities:
1. Press new or fixed lenght and create a clip with an specific lenght.
2. Press a "red pad" on an armed track in the session view and, when ended, press the record button and it will stop recording and start looping that clip.
The thing is, I believe it's much more faster to just press one button to start the recording and the same again to stop it. That way you don't have to worry about lenghts and doesn't have to be doing buttons combinations which usually drives me to press it too late and record out of time.
As I said, I didn't find this option in the manual but I suppose It's probably there so, if you can tell me how to do it, I will appreciate it a lot.
Thank you very much in advance!!!

[Yepman]

I have a Launchpad S and would like to implement support for your extension. Can you give me some hint, how this would be achieved best, i.e. where to make changes to your source code? I did not yet dive into programming of the Launchpad, but my guess is that the protocol is somewhat different. Do you have a protocol layer in your code, so that another protocol can be "plugged in"?

[synce]

Hi Moss, great work on the Akai Fire!

I think I encountered a bug in Note Editing. After I enable Note Editing, select a note, then turn the Select knob, the values go either up or down by 0.8, 2, 8.4, 34, 96. No matter which way I turn the knob, the values will go in the same direction until I cancel and try again.

I'm new to BitWig but I inspected the piano roll and it seems the notes aren't actually moving but "micro-pitch expression editing" is happening. Screenshot attached.

Not sure what's going on, what do you think?
I'm using 21.2.0.

Also, I think you didn't mention it in the documentation but we can transpose clips by an octave by pushing and turning the Select knob.

[agrover]

Hi Moss, found some weird behavior (maybe a bug?)
I have a flexi device that assigns Track: Select Previous Track and Track: Select Next Track, and these allow me to use my device to move up and down tracks with no issue, unless I have inactive tracks, and I have "show deactivated tracks" turned off. Then, it does not advance the selected track to the next active track as expected.

[mevla]

On the Launchpad (Mini) the 'red box; sometimes does not follow. Not that much of an important issue I presume but wanted to report it. In the following example all 8 tracks including the group track are on the Launchpad which means the box should start one track lower :

launchpadBox.jpg