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.
Atom/Helium sustain question
I have a digistix setup with a drum kit. On the drum kit i have a cymbal crash, and when i hit the pad it resonates for a good while, as it should. However when i sequence a drum pattern in either atom or helium, it cuts off the trail of it really quick. I originally have it as one note in a 4 bar pattern, so my hope is it would resonate throughout most of it. I even tried dragging the cymbal note across the whole 4 bars. It still cuts off. Does anyone know how to remedy this?
Comments
It sounds like you may have the pad for the cymbal crash not configured for One Shot. I tried using the cymbal crash from one of the built-in kits, and triggered it from Helium along with some other sounds, which would overlap the tail, and it still rings out. In Digistix 2, if you tap, hold very briefly, than swipe up on the pad for the Cymbal Crash you are using, Digistix 2 will bring up a dialog box with several options for how the pad operates. On the upper right, there is a knob called "Length" and it if is set to 100%, which is the default, it will show "One Shot." That should ensure that the sample does not get cut off. If that's not it, then the only possibility I can think of from within Digistix 2 that would cause this is if there is a Mute Group configured, which would override that.
Thank you. That pad is set with Length at 100
I do notice that when it plays the cymbal note, as soon as it hits bar 2, thats where it cuts off. That makes me think its something with Atom piano roll 2 that im missing
So heres something new. In Atom, I duplicated this pattern ive been talking about, which has a kick, a snare and a hat. When I removed the snare notes, the cymbal doesnt get cut off. I am not sure what is going on. The drums are showing up starting at C3 on up 16 notes, with the cymbal being on the 16th note, which is a D#4. The snare is on C#3, kick is on C3 and the hats are on D3. If I put the snare on F3, the cymbal doesnt get cut off. So only when I have my snare on C#3.
This really sounds like a mute group issue. Mute groups mean that only one pad assigned to the group plays at a time. It's meant for situations like hi-hats where it doesn't make sense for both a closed and open hi-hat sound to happen at the same time. In your case, it seems like C#3 has a mute group assigned to it, and that somehow the cymbal got set to that same mute group. Remove the mute group from whatever pad the crash and cymbal are on and you should be fine.
Also remember, settings are per-pad, not per sound.
Sounds like a choke group that was set up for a kit that no longer has the things in the original place, e g. the snare is where the closed hat was and the crash is where the open hat was, or something like that.
Edit: d’oh, @wim beat me to it.
What happens if you try to recreate the pattern by hitting the pads in the same order?
I looked at my kit and every pad has mute groups turned off
Playing them live, the cymbal sustains with no issues. I dont know what else to look for
You're absolutely sure that the pad with the cymbal is set to One-Shot and no mute group?
I can't replicate what you're seeing, at least not with Digistix 1.
Yes
Its a custom kit i made, and the cymbal sample trails for a bit. It sounds fine every other way except when i add in a snare note on c#3
Does it behave that way with a factory kit?
You're working with the standalone version? How is Atom triggering the standalone version?
That's got to be a clue. The crash cymbal is being cut short in one of two ways:
(1) A MIDI command being sent to Digistix which converts to a Note Off event (I'm not expert enough in MIDI to say all commands that might qualify).
(2) Some condition within Digistix 2 and the settings triggering it.
An example of (1) would be a Note Off MIDI command on D#4.
An example of (2) would be a mute group as was already covered.
There's one other thing which I doubt is related but Digistix will react strangely to incoming MIDI data sent over CH 2 to trigger pads. They will play in reverese. It's by design, and Paul explained it to me and I got it, but I'm not able to re-explain it here. So make sure that all of the input to Digistix is over CH 1. If you are using AUM you can filter out all other MIDI channels to prevent anything extraneous as well.
I'm hoping this might prompt further ideas.
The screenshot is the standalone, but im using atom and digistix inAUM.
Did you check the pad settings in the AUv3 specifically also?
Yes
Additionally when i recreate the same drum pattern just in digistix not using Atom, the cymbal sustains with no issue. I dont want to use digistix sequencer though because it doesnt allow me to sequence free of quantize, in case i want to draw a note slightly off beat