Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
I thought about that, but then the wheel won’t work for someone else. Is there another way? I don’t want to sell patches, but I would like to add to the stock of instruments.
Great!
First of all, I'd rather use values like 1, 2, 3 on the buttons and scale the values down by a fixed factor using the Scale or Scale + Offset module.
Much easier to handle and understand.
Then, you can p-lock buttons. All you have to do is hold the last step and tap on the button of your choice to automatically push that button at that time. Then, at the beginning of the next pattern, hold the first step and tap the button twice to disable its value again (and make it ready for the next press).
A simple way to adjust the amount of modulation is to MIDI map the modwheel to an LFO's "Amount" knob.
Another, more flexible way is to place an Amp module in between the modulation path and control its Amp knob by the modwheel. It'll also give you a nice visual clue how the modwheel changes modulation depth.
I was trying out what @AppJunky is doing with buttons and used @rs2000 suggestion of setting the buttons to values 1,2,3… and then applying a scale factor. I started with a multiply module with a a value of 0.08 (1/127). Then tried with the scale module, which is indeed cleaner, just use 1/127 as the scale factor.
What I can’t understand is how the “S&H” module prevents a trigger when you choose multiple buttons… without s&h (connect the midi Cc generator to the scaler module) if you press buttons 1+2+3 you get Cc 6, which is expected. But with S&H only when value is changed FROM zero the value is triggered… why?.
Also for a pattern changing chain as this one… what would you use so that buttons are mutually exclusive (one at a time)?.. I know you could do this with a “switch N-1” or the like, but that means a more cluttered setup and a lot more modules and connections. Wouldn’t it be useful to have an “exclusive” mode where only 1 button could be selected at a time (like switch but easier)?
how would one go about running a clock to which Drambo is a follower to, in to a MIDI AU instance?
@tahiche Buttons can now have their own on-values, a very recent addition.
What I mean is giving button 1 value=1, button 2 value=2 and so on, then use Scale/Offset to "convert" the values into what the CC Generator expects: A value between 0 and 1 which will result in a MIDI value between 0 and 127.
You can give the buttons any name (Short name of the preset etc), it doesn't matter.
The only thing to be aware of is that when using the Adder, make sure only one button is active or the values will add up.
You're right, a radio button mode would be good and I've already voted for adding it later 👍🏼
The N-to-1 switch already has that behavior and you could use that as well, the problem is that you'd have to feed it a different constant number on each input - not a big deal but not as elegant.
@AppJunky This should do what you want.
Actually, you can collect those 4 modules into a Processor Rack. This is actually what I posted earlier, just adapted to delay the CV signal and trigger the S&H. The input to the Bar Start Delay rack is the Adder output, and the output is sent to the S&H trigger.
Edit: To see how this works, use a Scope to view the various signals, starting with the Adder output and the GM output.
I want to implement this sort of workflow inside Drambo:
Is all that possible within a single Drambo track, or would I have to send the NRPN out to the controller in e.g. Track 1, then listen for the response from the controller on e.g. Track 2?
@uncledave 👍🏼
@AppJunky Exciting stuff indeed! 😃
It should be ok in one track. Just make sure you don't create a MIDI loop. The outputs sent to the controller must be only those generated by the track. I assume you'll MIDI Learn those input messages to controls or parameter values in Drambo.
Is this a controller that you are engineering yourself? I ask because most complex controllers use SysEx messages to request this data, and the reply is another large SysEx message.
Finally, it might be easier to use a StreamByter script for this. It could absorb the data from the controller, make (possibly) complex decisions with it, and send straightforward CCs or Notes to Drambo.
I’ve been thinking about this.
I don’t have a Cirklon but what I have done is this….
I’ve put together a 16 step input sequencer Midi Rack
with faders for individual Pitch, Velocity and Gate length.
I have also made a 32 and 64 step version which I’m finishing off.
Basically from one instance of dRambo I can have 16 x 16 or 32 or 64 step sequencers
and when hosted as auv3 I can then multiple them upwards and combined with
some of the other modules I can change the speed or even have it running backwards.
My sequencers are rather basic.
dRambo’s inbuilt sequencer is far more eloquent.
Hi. Right. The second And input should be direct from the GM, not the Negate. Notice that GM and Negate are different colors in my pic, but the same in yours. Drambo makes them the same color when they're a chain, with output from the end, but different colors when the chain is broken. It needs to do that for the color-matched connection tags to make sense. Should work with that fixed.
@rs2000 @uncledave im still very curious about the S&H module in this case… Why isn’t it triggered when one button is already selected?.
Because you've previously added the values and you're using them as a trigger for S&H at the same time.
The trigger threshold is defined as a signal increase from zero (or below) to positive.
If another button is selected already, the zero level isn't reached anymore.
If you want to trigger the S&H anytime a switch value changes, you can pass the signal through a HPF and a Full Rectify module.
@AppJunky Your connections look correct, including the S&H, which is triggered by the Bar Delay, and samples the scale output. I used 16 steps for the GM, and took one for the pulse. So I had one 16th note for pulse duration, you have 2/64 or one 32nd note. Should make no difference.
Have you set the button values to 1,2,3, etc.?
Do the scope transients look correct?
Here are my scope shots. Cannot catch the rising edge of the button or the counter because the scope is too fast.
@AppJunky I don't think it was 16 steps vs 64, because I tried your steps with no problem.
Edit: I just looked at your plot again, and you had 2 ms smoothing. That should be 0 for uses like this, where we're not actually modulating an audio signal. That might have interfered with the shorter pulse you were using. If the peak never quite reached 1, the NEG would never be zero, so the counter woukd not reset.
Anyway, I'm glad it's working. The shape of the And output depends on when you hit the button. It'll be short if it's near the end of the bar.
Sorry, I'm not going to start testing ChordBud, or the synth you're hearing. Have you looked at the MIDI from CB to be sure the note offs are there? And what about the synth release time?
Thanks @uncledave.
I'm sending those messages from Drambo to a Linnstrument to get its tuning details (i.e. are the rows of pads configured to be 5, 6, 7 or 12 semitones apart?), then I want to act on that info when it comes back. The outgoing messages are a set of NRPNs (basically, for each of the 8 rows of pads, tell me the MIDI note corresponding to the leftmost pad), then the Linnstrument sends back (a row ID as CC#98 and the MIDI note ID for the leftmost pad in that row as CC#38) 8 times - one for each row of pads.
It works great when I send the "request" on one Drambo track, and process the "response" on another Drambo track. I'll try combining them into a single track tonight.
Glad you got it working!.
It seems like you’re using p-locks to deselect the buttons, right?. That is, select the button for the pattern you want and deselect the others… I believe that has to do with what I was asking about the S&H module. Have you tried @rs2000 advice so that you’d only need to p-lock the button you want?.