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

[xtreme sounds]

hi heres a feature request - can we using the return fx on drum machine to apply a delay for example on only hats etc?

[moss]

scales buttons do not work on piano mode or poly mode

It is not supposed to work on piano mode but should on poly sequencer, will check.

I look into that. In Sequencer and Poly sequencer modes the grid buttons select the edit page and the grid resolution. To change the scale please switch to the Play mode, change it there and then back to the sequencer (alternatively you can set it in the right hand sidebar of Bitwig).

[moss]

Thank you Moss for your answer.
I've discovered today a very weird behavior :
When auto-arm is deactivated in Bitwig preferences (recording), it's no more possible to arm a track on the Push 2 (the selection button becomes orange instead of red, and put me directly in device view ).

That is intended. If you select a selected track again you "dive into" it. If it is a group you enter the group if it is only a track you go down to the devices. From there you enter either layers or parameters.
To change rec arm:
1) keep the Record button pressed and select the track.
2) Keep Select button pressed and choose "Rec Arm" from the menu.

I absolutely need the auto-arm off for some of my performances.

Also, when auto arm is activated, and I change a page on the Push (session view), it automatically arms the last or the first track of the new page.
Same thing when I launch a scene, it changes the page and arms another track.
It's very very problematic if I was playing at the same time on a device of the previous armed track or on another keyboard.

I am afraid this is how auto rec arm works.

[moss]

hi Moss

it seems the akai fire has some drum sequencer recording issues. So I press Alt + record to start a new pattern and enter steps. It works on the first pattern (scene 1). But then when I pres the pattern up button to go to next scene (pattern) then press alt + record. entering steps on the fire is not triggering any sound. I see the steps entered on the fire but no sound. I switch over to the note sequencer and I can trigger sounds. On the pc screen I see a midi clip created and then overdub and record are enables theres movement but no midi notes are appearing on the the midi clip. I decided to erase those extra patterns and start over and went back to pattern 1 (scene 1) and try again and it will not record notes either. I did just update to 3.2.5 if that helps

I ended up having to unplug it and restart everything and it works. So sometimes it works and sometimes it doesnt.

And I got a stuck note on the drum sequencer I cannot delete again. D1 I went to a different track and added notes for a bassline etc. And went back to my drum pattern and started removing notes and some wont remove.

3. then I went back to record and all my pads got muted. Not sure what happened. but nothing is entering into the midi clip again. It happened after i went to the page where I hold down shift and change repeats and arps. All the green buttons on the left are now blacked out (Green light is off) I also cannot use the selector knob to switch notes up and down on the drum sequencer. - i think i somehow ended up on the master bus.

Finally I cant get the arp to work on basses and leads using the note sequencer. Why it turned off I dont know whats happening there.

Sorry, I cannot reproduce any of these issues. Could you maybe do a video or give a step by step instruction what you do?
BTW: You do not need to move to the next empty slot, pressing alt + record does that automatically.

[moss]

hi heres a feature request - can we using the return fx on drum machine to apply a delay for example on only hats etc?

You already can do that:
Select the CHANNEL mode. This controls now the drum cell which belongs to the selected row (the one with the green lit LED). FILTER and RESONANCE control Send 1/2. Use all 4 knobs in combination with ALT for Send 3-6.

[xtreme sounds]

hi Moss

it seems the akai fire has some drum sequencer recording issues. So I press Alt + record to start a new pattern and enter steps. It works on the first pattern (scene 1). But then when I pres the pattern up button to go to next scene (pattern) then press alt + record. entering steps on the fire is not triggering any sound. I see the steps entered on the fire but no sound. I switch over to the note sequencer and I can trigger sounds. On the pc screen I see a midi clip created and then overdub and record are enables theres movement but no midi notes are appearing on the the midi clip. I decided to erase those extra patterns and start over and went back to pattern 1 (scene 1) and try again and it will not record notes either. I did just update to 3.2.5 if that helps

I ended up having to unplug it and restart everything and it works. So sometimes it works and sometimes it doesnt.

And I got a stuck note on the drum sequencer I cannot delete again. D1 I went to a different track and added notes for a bassline etc. And went back to my drum pattern and started removing notes and some wont remove.

3. then I went back to record and all my pads got muted. Not sure what happened. but nothing is entering into the midi clip again. It happened after i went to the page where I hold down shift and change repeats and arps. All the green buttons on the left are now blacked out (Green light is off) I also cannot use the selector knob to switch notes up and down on the drum sequencer. - i think i somehow ended up on the master bus.

Finally I cant get the arp to work on basses and leads using the note sequencer. Why it turned off I dont know whats happening there.

Sorry, I cannot reproduce any of these issues. Could you maybe do a video or give a step by step instruction what you do?
BTW: You do not need to move to the next empty slot, pressing alt + record does that automatically.

thanks ill keep working with it. Its hard to capture as it just happens as Im playing along. What I can tell you is if I get my mouse involved clicking midi tracks in bitwig seems to start the issue. like it gets off sync or something or something loses focus

[dot.solenoid]

Hello,

DBM 10.1
OSX 10.15.5
Bitwig 3.2.5
Akai fire

Fire updates are really slow, OLED screen updates are executed line for line (top/bottom). Turning multiple notes on-off or turning knobs seems to slow down the updates refresh rate. Turning knobs takes a few seconds to be executed.

Used the same controller under windows: no problem.

[moss]

Hello,

DBM 10.1
OSX 10.15.5
Bitwig 3.2.5
Akai fire

