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

[Dazel77]

Hi Jurgen,
As many others have stated, I'm very grateful for your hard work for all your utilities!

I'm wondering if you have a more thorough manual for the Generic Flexi particularly. I'm having difficulties with understanding the various individual components, such as:
- What is the selected mode and how can you change it?
- What are Selected slot trigger, device update, and function?
- How are the options actions used?

The above are just a few, but you get the idea. I'm the type of person I struggle understanding things without understanding the items which they are based on. I've been guessing and testing for the better part of a week, researching, reading articles, MIDI, etc. and I feel as if I'm drowning honestly.

Short story - I had all my music/studio gear "shelved" following a fairly significant unfortunate family event, and am just now getting back into it in efforts to "cope" . So I bought Bitwig 5, and proceeded to set everything up. I was met with obsolescence for my old M-Audio Axiom 61 v1 and NanoKontrol v1, and am trying to understand in order to manually configure usability, and I feel journey in efforts to appease my life issues is starting to contribute to my own stresses.

I'd like to setup my nanoKontrol for track levels, pan, arm, and mute, and then mu Axiom for VST parameters and such. But I need to understand. I'll put in the work researching and testing, but I can't seem to find the missing piece in order to understand.

Any help you can provide, or point me to is greatly appreciated!!

Cheers!

[moss]

Hi Jurgen,
As many others have stated, I'm very grateful for your hard work for all your utilities!

I'm wondering if you have a more thorough manual for the Generic Flexi particularly. I'm having difficulties with understanding the various individual components, such as:
- What is the selected mode and how can you change it?
- What are Selected slot trigger, device update, and function?
- How are the options actions used?

The above are just a few, but you get the idea. I'm the type of person I struggle understanding things without understanding the items which they are based on. I've been guessing and testing for the better part of a week, researching, reading articles, MIDI, etc. and I feel as if I'm drowning honestly.

Short story - I had all my music/studio gear "shelved" following a fairly significant unfortunate family event, and am just now getting back into it in efforts to "cope" . So I bought Bitwig 5, and proceeded to set everything up. I was met with obsolescence for my old M-Audio Axiom 61 v1 and NanoKontrol v1, and am trying to understand in order to manually configure usability, and I feel journey in efforts to appease my life issues is starting to contribute to my own stresses.

I'd like to setup my nanoKontrol for track levels, pan, arm, and mute, and then mu Axiom for VST parameters and such. But I need to understand. I'll put in the work researching and testing, but I can't seem to find the missing piece in order to understand.

Any help you can provide, or point me to is greatly appreciated!!

Cheers!

The videos on my Youtube channel should answer all these questions. Here is the playlist:

[Dazel77]

Hi Jurgen,
Thanks a ton for the quick feedback!
I've already watched all your pertinent videos, read the available documentation, completed lengthy guess and test, and I think I'm just dumb, lol

For some reason I'm struggling to understand this, yet in my professional life I'm an industrial programmer and think I should be able to grasp, but I'm still struggling (Maybe that's my problem)

So after all I still can't seem to setup my nanoKontrol to adjust track volume of the first 8 tracks with the 9th group for master volume. So I was thinking, to shorten my guess and testing to maybe read up on the individual parameter details/specs/ reference material as to form the understanding necessary to program efficiently.

I asked on another thread if anyone can provide me their Ex/Import files for the nanoKontrol v1 so I can load it, then learn from how that's setup to then adjust to my liking if necessary and go from there.

I apologize that I appear to have a thick skull, lol. Its clearly me because it seems so many other get it.

Anyways, thanks again, and if there is any reference material you can think of to send my way, I'd very much appreciate it!
Cheers!

[el davo]

Hi Juergen, just a heads up in case you had not noticed yet - your site is down today (DNS lookup error).

[Dazel77]

Hi Juergen, just a heads up in case you had not noticed yet - your site is down today (DNS lookup error).

FYI - Its working over here. It was likely a temporary thing.

Cheers!

[Clearscreen]

Are you maybe seeing a cached version? Sites not working here...

[zvuku]

I'l trying to get to the site as well - but just getting server not found errors. Could someone post the bitwig push scripts zip here?

[moss]

Seems my DNS provider is down (they created a swimming pool in their computing centre).
For the time being you can reach the server directly: https://92.205.106.63 (you have to ignore the SSL warning).

[Dazel77]

Hi Jurgen,
I made some significant headway last night and was able to program all my NanoKontrol groups and such and am gaining understanding of the approach moving forward. I do have some more specific questions for you now if you don't mind. Its in regards to the options and modes. I'm not sure how this aspect works and am wondering if you could provide some detail?

[trostiflex]

I use the Generic Flexi script with my Midi Fighter Twister and it works really great, thanks moss ! There's just one thing I can't do : scroll parameter pages of a device.

How can I do this ? When I select this in the Generic Flexi script and I tweak a knob with my Midi Fighter Twister nothing happens. That's weird because, otherwise, everything works, I can select one specific page, I can go to the next pages, the previous pages, but not scrolling.

[Gross138]

I have the same issue with a twister and the flexi script. A work around was to set two encoder buttons to previous and next page.

[moss]

Hi Jurgen,
I made some significant headway last night and was able to program all my NanoKontrol groups and such and am gaining understanding of the approach moving forward. I do have some more specific questions for you now if you don't mind. Its in regards to the options and modes. I'm not sure how this aspect works and am wondering if you could provide some detail?

It is quite simple: you can assign 8 knobs and 8 buttons which will be used in all modes. Then assign buttons to directly select a mode or buttons switch modes. The modes are explained in the manual.

[moss]

I use the Generic Flexi script with my Midi Fighter Twister and it works really great, thanks moss ! There's just one thing I can't do : scroll parameter pages of a device.

How can I do this ? When I select this in the Generic Flexi script and I tweak a knob with my Midi Fighter Twister nothing happens. That's weird because, otherwise, everything works, I can select one specific page, I can go to the next pages, the previous pages, but not scrolling.

It is not intended to be scrolled. You need to assign it to buttons.

[trostiflex]

It is not intended to be scrolled. You need to assign it to buttons.

I assigned it to a Midi Fighter Twister knob, like I did for all the other Flexi parameters I assigned. Are you making a difference between buttons and knobs and saying that the Midi Fighter Twister cannot use this parameter because it doesn't have buttons, only knobs, or am I misunderstanding you ?

[moss]

It is not intended to be scrolled. You need to assign it to buttons.

I assigned it to a Midi Fighter Twister knob, like I did for all the other Flexi parameters I assigned. Are you making a difference between buttons and knobs and saying that the Midi Fighter Twister cannot use this parameter because it doesn't have buttons, only knobs, or am I misunderstanding you ?

Yes, that's what I am saying. Triggering this from a knob basically means triggering a button multiple times, which needs to be slowed-down as well.