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

Post Reply New Topic
RELATED
PRODUCTS
Bitwig Studio 6$399.00Buy Maschine

Post

Hi sir. no rush on these. I just wanted to give some akai fire feedback before a new version is released. Im still learning. the controls are not always intuitive to me.

turning the knob right advances to next track and turning left goes to previous.
velocity is low using the sequencer orange button 3rd from left - i have to activate fixed accent under options other wise its like 1 velocity.
what do the options mean under extension settings?
why does pressing play on controller not always play back clip after normal record mode? I must be doing something wrong.
scales buttons do not work on piano mode or poly mode
id like to see the knobs change the parameter a little faster if possible
at one point on the drum sequencer I got a step with a g1 note one that would never go away unless I unplugged the fire.
at one point I lost control of the pitch controls on drums (user 1 knobs) and I couldnt sequence anything. could get back to the proper c in the step sequencer. major scale also overrid the pads so its was strange. again a mystery note showed up i couldnt get rid of.
double clicking play goes back to start of song but doesnt play. acts more like double clicking stop.
alt-shift and play punch out? not sure how that works

No answers needed here just trying to figure out if this thing can work more smoothly. thanks
Last edited by xtreme sounds on Tue Jul 14, 2020 10:30 pm, edited 2 times in total.

Post

antic604 wrote: Tue Jul 14, 2020 8:18 am Hi Moss, is it intentional that "arrow" buttons in Launchpad X script while in Custom mode are swapped around? I mean the up/down buttons move between devices, whereas left/right move between remote pages. Shouldn't it be the other way around, to correspond with what's on Bitwig's screen?
Yes, that is intentional. Logic is that the higher level (devices) are first and lower level parameter pages are second. I guess Western logic :-) Also if you switch to Mix layout they are aligned vertical.
antic604 wrote: Tue Jul 14, 2020 8:18 am Also, is it possible to somehow access devices that are hidden in nesting slots? And reveal the remotes page if it's hidden? Or are those features not available in API at all yet?
Yes, that is possible but I only did that on the Push so far because I think without a display you are totally lost if you would want to navigate hierarchies. Same for layers and nested devices.

Post

moss wrote: Tue Jul 14, 2020 7:02 pm
antic604 wrote: Tue Jul 14, 2020 8:18 am Hi Moss, is it intentional that "arrow" buttons in Launchpad X script while in Custom mode are swapped around? I mean the up/down buttons move between devices, whereas left/right move between remote pages. Shouldn't it be the other way around, to correspond with what's on Bitwig's screen?
Yes, that is intentional. Logic is that the higher level (devices) are first and lower level parameter pages are second. I guess Western logic :-) Also if you switch to Mix layout they are aligned vertical.
antic604 wrote: Tue Jul 14, 2020 8:18 am Also, is it possible to somehow access devices that are hidden in nesting slots? And reveal the remotes page if it's hidden? Or are those features not available in API at all yet?
Yes, that is possible but I only did that on the Push so far because I think without a display you are totally lost if you would want to navigate hierarchies. Same for layers and nested devices.
Well, both of your replies rely on the assumption that people don't look at (computer) screen when using LP, which I don't think is true. In my case I use the X because it replaces a normal MIDI keyboard + adds clip launching + aftertouch + scales AND is much smaller and more portable at the same time. So I still look at the computer almost all the time and I don't think I'm alone in this. That's why it's jarring to see left/right arrows move up/down and vice versa.

But obviously, I can't ask you to make any modifications to the script or introduce toggles in settings for other than "western" flavours of logic because you're doing this for free...

Thanks anyway :) :tu:
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

antic604 wrote: Tue Jul 14, 2020 7:25 pm But obviously, I can't ask you to make any modifications to the script or introduce toggles in settings for other than "western" flavours of logic because you're doing this for free...
Thanks anyway :) :tu:
you are more "western" than all the functions on the script :o :tu:
And yes Thanks for all you hard work Moss ! I love all you did and do ! :clap:

Post

melodyz wrote: Tue Jul 14, 2020 6:43 pm turning the knob right advances to next track and turning left goes to previous.
Turning a knob to the right increases values, therefore I find it logical to move to the next track but I guess that is up to taste.
melodyz wrote: Tue Jul 14, 2020 6:43 pm velocity is low using the sequencer orange button 3rd from left - i have to activate fixed accent under options other wise its like 1 velocity.
Velocity is pretty unusable on this device, there is nothing I can do about it. Better have Fixed Velocity enabled all the time.
melodyz wrote: Tue Jul 14, 2020 6:43 pm what do the options mean under extension settings?
That is on my TODO list to document the settings of all devices.
melodyz wrote: Tue Jul 14, 2020 6:43 pm why does pressing play on controller not always play back clip after normal record mode? I must be doing something wrong.
Not sure what you mean. Play button toggles the playback of the arranger not of single clip launcher clips.
melodyz wrote: Tue Jul 14, 2020 6:43 pm 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.
melodyz wrote: Tue Jul 14, 2020 6:43 pm id like to see the knobs change the parameter a little faster if possible
Might happen in the future.
melodyz wrote: Tue Jul 14, 2020 6:43 pm at one point on the drum sequencer I got a step with a g1 note one that would never go away unless I unplugged the fire.
at one point I lost control of the pitch controls on drums (user 1 knobs) and I couldnt sequence anything. could get back to the proper c in the step sequencer. major scale also overrid the pads so its was strange. again a mystery note showed up i couldnt get rid of.
Can you give steps to reprocude?
melodyz wrote: Tue Jul 14, 2020 6:43 pm double clicking play goes back to start of song but doesnt play. acts more like double clicking stop.
That is how it is implemented. Do you expect to start playback from the start?
melodyz wrote: Tue Jul 14, 2020 6:43 pm alt-shift and play punch out? not sure how that works
This toggles the Punch Out which you find in the Transport bar of Bitwig. See the Bitwig manual what it does.

