That's how note repeat is implemented! It facilitates a MIDI Arp which is inserted in the input FX...
Maybe that is why your note repeat length is not working because you tinkered with the settings?!
Ah haha, I had no idea... I didn't mess with any of the settings, though. Still experiencing that glitchy skipping! haha. Thanks again for all your hard work, Jurgen! I stupidly didn't know that JS effect was the Note Repeat. Just never looked at my laptop that deeply, only at Push 2.
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Last edited by themixtape; 03-27-2020 at 03:24 PM.
These warnings can be ignored. It just means you have not configured Folders in the device dialog.
On some platforms sometime the Reaper configure dialog blocks the DrivenByMoss configuration dialog. Try to close the dialogs in the background. You can also assign a key command to the DrivenByMoss configuration dialog.
Thanks Moss, worked a treat.
Question: Is there a way to set values to scalar float? (0.0-1.0)
It is Shift+New but I noticed that it did also activate record. Will be fixed in the next update!
Cool! Awesome.
I am messing with the sequencers. I think they could be one of the most powerful parts of Push 2 and your software.
Reporting back:
Hit note. When hitting the layout button, it cycles between seq types. It skips Poly Seq.
Raindrop is kind of unpredictable. If I hit a pad twice, some notes remove last written notes (intended), some of them not. I noticed it is related to the fact that the pattern could have only one visible note. It won't remove it if that is the case.
Raindrop undo deletes note per note. I suggest undo to delete the whole bunch of notes it wrote (useful in a long clip)
The clip section selection pads work really awkwardly. If I hit the last lit pad twice, it deletes the clip and places it in the next bar...
I also find awkward that, in the play, piano, seq, etc menu, it goes immediately to Device/Mix/Browse/Clip menu. It is probably for speed but actually increased the number of button presses for me since sometimes you would use both play and sequence interchangeably.
I am getting: Crash during flush. java.lang.ArrayIndexOutOfBoundsException Do not know if it is related to the behavior above.
I am getting a lot of color palette complaining messages. Colors work, tho.
I am attaching a log of the session where I recorded this videos.
Hi Moss, "Disable saving full plug-in state" --> Ticking this option also make reaper stable and no lag. So I believe we found the problem of this lag. Do you think can you fix it now?
In push 2 and probably other 64 pad controllers, the Drum 64 mode is really useful (especially with MPS RS5K script) However, I have recurring mapping issues if the different software (eg: Geist) expects a different layout.
Having this in mind and also the fact that the various drum plugins expect chromatic notes coming in a certain order:
Being the natural pad naming like this: (and what most plugins are expecting)
Hit note. When hitting the layout button, it cycles between seq types. It skips Poly Seq.
This is depending on the clip length and I guess it could be to get weird results.
Quote:
Originally Posted by barbaroja
The clip section selection pads work really awkwardly. If I hit the last lit pad twice, it deletes the clip and places it in the next bar...
Hmm, yes. Reaper is not really clip based as Bitwig.
Quote:
Originally Posted by barbaroja
I also find awkward that, in the play, piano, seq, etc menu, it goes immediately to Device/Mix/Browse/Clip menu. It is probably for speed but actually increased the number of button presses for me since sometimes you would use both play and sequence interchangeably.
Sorry, do not understand what you mean.
Quote:
Originally Posted by barbaroja
I am getting: Crash during flush. java.lang.ArrayIndexOutOfBoundsException Do not know if it is related to the behavior above.
Thanks, fixed!
Quote:
Originally Posted by barbaroja
I am getting a lot of color palette complaining messages. Colors work, tho.
You can ignore them, the Push sometimes behaves a bit stubborn in accepting the color messages.
Hi Moss, "Disable saving full plug-in state" --> Ticking this option also make reaper stable and no lag. So I believe we found the problem of this lag. Do you think can you fix it now?
Not sure what you mean. As several people confirmed in that thread it is fixed since 8.92.
In push 2 and probably other 64 pad controllers, the Drum 64 mode is really useful (especially with MPS RS5K script) However, I have recurring mapping issues if the different software (eg: Geist) expects a different layout.
Having this in mind and also the fact that the various drum plugins expect chromatic notes coming in a certain order:
Being the natural pad naming like this: (and what most plugins are expecting)
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Oh my, cannot tell you how much I hate dealing with pad layouts :-)
First one is already possible if you use Play mode and turn on chromatic.
Haha, the good thing is that you only deal with them once and they are good to go.
I tried in drum64 mode, piano, play, chromatic, non-chromatic... none of them worked.
Another HUGE feature would be some way to change the channel on the controller while retaining layout. Vey very useful when laying down multi-channel instruments. I tried everything and did not find a way to do it. I know in the config dialog you can but it completely breaks the workflow. This should work on a per-track basis, ie: The plugin remembers the channel you are working in each track, as it remembers let's say piano, drum64 or whatever you set it in.
Any ideas on the raindrop issue and the clip selection pads?
it completely breaks the workflow. This should work on a per-track basis, ie: The plugin remembers the channel you are working in each track, as it remembers let's say piano, drum64 or whatever you set it in.
It already works that way (that the track remembers the selected layout). Just tried it and it works fine for me.
Quote:
Originally Posted by barbaroja
Any ideas on the raindrop issue
I am afraid I cannot fix this.
Quote:
Originally Posted by barbaroja
and the clip selection pads?
What was that again?
Quote:
Originally Posted by barbaroja
I detected an issue with the pad gain control:
Cannot reproduce that. Did you change the knob speed ("Knob speed normal")? Mine is set to 10.
Cannot reproduce that. Did you change the knob speed ("Knob speed normal")? Mine is set to 10.
10 Here as well.
I checked out the new automation options and I find each time you hit the automate button, it comes back to read every time, (not trim which is the default mode). Could it be that it comes back to the previous mode? or at least the default track mode or trim?
I checked out the new automation options and I find each time you hit the automate button, it comes back to read every time, (not trim which is the default mode). Could it be that it comes back to the previous mode? or at least the default track mode or trim?
It already works that way (that the track remembers the selected layout). Just tried it and it works fine for me.
I am afraid I cannot fix this.
What was that again?
Cannot reproduce that. Did you change the knob speed ("Knob speed normal")? Mine is set to 10.
Quote:
Originally Posted by moss
I am afraid that is also a limitation.
Hm, then I have no idea.
Will check. Trim should be possible.
Ok. Another idea I have is having bidirectional communication for the scales between controller and reaper. Like if a midi clip has a scale set on the midi editor, push2 will read that and set the scale accordingly. If you change it in push, then reaper gets that in the midi clip. Cool, huh?
Hi
First, I want to say thanks for this great project.
Are there any plans on adding support to Novation LC XL?
I found the Mackie HUI which actually covers most of the XL's functionality (thanks again!).
What I found missing were two things:
a. support for the two upper knob rows
b. Feedback to the Buttons' LEDS. For example, when choosing Arm/record for a specific track it wouldn't change the color or light it stronger. That's how it works in Ableton (which is the "native" app for LC XL). It's the same with "Solo" and "Mute".
BTW, one exception is the Master track: If you choose Mute or Solo it does brighten the button color. Yet, it always does it on the most left button, regardless of what track this channel represent.
Hi
First, I want to say thanks for this great project.
Are there any plans on adding support to Novation LC XL?
I found the Mackie HUI which actually covers most of the XL's functionality (thanks again!).
What I found missing were two things:
a. support for the two upper knob rows
b. Feedback to the Buttons' LEDS. For example, when choosing Arm/record for a specific track it wouldn't change the color or light it stronger. That's how it works in Ableton (which is the "native" app for LC XL). It's the same with "Solo" and "Mute".
BTW, one exception is the Master track: If you choose Mute or Solo it does brighten the button color. Yet, it always does it on the most left button, regardless of what track this channel represent.
Hmmm, just remembered one more thing regarding the device "required" behaviour:
Buttons should light only if a corresponding track exists. e.g. if only 6 tracks exist, buttons in positions 7-8 should be off.
Thanks
Joe
The issue I'm having with the Java Virtual Machine is attached. When I press configure, nothing happens - the interface doesn't show up. Any idea what the issue might be? I installed the same way I always do. It's my first time trying it on this particular computer but I've installed it the same way on another computer using an older version and it worked fine.
The issue I'm having with the Java Virtual Machine is attached. When I press configure, nothing happens - the interface doesn't show up. Any idea what the issue might be? I installed the same way I always do. It's my first time trying it on this particular computer but I've installed it the same way on another computer using an older version and it worked fine.
Not using 8.92 are you? That was a huge problem with it. 8.94 is solid, thus far.
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
Are there any plans on adding support to Novation LC XL?
I found the Mackie HUI which actually covers most of the XL's functionality (thanks again!).
It's a nice device but don't have it, so no there won't be specific support.
Quote:
Originally Posted by Joebox
What I found missing were two things:
a. support for the two upper knob rows
I only have some devices with a very rudimentary HUI protocol (also do not have the original). So, there is definitively stuff missing.
You could give the Generic Flexi a look, should give you more options to configure your device.
Quote:
Originally Posted by Joebox
b. Feedback to the Buttons' LEDS. For example, when choosing Arm/record for a specific track it wouldn't change the color or light it stronger. That's how it works in Ableton (which is the "native" app for LC XL). It's the same with "Solo" and "Mute".
Hmm, sorry cannot spot an error.
Quote:
Originally Posted by Joebox
BTW, one exception is the Master track: If you choose Mute or Solo it does brighten the button color. Yet, it always does it on the most left button, regardless of what track this channel represent.
Since there are no dedicated buttons for the Mute/Solo on the master track, this can only happen if it is "visible" on the last page of the track bank. I tried that and it lights the buttons correctly. I guess you tested with no other track present which then lights the first one since this is the master track in that case.
You could give the Generic Flexi a look, should give you more options to configure your device.
I would love to check Generic Flexi. It looks very customizable, however, I got lost over there. Is there any document/video/anything explaining it?
Also, is it possible to enable it in parallel with the HUI controller, both using the same MIDI input/output?
Quote:
Originally Posted by moss
Since there are no dedicated buttons for the Mute/Solo on the master track, this can only happen if it is "visible" on the last page of the track bank. I tried that and it lights the buttons correctly. I guess you tested with no other track present which then lights the first one since this is the master track in that case.
No, I checked it with several tracks. The behaviour looks like that:
Added 3 tracks. Therefore, the 4th position became Master.
all controls in the 4th column (volume fader, Pan knob, arm, solo, mute) work fine, controlling the master. Only the feedback not shown in the 4th- the LED changes color in the 1st column...
Are you planning to implement the functionality of A|B buttons on APC40Mk2? It would be great to control different tracks by setting them to A or B. Are you considering ableton-like option to override default mapping (panorama/send knobs) in the future?
I would love to check Generic Flexi. It looks very customizable, however, I got lost over there. Is there any document/video/anything explaining it?
Also, is it possible to enable it in parallel with the HUI controller, both using the same MIDI input/output?
No, I checked it with several tracks. The behaviour looks like that:
Added 3 tracks. Therefore, the 4th position became Master.
all controls in the 4th column (volume fader, Pan knob, arm, solo, mute) work fine, controlling the master. Only the feedback not shown in the 4th- the LED changes color in the 1st column...
Hi,
Are you planning to implement the functionality of A|B buttons on APC40Mk2? It would be great to control different tracks by setting them to A or B. Are you considering ableton-like option to override default mapping (panorama/send knobs) in the future?
It is like that on Bitwig, but how should that work with Reaper? There is no A/B state.
Nothing changed after overwriting previous 8.94 with v8.95 (including this "Fixed: DO not light LEDs for non-existing tracks").
Only after deleting all (relevant) files and folders under UserPlugins and re-install changes took place. (BTW, is it the common practice?)
And now, the funniest thing happened:
Now, almost everything works perfectly including the LED feedbacks- for each channel and for the Master!
The only thing DOESN'T work is the fix you did ( DO not light LEDs for non-existing tracks)...
Nothing changed after overwriting previous 8.94 with v8.95 (including this "Fixed: DO not light LEDs for non-existing tracks").
Only after deleting all (relevant) files and folders under UserPlugins and re-install changes took place. (BTW, is it the common practice?)
And now, the funniest thing happened:
Now, almost everything works perfectly including the LED feedbacks- for each channel and for the Master!
The only thing DOESN'T work is the fix you did ( DO not light LEDs for non-existing tracks)...
Never copy it over! Otherwise you have different version of files and you get random effects depending on which one is picked up first...
Can you tell me which LEDs do not work? I tested also in the simulator and it works fine, maybe you can compare with that too (Debug button -> Simulator).
thank you for this great job!
I have an issue with you're "driver" with mac os 10.12.6+ MCU pro + reaper 6 : When i select touch mode on a track ( with every kind of automations volume etc) and move a fader or o knob, the curve constantly make shorts peaks. I try to attach an Screen shot to explain that. If i use latch mode i haven't this issue.
If i use the generic driver for MCU control, i don't have any issu with the touch mode.
Never copy it over! Otherwise you have different version of files and you get random effects depending on which one is picked up first...
Can you tell me which LEDs do not work? I tested also in the simulator and it works fine, maybe you can compare with that too (Debug button -> Simulator).
As I said, it works well now: the channel LEDs changes color/brightness when choosing solo/mute/arm for every channel. The feedback for the master is also lighting at the correct channel (which is dynamic). Great!
What doesn't work: still, all LEDs are working, even for non-existing channels.
Another thing I noticed is that the "Send a/b/c/..." is toggled by the "Device" button
whilst it should be done (at least in LC XL) by Send up/down (two buttons).
If this helps- the Send up = CC 104 and Send Down = CC 105.
I'm having trouble installing this on OSX 10.13.6. REAPER v6.07/64
This is a mid 2010 Macbook Pro that has been repaired after being out of commission for 4-5 years. I've upgraded the the OS, however there is still a bunch of outdated and legacy software installed.
I'n not very savvy so not sure what I'm doing wrong. I followed the instructions in the .zip. I didn't have the REAPER/userplugins folder so I created it. I can see DBM4R in the control surface menu. I also tried following the installation youtube video, but after editing the info.plist, Reaper wouldn't start, so I restored that file back to the original.
My JAVA HOME path is: /Library/Application Support/REAPER/UserPlugins/java-runtime
When I open the configure pane this is what I'm getting:
Loading device INI files from /Users/ryanbertolami/Library/Application Support/REAPER ...
/Users/ryanbertolami/Library/Application Support/REAPER/reaper-fxfolders.ini not present, skipped loading.
Mackie MCU - Control Universal: Starting...
Mackie MCU - Control Universal: Running.
Invalid MIDI data.
javax.sound.midi.InvalidMidiDataException: data1 out of range: -15
at java.desktop/javax.sound.midi.ShortMessage.setMessage(Unknown Source)
at java.desktop/javax.sound.midi.ShortMessage.<init>(Unknown Source)
at de.mossgrabers.reaper.framework.midi.MidiConnectio n.createShortMessage(MidiConnection.java:294)
at de.mossgrabers.reaper.framework.midi.MidiConnectio n.sendRaw(MidiConnection.java:218)
at de.mossgrabers.reaper.framework.midi.MidiOutputImp l.sendMidiShort(MidiOutputImpl.java:51)
at de.mossgrabers.framework.daw.midi.AbstractMidiOutp utImpl.sendChannelAftertouch(AbstractMidiOutputImp l.java:74)
at de.mossgrabers.controller.mcu.MCUControllerSetup.u pdateVUandFaders(MCUControllerSetup.java:720)
at de.mossgrabers.controller.mcu.MCUControllerSetup.l ambda$flush$0(MCUControllerSetup.java:183)
at java.base/java.util.ArrayList.forEach(Unknown Source)
at de.mossgrabers.controller.mcu.MCUControllerSetup.f lush(MCUControllerSetup.java:175)
at de.mossgrabers.reaper.controller.AbstractControlle rInstance.flush(AbstractControllerInstance.java:19 5)
at java.base/java.util.ArrayList.forEach(Unknown Source)
at de.mossgrabers.reaper.controller.ControllerInstanc eManager.flushAll(ControllerInstanceManager.java:1 86)
at de.mossgrabers.reaper.MainApp.flushToController(Ma inApp.java:247)
at de.mossgrabers.reaper.MainApp.lambda$new$1(MainApp .java:90)
at java.desktop/javax.swing.Timer.fireActionPerformed(Unknown Source)
at java.desktop/javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.desktop/java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Unknow n Source)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessI mpl.doIntersectionPrivilege(Unknown Source)
at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilter s(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(U nknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarch y(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)
Invalid MIDI data.
javax.sound.midi.InvalidMidiDataException: data1 out of range: -15
at java.desktop/javax.sound.midi.ShortMessage.setMessage(Unknown Source)
at java.desktop/javax.sound.midi.ShortMessage.<init>(Unknown Source)
at de.mossgrabers.reaper.framework.midi.MidiConnectio n.createShortMessage(MidiConnection.java:294)
at de.mossgrabers.reaper.framework.midi.MidiConnectio n.sendRaw(MidiConnection.java:218)
at de.mossgrabers.reaper.framework.midi.MidiOutputImp l.sendMidiShort(MidiOutputImpl.java:51)
at de.mossgrabers.framework.daw.midi.AbstractMidiOutp utImpl.sendChannelAftertouch(AbstractMidiOutputImp l.java:66)
at de.mossgrabers.controller.mcu.MCUControllerSetup.u pdateVUandFaders(MCUControllerSetup.java:697)
at de.mossgrabers.controller.mcu.MCUControllerSetup.l ambda$flush$0(MCUControllerSetup.java:183)
at java.base/java.util.ArrayList.forEach(Unknown Source)
at de.mossgrabers.controller.mcu.MCUControllerSetup.f lush(MCUControllerSetup.java:175)
at de.mossgrabers.reaper.controller.AbstractControlle rInstance.flush(AbstractControllerInstance.java:19 5)
at java.base/java.util.ArrayList.forEach(Unknown Source)
at de.mossgrabers.reaper.controller.ControllerInstanc eManager.flushAll(ControllerInstanceManager.java:1 86)
at de.mossgrabers.reaper.MainApp.flushToController(Ma inApp.java:247)
at de.mossgrabers.reaper.MainApp.lambda$new$1(MainApp .java:90)
at java.desktop/javax.swing.Timer.fireActionPerformed(Unknown Source)
at java.desktop/javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.desktop/java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Unknow n Source)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessI mpl.doIntersectionPrivilege(Unknown Source)
at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilter s(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(U nknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarch y(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)
New: Added option to send the LED value even when command is received from the device.
Komplete Kontrol Mk 1
Fixed: Modulation wheel did trigger button press of the main encoder
Komplete Kontrol Mk 2
Fixed: Simulator view did not work
Launchpad
New: Poly Sequencer: Currently played sequencer notes are also lit on the play area
Fixed: Note mode menu could not be called up from any drum mode
Fixed: Fixed a crash in Raindrop sequencer
Mackie HUI:
Fixed: New command could not be triggered from footswitch
Fixed: Simulator GUI did not work
Fixed: DO not light LEDs for non-existing tracks
Push 1/2
New: Poly Sequencer: Currently played sequencer notes are also lit on the play area
New: When Automation is turned off it is set to Trim/Read instead of Read.
Fixed: Shift+New did also activate Record but should not
Fixed: Fixed a crash in Raindrop sequencer
Fixed: Push 2: Clip Mode in midi grid layout did not show the notes
Enjoy!
Love it. Thanks, Jurgen! Slightly weird behavior (not a big deal as I rarely use it) but Clip View when using the Raindrop Sequencer is a bunch of garbled stuff on the display... a bit strange, but not a big deal.
No lag with anything at all. The Note Length with Note Repeat still skips over 1/16 and 1/32, but no big deal. Everything else is working great. Thanks again for all your hard work!
__________________
FREE copyright-safe/DMCA-safe music for Twitch/Kick streamers, classrooms, waiting rooms (playlists on all streaming platforms): https://tinyurl.com/copyrightsafemusic
thank you for this great job!
I have an issue with you're "driver" with mac os 10.12.6+ MCU pro + reaper 6 : When i select touch mode on a track ( with every kind of automations volume etc) and move a fader or o knob, the curve constantly make shorts peaks. I try to attach an Screen shot to explain that. If i use latch mode i haven't this issue.
If i use the generic driver for MCU control, i don't have any issu with the touch mode.
G
I can reproduce that but sadly have no idea what to do about it. The code is the same as with the other modes, just that it is a different mode.
As I said, it works well now: the channel LEDs changes color/brightness when choosing solo/mute/arm for every channel. The feedback for the master is also lighting at the correct channel (which is dynamic). Great!
What doesn't work: still, all LEDs are working, even for non-existing channels.
Another thing I noticed is that the "Send a/b/c/..." is toggled by the "Device" button
whilst it should be done (at least in LC XL) by Send up/down (two buttons).
If this helps- the Send up = CC 104 and Send Down = CC 105.
Could it be that the colors are toggled by the device itself? Did you compare with the simulator?
I'n not very savvy so not sure what I'm doing wrong. I followed the instructions in the .zip. I didn't have the REAPER/userplugins folder so I created it. I can see DBM4R in the control surface menu. I also tried following the installation youtube video, but after editing the info.plist, Reaper wouldn't start, so I restored that file back to the original.