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

[moss]

Fire issue -with drum machine. Hi Moss did you ever look into why dragging a sample onto the drum machine pad instead of loading it from the small plus sign in the pad causes the drum machine to stop responding to the fire? When I place the sample in slot E3 then the fire drum machine goes blank. When I remove the sample, it comes back online showing all the steps etc.

If I remember correctly I did and somehow the view is moved when the you dragged instead of plus.

[moss]

DrivenByMoss 10.9.4 is online!
Get it from http://mossgrabers.de

• Requires Bitwig 3.2.5+
• Launchkey Mini Mk3
  • New: Added options to choose the function for the record and shift+record button.
• Fire
  • New: Alt + Mute/Solo buttons display the drum sounds name in drum sequencer mode.
• Generic Flexi
  • New: Replaced Select/Export/Import buttons with Load/Save buttons. Remove and add the extension to remove the old buttons (Bitwig bug)!
  • Fixed: File dialogs did not work on Linux.
  • Fixed: Dialog height was *jumping
  • until you changed the height.
  • Fixed: Item Select in Parameters mode did not set the parameter page.
• Push
  • Fíxed: Play view could be off if quickly switching between track pages.

Enjoy!

[artsense]

[*]Fíxed: Play view could be off if quickly switching between track pages.

Thanks a lot!

[absoluterbeginner]

[*]New: Added options to choose the function for the record and shift+record button.

WOW! That was ridiculously fast. Amazing! I am really happy that people like you exist! I couldn't find a possibility to spend you some beers on your website. Do you have Paypal or sth?

[moss]

[*]New: Added options to choose the function for the record and shift+record button.

WOW! That was ridiculously fast. Amazing! I am really happy that people like you exist! I couldn't find a possibility to spend you some beers on your website. Do you have Paypal or sth?

No need to, just enjoy
If you want, check out my first solo album I just released yesterday and spread the word: mossifier - Project Kite - available on all digital distribution platforms.

[xtreme sounds]

Fire issue -with drum machine. Hi Moss did you ever look into why dragging a sample onto the drum machine pad instead of loading it from the small plus sign in the pad causes the drum machine to stop responding to the fire? When I place the sample in slot E3 then the fire drum machine goes blank. When I remove the sample, it comes back online showing all the steps etc.

If I remember correctly I did and somehow the view is moved when the you dragged instead of plus.

I figured out whats happening. BItwig selects the sampler instrument that is loaded onto the pad instead of focusing on the drum machine. I have to reclick the drum machine plugin to bring it back online on the fire. I figured out if I lock the Drum machine to the fire in the right pane it works now fine. Any other work arounds?

[xtreme sounds]

fire feature request duplicate sequencer pages, and drum sequencer pages over several pages with a few clicks. Maybe thats already in there. but how?

[moss]

fire feature request duplicate sequencer pages, and drum sequencer pages over several pages with a few clicks. Maybe thats already in there. but how?

If you mean you want to double the clips content, you can do that with the "Double" function I recently added to Shift mode together with Copy and Delete.

[xtreme sounds]

Fire - hi Sir. For the individual drum volumes on each part, the fire is currently only responding to the first pad. I can see and select the other pads. Im in channel mode and trying to turn the volume knob. No success. I can see the name of the proper pad in the display as well but it just isnt respond to anything.

I reloaded my project and tried again with new samples. i see now that pad 2 is responding while pad 1 is not. I figured out that in order to change the pad volumes, I have to cycle through the channel mixer user1 and user 2 modes and come back to channel to affect the volume on the proper pad. Otherwise all pads are locked. Weird.

[el_gato_loco]

@moss
First of all a big respect for your work on the Bitwig extension "DrivenByMoss" what a brilliant work, I wish I was as talented as you !
Since a few days I'm trying to "program" my Midi-Controller "Nektar Aura Beat Composer" with Javascript - well, more bad than good . I have watched all your videos !
I first tried to decrypt the script of Nektar (encrypted and compressed code) when I understood roughly how the script works and how the controller talks to Bitwig I intercepted the sysex data and use them partly to initialize my controller, e.g. assignment of buttons and rotary knobs. Would you like to help me with this or could you give me some tips on how to do it best ? I already tried your Generic Flexi but unfortunately it only supports one output and one input.
I would be super grateful for the smallest hint

[moss]

