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
MidiFire and StreamByter have solved problems for me on iOS that no other app could--especially when I throw in Nic's willingness to help troubleshoot. Given the creativity that has ensued, I'd say "top job"!
E> @lukesleepwalker said:
+1
There you have it, and it's free: MobMuPlat.
AUv3 support could be added by somebody with experience in developing AUv3 plugins who feels like investing some time.
+1
Any complex issue I pretty much know I can solve with Streambyter. MidiFire too, but I like the small purpose-built streamlineyness of Streambyter, and the AUv3 portability and state saving.
That said, I love the mfx Series plugins as well for when I don’t feel like diving into code, or especially when recommending a solution to others that might not see coding as “fun”.
I use the mfx convert plug in almost daily. So handy. Had a great time with the wobbler recently too.
Cool name. I think it's Latin for "Syllable Truncator"
Mob(ile)
Mu(sic)
Plat(form)
Someone should fork a version and call it (IleSicForm).
I surprised this wasn't mentioned before. It looks like a single programmer that doesn't expect to make money from the effort. Sometimes they change the world (@analog_matt) if enough people pitch in to make change happen.
Investing or donating?
Anyway... thx for the heads. I'll poke the tires since that investment will cost me little.
For those that don’t know MobMuPlat is a front-end for the Pure Data which is a free , Open Source language from Miller Puckette who created MAX. It is quite similar to MAX.
https://en.m.wikipedia.org/wiki/Pure_Data
That really filled in a lot of holes in 20 years of history connecting dots. I had a Google started link ride across the decades finding some software roots I played with in the 80's
(Sound) and followed the trail to Ableton.
I'm on geek overload. Thx. Cost? $0.00 Value? A priceless maze of tech puzzles to solve
that include the potential to generate art.
@McD @espiegel123
If you're looking for some art done by others, here's a few:
MobMuPlat PD patches
https://github.com/otem/mobMuPlat_patches
https://github.com/Ridwy/MobMuPlat-Funhouse
https://github.com/megalon/pd-AUTOMATONISM-sampler
Automatonism patches work if only using the native PD GUIs, otherwise you'll have to make the PD core patch "CV-controllable" (in PureData speak).
Also, search for "mobmuplat" on https://forum.pdpatchrepo.info
I guess the decision is @audeonic whether you want your app to be used only by @McD’s smart people or you want to open it up to the not so smart ones as well.
Thats not quite correct
.
For the complex „distribute incoming poly midi to N mono channels“ script i wrote a simple simulation environment in a high level language (no sound, just for note on/off events) to find/debug the algorythm for what i wanted to archieve with the script.
When it was running for the test cases i fed into it, i changed the code to no longer use nested loops, or ‚else‘ constructs - still verifying it was working.
And then changed again to simple single line instructions like streambyter has. I saved that code and used it as comment (and hint during the code conversion) for the streambyter script.
.
TDLR I kind of was my own pre-processor, all was done in brain-ware not software
@supadom : no tool can be everything for everyone. He has also built some easy-to-use tools that do quite a lot. MidiFire itself does an awful lot without needing to code. So, it isn't fair in my opinion to treat audeonic as if he were being elitist or insensitive to people's needs.
It isn’t about being elitist and I don’t think being able to code makes you part of an elite.
What I’m saying is that the more accessible your app is the more people will use it. There’s nothing wrong with trying to make a tool more accessible. Clearly, enough different user groups made valid points here to at least consider this as an issue.
Of course if it’s never been a vision for this app then that’s that.
Then, maybe there isn’t much point venting on a forum that is frequented by the not so smart types, is it?
This is my point entirely. StreamByter is aimed at customers with specific use cases that are not easily solved (if at all) by some sort of GUI app. These customers are either boffins or people eager to learn how to do those things themselves or customers who do not wish to do any scripting but happy to use the provided or 3rd party scripts or ask me or 3rd parties to write scripts for them. For the others there is mfx Series or MidiFire (or similar)
What I will say is that the demand for this type of scripting app is very, very small. StreamByter has been out for almost a year and I have sold less than 300 copies. The effort I put into getting it to where it is today has been vast. I do this as my (mostly) fulltime job in order to provide for my family so I need to charge for my work and even then I would be better off drawing the dole. Investing massive amounts of effort in trying to make the language less boffin friendly is simply not worth it for possible extra sales this would result in; law of diminishing returns. I don't think it matters how approachable the language is; I suspect the market is pretty much the same size for StreamByter or some other 'better' scripting product. Customers have to a) understand MIDI and b) learn the proprietary scripting language.
Yes, and you probably have the most accurate overview of the situation. It’s always a balance. I’ve read somewhere about the iron triangle yesterday and it totally applies here: price vs resources vs time. It indeed is niche market and I guess it won’t get bigger if you make it easier to use. If it’s not viable than it is more than fair enough. I ended up getting softstep just to avoid dealing with scripts.
@tja,
Yes I have a youtube channel where there are a number of videos for all my apps.
https://www.youtube.com/user/audeonic
MidiFire has a built-in Scenes Club where I place useful scenes and for StreamByter I add them to the factory presets as well as the soapbox.
I have to say that although Streambyter code looks shockingly cryptic at first sight (and I'm sure that's why many users become discouraged too early), getting used to it doesn't take much longer than learning any other "language".
When I find the time and patience, I might create a cheat sheet for the StreamByter with all the important elements and a few short examples where appropriate.
This helped me to understand the standard Midi messages available:
ditto
Nice, thanks!!
It’s certainly harder to communicate via written language than orally face to face. I hope my previous post didn’t hurt. The fact is I use MidiFire everyday, it’s incredibly useful for me and Nic has helped a lot with my project, with special multiple taps and round robin features. I especially like Rotary Knob module too. I’m even able to modify some things in the scripts :-) So it’s a total win for me. On the other side, I suppose I could learn writing code, I’m not lazy, but it’s more about time as my needs are complex and I will always need some help at some time. So at the end, MidiFire IMO can’t be replaced and is a nice offer with all help provided by Nic and others, even for those like me which have difficulties learning scripting. That was essentially what I wanted to mean.
Ill just add that I was able to get a quick guidance to my initial specific script question from the Audeonic forum when I got streambyter (converting notes to PCs from an app with no PCs) and I was able just to find an example of a second line (my pitch wheel didnt play nice with the Moog Sirin for some reason) and make it all work.
I wouldnt call myself a coder at all. Im not even the most expert computer musician, come from a rock n roll background. I was willing to read, experiment, and figure out how to basically transpose the code, but I think my DAW has as much much larger learning curve for comparison.
We live in a time where a considerable percentage of app purchasers don't want to invest any time in learning how to use an app...a 20 minute investment of time to read a short manual or QuickStart guide is more than most are willing to invest...let alone spending an hour or two to learn things that will pay them back in time-saved and improved productivity many times over.
It is rough for anyone that creates something with any degree of complexity or something that requires some knowledge. Over the last 10 or 15 years or so there has been a noticeable shift for users wanting instant gratification.
It is rough for developers and manual writers and tutorial makers of anything other than widgets.
So much is available to people that they tend to want to move on to something else rather than invest some time.
Dude, get off your soapbox....or get your numbers right, or at least cite a source of your research. It isn’t couple of hours or we’d all be singing and dancing using streambyter and the likes.
A vast majority of regulars here have invested more than they ever should working out complex apps. I know because I’ve been here for years watching it happen. You are confusing laziness with priorities and if your priority is to work out scripts, more power to you, but you can’t go around calling people lazy @espiegel123 or not-smart @McD. Just get your heads out and try to work out other people perspective if you’re so switched on.
@supadom: you are the one injecting words like lazy and smart. I’ve been in software development and doc and tutorial writing for 35+ years. The trend I am talking about is oft-discussed among developers and doc writers whose careers have spanned a long enough time to watch the trend.
It isn’t about people being lazy or smart or not-smart. It is an understandable trend. And one that is unfortunate if you happen to be creating something that by its nature requires some specific background knowledge. People are certainly entitled to their priorities. It is simply the case that user expectations and desires have changed in this respect. I am not saying people are lazy. They have a lot going on in their lives and lots of things competing for their attention.
I appreciate having a tool like StreamByter available for solving those custom MIDI setups. The possibilities for these sorts of scenarios is endless and therefore I can see why having a GUI for such a setup isn’t possible. You can get StreamByter code as an IAP in MIDI Designer Pro 2 so you can bake the functionality of the scripts into a GUI. I will also say that the more people share how they use custom scripts in StreamByter that they or others including the developer Nic have helped them with, the more the word will get out. Finding a script that does something you wouldn’t otherwise be able to do, definitely makes the app purchase worthwhile for me. Nic has been very gracious helping musicians to address their MIDI needs since the beginning of iOS.
MobMuPlat is great. It would be even more useful if their were a way to create the GUI in iOS rather than having to use a computer.
I really enjoy BitWiz as you can get some complex wave forms that have long periods before they repeat and variables can be controlled via MIDI CC so you can have some relationship to tempo or other musical structure. Fooling around with the codes which generate the sounds can be a fun exploration without really needing to know the math or meaning behind them. Pair the output from BitWiz with any number of effect apps and you’re good to go. Hopefully at some point @j_liljedahl will provide AUv3 support though as @audeonic has pointed out with StreamByter code, it’s a small market and can’t be relied upon to support a family.
I hear a lot of people say they’re not inspired by the sounds they hear from Audulus 3. I don’t think there’s an inherent limitation to what sorts of sounds you can create with Audulus though figuring out how to create patches which produce sounds you’re aiming for is a different matter. I do think it can be an excellent way to learn about synthesis. When Audulus 4 is released, it will have MIDI out, be able to use samples, and have AUv3 support. Being able to use Audulus 4 as a sequencer for MIDI will be a function I’ll definitely take advantage of.
Apologies, something's triggered all that came out. The thing is that the fact that people do have hectic lives, even if just because of scrolling through social media and watching apple TV, means that technology will have to evolve to accommodate this and not vice versa.
For now, of course, we have the tools we do and I'm only too glad not to need them anymore. Should be on best behavior though in case drambo and boppad don't play nicely together and I'll have to shuffle to audeonic forum for help.
It will in the end be rough for society as a whole, as most really "important" stuff (how to keep an economy working ; how to seed and harvest food ; etc.) has a very low "instant gratification factor" and it'll be interesting to see what happens when "Generation Instant Gratification" gets swept to the control panels of power