Rompler for OB-Xd (v0.9)
Script to select and send patches to OB-Xd via CC Midi
– first knob selects a bank. Second knob pages through patches.
– touch a pad to send its patch to OB-Xd on channel 1
– can also send Midi bank select (CC#0) and PC messages to Mozaic plugin
Setup in AUM (required):
– unzip (e.g. in AudioShare)
– load the Mozaic scripts into standalone Mozaic
– use the provided AUM preset that exposes OB-Xd parameters via CC.
– insert one of the Mozaic presets to the Midi lane.
– link Midi from Mozaic into Midi-Control with: [hamburger] – MIDI CTRL.
– connect a source of notes to OB-Xd (can route through Mozaic also)
Notes:
– Sorry, no preset saving (unless you edit it into Mozaic code)
– Also, Mozaic script size limit does not permit to include all banks,
thus patches are divided in several volumes.
– For the OB-Xd AUv3 to receive a patch, its exposed parameters use:
CC1, CC2, … CC70 in this order (except for using CC71 instead of CC7).
– src.zip contains patch sources and a Groovy script to extract them from *.fxb banks.
– It appears that AB / apeMatrix are not as straightforward to set up as AUM.
Please do share if / how you get those to work, when you do!
Script based on Gnu-licensed programs.
This work is not affiliated with, nor constitutes an endorsement of the iOS app.
I have followed the instructions and something is wrong. I also sent Mozaic into a MIDI Monitor and do not see any MIDI events from Mozaic when hitting a patch pad.
Any advice?
I was able to get the patches loaded and working with all five sets of preset banks. At times I would get a clicking sound rather than what I would expect the patch to sound like based upon its description so it seems like there are still some glitches with the script. I could frequently work around these glitches by selecting other patches and then selecting the one I wanted. Pausing the MIDI note input into OB-Xd can help to reduce preset loading glitches. Some of the presets might just be broken? I don’t know if routing the notes MIDI messages directly to OB-Xd directly rather than having it passed through the Mozaic script would help?
In general a very useful script that provides a great number of wonderful presets available to you at the touch of a pad despite some glitches. Lots of great work in this script.
Thanks @Paulinko!
I now figured out the patch problem – the Loudness Attack value was also sent to the Loudness Delay in the AUM preset. If you have downloaded Rompler v0.9 you can fix this quickly as follows in AUM:
open: [Hamburger] -> MIDI CTRL -> 1:OB-Xd -> Parameters -> LoudnessDecay
change: to
This should address most of the problems with the patches (a small number still produce no sound).
@McD – you should see a bunch of CC events for Channel1. However, these need to be routed into “MIDI Control / BUILT-IN” in the AUM Midi-Matrix in order to control the OB-Xd plugin, and not to the OB-Xd itself.
The most important part of the fix got swallowed:
on _LoudnessDecay_ change *CC17* to *CC18*
Tom6502:
Thanks.
MIDI Spy must not have been configured to display CC’s. I’ll check to see how it functions with CC
events.
Then I suppose I also need to change the CC17 to CC18 as well.
UPDATE: I added the CC17 to CC18 change and figured out why I didn’t see any CC’s. I wasn’t using enough Velocity on the PAD to trigger the sending of Patches. All is well for me now. Lowering the threshold for in pad velocity would help… just touch the pad should be enough.
Tom6502:
UPDATE: I added the CC17 to CC18 change and figured out why I didn’t see any CC’s. I wasn’t using enough Velocity on the PAD to trigger the sending of Patches. All is well for me now. Lowering the threshold for in pad velocity would help… just touch the pad should be enough.
This is only working sporadically for me. Is it still working for folks?