@moss
First of all a big respect for your work on the Bitwig extension "DrivenByMoss" what a brilliant work, I wish I was as talented as you !
Since a few days I'm trying to "program" my Midi-Controller "Nektar Aura Beat Composer" with Javascript - well, more bad than good . I have watched all your videos !
I first tried to decrypt the script of Nektar (encrypted and compressed code) when I understood roughly how the script works and how the controller talks to Bitwig I intercepted the sysex data and use them partly to initialize my controller, e.g. assignment of buttons and rotary knobs. Would you like to help me with this or could you give me some tips on how to do it best ? I already tried your Generic Flexi but unfortunately it only supports one output and one input.
I would be super grateful for the smallest hint

I am sorry but I don't have the device, so cannot help you with this.

[moss]

Fire - hi Sir. For the individual drum volumes on each part, the fire is currently only responding to the first pad. I can see and select the other pads. Im in channel mode and trying to turn the volume knob. No success. I can see the name of the proper pad in the display as well but it just isnt respond to anything.

I reloaded my project and tried again with new samples. i see now that pad 2 is responding while pad 1 is not. I figured out that in order to change the pad volumes, I have to cycle through the channel mixer user1 and user 2 modes and come back to channel to affect the volume on the proper pad. Otherwise all pads are locked. Weird.

To control the volumes you need to be in CHANNEL mode. The knobs control then the parameters of the selected drum pad / layer. This is the one which is indicated by the green mute/solo LED. Also as you found out already, it is not working if you are in a sub-device (this is a Bitwig issue), so make sure one of the top level devices is selected.

[xtreme sounds]

Fire - hi Sir. For the individual drum volumes on each part, the fire is currently only responding to the first pad. I can see and select the other pads. Im in channel mode and trying to turn the volume knob. No success. I can see the name of the proper pad in the display as well but it just isnt respond to anything.

I reloaded my project and tried again with new samples. i see now that pad 2 is responding while pad 1 is not. I figured out that in order to change the pad volumes, I have to cycle through the channel mixer user1 and user 2 modes and come back to channel to affect the volume on the proper pad. Otherwise all pads are locked. Weird.

To control the volumes you need to be in CHANNEL mode. The knobs control then the parameters of the selected drum pad / layer. This is the one which is indicated by the green mute/solo LED. Also as you found out already, it is not working if you are in a sub-device (this is a Bitwig issue), so make sure one of the top level devices is selected.

I did all that and it wasnt working properly unless I kept switching through the modes back to channel each time after selecting a pad to modify. I will try again to detail the steps that lead to the issue but something isnt smooth. Maybe what is happening is if we leave the top device level at any time (which can happen because we are messing with the sample layer), then it doesnt work. I added some modulation knobs in the top drum layer that interact with the sub device samplers.

[moss]

Fire - hi Sir. For the individual drum volumes on each part, the fire is currently only responding to the first pad. I can see and select the other pads. Im in channel mode and trying to turn the volume knob. No success. I can see the name of the proper pad in the display as well but it just isnt respond to anything.

I reloaded my project and tried again with new samples. i see now that pad 2 is responding while pad 1 is not. I figured out that in order to change the pad volumes, I have to cycle through the channel mixer user1 and user 2 modes and come back to channel to affect the volume on the proper pad. Otherwise all pads are locked. Weird.

To control the volumes you need to be in CHANNEL mode. The knobs control then the parameters of the selected drum pad / layer. This is the one which is indicated by the green mute/solo LED. Also as you found out already, it is not working if you are in a sub-device (this is a Bitwig issue), so make sure one of the top level devices is selected.

I did all that and it wasnt working properly unless I kept switching through the modes back to channel each time after selecting a pad to modify. I will try again to detail the steps that lead to the issue but something isnt smooth. Maybe what is happening is if we leave the top device level at any time (which can happen because we are messing with the sample layer), then it doesnt work. I added some modulation knobs in the top drum layer that interact with the sub device samplers.

If you remap knobs you must do that in USER2 mode, if you are in another mode you will overwrite its' function.

[xtreme sounds]

found some of the problem. its the fire display. turning the knobs does affect eh sound like volume and pan but the display doesnt show anything moving. BUT that is not the whole story either. its hit or miss.
The issue also occurs dragging samples from adsr into the sampler area and then clicking back on the drum machine (top device). The fire display freezes up and stops responding to volume and pan changes per pad. (Probably affecting changing gains on individual steps too)