DrivenByMoss for Bitwig and Reaper

General discussion
61

I am waiting for 3.5.1 so I can test again.

2 Likes
62

It is out now. Sorry that it took so long. I wanted to have more stuff in the release, but I understand that this was quite blocker on mk1.

2 Likes
63

Aah, my issue ended up being an older extension file was installed in the Bitwig extension folder which I hadn’t replaced with the new one. All fixed now!

The template is amazing! Great work moss!!

1 Like
64

Thanks! Works fine again!

1 Like
65

@moss how did you program the knob gestures? I’d like to add that for individual synth presets as well. Could you possibly even just point out where you did this in the script? Thanks!

66

@moss Is there a way to fine-tune the control that moves the play cursor? As of now, it’s very sensitive, and a tiny move pushes the cursor several bars forward/backward.

In a perfect world, in addition to customizing the sensitivity of that knob, we would hold a hardware button while turning the knob for fine adjustments (beats instead of bars). It would be so useful for every parameter. The MIDI Twister has different scripts for achieving this, and I think it’s missing for the E1.

2 Likes
67

The Electra One sends MIDI sysex messages when a button is touched. The analysis of the combinations is implemented in the Bitwig extension.

68

Touch Knobs 1, 2 and 7: this emulates the pressing of a ‘shift’ button. Currently, this allows to fine tune all knobs.

69

Thanks, it works as expected (moving beats instead of bars), but, if I may:

  1. That combination of gestures is not handy. Why not just touching “knob 1” for example? Maybe we can hope for a “toggle” action (instead of a “hold” action) to switch between bars and beats. That way, we could move the play cursor with only one hand. Or maybe an option in the controller section (Bitwig preferences) to choose between bars or beats. By the way, I remember that Martin talked about customizing hardware buttons someday. At this time, I hope we will be able to have a “real” shift + twisting knob, that would work for every parameter, not just the play cursor

  2. The sensitivity is still too high. Is there a way to reduce it, please?

70

Little bug: contrary to changing bank tracks, changing bank markers (transport page) is inverted. The previous button goes to the next page and vice and versa.

71

In the preferences, I see an option for the behaviour on the stop button, but I can’t see a stop button on the transport page. There are just a play button that play/pause, and a record button. If there is actually no stop button, I think we should have the ability to choose between a “play/pause” or “play/stop” behaviour concerning this “play” button.

72

The problem with transport speed is that there is no info about the current zoom factor. As soon as you zoom out a bit it gets slower and quickly too slow. Will add it to wishlist for Bitwig.

Thanks for the 2 bug reports! Both will be fixed in the next update.

2 Likes
74

Sorry, but I think I don’t understand. The sensitivity is the same whatever the current horizontal zoom. Currently, half of a revolution knob equals around 70 bars, which is a lot, even with a project with a big zoom-out. Do you think users could benefit from at least an option to adjust that sensitivity, please? If a user wants to move forward/backward very quickly, he would prefer using markers, in my humble opinion. Maybe I am nitpicking, but coming from a MIDI Twister controller, with a play cursor integrated perfectly, it’s like a shock to switch to the E1.

Thank you very much for the two bugs.

75

If I may, here are two other inconsistencies @moss

  • turning the knob for the previous bank navigation only works clockwise, which is counterintuitive because we tend to turn the knob in the other direction to display previous tracks (disposed at the left of the current view) ; so I suggest allowing both directions
  • we would expect to turn several pages when turning a knob for bank navigation. Currently, we have to turn the knob one time to go to the second page, then another one to go to the third one. Only one twist should scroll through several pages
  • therefore, I suggest bank navigation buttons work differently with knobs: each of the two knobs could navigate to previous/next track pages if we would turn it counterclockwise/clockwise, because in the end, we only need one knob to scroll pages (but I can see the benefit of the two buttons, of course)

What do you think?

Thanks,

creal.

EDIT: I also think you should remove the “rec arm” buttons for FX and master tracks. It would make the readability better.

76

That’s how the device works. I cannot change this. Maybe @martin can comment on this.

77

I assume it is a momentary pad (not a toggle).

momentary pads send the “on” signal when they receive a clockwise change on the knob. “off” is sent when the user releases the knob.

The toggle pads send “on” on clockwise change and “off” on counter-clockwise change.

What I could possibly do is to send “on” of momentary pads when there is a knob change without taking the direction in account.

79

I agree with your suggestion. It could solve the first point I mentioned.

Thank you.

80

In LUA, I often add extra code to prevent the “off” message from being sent with a momentary control. Not sure if that’s a viable approach in this case.

81

I wish you all a happy new year!

DrivenByMoss 22.1.0 is out and there are some goodies for the Electra One:

  • New: Added knob sensitivity (speed) settings.
  • New: Made knob touch combinations configurable with plenty of options.

Enjoy!

8 Likes
82

Perfect!! Thanks for this @moss :hugs:

Just 12hrs ago I was automating 2 parameter knobs in a session and my hand touched a 3rd one and it switched to the mixer and started automating volume instead. Was wondering if there was a way to disable it.