first of all, thank you for this incredible tool you've created. Chapeau. I've started to experiment with it alongside the manual. There is one thing i can't figure out by myself. Is there a way to tell which EFX/VSYNTH parameters are shown in the device and is it possible to change the naming? At the moment my SL49 MK3 populates automatically with all the parameters of the Vsynth on the track, sometimes in a strange order and sometimes with names that are too long. I am thinking of a system like NI Komplete, where i can choose which paramter is shown, and what name it should have. I tried it with the Komplete Wrapper, but with that it only shows the scale and arp parameters. I hope could make it clear what i am looking for and hope you can give me a hint into the right direction. all the best, Sebastian
I have a Behringer-X touch and I wanted to connect it via rtpMidi. I installed rtpMidid and was able to connect my control surfaces to my computer. I see in the QJackctl interface that both consoles are detected as ALSA midi ports. But in DBM these midi ports are not visible.
Perhaps I don’t understand something and am doing it wrong. Is there a possibility to make this work?
PS. My control surfaces work without problems over USB.
Sorry, no idea. I simply list the MIDI ports available to the system.
I've absolutely overseen this. Sorry. You are awesome! You prevent me from goin back to ableton, what makes me sooooo happy. Donation will follow. all the best, sebastian
Ok, then check also if all MIDI i/o for the device are deactivated in Reaper.
Yes, I've deactivated the device in Reaper's midi I/o
Quote:
Originally Posted by moss
This simply means that no device is selected from the controller on the current track (or there is no device).
Okay, I thought it could help troubleshooting my problem.
Quote:
Originally Posted by moss
What do you mean by "Midi is working"?
It means that when I press the piano keys on the S49, midi comes into Reaper.
I've disabled all midi I/o so DrivenByMoss is handling the midi input I guess?
But the transport buttons (or any other button) do not work.
Last edited by Nombra101; 07-25-2024 at 03:29 AM.
Reason: quotes were not in the right place
It means that when I press the piano keys on the S49, midi comes into Reaper.
I've disabled all midi I/o so DrivenByMoss is handling the midi input I guess?
But the transport buttons (or any other button) do not work.
Check if you flipped the two ports:
1. Select the MIDI input and output ending with "DAW" as the first channel.
2. Select the MIDI input and output without an ending as the second.
1. Select the MIDI input and output ending with "DAW" as the first channel.
2. Select the MIDI input and output without an ending as the second.
Thanks for all your help! It's not your software, it's me...
I thought I had a mk2 s49, but it's a mk1. Everything works now.
Sorry for all your trouble and keep up the good work!
Edit: Well, I thought everything worked. I can press play and stop on the transport of the s49 and Reaper responds. But when I press rwd or ffw, the edit cursor goes to the beginning of the session.
Did you change this behaviour? It used to back up a bit or fast forward a bit. Loved that feature during tracking.
Thanks for all your help! It's not your software, it's me...
I thought I had a mk2 s49, but it's a mk1. Everything works now.
Sorry for all your trouble and keep up the good work!
:-)
Quote:
Originally Posted by Nombra101
Edit: Well, I thought everything worked. I can press play and stop on the transport of the s49 and Reaper responds. But when I press rwd or ffw, the edit cursor goes to the beginning of the session.
Did you change this behaviour? It used to back up a bit or fast forward a bit. Loved that feature during tracking.
Works fine here. Could it be that you tested with an empty project?
Works fine here. Could it be that you tested with an empty project?
Yes, I tested it with an empty project. It works fine if the project has items in it.
So ashamed to have bothered you with unnecessary questions. It was all just me being stupid.
Again, thanks for your replies and your hard work on this great piece of software!
Not sure, if it's an user error. Starting Reaper, the display on my Novation SL49 MK3 shows "Master" and "Plerase select a track" on black, but doesn't react to any button. As soon as i select the master track, it shows up correctly, but still no button works. I have to start the config page with CTRL+SHIFT+J and disable and enable the controller. Then it starts working. I am telling this, because from the start it was irritating and i thought the scrip is broken. This is how to adress this beahviour.
1h later:
Just one more thing i see now. This only works, when i start a project from scratch. When i load an existing project, the novation can't be activated. All lights light up correctly, but no button can be pressed with function, even after disabling and reactivating the novation in the setup dialogue (CTRL+SHIFT+J) If i do it in a epmty/new project and use the workaround as described first and then load the other project everything works. It seems that Reaper talks to the Novation, but not the other way round. Any idea?
Last edited by schnudiesounds; 07-30-2024 at 11:31 PM.
Using launchpad Pro MK3 which I enjoy but would like a controller that shows more info about which parameter I am editing and which track I am on for example without having to constantly look at the computer. Between Push 1, Push 2, or Oxi one which would you recommend? Thank you!
Using launchpad Pro MK3 which I enjoy but would like a controller that shows more info about which parameter I am editing and which track I am on for example without having to constantly look at the computer. Between Push 1, Push 2, or Oxi one which would you recommend? Thank you!
Hi! I have the X-touch extender and in previous versions the extender tracks were colored according to the colors of the tracks in Reaper. With this latest version it stopped working and all the tracks look the same color on the extender.
Hi! I have the X-touch extender and in previous versions the extender tracks were colored according to the colors of the tracks in Reaper. With this latest version it stopped working and all the tracks look the same color on the extender.
Maybe it is in a wrong mode? Didn't change anything with that.
New: Added new setting 'Turn off scale pads'. If enabled, all pads which represent notes which are in-scale are switched off (instead of white).
New: Played chords are displayed in play modes.
Fire
New: The Shift Mode allows to pin the cursor track, cursor device and cursor clip (3 green buttons in the 2nd row from the top).
New: The Automation Write Mode can be selected in the Shift Mode (buttons of the 3rd row).
New: The initial pad brightness is now set to 20%.
New: Switched button combinations for changing the root note and changing the scale layout.
New: Toggling clip launcher/arranger automation gives now feedback in the display.
Generic Flexi
New: Functions can now be assigned to 10 different layers. With the 'Function Layers' functions each layer can be temporarily or permanently activated.
Maybe it is in a wrong mode? Didn't change anything with that.
Hi. I was doing some tests. I was using version 22.0 in which the track colors on the X-Touch Extender worked correctly. I have tried all subsequent versions. The latest version where this works correctly is 23.0.1. Already in 23.2.0 it stopped working.
New: Improved logging area. Errors are now printed in red.
New: After changing the settings of a controller, only this controller is restarted.
New: The controller can now be double clicked to open the setting dialog.
New: Switched setting of automation to global automation mode (instead of per track).
New: 'Toggle Cue Marker Visibility' triggers now the Reaper action 'Ruler: Display project regions/markers as gridlines in arrange view'.
New: 'Toggle Track Height' triggers now the Reaper action 'View: Cycle track zoom between minimum, default, and maximum height (limit to 100%)'.
Fixed: The controller specific project settings were not restored when a project was auto-loaded on Reaper startup.
Fixed: Fixed some issues related to the controller listbox.
Fixed: There were several startup issues when the extension was initiated for the 1st time and the Reaper configuration dialogs were not closed before making changes in the DrivenByMoss window. The user interface is now blocked until the dialogs are closed. Additionally, some measure are now taken to fix broken configuration files.
All devices
New: When scrolling track bank page left the 1st instead of the last track of the new page is selected.
New: Added option to disable showing played chords.
New: Renamed setting *Default note view
to *Startup view*.
Fire
New: The Shift mode is not activated when ALT is already pressed.
Fixed: Slow knob mode got stuck when pressing SHIFT a second time.
Launchpad
New: The bird's eye view in session mode is now closed automatically if the Session button is kept pressed.
New: In Project/Track params mode the scene buttons do now select the pages 1-8 (instead of blocks of 8 pages).
Fixed: Extension crashed when pressing one of the cursor keys in clip loop edit view.
Fixed: Shift mode should not be activated when used in combination with cursor keys in session mode.
Maschine, OXI One
New: Added new setting 'Startup view' which allows to auto-select the preferred view on startup.
MCU
New: Keep the Option button pressed to show the parameter pages of the selected device. Press the respective knob to select the page for editing.
New: Device mode shows number of available pages on 2nd display.
Push 1
New: Notification messages which are shorter than 18 characters are now shown in the right upper corner of the display instead of clearing the whole display.
Oh wow, I could never get this to work, thanks for the video!
I have a couple more questions...
1. It only seems to match the parameters to the knobs on the P1-X. Can it do knobs, knob press, and faders?
2. Even though my controller is "Mackie MCU - Control Universal + 2 Extenders" it only displays 8 parameters at a time on the 1st device. Can it utilize all three devices?
3. If it can't utilize all three devices at the same time, can I tell it which device to display on?
Oh wow, I could never get this to work, thanks for the video!
I have a couple more questions...
1. It only seems to match the parameters to the knobs on the P1-X. Can it do knobs, knob press, and faders?
No. If you want to create a very individual setup you better choose another solution.
Quote:
Originally Posted by TheFancyWolf
2. Even though my controller is "Mackie MCU - Control Universal + 2 Extenders" it only displays 8 parameters at a time on the 1st device. Can it utilize all three devices?
Currently, not for several reasons. I might have a solution for it in the future but it is tricky and no fun at all to implement ;-)
Quote:
Originally Posted by TheFancyWolf
3. If it can't utilize all three devices at the same time, can I tell it which device to display on?
I'm using 24.3 with my QCon G2 and the latest Reaper for MAC. Now when I hit "play" all the channel faders move to the central null TRIM position. If I touch a fader the level of the track adjusts to the fader position as if it were not in Trim mode. Only when I move through the banks first do the faders move to reflect the actual level of the channel. Any way to prevent this happening please? Thank you for all your fine work!
I'm using 24.3 with my QCon G2 and the latest Reaper for MAC. Now when I hit "play" all the channel faders move to the central null TRIM position. If I touch a fader the level of the track adjusts to the fader position as if it were not in Trim mode. Only when I move through the banks first do the faders move to reflect the actual level of the channel. Any way to prevent this happening please? Thank you for all your fine work!
Best
Simon
Sorry, no real idea. Could it be that "flip" is active and it is set to control parameters?
New: The horizontal scrolling in the arranger is now adaptive to the zoom factor! Furthermore, in slow-mode (normally if combined with the SHIFT button) snap to grid is ignored.
New: Switched to getting available plugins from Reaper API instead of parsing configuration files.
New: Several well known plug-ins are now categorized
New: A plugin is now automatically selected when selected in Reaper but only if the track is selected (if the track would be auto-selected, it would get stuck and no other track could be selected. I tried it).
New: A clip is now indicated as playing when the play cursor is in the range of the region marker with the same index as the clip and playback is active.
New: A slot is now indicated as recording when the play cursor is in the range of the region marker with the same index as the slot and the track is armed.
New: Updated to JDK 21.
Fire
New: Added setting 'Color all track states (mute, solo, rec arm)' which allows to switch off the colors for the deactivated states in Mix mode.
New: Press Alt+Select knob to toggle the on/off state of the current device.
Since a longer while I got an error message on my Windows7 machine (which is not connected to the internet). It was working before. Can't say what I have changed. Today I try the newest version, but no difference.
It's working on my Linux machine, so I guess it's a damaged/missing windows file. Any idea what I can try? Thanks in advance.
I cannot get the DrivenByMossReaper-24.4.0-Windows version to work.
It's getting a message similar to what another user wrote.
Initialized.
Loading device INI files...
Could not load device INI files: Input length = 1
Loading device INI files...
Could not load device INI files: Input length = 1
When I attempt to check the config it will not allow any devices to be detected or added (options are greyed out).
Everything works fine when I revert back to version 23.2.1. (deleting all the User Plugin files and replacing them).
I'm on Windows 10. Any thoughts as to what might cause the issue?
Since a longer while I got an error message on my Windows7 machine (which is not connected to the internet). It was working before. Can't say what I have changed. Today I try the newest version, but no difference.
It's working on my Linux machine, so I guess it's a damaged/missing windows file. Any idea what I can try? Thanks in advance.
I cannot get the DrivenByMossReaper-24.4.0-Windows version to work.
It's getting a message similar to what another user wrote.
Initialized.
Loading device INI files...
Could not load device INI files: Input length = 1
Loading device INI files...
Could not load device INI files: Input length = 1
When I attempt to check the config it will not allow any devices to be detected or added (options are greyed out).
Everything works fine when I revert back to version 23.2.1. (deleting all the User Plugin files and replacing them).
I'm on Windows 10. Any thoughts as to what might cause the issue?
Thanks
Ryan
Must be a mixup of the new and old version, since this error message does not exist anymore in the latest release.
Linear Mode
