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

Post Reply New Topic
RELATED
PRODUCTS
Bitwig Studio 6$399.00Buy Maschine

Post

Attuned wrote: Mon May 30, 2022 7:58 am Hi all. I've just started testing out @Moss's Open Stage Control template. There's an issue on Safari on iPadOS where the modal for the Sends doesn't come to the top of the interface but seems to stay at the back of the screen.

Screenshot 2022-05-30 at 09.35.59.png

I've had a look at the edit screen but can't seem to figure out if this is a bug because of Safari or if it's something that can be fixed in the edit screen.
Just tested with latest Open Stage Control 1.16.1 with Firefox and Google Chrome and it looks fine. So I guess it is a Safari issue.

Post

Attuned wrote: Mon May 30, 2022 11:04 am Hi Moss. Firstly, thanks for your amazing work! It's really appreciated.

I'm implementing the OSC controller in one of my projects and going through the documentation, there are formatting issues on a few of the pages (128,129,134) that make it difficult to see what the various parameters are that need to be passed. Could you provide an update version of this doc please?

Thanks
Will see if I can improve that. For the time being look here:
https://github.com/git-moss/DrivenByMos ... l-(OSC).md

Post

psyco_tik wrote: Tue May 31, 2022 8:55 am I am using bitwig v3.1.2 and drivenbymoss v8.98 but cannot seem to get "Scene: previous bank" or "Scene: Select next Bank" to work (theres no ui change) for a Flexi controller. Also, there is no Play scene that I can see, without a play scene I don't know that i understand the use of being able to navigate thought available scenes.
There should be 8 functions in the Scene menu "Scene X: Launch Scene".

I have something in the back of my head that I forgot them in older versions but could not find it in the changes log.

Post

moss wrote: Wed Jun 01, 2022 9:46 am
psyco_tik wrote: Tue May 31, 2022 8:55 am I am using bitwig v3.1.2 and drivenbymoss v8.98 but cannot seem to get "Scene: previous bank" or "Scene: Select next Bank" to work (theres no ui change) for a Flexi controller. Also, there is no Play scene that I can see, without a play scene I don't know that i understand the use of being able to navigate thought available scenes.
There should be 8 functions in the Scene menu "Scene X: Launch Scene".

I have something in the back of my head that I forgot them in older versions but could not find it in the changes log.
yes, those are there. do you recommend using those?

Post

psyco_tik wrote: Thu Jun 02, 2022 4:58 am
moss wrote: Wed Jun 01, 2022 9:46 am
psyco_tik wrote: Tue May 31, 2022 8:55 am I am using bitwig v3.1.2 and drivenbymoss v8.98 but cannot seem to get "Scene: previous bank" or "Scene: Select next Bank" to work (theres no ui change) for a Flexi controller. Also, there is no Play scene that I can see, without a play scene I don't know that i understand the use of being able to navigate thought available scenes.
There should be 8 functions in the Scene menu "Scene X: Launch Scene".

I have something in the back of my head that I forgot them in older versions but could not find it in the changes log.
yes, those are there. do you recommend using those?
Sure.

Post

Hi, I noticed the pressure/polyphonic aftertouch information doesn't seem to be recognized with my Launchpad Pro Mk3. Do I miss something? Convert Poly Aftertouch to Poly Aftertouch is on in the settings.

Post

ottsch wrote: Thu Jun 02, 2022 1:55 pm Hi, I noticed the pressure/polyphonic aftertouch information doesn't seem to be recognized with my Launchpad Pro Mk3. Do I miss something? Convert Poly Aftertouch to Poly Aftertouch is on in the settings.
How did you try to use it? Are you using the expression modulator?

Post

moss wrote: Thu Jun 02, 2022 9:07 pm
ottsch wrote: Thu Jun 02, 2022 1:55 pm Hi, I noticed the pressure/polyphonic aftertouch information doesn't seem to be recognized with my Launchpad Pro Mk3. Do I miss something? Convert Poly Aftertouch to Poly Aftertouch is on in the settings.
How did you try to use it? Are you using the expression modulator?
Yes

Post

