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

[moss]

Introducing the MIDI monitor:

I'm trying to get this going on BSW 3.3b3 and when I select "Impulse - Impulse" as my MIDI source, it complains and tells me that the source is already in use, which to be fair, it is - it's how I am able to play notes
What am I missing that would enable me to play my keyboard *and* monitor it on screen?

Since the driver of your device seems not to be multi-client you have to disable one or the other.

[carlca]

Since the driver of your device seems not to be multi-client you have to disable one or the other.

Thanks, Jürgen! You are correct, I think. If I disable the "Impulse 25/49/61", I can indeed launch the MIDI Monitor tool. Interestingly, the keyboard still seems to send MIDI data to BWS, but presumably with a reduced feature set.

I've left an issue with the dev of the Impulse script at https://github.com/tlipinski/bitwig-nov ... /issues/16.

[ElectronicBattle]

Hello all

Using the latest DrivenByMoss script 10.8.0 on linux (Linux Mint 20 == ubuntu 20.04) , I can't get BWS 3.28 or 3.3 beta to work reliably with my APCMini. It s more than feasible that I am doing something wrong i.e. using BWS incorrectly and I wondered if someone could offer me some advice please.

Symptoms:

(1) often, but not always, the button lights when in drum machine or sequencer mode are either erratic (they might remain unchanged, or they might change by themselves but not in any relationship to the clip contents) or non-existent (the drum machine grid of 4x4 in the bottom LHS doesn't appear, the sequencer "bar" which steps across the 8x8 grid doesn't appear).

(2) Occasionally, during a session the APCMini seems to work properly - the drum machine grid triggers the drum machine voices and the drum machine sequencer causes notes to be populated in the grid.

3) Once or twice out of a few dozen attempts the sequencer page (shift and button 4) has worked and I have been able to generate a sequence, run the sequence and add notes "live". The rest of the time, I can't get the sequencer to run i.e. no vertical green LED "playhead" scrolling across the grid.

4) most of the time the shift-1/2/3/4/5 buttons do work and the onscreen message corresponds "session"/"play"/ etc.) and pressing shift shows that that button is now green - but I can't get a sequence to record into a clip. I just get the same buttons lit in each of the five modes (once I release "shift"). I end up with a display where there are ten amber lit buttons to mark the start/end of overlapping octaves (i.e. diagonal stripes running up and right). This is (I think) the "play" mode which simulates a playable surface with marked octave points. All the sliders work properly.

I saved a bitwig session when the drums did work and the sequence did work - but recalling it later and I am unable to get the APCMini to do anything tangible.

BWS seems to detect the APCMini correctly but I'm either doing something very wrong somewhere or there's a problem which I am causing somehow. Can anyone show me some very simple, very beginner-orientated guides to how to get the grid controller to work as a drum machine and as a sequencer please? Perhaps I am failing to grasp something fundamental.

edit: the controller script console merely states for "global":
Added MIDI IN: APC MINI MIDI 1
Added MIDI OUT: APC MINI MIDI 1

and for APCmini:
Called init()
CC 56 should be handled in framework...
Running.

[moss]

Using the latest DrivenByMoss script 10.8.0 on linux (Linux Mint 20 == ubuntu 20.04) , I can't get BWS 3.28 or 3.3 beta to work reliably with my APCMini. It s more than feasible that I am doing something wrong i.e. using BWS incorrectly and I wondered if someone could offer me some advice please.

I am afraid it is the device that is a bit wonky. I had similar issues since the beginning, like lights going of for no particular reason. Only solution is then to unplug and replug it.

[ElectronicBattle]

Hello Moss

OK - I did wonder if the problem might have been the APCMini (but usually the problem is me, so I had to err on the side of caution!).

Thanks for the information; I have been thinking of upgrading to a grid with (e.g.) velocity sensitivity and I imagine the Novation products might suit.

Without necessarily making a product recommendation, please could you say which in your opinion has been the most reliable device that you have written for? It'd help me stay away from anything wonky!

Again, thanks for helping.

Best wishes


EB

[moss]

OK - I did wonder if the problem might have been the APCMini (but usually the problem is me, so I had to err on the side of caution!).

Thanks for the information; I have been thinking of upgrading to a grid with (e.g.) velocity sensitivity and I imagine the Novation products might suit.

Without necessarily making a product recommendation, please could you say which in your opinion has been the most reliable device that you have written for? It'd help me stay away from anything wonky!

Luckily, the APCmini is the only device which has such issues. The new Launchpads (especially the Pro Mk3) are really nice devices, if you can live without faders and knobs.

[ElectronicBattle]

Excellent - I'll aim for a Pro MK3 in that case (I can continue to make use of the sliders on my APCMini if necessary). Thanks very much for your help and advice and naturally I want to add thanks very much for writing, releasing and updating your controller scripts.

