DrivenByMoss: Support for many hardware controllers (version 23.2.1)

[Pieter]

Originally Posted by moss

I am afraid there is nothing I can do about it. Haven't heard about this issue before and it works fine on my QCon Pro X. Have you checked for latest Firmware?

This unit's latest firmware is V1.23 and they are no longer suported.
This problem is not a gamechanger for me, I can deal with it and just wanted to know if there is a solution.
Thanks for your help and all the good work
!

[Tiggerdyret]

Hi Moss, I found bug with the Maschine software, when having Driven By Moss installed for using my Launchpad X and the Maschine Plugin. When the driver is engaged for my the undo function in Maschine doesn't work at all and doesn't register any actions to the undo/redo list. When the project is playing it does work correctly, but once I hit stop the undo data gets erased. I have tried to uncheck and remove the MK3 from the Moss devices list, but the problem persists. Only removing the driver completely from the control surface list fixes it. But then I can't use my Launchpad with Moss functionality ��

Edit: Here is the problem in action: https://www.youtube.com/watch?v=1_6RAspYRn8

[moss]

DrivenByMoss 4 Reaper 11.5.1 is online!

• Requires Reaper 6.12+
• All devices
  • New: Added 128 dummy drum channels to the drum pad bank. This allows e.g. to scroll now the rows of the drum sequencer of the Akai Fire.
  • Fixed: User parameters could not be changed.
• APC40
  • New: Knob LEDs are totally turned off if parameter does not exist.
• Fire
  • New: In Note Sequencer Shift + Grid buttons change the Scale, Shift + Alt + Grid buttons change the Scale Base key. For consistency the button combinations in Play and Piano modes are adjusted accordingly.
  • New: Use Shift + Select knob in note and Poly Sequencer mode to transpose notes of clip up/down.
  • Fixed: Channel parameters did not get reassigned when drum pad was changed.
  • Fixed: Selection got lost when scrolling too fast through drum pads in drum sequencer.
  • Fixed: Wrong parameter name was shown in combination with ALT button.
• Generic Flexi
  • New: Added functions to toggle user parameters between minimum and maximum value.
• Launchpad
  • Fixed: Tap tempo in Shift Mode did not work.
• Maschine Mk3 / Mikro Mk3
  • New: Channel and Polyaftertouch of the pads are now routed to Reaper.
• Push
  • Fixed: Device data on Info page was not displayed.

Enjoy!

[Biz92k]

Hi Moss, I saw that the Novation Launchkey mini mk3 is now supported. Any chanches that also the mk2 is going to work? Or it will need specific adaptations?

[shmuelyosef]

Before I dive into this, just wanted to verify whether the Beatstep PRO is supported with the <Beatstep> instance?

thanx, Jeff

[moss]

Originally Posted by Biz92k

Hi Moss, I saw that the Novation Launchkey mini mk3 is now supported. Any chanches that also the mk2 is going to work? Or it will need specific adaptations?

Sorry, the MkII is not supported. You can use the Generic Flexi to get the same functionality except the pads.

[moss]

Originally Posted by shmuelyosef

Before I dive into this, just wanted to verify whether the Beatstep PRO is supported with the <Beatstep> instance?

thanx, Jeff

No, it is not supported anymore because what you can program is even more limited (only white color on pads) than with the Beatstep.
But you can get the same functionality by using the Generic Flexi.

[mrdave45]

I've been playing around with various setups for my x touch. I was wondering why the driven by moss config page for mcu based devices only have 5 function keys? The mcu and icon qpro have 8 f keys and the xtouch one has 6.
Have I missed a setting somewhere. I've been searching around for a while and can't figure out how to make use of the other f keys. Thanks.

[eniwhite]

mrdave45: can you please verify if the vu meters of your x touch match with the vu meters of your DAW? In my case the x touch vu meters are too low.

Thanks!

[moss]

Originally Posted by mrdave45