Post

Is there any way to delete a clip directly from the APC40MKII ? I can't find this function in wiki.
If it's not implemented yet, it would be a nice feature to have !

Post

gelabs wrote: Wed Jul 15, 2020 10:12 am Is there any way to delete a clip directly from the APC40MKII ? I can't find this function in wiki.
If it's not implemented yet, it would be a nice feature to have !
No, there is not since there is no Delete button. Where do you think this feature could fit in?

Post

the drivenbymoss scripts are excellent. wow.

one remark, i only have installed t drivenbymoss resources on my desktop, with 9 controllers not a bad idead.
or two remarks:

when i first load bitwig, the audio engine takes 15% (of a i7 6700K @4.4 full). without any devices.
second time, normal behavior.

on my laptop i don't see this behavior.

second remark:

drivenbymoss, or bitwig, better bitwig does not seem to release controllers (nektar panaroma p1, is used via nektar software).
for the push 2 this means, when i switch to ableton (yes! i have also ableton, and will still use it..), that the color schemes are totally wrong.
i think this is more a bitwig thing? or some setting? reaper releases controllers, if you do a setting, i believe.

EDIT: of course turning of push 2 or turning on works...

but, great implementations for my push 2, also have maschine mk3 (don't use it for remote), and 2 novation's sl mkii (zero, 49), all work well. didn't try the mackie yet, i have an old MCU (2003 version) connected via midi.

normally i prefer mixing on my MCU, but because i use two screens, and the nektar panaroma p1 (that is used for plugins, and for reaper/reason transport/instruments, i now use as mixer, works alsa great for bitwig).

especially the push 2 is excellent. (but why only 8 encoders, bitwig!, momentary, toggle, step buttons... o well)

Post

moss wrote: Wed Jul 15, 2020 10:22 am
gelabs wrote: Wed Jul 15, 2020 10:12 am Is there any way to delete a clip directly from the APC40MKII ? I can't find this function in wiki.
If it's not implemented yet, it would be a nice feature to have !
No, there is not since there is no Delete button. Where do you think this feature could fit in?
Is it possible to do that with a combo ? Something like [clip]+[device on/off] or [clip]+[track select], or something like that ?

Post

WasteLand wrote: Wed Jul 15, 2020 10:31 am two remarks:

when i first load bitwig, the audio engine takes 15% (of a i7 6700K @4.4 full). without any devices.
second time, normal behavior.

on my laptop i don't see this behavior.

second remark:

drivenbymoss, or bitwig, better bitwig does not seem to release controllers (nektar panaroma p1, is used via nektar software).
for the push 2 this means, when i switch to ableton (yes! i have also ableton, and will still use it..), that the color schemes are totally wrong.
i think this is more a bitwig thing? or some setting? reaper releases controllers, if you do a setting, i believe.
I guess these are questions for Bitwig support and maybe Nektar support for the second issue.

Post

gelabs wrote: Wed Jul 15, 2020 11:04 am
moss wrote: Wed Jul 15, 2020 10:22 am
gelabs wrote: Wed Jul 15, 2020 10:12 am Is there any way to delete a clip directly from the APC40MKII ? I can't find this function in wiki.
If it's not implemented yet, it would be a nice feature to have !
No, there is not since there is no Delete button. Where do you think this feature could fit in?
Is it possible to do that with a combo ? Something like [clip]+[device on/off] or [clip]+[track select], or something like that ?
Hmm, you see it is not easy :-) Will think about it...

Post

moss wrote: Thu Jul 16, 2020 8:36 am
WasteLand wrote: Wed Jul 15, 2020 10:31 am two remarks:

when i first load bitwig, the audio engine takes 15% (of a i7 6700K @4.4 full). without any devices.
second time, normal behavior.

on my laptop i don't see this behavior.

second remark:

drivenbymoss, or bitwig, better bitwig does not seem to release controllers (nektar panaroma p1, is used via nektar software).
for the push 2 this means, when i switch to ableton (yes! i have also ableton, and will still use it..), that the color schemes are totally wrong.
i think this is more a bitwig thing? or some setting? reaper releases controllers, if you do a setting, i believe.
I guess these are questions for Bitwig support and maybe Nektar support for the second issue.
i shall contact bitwig support. thanks! this rules out some things.
(i have a lot of controllers who can react to drivenbymoss, so..)

Post

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 :o ).

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.
Last edited by Invisble Man on Sat Jul 18, 2020 12:57 am, edited 5 times in total.

Post

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.

Post

hi Moss

it seems the akai fire has some drum sequencer recording issues (akai fire). 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. ;-)
Last edited by xtreme sounds on Sat Jul 18, 2020 11:41 pm, edited 4 times in total.

Post Reply

Return to “Controller Scripting”