Fire updates are really slow, OLED screen updates are executed line for line (top/bottom). Turning multiple notes on-off or turning knobs seems to slow down the updates refresh rate. Turning knobs takes a few seconds to be executed.

Used the same controller under windows: no problem.

Yes, it is in the Known Issue section in the manual. Also works fine with my Reaper implementation on Mac, so I am guessing currently that it is an issue with the Bitwig Sysex implementation on Macos. Especially, since there is a similar issue with the SL MkIII.
I reported it to Bitwig but so far no answer.

[moss]

DrivenByMoss 10.2 is online!

Get it from http://www.mossgrabers.de

• Requires Bitwig 3.2+
• All devices
  • New: All settings are now documented in the manual.
• Akai APC40
  • New: The cursor keys can now be used in the browser mode: Left/right select the previous/next tab. Up/Down select the previous/next result.
• Akai Fire
  • New: Pressing Select knob toggles the window of the current device.
• Generic Flexi
  • New: Option to execute one of 8 Actions.
• MCU
  • New: Added option - include FX and master tracks in track bank
  • New: Added option - pin FX tracks to last device
  • New: Footswitches and Functions keys can now execute an Action. Select *Action
  • from the list, then select the Action from the list below.
  • New: Option to disable Master VU (iCON extension)
  • Fixed: New function did not work
• OSC
  • New: Updated the Open Stage Control template for Open Stage Control 1.0.0. VU meters are now gray if track is muted.
  • New: /action/{1-8}/ to execute 8 different Actions.
  • Fixed: /automationWriteMode was broken
  • Fixed: /click/ticks did always toggle and was not documented
• Push
  • Fixed: Device and Parameter navigation was broken

Enjoy!

[xtreme sounds]

Thanks for the akai fire update today. works!

ok I figured out something that is going strange on the sequencer as you requested. So I used the sequencer (1st pad on left) to sequence my external keyboard (drums) the kick is on C1. and I did a bunch of stuff. sounded good.

Then I switched to a vst plugin for bass on a different track. I switched the root note and scale!!!. I went to the 2nd pad from left then held shift and pressed grid buttons and alt and pressed grid buttons changing 4ths and so forth, and also just grid buttons for scale.

I recorded some stuff in. fine. But then when I went back to the sequencer (pad 1 option) and the drum part I recorded before switching roots and scales all the notes are off from where I placed them. Now there are stuck notes in places I didnt put them. So its changing the root note and scale setting after recording something to a midi file that is affecting what is displayed on the fire.

There was also a bunch of green notes (not blue) placed on play mode (2nd pad from left) even though Im not touching the controller.

This may be whats causing the problems I am experiencing. Something with how this is handled.When I unplug the fire and plug it back in it goes back to the way it should.

[xtreme sounds]

Heres an Akai Fire feature request - what about a controller option to switch views to mix view when the perform button is selected? This would make what we see in bitwig match a little better with the fire.

Also when switching the controller transport option Flip arranger and clip record/automation. Or vice versa is there a way to record the automation into the clip area? I think the manual lists it backwards. The red record and automation button should go to the arranger timeline. While the just override button will record automation to the clip. shift plus record should enable the orange clip launcher automation button for clip recording. page 187 of bitwig manual.

Also can shift plus alt and turn knobs 1-4 reset value to 0? unless there is a better use for a shift plus alt turning the knobs.

[xtreme sounds]

sorry one more thing that happened after i assign the mod wheel from the legend plugin to the fire user knob 2 first knob. I lost control of the volume parameter on the mixer option for volume knob. it has only happened once so far.

[xtreme sounds]

Hi on the fire I got the arpegiator working (you have have note repeat on). but why does the recorded notes not sound the same as what was played? (slower).

Also is there a way to make the preroll feature work before recording?

[moss]

Thanks for the akai fire update today. works!

ok I figured out something that is going strange on the sequencer as you requested. So I used the sequencer (1st pad on left) to sequence my external keyboard (drums) the kick is on C1. and I did a bunch of stuff. sounded good.

Then I switched to a vst plugin for bass on a different track. I switched the root note and scale!!!. I went to the 2nd pad from left then held shift and pressed grid buttons and alt and pressed grid buttons changing 4ths and so forth, and also just grid buttons for scale.

I recorded some stuff in. fine. But then when I went back to the sequencer (pad 1 option) and the drum part I recorded before switching roots and scales all the notes are off from where I placed them. Now there are stuck notes in places I didnt put them. So its changing the root note and scale setting after recording something to a midi file that is affecting what is displayed on the fire.

There was also a bunch of green notes (not blue) placed on play mode (2nd pad from left) even though Im not touching the controller.

This may be whats causing the problems I am experiencing. Something with how this is handled.When I unplug the fire and plug it back in it goes back to the way it should.

You are aware that the Scale setting is global and not specific to one of the sequencers/play views?

[moss]

Heres an Akai Fire feature request - what about a controller option to switch views to mix view when the perform button is selected? This would make what we see in bitwig match a little better with the fire.

Nice idea. Will put it on the wishlist.

Also when switching the controller transport option Flip arranger and clip record/automation. Or vice versa is there a way to record the automation into the clip area? I think the manual lists it backwards. The red record and automation button should go to the arranger timeline. While the just override button will record automation to the clip. shift plus record should enable the orange clip launcher automation button for clip recording. page 187 of bitwig manual.

Sorry, didn't get that. Are you saying the colors are mixed up or the is there a problem with the functionality?

Also can shift plus alt and turn knobs 1-4 reset value to 0? unless there is a better use for a shift plus alt turning the knobs.

That is already in use for fine adjustments of parameters 5-8.