I've been playing around with various setups for my x touch. I was wondering why the driven by moss config page for mcu based devices only have 5 function keys? The mcu and icon qpro have 8 f keys and the xtouch one has 6.
Have I missed a setting somewhere. I've been searching around for a while and can't figure out how to make use of the other f keys. Thanks.

F6 to F8 have fixed functions (see the manual). The reason is that I originally wrote this for the QCon Pro X with the Bitwig overlay.

[Tiggerdyret]

Hi Moss. Did you take a look at the problem with your script messing up the undo function in the Maschine plugin?

[moss]

Originally Posted by Tiggerdyret

Hi Moss. Did you take a look at the problem with your script messing up the undo function in the Maschine plugin?

Sorry, I overlooked that message being busy with the last release.
Could you please explain in more detail what you are doing? What do you mean "Undo in Maschine"?
Please give some steps to reproduce the issue.

[mrdave45]

Haven't checked the vu meters yet, I only really use them for an idea as they've only got 8 segments.

I've been mainly working on a template and figuring out which system to use. I seem to be having most luck with driven by moss.

Ive done work arounds using my largely unused machine controller which I'll probably replace with a more compact stream deck.

I've really been getting into the cycle actions with conditions etc.

The faders don't seem to behave quite as smoothly as with klinke, I could be imagining this though.

Currently I'm refreshing at 30hz.

[Tiggerdyret]

Originally Posted by moss

Sorry, I overlooked that message being busy with the last release.
Could you please explain in more detail what you are doing? What do you mean "Undo in Maschine"?
Please give some steps to reproduce the issue.

Sure, thanks man

This is my original post. There is a video link so you can see the bug in aciton. I think that is better than explaining:

"Hi Moss, I found bug with the Maschine software, when having Driven By Moss installed when using Launchpad X and the Maschine Plugin. When the driver is engaged the undo function in the Maschine plugin doesn't work at all and doesn't register any actions to the undo/redo list. When the project is playing undo still does works correctly, but once I hit stop the undo data gets erased. I have tried to uncheck and remove the MK3 from the Moss devices list, but the problem persists. Only removing the driver completely from the control surface list fixes it. But then I can't use my Launchpad with Moss functionality... And Moss functionality is awesome!

Here is the problem in action: https://www.youtube.com/watch?v=1_6RAspYRn8 "

[nickstomp]

Hi
Thanks for this driver!!!
anyone can help me to do the setup?
I have the x touch one and the bcf2000 from behringer
Is possible to use both at the same time?
How I need to configure it?

the x touch one in what mode should be? (mackie or reaper?)

Thanks

[cjewellstudios]

It's been a while since I commented.

Recently updated and very impressed with the improvements to the workflow of the Maschine Mikro!

Pressing the Pad Mode/Keyboard Mode buttons twice to bring up some configuration stuff is pretty awesome.

.....

I had a little idea while I was messing around.

We should have a mode for the touch strip to control the last touched parameter. Clicking on a parameter and then adjusting it with the touch strip would be a killer workflow!

[moss]

Originally Posted by nickstomp

Hi
Thanks for this driver!!!
anyone can help me to do the setup?
I have the x touch one and the bcf2000 from behringer
Is possible to use both at the same time?
How I need to configure it?

the x touch one in what mode should be? (mackie or reaper?)

Thanks

To setup the X-Touch One, see this video: https://www.youtube.com/watch?v=yLDLYiaIeFE (it is for Bitwig but works the same for Reaper)

You can combine up to 4 MCU devices with DrivenByMoss, but since the One has only 1 fader I guess that does not make much sense. Therefore, I suggest to use either the One or the BCF with Generic Flexi and learn some individual functions which are missing on the other device.

[moss]

Originally Posted by Tiggerdyret

Sure, thanks man

This is my original post. There is a video link so you can see the bug in aciton. I think that is better than explaining:

"Hi Moss, I found bug with the Maschine software, when having Driven By Moss installed when using Launchpad X and the Maschine Plugin. When the driver is engaged the undo function in the Maschine plugin doesn't work at all and doesn't register any actions to the undo/redo list. When the project is playing undo still does works correctly, but once I hit stop the undo data gets erased. I have tried to uncheck and remove the MK3 from the Moss devices list, but the problem persists. Only removing the driver completely from the control surface list fixes it. But then I can't use my Launchpad with Moss functionality... And Moss functionality is awesome!

I did some testing and to me it looks like an issue with the Maschine plugin. I tested it in Bitwig without controllers and it looses frequently its' Undo state. I could not find a real pattern but it seems to be related to starting / stopping playback from the host.

[moss]

DrivenByMoss 4 Reaper 11.5.2 is online!

Get it from http://www.mossgrabers.de

• Requires Reaper 6.12+
• APC40mkI/mkII
  • New: Press Stop Clip + Pad In Session Mode to delete the clip.
  • New: Press Select + Pad In Session Mode to duplicate the clip.
• Launchkey Mk3
  • New: Press Undo + Pad In Session Mode to delete the clip.
  • New: Scenes/Clips scroll now by 1 instead of 2, which is a bit less confusing.
• Launchpad
  • New: Temporary session mode: if any mode except session is active, hold the session button and then start a clip or scene. When the session button is released the previous mode is restored.
• Maschine
  • Fixed: Could not scroll browser results.
• MCU
  • New: The scaling of the VU meters is now in the range from -60 to +6dB like in the Reaper mixer display.

Enjoy!

[eniwhite]

Originally Posted by moss

[*]MCU

• New: The scaling of the VU meters is now in the range from -60 to +6dB like in the Reaper mixer display.

Thank you very much. I've already done testing and it works now correct.
Great work!

[moss]

Originally Posted by eniwhite

Thank you very much. I've already done testing and it works now correct.
Great work!

Good to hear! That caused me some serious headscratching :-)

[Tiggerdyret]

Originally Posted by moss

I did some testing and to me it looks like an issue with the Maschine plugin. I tested it in Bitwig without controllers and it looses frequently its' Undo state. I could not find a real pattern but it seems to be related to starting / stopping playback from the host.

Thanks for taking a look. Did you try without the Moss driver installed? The problem is only there when it is installed for me. Works like a charm as long as the driver is not active. If the problem is between Moss and Mashcine it would occur in Bitwig as well, right?

[Eufonic]

When i try to assign a custom action to F keys, the predefined ones work (ie: add audio track,add instrument track, add FX track) but when i choose a custom action it just starts recording on the selected track. What could it be ?
I'm using the latest update!

I'm using the MCU settings, replicable from the device simulator.

[wdamian]

Hi Moss, I hope you're doing fine

First of all, thank you very much for your work and for sharing with us.

I've just got a PreSonus FaderPort v2 2018 and during my research to make it work with Reaper, I first found Klinke's driver that mentions my controller. It works partially good, but many features missing.

Then I found yours that doesn't mention the FaderPort but since you had on your list the MCU protocol, I decided to test it.
It works very very well, it has more accurate and more features compared to Klinke's, but I see a couple of assignments that it would make it the Ultimate driver for this controller.

Unfortunately, I couldn't find access to the map so I could assign those simple features. Could you help me, please?

To give an exemple of how little assignments are missing :
- Bypass FX in one track (pressing Bypass);
- Bypass FX in All tracks (pressing Shift + Bypass);
- Jump to Next Marker (pressing Marker);
- Pan (turning the knob after the button Pan is active)
- Return to Zero (pressing Rewind and Fast Forward buttons simultaneously) actually this is assigned as pressing two times stop;

I really apreciate your attention and help to the community.
Have a good night!

DB

[moss]

Originally Posted by Eufonic

