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

Post Reply New Topic
RELATED
PRODUCTS
Bitwig Studio 6-25%$299.00Buy Maschine

Post

Hi Moss,
I am running latest Windows 10, latest Bitwig 3.2.7 on
MB: Asus Pro WS X570-ACE
CPU: AMD Ryzen 9 3950X
RAM: 4x G.Skill F4-3200C15-16GTZSW

Post

IllusionCatalyst wrote: Sat Sep 19, 2020 6:52 am Hi Moss,
I am running latest Windows 10, latest Bitwig 3.2.7 on
MB: Asus Pro WS X570-ACE
CPU: AMD Ryzen 9 3950X
RAM: 4x G.Skill F4-3200C15-16GTZSW
No real idea. Where do you see this information? In the normal task manager? Can you post a screenshot?

Post

moss wrote: Wed Sep 16, 2020 8:01 am
melodyz wrote: Tue Sep 15, 2020 1:41 pm Hi there. Heres a request for the fire, but not sure if it can be done. Is there a way to lock the displayed pattern to a specific track so that selecting another track with the mouse that is not receiving midi from the fire will not altar the note display as it is locked to a specific track already? I was playing with 2 controllers - the fire and my keyboard and when I clicked the other track under keyboard control the fire changed displayed notes even though that track is not receiving from the fire.
Yes, pinning of tracks and devices is possible. Lets see if I can squeeze it in somewhere. Note, that you can already pin the track in Bitwig from the document pane on the right.
Hi sir

I see that now. I tried pinning a track from the device panel. It works. However that pesky stuck note thing came back. I selected the step sequencer mode after entering some notes from the note sequencer. And I removed some notes on the step sequencer page of fire. However I cannot tap the pads to adds notes back in.

Post

melodyz wrote: Sat Sep 19, 2020 1:09 pm
moss wrote: Wed Sep 16, 2020 8:01 am
melodyz wrote: Tue Sep 15, 2020 1:41 pm Hi there. Heres a request for the fire, but not sure if it can be done. Is there a way to lock the displayed pattern to a specific track so that selecting another track with the mouse that is not receiving midi from the fire will not altar the note display as it is locked to a specific track already? I was playing with 2 controllers - the fire and my keyboard and when I clicked the other track under keyboard control the fire changed displayed notes even though that track is not receiving from the fire.
Yes, pinning of tracks and devices is possible. Lets see if I can squeeze it in somewhere. Note, that you can already pin the track in Bitwig from the document pane on the right.
Hi sir

I see that now. I tried pinning a track from the device panel. It works.

Post

DrivenByMoss 10.7.0 is online!

Get it from http://mossgrabers.de
  • Requires Bitwig 3.2.5+
  • APCmini
    • New: Faders use new hardware API, simulator shows positions
  • NI Kontrol Mk 1
    • New: Knobs use new hardware API, simulator shows positions
    • New: Added settings for knob speed
  • NI Kontrol Mk 2
    • New: Knob speed settings are now from -100 to 100
  • Launchpad
    • Fixed: Pro Mk3: The last selected play / sequencer mode was not restored
    • Fixed: Volume, Pan and Sends view was canceled when track selection changed.
  • MCU
    • New: Added settings for knob speed
  • NI Maschine Mk3
    • New: Added settings for knob speed
  • OSC
    • Fixed: /vkb_midi/note/{0-127}/color did not send scale colors, only played notes
    • Fixed: Page size of user parameters was not changed (was always 8 )
  • Push 2
    • New: Knobs use new hardware API, simulator shows positions
    • Fixed: Shutdown of the display process did not always exit cleanly
    • Fixed: In user mode the value changes couldn't be slowed down by using Shift
Enjoy!

Post

moss wrote: Sat Sep 19, 2020 7:19 am
IllusionCatalyst wrote: Sat Sep 19, 2020 6:52 am Hi Moss,
I am running latest Windows 10, latest Bitwig 3.2.7 on
MB: Asus Pro WS X570-ACE
CPU: AMD Ryzen 9 3950X
RAM: 4x G.Skill F4-3200C15-16GTZSW
No real idea. Where do you see this information? In the normal task manager? Can you post a screenshot?
Hi Moss, I have done a bit of troubleshooting. The core at 100% happens after a bit of use (I had two tracks with Diva vst3 and one with a Kontakt instrument), but I cannot tell exactly what is causing it. I see it in the Task Manager and the first time I noticed it because the CPU fan was spinning faster than usual.

It is the Audio Engine process that goes to 100% when the driver is running, even if there are no tracks at all in the project (I deleted them all). When it happens, if I either disable the driver leaving the Audio Engine on, or disable the Audio Engine leaving the driver on, the CPU core goes back to very low activity.

I do not think it is related to your driver, seems more like an internal Bitwig issue.

I have a feature suggestion too. It would be very nice if it would be possible to Duplicate Clips like in the Novation Circuit: Press Duplicate and keep it down, then click the source Clip and then one or more target Clips, even across different tracks, like a copy/paste. The current Duplicate behavior could be kept by clickling twice the same Clip. I think it would make the Duplicate way more flexible, and allow one less mouse interaction.

