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

[dcarmich]

Hello mister moss. AKAI Fire and Bitwig 4.4.2 seems to have issue with your script.

Since the latest Bitwig update (4.4.2) Your script and AKAI Fire does not work properly and entirely anymore.

In a way that prior to this 4.4.2 update when I was shutting Bitwig projects then the FIRE controller said goodbye, and it shut down itself (turned lights off). After update 4.4.2 it does not work like that any more it stays open all the time, no matter which Bitwig project is closed or opened, and I need to unplug USB. Everything else seems to be working it just does not turn off controller anymore.

Now I am unsure is this Bitwig issue or your script issue, perhaps they changed something?

Can anyone confirm?

I've had the same issue with my Launchpad Pro Mk3.

[moxxi]

Hello mister moss. AKAI Fire and Bitwig 4.4.2 seems to have issue with your script.

Since the latest Bitwig update (4.4.2) Your script and AKAI Fire does not work properly and entirely anymore.

In a way that prior to this 4.4.2 update when I was shutting Bitwig projects then the FIRE controller said goodbye, and it shut down itself (turned lights off). After update 4.4.2 it does not work like that any more it stays open all the time, no matter which Bitwig project is closed or opened, and I need to unplug USB. Everything else seems to be working it just does not turn off controller anymore.

Now I am unsure is this Bitwig issue or your script issue, perhaps they changed something?

Can anyone confirm?

Check this post viewtopic.php?p=8545849#p8545849 and this post viewtopic.php?p=8549321#p8549321

As Moss said, the issue was introduced in 4.4.1.

[moss]

I found a little issue. When either the drum 4 or drum 8 sequencers are active and I move sequncer page up/down with the octave up/down buttons, on the display it says I move by 16 notes, which is wrong and little confusing.

Can't see anything wrong. When I press Octave up it say "E1.." and if I down again "C1".

The issue is not with the lower note of the range, but rather with the higher note.
For example, for the drum 4 it says 'C1 to Eb2', 'E1 to G2', et cetera. How it can be more than an octave if it only can sequence 4 pads at once? Same with drum 8.
It's really a minor issue though. I already got used to it, but the first time I tried using drum 4 it was disorienting a bit.

Ah, I see. Will look into it.

[moss]

Regarding the APC40 problem: There is still something wrong with the drum pads. Counting from the bottom up:

-The first row works fine, now. The drumpads play and select the according pads on the drum machine. (Row content: Kick1, Snare, Hi-Hat, Hi-Hat)
-The second row to the bottom only selects the drumpads from the second row of the drummachine, but no sound is triggered. Just like before the update. (Row content: Kick2, Clap, Rim, Snare)
-The third row from the bottom selects the drumpad from the third row, but plays the drumpad from the second row.
Shaker selected, Clap played (Row content: Kick3, Shaker, Clave, Cowbell)

You are still awesome!

Will check.

[moss]

It's such a bummer we can't change gain/pan/pitch/timbre/pressure spread value via the Bitwig API. Since you can assign those expressions to any parameter in Bitwig, that would turn Push into a very powerful step sequencer where you would be able to add desired amount of randomness to any step to up to five different parameters.
Where to submit a feature request? https://github.com/teotigraphix/Framework4Bitwig ?

You need to send it to Bitwig support.

[kmonkey]

Hello mister moss. AKAI Fire and Bitwig 4.4.2 seems to have issue with your script.

Since the latest Bitwig update (4.4.2) Your script and AKAI Fire does not work properly and entirely anymore.

In a way that prior to this 4.4.2 update when I was shutting Bitwig projects then the FIRE controller said goodbye, and it shut down itself (turned lights off). After update 4.4.2 it does not work like that any more it stays open all the time, no matter which Bitwig project is closed or opened, and I need to unplug USB. Everything else seems to be working it just does not turn off controller anymore.

Now I am unsure is this Bitwig issue or your script issue, perhaps they changed something?

Can anyone confirm?

Check this post viewtopic.php?p=8545849#p8545849 and this post viewtopic.php?p=8549321#p8549321

As Moss said, the issue was introduced in 4.4.1.

Thank you for additional info

[KTlin]

DrivenByMoss 18.2.0 is out!
...
[*]APC40
[*]New: Footswitches are now configurable in the settings.

This is great! Very useful to have all those option assignable to the footswitch pedal. But I'm missing a very simple start recording on the selected clip option. Those two options available in this latest update (New Button and Clip Based Looper) both create a new clip with a predefined length but I much prefer to have the option to start recording a new clip when I press the footswitch pedal and end the recording when I press it again (which is how the footswitch works in Ableton). Would it be possible to implement something like this?