When i try to assign a custom action to F keys, the predefined ones work (ie: add audio track,add instrument track, add FX track) but when i choose a custom action it just starts recording on the selected track. What could it be ?
I'm using the latest update!

I'm using the MCU settings, replicable from the device simulator.

Can you please post a screenshot of your settings?

[gxray]

Hey moss, there's no "Sponsor" button your Github repo or way to donate to you linked from your site.

How can we donate to you?

[MCJ]

Hello Jürgen,

Thanks for your awesome work!

I was wondering about the following:
I’m using DrivenByMoss4Reaper with an MCU Pro surface, the option “select channel on fader touch” is set to Off, but when using the Master fader on the MCU, Reaper still selects the Master fader channel. Is there a way to circumvent that?

Thanks again,
Merlin.

[moss]

Originally Posted by gxray

Hey moss, there's no "Sponsor" button your Github repo or way to donate to you linked from your site.

How can we donate to you?

You simply don't ;-)
... or checkout my music and get an album: mossifier, Arilyn, Individual Totem

[moss]

Originally Posted by MCJ

Hello Jürgen,

Thanks for your awesome work!

I was wondering about the following:
I’m using DrivenByMoss4Reaper with an MCU Pro surface, the option “select channel on fader touch” is set to Off, but when using the Master fader on the MCU, Reaper still selects the Master fader channel. Is there a way to circumvent that?

Thanks again,
Merlin.

I guess that's not intended. Will look into it.

[moss]

Originally Posted by Tiggerdyret

Thanks for taking a look. Did you try without the Moss driver installed? The problem is only there when it is installed for me. Works like a charm as long as the driver is not active. If the problem is between Moss and Mashcine it would occur in Bitwig as well, right?

I tried in Bitwig without DrivenByMoss and had the issue. Furthermore, I have no idea what influence it should have on the internal Undo/Redo of Maschine.

[moss]

Originally Posted by Eufonic

When i try to assign a custom action to F keys, the predefined ones work (ie: add audio track,add instrument track, add FX track) but when i choose a custom action it just starts recording on the selected track. What could it be ?
I'm using the latest update!

I'm using the MCU settings, replicable from the device simulator.

Check that you have also selected "Action" from the F1 drop down list! It is not enough to select an action.

[moss]

Originally Posted by wdamian

Hi Moss, I hope you're doing fine

First of all, thank you very much for your work and for sharing with us.

I've just got a PreSonus FaderPort v2 2018 and during my research to make it work with Reaper, I first found Klinke's driver that mentions my controller. It works partially good, but many features missing.

Then I found yours that doesn't mention the FaderPort but since you had on your list the MCU protocol, I decided to test it.
It works very very well, it has more accurate and more features compared to Klinke's, but I see a couple of assignments that it would make it the Ultimate driver for this controller.

Unfortunately, I couldn't find access to the map so I could assign those simple features. Could you help me, please?

To give an exemple of how little assignments are missing :
- Bypass FX in one track (pressing Bypass);
- Bypass FX in All tracks (pressing Shift + Bypass);
- Jump to Next Marker (pressing Marker);
- Pan (turning the knob after the button Pan is active)
- Return to Zero (pressing Rewind and Fast Forward buttons simultaneously) actually this is assigned as pressing two times stop;

I really apreciate your attention and help to the community.
Have a good night!

DB

If you have one or more function keys (F1-F6) on the device you can assign any Reaper action to it.

[beowulf]

Hey all,

Trying my hand with this.. I am tired of using mouse to select sounds in any instrument.. and saw that my NI M32 with Komplete Kontrol should be able to use the scroll wheel/knob and such to select instruments, load them, etc.

So.. how do I use my M32 to control the instrument selection for a given track/instrument? Does it only work with NI instruments (I have Komplete 13 loaded).. or other VST plugins as well?

Not seeing how to set that up.

Also.. not sure why, but the play/stop work, Record does not.

[moss]

Originally Posted by beowulf