edit: ordered!

[carlca]

Hi Jürgen,
sorry if this is an old question - I tried searching for it but didn't find any mention of it - is there any reason why the MIDI Monitor tool displays Middle C as MIDI note 60 as one would expect, but calls it C6 ? From what I've read, C4 is the accepted musician's standard for denoting Middle C.

[carlca]

Hi Jürgen,
sorry if this is an old question - I tried searching for it but didn't find any mention of it - is there any reason why the MIDI Monitor tool displays Middle C as MIDI note 60 as one would expect, but calls it C6 ? From what I've read, C4 is the accepted musician's standard for denoting Middle C.

Problem solved! I made a change to

Code: Select all

/Volumes/OS2/Bitwig/DrivenByMoss/src/main/java/de/mossgrabers/controller/midimonitor/controller/MidiMonitorControlSurface.java

and changed the calls in the Note Off and Note On cases within the handleMidi method to

Code: Select all

Scales.formatNoteAndOctave (data1, -2));

I then just rebuilt with Maven and everything is good

[moss]

Problem solved! I made a change to

Code: Select all

/Volumes/OS2/Bitwig/DrivenByMoss/src/main/java/de/mossgrabers/controller/midimonitor/controller/MidiMonitorControlSurface.java

and changed the calls in the Note Off and Note On cases within the handleMidi method to

Code: Select all

Scales.formatNoteAndOctave (data1, -2));

I then just rebuilt with Maven and everything is good

Thanks! Seems you are the first one who noticed that! Just fixed it as well.

[carlca]

Thanks! Seems you are the first one who noticed that! Just fixed it as well.

I suspected it must have been an oversight rather than by design; the fact that you have a parameter called octaveOffset told me that

[moss]

DrivenByMoss 10.9.0 is out!

Get it from http://mossgrabers.de

• Requires Bitwig 3.2.5+
• Fire
  • New: In Shift mode the 10th button of the first row (blue) activates duplicate mode. Can be used with the first row of the Mix mode to duplicate tracks and with clips in the Session mode.
  • New: In Shift mode the 12th button of the first row (red) activates delete mode. Can be used with the first row of the Mix mode to delete tracks and with clips in the Session mode.
  • New: In Shift mode the 11th button of the first row (green) doubles the content of the currently selected clip.
  • New: Press Stop+Clip in Session mode to stop the playback of the clip.
• Midi Monitor
  • Fixed: Displayed note octave was wrong for Note on/off and Poly aftertouch (e.g. showed C6 instead of C4).
• MCU
  • New: Added User mode. Press Device button twice to activate user mode.
• OSC
  • New: Added /update before and after each update cycle (if there is at least 1 update message).
  • New: /track/{1-8}/name {text} - Set a new name for the track
  • New: /device/layer/{1-8}/name {text} - Set a new name for the layer
  • New: Open Stage Control template: name of track and layer can be set
  • New: Open Stage Control template: added data receive indicator LED to transport bar
• SL Mk III
  • Fixed: Lightguide was only drawn black but not turned off on the hardware when disabled in the settings. The hardware light guide can now used again when the settings is disabled.

Enjoy!

[xtreme sounds]

Nice thanks for all this!

[ElectronicBattle]

I'm getting on quite well (but quite slowly) with my Launchpad Pro mk3 and DrivenByMoss. Ought I to learn the manual for the unmodified launchpad pro 3 as intended for Ableton, or is the DrivenByMoss effectively a complete replacement "OS" which I should be learning instead?

One thing I hope might be feasible to achieve is to record a sequence (using whichever sequencer: seq, polyseq or raindrops) and the transpose it "live ("on the fly") using one of the note modes. Ideally I would be able to transpose instantly and also by generating a clip containing the sequence and then transpose the clip in the usual timed mode i.e. the next clip repeat is transposed. Do you think this is achievable and how might I go about it?)

I reckon I have touched about 10% of it so far (both BWS and DrivenByMoss to be honest - and I have had BWS for more than three years - I'm a slow learner) and it is very enjoyable!

[xtreme sounds]

HI I adjusted my knob sensitivity to +15 on the Fire which feels better, however I noticed when selected plugins from the browser turning the select knob now skips every other plugin. Is there a way to restrict the knob sensitivity parameter to only user 1 and user 2 control knobs in a future update?

Also for the 4 knobs in browser mode, I dont think the 4th knob does anything. I also see there is one more menu that can be navigated which is the Any Device type vs , fx ,instrument pane in the bottom left of the browser.

also sometimes pressing just the play button engages recording a new clip whereas other times it does not (not sure about why that happens). also sometimes there is a count in other times not.