And another thing: I would like to be able to control the Cue Level with the Cue Level knob (like it's the case in Ableton) and not to move the play cursor with it. Would it be possible to add this option in the settings?

[moss]

Hello mister moss. AKAI Fire and Bitwig 4.4.2 seems to have issue with your script.

Since the latest Bitwig update (4.4.2) Your script and AKAI Fire does not work properly and entirely anymore.

In a way that prior to this 4.4.2 update when I was shutting Bitwig projects then the FIRE controller said goodbye, and it shut down itself (turned lights off). After update 4.4.2 it does not work like that any more it stays open all the time, no matter which Bitwig project is closed or opened, and I need to unplug USB. Everything else seems to be working it just does not turn off controller anymore.

Now I am unsure is this Bitwig issue or your script issue, perhaps they changed something?

Can anyone confirm?

Check this post viewtopic.php?p=8545849#p8545849 and this post viewtopic.php?p=8549321#p8549321

As Moss said, the issue was introduced in 4.4.1.

Thank you for additional info

Fixed in 4.4.3!

[catzilla]

Hey,
I'm working on a big update for the Push 2 integration. It aims at improving MIDI clip visualization on the p2 display.
Some features:
higher vertical resolution for finer timing accuracy (256 instead of current 8 )
expressions & operators visualizations (velocity, panning, repeats, recurrence and so on)
drum machine support: notes are named and colored the same as pads in the drum machine
full support for scales (notes highlighted differently depending on how they relate to the current scale). When 'In Scale' is active, notes that are off scale are hidden
folding (i.e. hiding key lanes where notes are not present)
for drum machine, key lanes of empty drum pads can be hidden
synchronization with sequencers with an option to zoom out and in (in the last photo I attached you can see a green frame - that is current sequencer page)
scroll bars (when either of the sequencers is active)
currently playing notes/keys are highlighted, either that are played in clips or 'by hand'
it just looks better

There are more features, I just can't remeber them all for now.

I'm going to submit a pull request when I'm done. Now I'm polishing and testing things.
Let me know know what you think guys.

[petedako]

Wünderbar. I think it looks fabulous Catzilla.

[xv770]

I'm new to OSC and have an embarrassingly simple question: I am able to send OSC messages from Bitwig to another app correctly, but so far I've only been able to send what seem to be "GUI" related messages (fader volumes, whether a channel is selected or muted, transport running etc).

I see there's a TON of options of messages to send, but I haven't figured out something super basic which is how to a) send midi triggers from Bitwig to OSC, and b) how to send modulation messages. Can someone please enlighten me what I'm missing?

Sorry for the silly question. Thanks.

[kmonkey]

Hello mister moss. AKAI Fire and Bitwig 4.4.2 seems to have issue with your script.

Since the latest Bitwig update (4.4.2) Your script and AKAI Fire does not work properly and entirely anymore.

In a way that prior to this 4.4.2 update when I was shutting Bitwig projects then the FIRE controller said goodbye, and it shut down itself (turned lights off). After update 4.4.2 it does not work like that any more it stays open all the time, no matter which Bitwig project is closed or opened, and I need to unplug USB. Everything else seems to be working it just does not turn off controller anymore.

Now I am unsure is this Bitwig issue or your script issue, perhaps they changed something?

Can anyone confirm?

Check this post viewtopic.php?p=8545849#p8545849 and this post viewtopic.php?p=8549321#p8549321

As Moss said, the issue was introduced in 4.4.1.

Thank you for additional info

Fixed in 4.4.3!

Indeed. Thank you!!

[moss]

I'm new to OSC and have an embarrassingly simple question: I am able to send OSC messages from Bitwig to another app correctly, but so far I've only been able to send what seem to be "GUI" related messages (fader volumes, whether a channel is selected or muted, transport running etc).

I see there's a TON of options of messages to send, but I haven't figured out something super basic which is how to a) send midi triggers from Bitwig to OSC, and b) how to send modulation messages. Can someone please enlighten me what I'm missing?

Sorry for the silly question. Thanks.

Not silly at all. Sending notes out of Bitwig is not supported because it is not possible to do this in a synchronized way. What could be done is to support sequencers but I decided against it since it would require many many commands.

For sending to Bitwig look at the /vkb_midi commands.

[moss]

Hey,
I'm working on a big update for the Push 2 integration. It aims at improving MIDI clip visualization on the p2 display.
Some features:
higher vertical resolution for finer timing accuracy (256 instead of current 8 )
expressions & operators visualizations (velocity, panning, repeats, recurrence and so on)
drum machine support: notes are named and colored the same as pads in the drum machine
full support for scales (notes highlighted differently depending on how they relate to the current scale). When 'In Scale' is active, notes that are off scale are hidden
folding (i.e. hiding key lanes where notes are not present)
for drum machine, key lanes of empty drum pads can be hidden
synchronization with sequencers with an option to zoom out and in (in the last photo I attached you can see a green frame - that is current sequencer page)
scroll bars (when either of the sequencers is active)
currently playing notes/keys are highlighted, either that are played in clips or 'by hand'
it just looks better

Wow, looks awesome!

[esq1]

Hey,
I'm working on a big update for the Push 2 integration. It aims at improving MIDI clip visualization on the p2 display.
Some features:
higher vertical resolution for finer timing accuracy (256 instead of current 8 )
expressions & operators visualizations (velocity, panning, repeats, recurrence and so on)
drum machine support: notes are named and colored the same as pads in the drum machine
full support for scales (notes highlighted differently depending on how they relate to the current scale). When 'In Scale' is active, notes that are off scale are hidden
folding (i.e. hiding key lanes where notes are not present)
for drum machine, key lanes of empty drum pads can be hidden
synchronization with sequencers with an option to zoom out and in (in the last photo I attached you can see a green frame - that is current sequencer page)
scroll bars (when either of the sequencers is active)
currently playing notes/keys are highlighted, either that are played in clips or 'by hand'
it just looks better

Wow, looks awesome!

Looks great. A youtube video will be fine.