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

[sj1]

Continuing to search for information on Auto Color (AutoColor), I found a video on YouTube (which I had not seen before) titled 'bitwig auto color'. This helped.

However, compared to my experience (now with BW 3.3.5 and DBM 11.6.1) this was incorrect because (unlike in the video) there is no 'Moss' listed in the Bitwig Hardware Vendor pick-box.

Bitwig - Add Controller - HW Vendor Picker 01.jpg

Bitwig - Add Controller - No Moss 01.jpg

This mystified me for awhile until ultimately I kept digging and looked under the Utilities label in the list.

Bitwig - Add Controller - Utiities - Auto Color 01.jpg

Voila! There it was, ready for me to Add it.

FWIW, I think making the current operational facts clear both in the docs and on YouTube would be desirable. Sometimes just a little bit more information can get people home alot quicker!

Hopefully this note will assist anyone reading here.

Thanks as always to the amazing Moss. The breadth and depth of the work you've done and made available continues to astound!

[sj1]

BTW, I made a little demo of Auto Color doing the Bitwig (3.3.5) colors.

I think there may be one discrepancy. Gray and Gray Half appear to be the same shade to me.

[moss]

BTW, I made a little demo of Auto Color doing the Bitwig (3.3.5) colors.

I think there may be one discrepancy. Gray and Gray Half appear to be the same shade to me.

I will update the manual to clarify the installation for the utility extensions. You are right, if you are new to Bitwig this is not clear.

Regarding the colors: the half gray value is the "off" selection in the Bitwig color menu. It is different then the normal Gray but very hard to notice. You can see it if you switch between the colors manually in the menu.

[yotah]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Dear moss, would it be possible to implement 14bit absolute values for MIDI CC mapping?
Ableton supports this feature and its very helpful. Many controllers send high resolution control messages this way.
Details are described here: http://little-scale.blogspot.com/2016/0 ... -midi.html (http://little-scale.blogspot.com/2016/07/ableton-live-and-high-resolution-midi.html)

Thank you very much for your amazing extension!

[moss]

Dear moss, would it be possible to implement 14bit absolute values for MIDI CC mapping?
Ableton supports this feature and its very helpful. Many controllers send high resolution control messages this way.
Details are described here: http://little-scale.blogspot.com/2016/0 ... -midi.html

Thank you very much for your amazing extension!

I guess you are referring to the Generic Flexi. I decided against supporting 14bit values since this would require some massive changes in my code and the benefit would be minimal since you can already use relative values and pitch bend for absolute ones.

[Tj Shredder]

The benefit would be 14 bit resolution. Why would that be minimal?

[moss]

The benefit would be 14 bit resolution. Why would that be minimal?

That was not what I meant. You can already do pitchbend which is also 14 bit or relative, which is even better.
Which controller are you using which has absolute controls and supports NPRN but not pitchbend (and is not supported by a Bitwig script anyway)?

[Tj Shredder]

Its about controllers which send 14-bit controller messages. For example a faderbox with 8, 9 or 16 different faders. None of them is sending pitchbend...
Its as simple as taking the MSB controller number and the LSB controller number (+32) and their values to combine them into one value with 14-bit resolution...

[dupont]

Hello, has this bug been solved in 3.3.5 ?
viewtopic.php?f=268&t=502948&p=8049396#p8049396

[moss]

Hello, has this bug been solved in 3.3.5 ?
viewtopic.php?f=268&t=502948&p=8049396#p8049396

I commented this above:

"I had a longish talk about this issue. Thing is that it is not a bug but a missing method for scrolling to a scene (there is currently only a method for scrolling to a track). Conclusion was that this should actually not be coded at all but a controller option in Bitwig, if it should follow or not but this needs some planning and thought. So, I am afraid this might take a bit more time."

[dupont]

Ok, thanks for the feedback.
This is a real showstopper for a live oriented DAW ! I must use the mouse to scroll down the session view during live act.

[moss]

Ok, thanks for the feedback.
This is a real showstopper for a live oriented DAW ! I must use the mouse to scroll down the session view during live act.

I agree but better complain at Bitwig support.

[dupont]

Ok, thanks for the feedback.
This is a real showstopper for a live oriented DAW ! I must use the mouse to scroll down the session view during live act.

I agree but better complain at Bitwig support.

true, I hope there are aware of this issue or they need some serious beta testers !

[Munaki]

Hello,
i recently purchase PUSH 2 for use in Bitwig. It would be amazing to be able use 16 velocities for sequencer? Right now is not very convenient to make changes of volume. Long press and change volume is not usefull for quick volume editing. way via accent is better, but you also need to set accented volu first, with is not very fast.
Anyway thank you very much for your work, it is magic!
Jan

[moss]

Hello,
i recently purchase PUSH 2 for use in Bitwig. It would be amazing to be able use 16 velocities for sequencer? Right now is not very convenient to make changes of volume. Long press and change volume is not usefull for quick volume editing. way via accent is better, but you also need to set accented volu first, with is not very fast.
Anyway thank you very much for your work, it is magic!
Jan

Could you describe how you envision it to work?