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

[moss]

Does the script for the Launchpad Pro mk3 sequencer include the micro steps feature?

There is no note editing for the Launchpads if that's what you mean.

I guess we are talking about the same thing. In the original version of the sequencer you can split a single note into up to 6 steps for off grid and ratcheting. I looked at the manual on your GitHub and it appears that maybe there is a note repeat that maybe a good alternative? Is that functional on the Launchpad Pro mk3? Sorry for all the questions, I haven't received my Launchpad yet. Just trying to mentally prepare.

You can change the resolution of the steps from quarter notes up to 32 triplets.

[D Halgren]

Does the script for the Launchpad Pro mk3 sequencer include the micro steps feature?

There is no note editing for the Launchpads if that's what you mean.

I guess we are talking about the same thing. In the original version of the sequencer you can split a single note into up to 6 steps for off grid and ratcheting. I looked at the manual on your GitHub and it appears that maybe there is a note repeat that maybe a good alternative? Is that functional on the Launchpad Pro mk3? Sorry for all the questions, I haven't received my Launchpad yet. Just trying to mentally prepare.

You can change the resolution of the steps from quarter notes up to 32 triplets.

Of each individual step, or just as a whole?

[moss]

Does the script for the Launchpad Pro mk3 sequencer include the micro steps feature?

There is no note editing for the Launchpads if that's what you mean.

I guess we are talking about the same thing. In the original version of the sequencer you can split a single note into up to 6 steps for off grid and ratcheting. I looked at the manual on your GitHub and it appears that maybe there is a note repeat that maybe a good alternative? Is that functional on the Launchpad Pro mk3? Sorry for all the questions, I haven't received my Launchpad yet. Just trying to mentally prepare.

You can change the resolution of the steps from quarter notes up to 32 triplets.

Of each individual step, or just as a whole?

For the whole grid.

[D Halgren]

Does the script for the Launchpad Pro mk3 sequencer include the micro steps feature?

There is no note editing for the Launchpads if that's what you mean.

I guess we are talking about the same thing. In the original version of the sequencer you can split a single note into up to 6 steps for off grid and ratcheting. I looked at the manual on your GitHub and it appears that maybe there is a note repeat that maybe a good alternative? Is that functional on the Launchpad Pro mk3? Sorry for all the questions, I haven't received my Launchpad yet. Just trying to mentally prepare.

You can change the resolution of the steps from quarter notes up to 32 triplets.

Of each individual step, or just as a whole?

For the whole grid.

Got ya, and there is no note repeat with the Launchpad Pro?

[Pencilina]

Hi All,
Moss, thanks for your ABSOLUTELY BRILLIANT and useful work.
Sorry, If I missed something in my searching but I'm using a little modified korg nano controller as control for the generic flex device to control various functions in BW. Is there any way to prevent it from sending (passing MIDI thru) its data to record enabled tracks?
Thanks,
Bradford

All MIDI you have mapped should be blocked and handed over to Bitwig (are you saying this is happening?). All other MIDI is passing through. There is no way to block this besides mapping that as well.

Hi Moss,
Thanks for the reply. Sorry for delay in responding. Yes, assigned parameters are passing the original midi data (which I want the flexi device to block and transform) as well as the function. So if I have c3 on my controller set to stop transport, the transport stops but I also hear C3 on my synth (if it's input is set to all devices or flexi in). All other devices are turned off except the flexi. Or for example, If I want this C3 to toggle CC17 0<>127 (slot>functon>midicc:>17), bitwig's mapping browser sees the note 60 (c3) not CC17.

Any tips?
Thanks,
Br

[xtreme sounds]

Sure you know pressing shift plus record enables the red record button and red automation button normally? There is an option under settings to flip between arrangement and clips for recording. I forget what its called, but anyway when enabling that. pressing shift plus record enables the orange overdub button. Next to that button on the left is an orange automation button. If that would also enable when pressing shift plus record then it will work. somewhere in this thread there are screen shots of the buttons . This will make sense as it will now allow us to record automation using the knobs for just each individual clip.

OK, let me explain:
1) Record button toggles Arranger Record
2) Shift+Record toggles Clip Override, I always use this as the "Clip record" since IMHO it is more useful than recording into a clip (Workflow: Use Create clip and then toggle override).
1) and 2) are flipped if you enable the option in the settings

There is currently no support for the Arrange and Clip Automation in the Fire extension since there is no Automation button. The button left of the Record button is the Stop button.
However, I could add that to the STOP button:
Shift+Stop: Toggle Arrange Automation
Alt+Stop: Toggle Clip Automation
What do you think?

HI I need to get on the same page with you here. I think there is a terminology block.
pressing shift and record only toggles clip override (when Flip Arranger and Clip record is ON under controller settings). There is an orange automation button next to the clip override. WE have to use our mouse to engage it. I just want that clip automation button to activate somehow.

[xtreme sounds]

RE FIRE SCRPIT - hi sir sorry the fire script is still glitchy. while the drum machine is playing the track - if I use my mouse in bitwig to select a different track which is laoded with adrs sample manager (i use it to select sounds and drop them in to the drum machine) after loading some more samples I use my mouse to select the drum machine track. The select knob will no longer scroll up and down octaves, the mute buttons are not green anymore yet all the parts are playing. pushing the mute buttons doesnt do anything. It doesnt always happen but it does happen daily.
Also one time I was playing around with the channel mode and parts of the drum machine and went back to the mixer mode so I could hold a step down and change the pitch and that wouldnt work.

I am afraid until you can give some clear steps to reproduce the issue I cannot fix it.

ok i just made it happen

