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

[xtreme sounds]

Hi Sir

I found something strange with the fire. If I go into drum mode (the one that shows the pink drum pads), and I play in a midi pattern, When I switch tot the drum sequencer mode )pressing Drum key), the different hits are all on the same row. double kicks appeared on the bottom row. Even though the midi pattern shows what it should look like in Bitwig. The only settings I adjusted before live playing were the scale for note mode, and turning on the keytrack for the kick sample. I am using the Irrrupt Kit 3. I deleted the midi file and it went away. Maybe I was hitting the kick lightly twice, I dont know. Just wanted you to be aware of it in case someone else notices.

[sequethin]

I'm trying to use a Push and a Launchpad, and have them display different session clips in the drum sequencer. It seems that no matter what I set for the midi input on the channels, the push and launchpad always show the same clip. I was hoping I could assign one pad controller to each drum machine. Is there something I'm not configuring correctly?

[sequethin]

I'm trying to use a Push and a Launchpad, and have them display different session clips in the drum sequencer. It seems that no matter what I set for the midi input on the channels, the push and launchpad always show the same clip. I was hoping I could assign one pad controller to each drum machine. Is there something I'm not configuring correctly?

I forgot to add that the pads DO play the correct tracks. I can play both drum machines, but the sequencers are linked to each other.

[astartes]

Hi Moss,
a Little Feature sugestion that might be interesting for the ones of us, who are working with more than one Controller:

The ability to tell the Script with what Page to start (Cliplauncher, Notes etc...) via selector in the Configuration would be handy. That way you can, say if working with two Launchpads, tell one to start with the cliplauncher and the other with Notemode as Startpage. Don´t know if it is implementeble but would be a handy feature i guess.

[sequethin]

I'm trying to use a Push and a Launchpad, and have them display different session clips in the drum sequencer. It seems that no matter what I set for the midi input on the channels, the push and launchpad always show the same clip. I was hoping I could assign one pad controller to each drum machine. Is there something I'm not configuring correctly?

I forgot to add that the pads DO play the correct tracks. I can play both drum machines, but the sequencers are linked to each other.

Haha Oh: one more thing!

I tried using the Push and Launchpad with Ableton and the experience is much worse. Driven By Moss + Bitwig is actually a vast improvement. Still would be nice to have my dream of 2 pad controllers in drum sequence mode mapped to 2 drum machines

[moss]

Hi @moss, I've been playing extensively with the novation sl 61 mkiii with your script. It's great! I have many things on my wishlist and some sort-of-bug report. On the wishlist as mentioned earlier, the possibility to quickly enable/disable automation record for clips from the keyboard. I figured out how to stop clips: find an empty row, disable arm, and press an empty clip. Not perfect but reasonable.

Will add it to the wish list.

