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

[moss]

Hi Moss,
Thank you so much for all your hard work, it is greatly appreciated, and makes a huge difference in the overall use of Bitwig!

A quick question, will you be supporting the new Novation Launchkey 37 [MK3] which will be released tomorrow? (There will also be 25, 49 and 61 key versions.)

Thanks again...

Sorry, no. But with these simple keyboards Generic Flexi should be sufficient.

[imcubix]

DrivenByMoss 10.6.1 is online!

Get it from http://mossgrabers.de

• APC40MkII
  • New: Scene buttons are lit in the color of the scene.
• Akai Fire
  • Fixed: Ghost notes could appear when quickly editing pitches in the sequencer and create a new clip.
  • Fixed: Removed session flip option, which did crash.
  • Fixed: Also prevent deletion of note in sequencer when knob was touched but not turned.
• Komplete Kontrol MkI
  • Fixed: Interpretation of knob speed was wrong.
• Push
  • Fixed: Mapped User Parameters did not show their name and value.

Enjoy!

Wow, that was fast. Works great now!

[imcubix]

Do you take donations? I'd like to buy you a beer

[JBlongz]

Hey Moss! This script is awesome. I would love to donate to have a feature tweaked if possible. The note repeat button works, but the time-division buttons dont, it seems the only way is to hit shift+repeat to get the scrollable menu. It is possible to make the time division buttons work as in Ableton? Name your price to make some time for this.

[xtreme sounds]

HI sir

Heres one more feature request probably not doable. Since the fire has only 4 knobs, is there a way to have an optional settings control where alt can toggle on and off so that the 4 knobs can go between a shifted mode for the other 4 parameters without holding down the alt button the whole time?

[astartes]

The Midi Output Error some users postet about in June seems to be back. I can´t connetct my M32 to Bitwig. Have allready checked the Names, same in MidiOX and Bitwig (Same in Reaper and Ableton as well). Allready tried to clear the Chache and reset Bitwig, no Luck. Re-Install (and before complete Reg Cleanup by Hand): No Luck. I always get: "KOMPLETE KONTROL M32 MIDI: Could not open MIDI output. There is not enough Memory for this TaskQuit one or more Aplications to increase availeble Memory and Try again". Teh only other App besides Bitwig i could cancel is windows 10 itself, nothing else is running. The M32 worked well until your Latest Script, installed under Bitwig 3.2.6 (Update to the latest Ver of Bitwig came a few days later). The M32 works without Problems in Reaper with your Script and in Ableton as well, only Bitwig causes Problems.

I use your Script for all of my Controllers (Launchpad Pro, Generic flexi on my Launchcontrol XXL, Mackie HUI on the XXL as well on the Second Midi Output, Same config in reaper, no problems there). It´s only the M32 that makes trouble, only in Bitwig. Strange indeed....

[moss]

The Midi Output Error some users postet about in June seems to be back. I can´t connetct my M32 to Bitwig. Have allready checked the Names, same in MidiOX and Bitwig (Same in Reaper and Ableton as well). Allready tried to clear the Chache and reset Bitwig, no Luck. Re-Install (and before complete Reg Cleanup by Hand): No Luck. I always get: "KOMPLETE KONTROL M32 MIDI: Could not open MIDI output. There is not enough Memory for this TaskQuit one or more Aplications to increase availeble Memory and Try again". Teh only other App besides Bitwig i could cancel is windows 10 itself, nothing else is running. The M32 worked well until your Latest Script, installed under Bitwig 3.2.6 (Update to the latest Ver of Bitwig came a few days later). The M32 works without Problems in Reaper with your Script and in Ableton as well, only Bitwig causes Problems.

I use your Script for all of my Controllers (Launchpad Pro, Generic flexi on my Launchcontrol XXL, Mackie HUI on the XXL as well on the Second Midi Output, Same config in reaper, no problems there). It´s only the M32 that makes trouble, only in Bitwig. Strange indeed....

Meanwhile, I have a M32 but don't have an issue with it. Can you please make sure to run the latest versions of everything:
- Bitwig 3.2.7
- Komplete 2.4.0 + the latest Firware Update that comes with it for the M32
- DrivenByMoss 10.6.1

[astartes]

KK/Firmware/BWS and your script are on the latest versions.

Have checked the issue with my second Machine, there are no porblems as well, all runs as it should. On my Main Machine it worked as well , all of a sudden that error apeared. Dunno what went wrong here, did nothing special. Hopefully there´s a way araound that prob without setting up the whole machine new *fingers crossed*