Thank you very much

Post

Hi Moss,

Thanks for the Launchpad restore fix, it works well now :)

But, now, when I press one of "Chord" or "Sequencer", it goes to either Chord or Sequencer mode, but then I can't go back to Note mode. I can go to Session mode.

Thanks :)

Post

moss wrote: Fri Aug 07, 2020 8:48 am
AFranke wrote: Thu Aug 06, 2020 3:03 pm Hi Jürgen,
if I press a key in InControl Mode of my SL MK3 the wrong LED lits up. The octave setting of the SL is set to 0. If I press C4, than C3 lits and so on. If I setup the octave setting to -1 the gap between the pressed note and the note even gets an octave wider. Tried it with 10.5 and 10.6 and can reproduce it all times... :-)

LG Andy
Is that a 61?
Yes it is the 61SL Mk3, will it be fixed in the near future? It's a little bit boring. :-) :D

Post

Hi!
I regularly use drivenbymoss with my launchpad pro with reaper. I'm trying it out now with bitwig.
Sorry if it already have been asked, but I can't figure out how to start and stop recording a clip when in note mode ?
Is there a way ? I did it within session mode but it's pretty hard to change mode to start or stop recording fast after playing in note mode.
Thanks for both extensions anyway !

Post

avoca wrote: Mon Sep 21, 2020 1:47 pm Hi Moss,

Thanks for the Launchpad restore fix, it works well now :)

But, now, when I press one of "Chord" or "Sequencer", it goes to either Chord or Sequencer mode, but then I can't go back to Note mode. I can go to Session mode.

Thanks :)
Sorry, will be fixed in the next update.

Post

AFranke wrote: Mon Sep 21, 2020 2:49 pm
moss wrote: Fri Aug 07, 2020 8:48 am
AFranke wrote: Thu Aug 06, 2020 3:03 pm Hi Jürgen,
if I press a key in InControl Mode of my SL MK3 the wrong LED lits up. The octave setting of the SL is set to 0. If I press C4, than C3 lits and so on. If I setup the octave setting to -1 the gap between the pressed note and the note even gets an octave wider. Tried it with 10.5 and 10.6 and can reproduce it all times... :-)

LG Andy
Is that a 61?
Yes it is the 61SL Mk3, will it be fixed in the near future? It's a little bit boring. :-) :D
I asked Novation about it but did not get an answer yet. I just sent a reminder.

Post

ElVincente wrote: Tue Sep 22, 2020 11:06 am Hi!
I regularly use drivenbymoss with my launchpad pro with reaper. I'm trying it out now with bitwig.
Sorry if it already have been asked, but I can't figure out how to start and stop recording a clip when in note mode ?
Is there a way ? I did it within session mode but it's pretty hard to change mode to start or stop recording fast after playing in note mode.
Thanks for both extensions anyway !
On the Launchpad Pro (first model):
To stop recording you can press User+Rec button
To create a new clip: User+Double

Post

moss wrote: Tue Sep 22, 2020 11:12 am
AFranke wrote: Mon Sep 21, 2020 2:49 pm
moss wrote: Fri Aug 07, 2020 8:48 am
AFranke wrote: Thu Aug 06, 2020 3:03 pm Hi Jürgen,
if I press a key in InControl Mode of my SL MK3 the wrong LED lits up. The octave setting of the SL is set to 0. If I press C4, than C3 lits and so on. If I setup the octave setting to -1 the gap between the pressed note and the note even gets an octave wider. Tried it with 10.5 and 10.6 and can reproduce it all times... :-)

LG Andy
Is that a 61?
Yes it is the 61SL Mk3, will it be fixed in the near future? It's a little bit boring. :-) :D
I asked Novation about it but did not get an answer yet. I just sent a reminder.
Cool, thank you so much! 😎

Post

moss wrote: Tue Sep 22, 2020 11:16 am
ElVincente wrote: Tue Sep 22, 2020 11:06 am Hi!
I regularly use drivenbymoss with my launchpad pro with reaper. I'm trying it out now with bitwig.
Sorry if it already have been asked, but I can't figure out how to start and stop recording a clip when in note mode ?
Is there a way ? I did it within session mode but it's pretty hard to change mode to start or stop recording fast after playing in note mode.
Thanks for both extensions anyway !
On the Launchpad Pro (first model):
To stop recording you can press User+Rec button
To create a new clip: User+Double
Thanks ;)

Post

moss wrote: Tue Sep 22, 2020 11:09 am
avoca wrote: Mon Sep 21, 2020 1:47 pm Hi Moss,

Thanks for the Launchpad restore fix, it works well now :)

But, now, when I press one of "Chord" or "Sequencer", it goes to either Chord or Sequencer mode, but then I can't go back to Note mode. I can go to Session mode.

Thanks :)
Sorry, will be fixed in the next update.
Super, thanks!

Post Reply

Return to “Controller Scripting”