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.
Axon 2 vs Ruismaker FM
Axon 2 vs Ruismaker FM. I own Ruismaker FM. Can somebody tell me the difference between those 2. Is the worth for me to purchase Axon2. Axon 2 looks from my own research a lot like Ruismaker FM.
Comments
Axon 2 Midi out is broken. Needs an update. Just a heads up on that aspect.
it crashes a fair bit too for me. Definitely worth having though but YMMV etc
Sound wise, I think they’re very similar, though Axon 2 has many more sound design possibilities with all the FM/AM mixing capabilities. That said, Ruismaker is more my go-to because of better UI, easier to understand and less fiddle controls, and because it’s universal.
I open up Axon mostly because of its sequencing thingy, which can help to break out of molds. Not so much for sound design.
My only frequent letdown with Ruismaker FM is there’s no delay section. Axon is way better in that department.
If I could only keep one I’d keep Ruismaker FM. But I’m glad I don’t have to choose.
20:01:15.421 [Note On] ch=0 note=41 velocity=85
20:01:15.421 [Note Off] ch=0 note=41 velocity=0
20:01:15.421 [Note On] ch=0 note=42 velocity=0
20:01:15.421 [Note Off] ch=0 note=42 velocity=0
20:01:15.758 [Note On] ch=0 note=37 velocity=98
20:01:15.758 [Note Off] ch=0 note=37 velocity=0
20:01:15.758 [Note On] ch=0 note=39 velocity=100
20:01:15.758 [Note Off] ch=0 note=39 velocity=0
20:01:17.122 [Note On] ch=0 note=37 velocity=98
20:01:17.122 [Note Off] ch=0 note=37 velocity=0
20:01:17.122 [Note On] ch=0 note=38 velocity=103
20:01:17.122 [Note Off] ch=0 note=38 velocity=0
20:01:17.122 [Note On] ch=0 note=39 velocity=100
20:01:17.122 [Note Off] ch=0 note=39 velocity=0
20:01:17.122 [Note On] ch=0 note=40 velocity=102
20:01:17.123 [Note Off] ch=0 note=40 velocity=0
20:01:17.123 [Note On] ch=0 note=41 velocity=85
20:01:17.123 [Note Off] ch=0 note=41 velocity=0
20:01:17.123 [Note On] ch=0 note=42 velocity=0
20:01:17.123 [Note Off] ch=0 note=42 velocity=0
20:01:18.829 [Note On] ch=0 note=37 velocity=98
20:01:18.829 [Note Off] ch=0 note=37 velocity=0
20:01:18.829 [Note On] ch=0 note=39 velocity=100
20:01:18.829 [Note Off] ch=0 note=39 velocity=0
20:01:18.829 [Note On] ch=0 note=41 velocity=85
20:01:18.829 [Note Off] ch=0 note=41 velocity=0
20:01:18.829 [Note On] ch=0 note=42 velocity=0
20:01:18.829 [Note Off] ch=0 note=42 velocity=0
20:01:20.193 [Note On] ch=0 note=37 velocity=98
20:01:20.193 [Note Off] ch=0 note=37 velocity=0
20:01:20.193 [Note On] ch=0 note=39 velocity=100
20:01:20.193 [Note Off] ch=0 note=39 velocity=0
20:01:20.535 [Note On] ch=0 note=41 velocity=85
20:01:20.535 [Note Off] ch=0 note=41 velocity=0
20:01:20.535 [Note On] ch=0 note=42 velocity=0
20:01:20.535 [Note Off] ch=0 note=42 velocity=0
20:01:21.557 [Note On] ch=0 note=37 velocity=98
20:01:21.557 [Note Off] ch=0 note=37 velocity=0
20:01:21.557 [Note On] ch=0 note=39 velocity=100
20:01:21.557 [Note Off] ch=0 note=39 velocity=0
20:01:22.236 [Note On] ch=0 note=38 velocity=103
20:01:22.236 [Note Off] ch=0 note=38 velocity=0
20:01:22.237 [Note On] ch=0 note=41 velocity=85
20:01:22.237 [Note Off] ch=0 note=41 velocity=0
20:01:22.237 [Note On] ch=0 note=42 velocity=0
20:01:22.237 [Note Off] ch=0 note=42 velocity=0
20:01:22.921 [Note On] ch=0 note=37 velocity=98
20:01:22.921 [Note Off] ch=0 note=37 velocity=0
20:01:22.921 [Note On] ch=0 note=39 velocity=100
20:01:22.921 [Note Off] ch=0 note=39 velocity=0
20:01:22.921 [Note On] ch=0 note=40 velocity=102
20:01:22.921 [Note Off] ch=0 note=40 velocity=0
What do you mean it doesn’t work?
@BiancaNeve
How did you get it to work? It has never worked for me. Many others have made the same claim. In fact Chris Randall even acknowledged that there was a Midi out bug shortly after it was released. So what's your secret?
Thanks, this was the answer I needed. I'll pass for now, also because I really havent explored Ruismaker.
@BiancaNeve C'mon! You got me all excited, but now you're not gonna spill the beans? Please, I want to be wrong!
I'd say for that price you shouldn't pass on Axon 2, it does sound quite different to the Ruismakers. Good to have them all.
I didn’t DO anything. Just loaded midi wrench and Axon and hit play in Axon
I got midi messages in a log as well. As far as actual sound, that would be no.
What are you connecting the midi out to, and how?
I can't remember exactly. I refunded it, and was waiting for it to get fixed. Is it working now for you as well? I didn't see anything about it being fixed in an update and was still waiting. But if it is working I want to get it on sale.
From what I remember, I tried a lot of things but never managed to get more than very sporadic bleep out of it when using the Midi out.
I showed similar data coming out of Axon2 via midiflow, but I could never get it to actually trigger anything. I too want to know the secret.
Every now and then it'd trigger a random note or two, but nothing consistent. If there really is nothing wrong with Axon2's midi out... that'd be awesome. Going to take another stab tonight if there really isn't anything wrong with it. However, I too recall reading the dev (Chris) acknowledging there was a midi out problem... though, I never saw that response from him myself... just hear-say.
Yeah shame no fix yet, all went quiet from AD though he did acknowledge the issue.....Midi only triggers occasional notes. As far as I could see it was getting note on offs around the wrong way, at least that's what it looked like when I observed the midi messages.
Confirmed. I can’t get anything going either.
Dang, that sucks! I was really wanting it to be working, somehow, maybe magically.
@carnbot I couldn't remember the super-sleuth who posted about the midi message mixup, but I remember thinking that was an awesome instance of bug hunting.
@skiphunt @wim Thanks for confirming. Guess I'll keep on waiting for that update.
As a side note related to Axon2... apart from the midi out issue... if you got the Rozeta suite and using in AUM, after setting up a little sequence in Axon2 and sending one of the Rozeta sequencers to it.. you can get some really cool results quickly. And, after you adjust the probability in whichever Rozeta plugin you're using, it can evolve into some nice compositions on it's own.
midi out is tricky with Axon but it’s working...i’m using it to drive iElectribe with midifire in between.
couple things are needed: on Axon “midi only” button (far right upper) needs to be engaged for each node
midifire set up:
Axon:
each rectangle must be selected, and midi only selected for it
@Littlewoodg
MidiFire is seeming more and more like vital piece of the iOS puzzle. It seems to do a lot of things that are hard or impossible without it. I think I need to take a closer look at it. It seemed pretty deep when it came out, but I wasn't sure what it did exactly. The more I hear, the better it sounds.
Well, for one thing, I didn’t realize the midi out only option was per pad. That helps! But I still can’t get anything consistent out of it even using MidiFire. If I host anything in AUM I get virtually nothing. If I take AUM out of the picture I get a few notes here and there, but nowhere near all of what Axon is generating, even at low tempos.
I don’t know what you’re doing that makes it works, cause it ain’t happening here no matter what I do.
I didn't know that midi-out only needed to be selected for each pad either. That would make sense with the results I've got so far, but the fact you say it still isn't working for you... and I know you mostly know what you're doing
Watching with popcorn on this one. I think the Audio Damage kids know what they're doing, so it's hard to accept they let this level of failure slip through the cracks... it's easier to believe it's my own ignorance thats the failure point.
It's weird, it triggers some things with higher success than others depending on the app, but if you check with Midiflow the note on offs go off then on. If you try it on a synth it hardly works at all.. For me anyway. I gave up with it but hope that the AU gets a midi out update along with a fix.
Senode does this kind of thing in a much deeper way so I'm hoping that gets Linked up soon.
Midifire is great. And actually there's probably a way to correct the midi data with it using the stream byter but I don't know how and I'm not skilled with it to even attempt something like that
My experience too. I haven't bought Senode yet. It's at the very top of my list. I know it's on launch discount already, but some apps went even lower... even though they were on launch discount last year, so I waited to see if this one would too.
Didn't, so I'll be nabbing it soon. It just looks like it really fits with the kind of sequencing interface I've been looking for. And, my somewhat loose budget for "black Friday/Cyber Monday" allowed for buying Senode no matter if it was discounted more or not.
sorry about that, wish i could be of more help-
there were 2 pieces that seem key to making it work: first the midifire set up involves the mf channel strip, which is set to accept all channels (from Axon) and to filter to 10 (which is iElectribe’s must-have), and second the correspondence between the notes of iElectribes voices and those of Axon. The midi map for iElectribe says it uses C2, D2, E2, F2, F#2, A#2, C#2, D#2...and that seems to line up with most of the nodes (didn’t try all)
also as with all ios midi the order of opening apps seems to play a role
other considerations: the faders, mute and solo buttons on Axons nodes affect the midi out, if the node is muted the midi doesn’t send from the node...which makes me wonder about the fx sends on each Axon channel, if they also affect the midi send.
also if you change presets you have to go back and do “midi only” on all the nodes again.
so far worked with iElectribe, bleep!BOX, Modrum
@Littlewoodg You must be a wizard. I am amazed you have gotten it to cooperate at all. I am thankful you are here as a helpful forum member. Rock on!
non-wizard...just stubborn
I’m confused. Are you saying you indeed have figured out how to get Axon 2’s midi out to work as expected for all notes routed to another synth? I just made a few more attempts, both inside AUM and without it. Also tried using midiflow for the routing and it still isn’t working. How exactly are you getting it to work?
yes, as above i’ve got it driving iElectribe, bleepBOX, Modrum...with all the specifics listed. i’m using midifire rather than midiflow, midifire has been helpful with many midi miscommunications, the rest is as described.
Hmmm... Ok. I don’t have midifire, but I just wanted confirmation that it’s possible. I’m stubborn too.
thx!
@skiphunt just ran DM1with it without the midifire...