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.
Drum Kit MIDI Templates
Hey all, I'm working on a new random MIDI generator app for the drum fills. I really like the Octachrone's drum kit templates, so I decided to implement the same feature. I also open sourced the code as well, so you can use it for your mosaic scripts or even your own app!
https://gist.github.com/cemolcay/3248a378b42f0c38661c67b0d5bac348
I'm also open for more app/hardware template suggestions. It could be a nice resource for that purpose.
Comments
That’s cool. Every app of that type would benefit from your work. Thanks for doing it!
That’s great. As a fan of your “bud” apps I am looking forward to that app. Thanks in advance!
I think it would be great to have the option to add multiple user drum maps that can be saved and loaded. This would add greatly to the flexibility of the app.
What I would love to see some day is a mapper that you can freely set the input map and the output map. For instance, setting "Korg Gadget" as the input and "Ruismaker" as the output, or vice-versa. Or General MIDI as input and "Gadget" as output.
The input would map to an internal enhanced map, and from there to an output. The internal "enhanced" map could just be the General Midi drum notes set, but structured so that you can make one-to-many relationships. For instance, mapping any of the several tom-tom GM notes to one or a few pads of Ruismaker.
Once mapped, any app (or General Midi) could be selected as the input and it would be mapped to the internal table, then any app could be deleted as the output and the internal table would know where to map the output. A universal data conversion tool.
Tools to create mappings and variations on those mappings would be ideal. Import and export of mapping files to something editable such as json would be great, so that mappings could be done in a plain text editor rather than in-app, and could also be exchanged with other devices and users would be the ultimate goal.
I have such a clear picture in my head of how it would work and how useful it would be. Unfortunately my developer skills just aren't up to the task.
Thanks!
Yes, that's the deafult behavior of the app! You can create as many kits as you want and save them as AU presets. Templates are just the quick starting points that would save you from the mapping hassle.
I don't think that's in the app's scope. BUT -- you can create big kits and set their MIDI channels to control multiple drum apps with Auto Fills.
It will be a "companion" app of your drum sequencer btw. Your fav sequencer will do the regular drums and Auto Fills will handle the fills that you don't want to write/spend time.
Excited about the midi drum sequence/pattern/groove sequencer you’re cooking up. Love to see some random and generative features, especially fills. Maybe a live fills button that you could toggle on/off while performing live and CC when sequencing, and lock/unlock for longer fills. several levels of randomness, and complexity with ability to select what tracks are created. I love octachron, and they do have a lot of apps, hardware, etc in mapped presets, plus custom ones too. If your making a drum sequencing app Octachron is as good a place to look as any for inspiration.
Sure, I know it's way out of scope for this app, and sorry for the OT post. I just keep tossing out the thought in hopes of snagging the interest of some developer out there. 😉
I think this is quite doable in Mozaic if you define a basic drumkit:
1. "Kick"
2. "Snare"
3. “Rim Shot"
4. “Closed HH”
5. "Open HH"
6. “Hi Tom"
7. “Mid Tom"
8. “Low Tom"
9. “Ride”
10. “Crash”
11. "Cow Bell"
12. “Clap”
and any extras
In Mozaic you create arrays for the 50 some odd apps Note Data as documented by Cem and @SevenSystems
using the slots as shown in the list above.
Then you present INPUT and OUTPUT App Selection Knobs so a Generator’s Note choices can be converted as needed to the Receiving Apps Note choices. Extra features like volume controls and potential modifying the defaults
would be nice.
I’m not committing to doing the work because it’s a lot of work to enter all the app data and creating what I’d guess would be very large “if-elseif…” structures to select the Apps.
This biggest question is if there are enough potential users.
Would be very cool. I would use that, for sure!
Remap multi channel is similar to that but the input is the channel.
I considered Mozaic, but it’s just not appropriate for what I had in mind.
If you have to edit code (not just modifying variables, but logic too, every time to add a map it’s not productive IMO. Also with such limited labeling options as Mozaic has, it becomes far more trouble than just simply saving presets in something like mfxConvert.
Tbh, mfxConvert is “close enough” for my purposes.
In fact, now that I think about it, two mfxConvert instances could be used effectively. One to map to GM Drum map, and one to map from GM Drum map could be pretty serviceable... 🤔
Anyway, I don’t want to further hijack this thread.
It’s not hijacking… I’m always looking for good ideas to get lost in Mozaic. I tried mfxConvert and I get so bored filling out forms. I like a logic puzzle.
Mozaic can label knobs with the names of the sender and reciever but the burden is on the programmer to add more targets… still… it’s probably worth doing with a good programming editor to copy lines and change the labels.
I wish Mozaic could put labels in arrays.
@cem_olcay sharing his swift code opens the door to stop complaining and just get into Swift Playgrounds to tackle new puzzles.
@SevenSystems exposes his Drum tables as json and that led to some clumsy python hacking to convert the data to plain text. I used the python 3 that comes with A-Shell in my favorite Editor… Vi(m). Vi moved into my brain in the 80’s and hasn’t left.
Yesterday I started hacking the plain text drum data to see if I can catch nvert to Mozaic arrays.
ChatGPT is fantastic for this type of reformatting, as I learned during another forum thread about Mozaic and Sysex. After last night's post, I asked ChatGPT to list the GM Drum map with note numbers, then asked it to add
#to each line to make it into Streambyter comment lines, then finally "Now create an array variable named "L00" using the note numbers." In under 20 seconds I avoided what would have been 20 minutes of boring reformatting work.(All done with the free ChatGPT at chat.openai.com)
@wim I guess it’s time to take ChatGPT seriously as a programmer’s resource. Time to learn to talk in riddles.
There’s a great podcast about Open Source AI that interviews Simon Willison ( of Django fame) that covers the current state of AI at:
https://overcast.fm/+4jBEcSNk4
Oxide and Friends podcast
That’s awesome @cem_olcay
The Bud apps make up probably 75% of all of my sequencing duties so I’m stoked about this.
It really is about time, because if you wait much longer, they'll have crippled it so badly that it'll be incapable of even answering to "Hello" 😉
(I'm slowly stopping to use it for anything because it has simply become unbelievably dumb and lazy over the past few months. At first I thought it was just me or the novely wearing off, but do a quick Google search if you like to confirm I'm not crazy 😬)
😄 we're surely not giving it a lot of slack!
I always try to be extra nice. Some day we'll be at AI's mercy. 😬
This looks interesting! Thanks for the open source material.
I'm just having a conversation about extracting the sampling rate from various audio file types, and this time around "he" is being amazing:
Response as useful and concise as anyone could wish for, with actual perfect example code in the next sentence:
So yeah, maybe I should retract my very black&white statement earlier. It's just a bit hit-and-miss recently.