*Edit* Tested a bit further: As long as i din´t use the MIDI Out i can use the M32 without Porblems

Edit2: Bomes Virtual Midi Port (NI uses it for the Komplete Kontrol DAW integration) is Blocking the Midi Out. As long as Bomes isn´t running the M32 starts up with no errors (an no Komplete Kontrol DAW Ports). The good Thing: I do not really need the MIDI out Port, i´ve ste the Midi out from my soundcard in your script and it works as it should. I can control Volume, pan sends and so on, can play notes and can control the KK Vst Plugin.

[Raffi]

Hi Moss,

I am using the Push2 script (latest DrivenByMoss) and noticed the Pad Dynamics setting is not recalled upon restart. It does save the value but I have to make a change every time to the Dynamics setting in order for it to react/resend this value to the Push. I didn't check the other settings which might suffer from the same issue. Basically this is the same issue as with the Display color settings not being sent through, which you've fixed later on.

As always thank you for the help and your great script.

[ingostr]

Hi Moss,
I'm using your bitwig extension scripts with a Launchpad Pro Mk3 on Linux. The device is correctly recognized and bitwig notifies me that it is now "ready to use". Unfortunately, that doesn't seem to be the case: The device appears to be operating in standalone mode. Bitwig seems to receive MIDI messages, because hitting the pads triggers note events. I tried changing the MIDI channel (e.g. 2 or 3 instead of 1) and that creates another Launchpad Pro Mk3 device with the channels set back to 1. Are there any other tricks to make this work and that I might have missed?

[moss]

Hi Moss,

I am using the Push2 script (latest DrivenByMoss) and noticed the Pad Dynamics setting is not recalled upon restart. It does save the value but I have to make a change every time to the Dynamics setting in order for it to react/resend this value to the Push. I didn't check the other settings which might suffer from the same issue. Basically this is the same issue as with the Display color settings not being sent through, which you've fixed later on.

As always thank you for the help and your great script.

Sorry, cannot find an issue. Tried all three parameters, which all get recalled an sent on startup.

[moss]

Hi Moss,
I'm using your bitwig extension scripts with a Launchpad Pro Mk3 on Linux. The device is correctly recognized and bitwig notifies me that it is now "ready to use". Unfortunately, that doesn't seem to be the case: The device appears to be operating in standalone mode. Bitwig seems to receive MIDI messages, because hitting the pads triggers note events. I tried changing the MIDI channel (e.g. 2 or 3 instead of 1) and that creates another Launchpad Pro Mk3 device with the channels set back to 1. Are there any other tricks to make this work and that I might have missed?

Just checked again but works fine for me on Linux (latest Ubuntu Studio).
Did you install the latest Firmware in the Launchpad? MIDI Channel should set to 1.

[xtreme sounds]

FIRE feature request. Hi On the perform button, is there any way to make use of the display to tell us which scene we are activating or which scenes the 4 rows are targeting? Its sort of difficult to tell which scene to enact with the 4 rows after scrolling down a ways.

Also there is an unused button on many sequencer pages (the top green button). I wonder if there is anything else we can use that for that is a good feature? Opening modulation panel? Or setting clip to loop or unloop? Or switching between arranger or clip view? Cant really think of anything super cool to add.

[moss]

DrivenByMoss 10.6.2 is online!

Get it from http://mossgrabers.de

• Requires Bitwig 3.2.5+
• Akai Fire
  • New: Shift + Scene: Selects the scene without starting it.
  • New: Selecting or starting a scene shows its' name in the display.
• Launchpad
  • New: Display the track number and name on track selection.
  • New: Display the function of the selected row in Mix mode.
  • New: Drum mode 4 and 8 move in steps of 4 and 8 up and down so that now all sounds can be reached.
  • Fixed: Not all selected modes were displayed in Bitwig and some names showed Session.
  • Fixed: Mix view was canceled when track selection changed.
  • Fixed: Long pressing a pad in a fader mode caused the selection of a track.
• Push
  • New: Drum mode 4 and 8 move in steps of 4 and 8 up and down so that now all sounds can be reached. The previous selection with Shift + Scene was removed.
  • New: Note Repeat + Scene - Change note repeat period
  • New: Shift + Note Repeat + Scene - Change note repeat note length

Enjoy!

[xtreme sounds]

Nice update on fire thanks!!!