step 1 loaded a kick sample into drum machine C1 (using adsr program on same track as drum machine)
using mouse I skipped to track 3 and loaded the legend vst
started playing some notes
changed scale using grid arrows to minor scale
pressed drum sequencer button ion fire then mouse selected track 1 with drum machine
now the select knob will not go higher than c1 but it will go lower down to A0 (is this because I dont have a sample loaded in D#1?)

I then decided to drop a sample into C2 (skipping slots D#1-B1). Fire froze up. The select knob wont work. What happens is even though I have the track selected it loses focus after using my mouse. If a track is selected but we see Device in the left panel fire will not work. We have to click the track until it says instrument track. I think that is the issue. I clicked a bunch on the track and it sometimes makes fires select knob work again and sometimes doesnt. also this type of issue will cause notes to freeze on the fire as well. I cant delete them. In summary it has something to do with moving from the fire to using the mouse to handle some tasks and back again.

If the select knob does work it will only advance up notes on the drum machine until it hits slots with no samples. Then it wont advance. So the sample I entered into slot C2 cannot be selected now unless I fill up the slots from C1-C2 with samples (I think)

[xtreme sounds]

Hi sir heres one more glitch. After I entered in some drum sequence into a pattern (drum machine track). I used the mouse to delete the midi clip. Then I used the mouse to press the little record button in the clip. Then I pressed one or 2 pads for C1 and All of the sudden the akai fire lit up with a bunch of notes on C#1 and D1 that shouldnt be there. And pressing them will not delete them

[moss]

There is no note editing for the Launchpads if that's what you mean.

I guess we are talking about the same thing. In the original version of the sequencer you can split a single note into up to 6 steps for off grid and ratcheting. I looked at the manual on your GitHub and it appears that maybe there is a note repeat that maybe a good alternative? Is that functional on the Launchpad Pro mk3? Sorry for all the questions, I haven't received my Launchpad yet. Just trying to mentally prepare.

You can change the resolution of the steps from quarter notes up to 32 triplets.

Of each individual step, or just as a whole?

For the whole grid.

Got ya, and there is no note repeat with the Launchpad Pro?

There is note repeat. Watch the Launchpad tutorial videos on my Youtube channel: https://www.youtube.com/playlist?list=P ... rQbZjqwWML

[moss]

HI I need to get on the same page with you here. I think there is a terminology block.
pressing shift and record only toggles clip override (when Flip Arranger and Clip record is ON under controller settings). There is an orange automation button next to the clip override. WE have to use our mouse to engage it. I just want that clip automation button to activate somehow.

Ah, you were talking about the Bitwig UI. You see it always helps to be specific
I implemented it now as I suggested in my previous post.

[antic604]

Launchpad

• New: Long press a pad in session mode to select the clip without starting it.
• Fixed: Modes could only be activated once (non-pro models)

THANK YOU!!! We spoke about this just a day before release and I was surprised to notice it's already there!!!



If I may be so bold as to ask for 3 more things for you to consider:

1) holding the send2, solo, mute, arm pads longer in Clip Launcher mode would temporarily (for as long as the pad is held) show the row of pads for selecting / soloing / muting / arming. Right now it works OK, but it's a bit of a workflow breaker to have to hold Capture, select row, then click a pad to perform the action, hold Capture again, hide the row.

2) swap around how arrow pads work in Device mode, so that left/right moves between devices and up/down between remote pages. A toggle in settings would be best probably, as I don't want to upset the users who's gotten used to current way?

3) set up a Patreon account, so that we - and Reaper users - could contribute financially to your work; as I said I don't feel Ok asking you for features, when I know you do this for free in your spare time that you could've devoted to your music or family - make this happen, please!

[moss]

If the select knob does work it will only advance up notes on the drum machine until it hits slots with no samples. Then it wont advance. So the sample I entered into slot C2 cannot be selected now unless I fill up the slots from C1-C2 with samples (I think)

I can reproduce that. I made some attempts to fix this but did not succeed. So, I can only suggest to not have empty slots.

[moss]

Hi sir heres one more glitch. After I entered in some drum sequence into a pattern (drum machine track). I used the mouse to delete the midi clip. Then I used the mouse to press the little record button in the clip. Then I pressed one or 2 pads for C1 and All of the sudden the akai fire lit up with a bunch of notes on C#1 and D1 that shouldnt be there. And pressing them will not delete them

Cannot reproduce that. But was surprised to see that you can while recording change the notes in the clip

[xtreme sounds]

Hi sir heres one more glitch. After I entered in some drum sequence into a pattern (drum machine track). I used the mouse to delete the midi clip. Then I used the mouse to press the little record button in the clip. Then I pressed one or 2 pads for C1 and All of the sudden the akai fire lit up with a bunch of notes on C#1 and D1 that shouldnt be there. And pressing them will not delete them

Cannot reproduce that. But was surprised to see that you can while recording change the notes in the clip

ok thanks for looking. I suppose the only work around to these problems is to avoid using the mouse as much as possible while using the fire controller for beatmaking. Or be prepared to unplug it over and over. Is there a way to build in a restart button in the controllers right panel in bitwig so we dont need to physically unplug the fires usb each time?

[moss]

Hi sir heres one more glitch. After I entered in some drum sequence into a pattern (drum machine track). I used the mouse to delete the midi clip. Then I used the mouse to press the little record button in the clip. Then I pressed one or 2 pads for C1 and All of the sudden the akai fire lit up with a bunch of notes on C#1 and D1 that shouldnt be there. And pressing them will not delete them

Cannot reproduce that. But was surprised to see that you can while recording change the notes in the clip

ok thanks for looking. I suppose the only work around to these problems is to avoid using the mouse as much as possible while using the fire controller for beatmaking. Or be prepared to unplug it over and over. Is there a way to build in a restart button in the controllers right panel in bitwig so we dont need to physically unplug the fires usb each time?

You can simply turn off/on the extension in the settings. No need to unplug.