Bitwig

moss · Post by **moss** » Sun Jan 03, 2021 2:16 pm

ChrisDW wrote: Sun Jan 03, 2021 1:50 pm I'm using your script with the Launchpad X. Is there any way to stop individual clips from playing while in session mode?

I used to use Maschine Jam and you could play/stop any clip by pressing the same pad which made live playing very fast.

Anyway you could have that on the Launchpad? Press to play and press again to stop?

You can show up the stop mode (first row) in session mode, which stops the playing clip of a track. This how this use-case is intended on the Launchpads.

ChrisDW · Post by **ChrisDW** » Sun Jan 03, 2021 2:48 pm

Everything is buggy when I try this with 'Flip Session' ON. Trying to play different clips in this mode results in other clips starting/recording etc.

Appears to work fine when 'Flip Session' is OFF.

Can you try and reproduce?

xtreme sounds · Post by **xtreme sounds** » Mon Jan 04, 2021 4:09 pm

HI there. Something strange happened on this project for the fire. I have never seen it before. When I press the scenes launch, record and automation is armed. It seems to only be happening in this project. It happens even if no track is armed. I started a new project and it didnt happen again. Any ideas? Another weird thing that just happened was pressing the scene 1 button using the mouse it wanted to count in before playing but I wasnt recording a clip or anything. It fixed after pressing the scene 1 launch on the fire. So there is some sort of strange buggy things happening if we switch between using the mouse for scenes verses the fire controller for scenes.

Could it have something to do with play settings like play recorded settings (under the play button) and causing some sort of conflict?

xtreme sounds · Post by **xtreme sounds** » Mon Jan 04, 2021 4:38 pm

Fire issue 2 - For some reason the send FX1 (added Delay 2) on the drums are still sending even though I turned it down to minus infinity db. Not all the pads but the kick is frozen with a delay on it.

moss · Post by **moss** » Mon Jan 04, 2021 6:23 pm

ChrisDW wrote: Sun Jan 03, 2021 2:48 pm Everything is buggy when I try this with 'Flip Session' ON. Trying to play different clips in this mode results in other clips starting/recording etc.

Appears to work fine when 'Flip Session' is OFF.

Can you try and reproduce?

You are right, there are some bugs when flipped and control mode is on. Will see how I can fix that...

moss · Post by **moss** » Mon Jan 04, 2021 6:29 pm

melodyz wrote: Mon Jan 04, 2021 4:38 pm Fire issue 2 - For some reason the send FX1 (added Delay 2) on the drums are still sending even though I turned it down to minus infinity db. Not all the pads but the kick is frozen with a delay on it.

I only know that the latest Bitwig release is pretty buggy and read in the forum that support suggested to stay 3.2.8 for the time being.

ChrisDW · Post by **ChrisDW** » Mon Jan 04, 2021 9:27 pm

moss wrote: Mon Jan 04, 2021 6:23 pm You are right, there are some bugs when flipped and control mode is on. Will see how I can fix that...

Thanks for investigating. Hope you're able to fix.

xtreme sounds · Post by **xtreme sounds** » Mon Jan 04, 2021 10:26 pm

moss wrote: Mon Jan 04, 2021 6:29 pm
melodyz wrote: Mon Jan 04, 2021 4:38 pm Fire issue 2 - For some reason the send FX1 (added Delay 2) on the drums are still sending even though I turned it down to minus infinity db. Not all the pads but the kick is frozen with a delay on it.
I only know that the latest Bitwig release is pretty buggy and read in the forum that support suggested to stay 3.2.8 for the time being.

Interesting. Do you have the link where they say to stay with the older version?

moss · Post by **moss** » Mon Jan 04, 2021 10:29 pm

DrivenByMoss 11 is online!

Get it from http://mossgrabers.de

Requires Bitwig 3.2.5+
All devices
- Fixed: 8th layout for scales which do not have 7 intervals was not aligned correctly (Push, Launchpad, APC).
Launchpad
- New: Press the 4th scene button (green) in the play mode to activate additional controls in the first pad row. First pad toggles sustain. Second and third pad are pitch down/up and the following pads switch to different intensities of the modulation wheel. You can slide these modulation wheel pads to imitate a modulation wheel.
- New: Press the 5th scene button (amber) in the play mode to activate chords mode. This mode allows to play a chord by pressing a single pad. The base note is taken from the current scale and increases from left to right. The rows from bottom to top contain the following chords: Triads, Dyads (Powerchords), Suspended second (Sus2), Suspended fourth (Sus4), Add sixth (6), Major seventh chord (maj7), Add ninth (9), Add eleventh (11). The same octave, scale and base note settings apply as with the play mode.
- New: Pro Mk3: Fixed Length button triggers the New clip command.
- New: The mode strip in session view is now displayed vertically if session is flipped (in the 8th column).
- New: Show the flipped state in Bitwig when Session is activated from a different view.
- New: Scrolling in Birdseye view is now per page.
- Fixed: Birdseye view in session mode should not display mode button row.
Push
- New: Added chord mode. Press Note and select Chords to enable it or use the Layout button. Functionality is like described above for the launchpad.
- Fixed: Push 2: Selected play view for a track was not remembered when changed via the Layout button.

Enjoy!

Luis887 · Post by **Luis887** » Tue Jan 05, 2021 4:04 pm

Thanks!! Máster!!!!

ChrisDW · Post by **ChrisDW** » Tue Jan 05, 2021 5:13 pm

Thank you very much!!!

mlew · Post by **mlew** » Tue Jan 05, 2021 9:48 pm

Thanks you very much !!

jeanclaudevanlee · Post by **jeanclaudevanlee** » Wed Jan 06, 2021 11:09 am

Hi guys!

I'm trying to setup a simple clip luncher in Bitwig with Monome 128 via OSC in Max/MSP.
I managed to make the connection and launch clips and scenes in Bitwig with Monome but I don't really know how to setup udpreceive to make all the clips visible on Monome.

I tried /track/1/clip/1/hasContent message to udpreceive but it didn't work.
I'm not very experienced with Max but can build simple stuff. I'm really stuck with setting up response from Bitwig back to Monome. Would really appreciate some help!

Thank you so much!

xtreme sounds · Post by **xtreme sounds** » Wed Jan 06, 2021 11:43 am

moss wrote: Mon Jan 04, 2021 6:29 pm
melodyz wrote: Mon Jan 04, 2021 4:38 pm Fire issue 2 - For some reason the send FX1 (added Delay 2) on the drums are still sending even though I turned it down to minus infinity db. Not all the pads but the kick is frozen with a delay on it.
I only know that the latest Bitwig release is pretty buggy and read in the forum that support suggested to stay 3.2.8 for the time being.

Heres Bitwigs response when I asked about all this. "those scripts are exclusively developed by Moss instead of us. Please be sure to report any bugs with them to him.
He also has a direct contact to us if he has to report any bugs in Bitwig he finds while working on his scripts."

shpa · Post by **shpa** » Wed Jan 06, 2021 2:10 pm

Hi, just wanted to let you know that I appreciate all you do for bitwig and support for these controllers.

I have an issue though with KK S88 MK2, it seems that in midi mode only channel 1 is working, if I split my keyboard and have more than one channel non works except channel 1.

I did the same test with the Novation 49SL MK3 and all channels are working.

I do see all midi inputs using midi monitor and the same does work in ableton so looks like it's a bug with the NI KK S driver.

Bitwig

KVR Audio

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