So.. how do I use my M32 to control the instrument selection for a given track/instrument? Does it only work with NI instruments (I have Komplete 13 loaded).. or other VST plugins as well?

Yes, that is the whole concept of the NI keyboards. They are specifically designed to work with the Komplete plugin, if you do not use it they are pretty useless. So, you can only use the browsing if a Komplete plugin is loaded on the channel.

Originally Posted by beowulf

Also.. not sure why, but the play/stop work, Record does not.

You can select the function of the record button in the settings. The default is "Record Clip" which simply does not have any meaning with Reaper. Select "Record Arranger" for the normal behaviour. "New clip" does also work.

[wdamian]

Originally Posted by moss

If you have one or more function keys (F1-F6) on the device you can assign any Reaper action to it.

I do have F1-F4 on the device and I'm using it for some extra functions.

What I meant on my example's list is that there's a specific button dedicated to those actions, I just wanted to make them work That's why I asked about the mapping, even though I'm not mega expert on that haha

I'm including an image of the device so is easier to see.

BTW I really enjoyed your Project Kite album! Your electronics with this 80s vibes are awesome! The Community of Boredom got repeated several times here! Thank you for mentioning on the other post!

[moss]

Originally Posted by wdamian

I do have F1-F4 on the device and I'm using it for some extra functions.

What I meant on my example's list is that there's a specific button dedicated to those actions, I just wanted to make them work That's why I asked about the mapping, even though I'm not mega expert on that haha

I'm including an image of the device so is easier to see.

I do not own any of the Presonus controllers, so I cannot specifically support them. I only know from several users that they make very "creative" use of the protocol, which means such functions are not on the original Mackie device.

Originally Posted by wdamian

BTW I really enjoyed your Project Kite album! Your electronics with this 80s vibes are awesome! The Community of Boredom got repeated several times here! Thank you for mentioning on the other post!

Glad you like it! This means a lot to me!

[Eufonic]

Originally Posted by moss

Check that you have also selected "Action" from the F1 drop down list! It is not enough to select an action.

I don't have an option for an action
https://drive.google.com/file/d/1_7e...ixYUcl3iy/view

here are my settings

https://drive.google.com/file/d/13DT...ew?usp=sharing

[Eufonic]

Originally Posted by Eufonic

I don't have an option for an action
https://drive.google.com/file/d/1_7e...ixYUcl3iy/view

here are my settings

https://drive.google.com/file/d/13DT...ew?usp=sharing

nevermind ) I didn't see I could scroll down, sorry )

[Tiggerdyret]

Originally Posted by moss

I tried in Bitwig without DrivenByMoss and had the issue. Furthermore, I have no idea what influence it should have on the internal Undo/Redo of Maschine.

Weird.. Could your Bitwig bug be different from what I'm experiencing in Reaper. My bug is 100% consistent. When Moss is active and Reaper is not playing all undo/redo states are deleted. When Reaper is playing the undo and redo is saved until hitting pause again. When Moss is removed from the driver list Maschine is working perfectly... For now I'll just remove the driver whenever I'm working with Maschine. It's not that hard to do, but I might mean using Moss for my live setup is out of the picture.

Again thanks for taking a look. This script is still amazing, so thanks for sharing and all the hard work you've put into it

[moss]

Originally Posted by Tiggerdyret

Weird.. Could your Bitwig bug be different from what I'm experiencing in Reaper. My bug is 100% consistent. When Moss is active and Reaper is not playing all undo/redo states are deleted. When Reaper is playing the undo and redo is saved until hitting pause again. When Moss is removed from the driver list Maschine is working perfectly... For now I'll just remove the driver whenever I'm working with Maschine. It's not that hard to do, but I might mean using Moss for my live setup is out of the picture.

Again thanks for taking a look. This script is still amazing, so thanks for sharing and all the hard work you've put into it

When you say, you can reproduce it 100%, could you please give the exact steps to do so?
1) ...
2) ...
...