What may be called a bug: on the one hand, using bitwig as a master clock is just broken. Arp clock will drift; sequencer may start at random positions. On the other hand, using the novation sl as a master clock, works, but transport can only be started and stopped from within the "sequencer" mode of the keyboard, which also causes issues, for instance one needs to first switch to "incontrol" just to press stop twice and reset transport, then go back to sequencer and press play. But if bitwig could be the master clock it would be better (dunno if that's possible right now).

This is not related to DrivenByMoss. You can configure Bitwitg as the MIDI-Clock master in the Synchronisation settings and the SL to receive it. Check both manuals.

[moss]

The long press for clip selection is awesome (many thanks for this function) been testing it lately and it comes in really handy for recording clips with a foot pedal. Select the clip/slot with a long press on the launchpad and use the "Launch current Slot or Scene" short-cut with a midi foot pedal. However I notcied something strange, there seems to be 2 "modes" of selection. One works with the short-cut, the other doesn't.

1st mode is when I select any clip via the mouse in the clip-launcher. There is a white outline around that selected clip/slot. Now with long presses on the launchpad I can select any slip/slot and start or stop recording with that pedal short-cut or the default ENTER key.

2nd mode is when I select a track via mouse and then use the long press on any clip/slot. The clip/slot gets selected but has a grey outline and the short-cut does not work anymore. I first have to select any clip/slot in the launcher via mouse or thouchscreen again for this to work.

Is this intended behavior? I had a look in BW settings but cannot find anything to get the clips always selected in the "proper" mode so they can be triggered by short-cuts.

This is a long standing Bitwig issue (I would call it a bug), that you once need to click on a clip in Bitwig (to set the focus) to make it work on the controller.

[moss]

I'm trying to use a Push and a Launchpad, and have them display different session clips in the drum sequencer. It seems that no matter what I set for the midi input on the channels, the push and launchpad always show the same clip. I was hoping I could assign one pad controller to each drum machine. Is there something I'm not configuring correctly?

I forgot to add that the pads DO play the correct tracks. I can play both drum machines, but the sequencers are linked to each other.

Yes, you can currently pin tracks and devices but not clips. So, you cannot do that.
I just noticed that since API 10 you can create pinnable clips. Will need to experiment with this when I find some time.

[vincenzoml]

@moss:

What may be called a bug: on the one hand, using bitwig as a master clock is just broken. Arp clock will drift; sequencer may start at random positions. On the other hand, using the novation sl as a master clock, works, but transport can only be started and stopped from within the "sequencer" mode of the keyboard, which also causes issues, for instance one needs to first switch to "incontrol" just to press stop twice and reset transport, then go back to sequencer and press play. But if bitwig could be the master clock it would be better (dunno if that's possible right now).

This is not related to DrivenByMoss. You can configure Bitwitg as the MIDI-Clock master in the Synchronisation settings and the SL to receive it. Check both manuals.

I know well! But the problem is: if bitwig is the midi-clock master, maybe novation's fault, but the clocks drift; it's not usable. With "dunno if that's possible" I mean I have to ask novation to fix their clock drift issue.

But in the meantime, I have to resort to keeping the novation master, and bitwig receiver, which is also good for me. But when I press PLAY on the novation and bitwig is not master, nothing happens! I need to switch out of "incontrol" to start/stop transport. But first, I need to press stop in "incontrol" because I need to reset bitwig's clock or they start with an offset.

That may seem correct, but maybe you can do something in your script: when you receive "play" and bitwig is not master, why not sending MIDI START *to* the novation SL? I believe that would work; more precisely I *think* I've read in the manual that the novation SL *always* obeys to MIDI START.

[xtreme sounds]

hi I am playing with the step sequencer on the fire (instruments). Im wondering if this can be reviewed to have a little better work flow with replacing and moving notes. What if we could copy a note over to an adjacent spot or simply replace the existing notes by pressing override. It seems now we have to delete the current notes on a step and press the step again to reenter it. What If I need to move the note over one step to the left or right. Its a bunch of button presses. Also is there a way to enter in the notes while other tracks are playing without hearing the full playback until we hit play or something (probably not since its linked to a midi file) but I thought i would ask anyway.

On another note, is there a possible conflict between changing the playback and record settings in the Bitwig menu verses the options in the shift panel? Im trying to change the default bar length before recording and it feels like choosing the one in the Bitwig menu overrides selecting on the fire.

Thanks again for your hard work. Its almost there there you know!

[CallejasV1]

Hi! Thanks Moss for the outstanding Job.
I'm new to Bitwig, but I have been working with Ableton for a year so i hope I con accommodate quickly to this new DAW.
I'm using Push 1 and I have an issue when working with Drum Machine

I can see all the pads/layers and their respective volume, pan and sends in the push 1 and selecting them with the first row of buttons, but in order to modify the volume, pan or send I have to select the pad, and then go back to the view with all the pads.
I don't know if its a bug or it is intended to work like that.
(Edit: It works if I press select+volume or select+pan, and have every knob change the volume of every layer, but not if I press select+track )

Thanks again for everything!
My English is not very good so if you can't understand I can try again with pictures

Thanks

[moss]

Hi! Thanks Moss for the outstanding Job.
I'm new to Bitwig, but I have been working with Ableton for a year so i hope I con accommodate quickly to this new DAW.
I'm using Push 1 and I have an issue when working with Drum Machine

I can see all the pads/layers and their respective volume, pan and sends in the push 1 and selecting them with the first row of buttons, but in order to modify the volume, pan or send I have to select the pad, and then go back to the view with all the pads.
I don't know if its a bug or it is intended to work like that.
(Edit: It works if I press select+volume or select+pan, and have every knob change the volume of every layer, but not if I press select+track )

Thanks again for everything!
My English is not very good so if you can't understand I can try again with pictures

Thanks

You can set "Auto select drum setting" (under "Drum Sequencer") to "Channel" in the settings. If I understand you correctly, this should do what you want.

[CallejasV1]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Hi Moss, thanks for everything

My English is not very good, I meant this view isn't working, I can change the selected pad but I can't change the volume, pan or sends.
(https://ibb.co/St1RfpY)

Hope that clears my question
THanks!!

[NKirn93]

Hi Moss.
Thank you for fixing the issue of only 8 user controls being available in your OSC script. I've come across an issue that happens on all controllers and I'm curious if you know what's causing it.
If a parameter has written automation and a physical knob (be it MIDI knob, MIDI encoder or OSC control) that I can move I'll come across a weird bug. The first MIDI/OSC message sent doesn't move the software control. So if a knob is at 0% and I send a MIDI/OSC message that should move it to 50% it doesn't do anything (it activates the green automation override dot and momentarily flashes the control as if it was moved to 50% for 1ms and the back to 0%) until I send a message that would move it to 51%. Then it's back to business.
I've tried this on 3 different controllers with different control scripts, one with knobs, one with encoders and OSCPilot.
Have you ever come across something like this, is this an old issue?
Thanks.

Edit: happens with the mouse as well. This is an internal Bitwig problem

[mattaudio]

Hi,
i'm having issue with flexi for selecting action, the list is huge and everything doesn't fit on my screen.
i can still select with arrows keys outside the screen but i can't see what i'm selecting.
https://imgur.com/a/U6QUy01
i'm on Bitwig 3.3 with DrivenByMoss 10.9.2
i'm on OSX 10.13.6

Thanks for you help.