ottsch wrote: Fri Jun 03, 2022 6:11 am
moss wrote: Thu Jun 02, 2022 9:07 pm
ottsch wrote: Thu Jun 02, 2022 1:55 pm Hi, I noticed the pressure/polyphonic aftertouch information doesn't seem to be recognized with my Launchpad Pro Mk3. Do I miss something? Convert Poly Aftertouch to Poly Aftertouch is on in the settings.
How did you try to use it? Are you using the expression modulator?
Yes
Just tested and it works fine.

Check if you have installed the latest firmware (use the Novation Components App).
Also check if Poly-Aftertouch is enabled in the settings (section 10.4 in the Launchpad Pro manual).

Post

moss wrote: Fri Jun 03, 2022 7:30 am
ottsch wrote: Fri Jun 03, 2022 6:11 am
moss wrote: Thu Jun 02, 2022 9:07 pm
ottsch wrote: Thu Jun 02, 2022 1:55 pm Hi, I noticed the pressure/polyphonic aftertouch information doesn't seem to be recognized with my Launchpad Pro Mk3. Do I miss something? Convert Poly Aftertouch to Poly Aftertouch is on in the settings.
How did you try to use it? Are you using the expression modulator?
Yes
Just tested and it works fine.

Check if you have installed the latest firmware (use the Novation Components App).
Also check if Poly-Aftertouch is enabled in the settings (section 10.4 in the Launchpad Pro manual).
Thanks for the hint! It was actually set to Channel Pressure on the Launchpad.

Post

Hey Moss . I am using the push 1 .i was wondering if there was a way to check the monitoring status of all 8 tracks on screen. Or a workflow suggestion because I do a mixture of audio clip looping along with midi looping. Because of the audio clip looping, I need to make sure it is the only channel being monitored.

Thanks.

Solved.

I think I found a workaround. In the preferences under-recording behaviour if auto arm is unchecked, When you hold Record on the push and hit the button below the track header it will enable and disable monitoring.

I would still like to know if there is similar workflow that can or another option available.

Thanks

Post

BrandenBreaks wrote: Sat Jun 04, 2022 4:20 pm Hey Moss . I am using the push 1 .i was wondering if there was a way to check the monitoring status of all 8 tracks on screen. Or a workflow suggestion because I do a mixture of audio clip looping along with midi looping. Because of the audio clip looping, I need to make sure it is the only channel being monitored.

Thanks.

Solved.

I think I found a workaround. In the preferences under-recording behaviour if auto arm is unchecked, When you hold Record on the push and hit the button below the track header it will enable and disable monitoring.

I would still like to know if there is similar workflow that can or another option available.

Thanks
Yes, this is dependent on the settings in Bitwig. You can enable auto-arm for audio and MIDI tracks separately, which will also enable monitoring. If you keep the Select key pressed you can see and change the monitoring state of the current track.

Post

Hi,
I am a new bitwig user and can not get the screens or pots on the Maschine MK3 to work at all. Everything else works as it should in driven by moss. The pots are weird as I can't even manually map them to anything. Everything else w/ the script works. I have tried everything including mapping the mcu button as shown in the old video.
As an interesting aside I also cannot get the screens to function in the scipt provided by bitwig themselves.
Is this something that was broken in a bitwig update?

Post

Hi there Moss...appreciate the great work. This may be something interesting....A Bitwig script for the new Orba 2 by Artiphon. This new version of the Orba would be perfect for a Bitwig script to control the many ways of making sounds with the Orba2 device. Think some scripts have already been written for some of the other DAW's. thoughts?

Post

bitnificent wrote: Sun Jun 05, 2022 10:01 pm Hi,
I am a new bitwig user and can not get the screens or pots on the Maschine MK3 to work at all. Everything else works as it should in driven by moss. The pots are weird as I can't even manually map them to anything. Everything else w/ the script works. I have tried everything including mapping the mcu button as shown in the old video.
As an interesting aside I also cannot get the screens to function in the scipt provided by bitwig themselves.
Is this something that was broken in a bitwig update?
Just checked and it works fine. Installing and loading the necessary Maschine template is a bit tricky. I documented the necessary steps in section 19.1 in the DrivenByMoss manual.

Post Reply

Return to “Controller Scripting”