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
Ace,this. The ease of access to Gadget instruments is tremendous. Thank you!
Your feedback made my day
Very happy that @SevenSystems chose to make them available directly in the app
AUM users will also benefit from looking at the Xequence wiki page hosting instruments and MIDI mapping files for a growing selection of AUv3 (Koala, TAL U-No LX, the Moog synths…)
Cheers!!
While this is very good with touch in mind, I can’t see myself using it when I need to use a host as i can’t send midi clock to xequence, need to save 2 files for each project and no audio tracks.
It has a good future if instead it goes the route of a full fledged simple daw, the midi is already done well but is quirky for everyday use because of the issues above
unless it’s meant To sequence outboard only and for this, it’s a good sequencer
(though it’s a very small niche so I don’t see it becoming very popular with this mindset set in place)
Now we just need more people like you in order to keep the promise of "growing number of factory instruments" 😄
Business speaking I think it’s a mistake to release these mappings for free, sell each map for 1$
This way we won’t have a huge list of maps for things we don’t use, and you can make money for these crafted map add-ones.
It is something worth considering for future packs for sure! Not this time however, as almost all of the included factory instrument configurations have been volunteered by @crushed so it would be quite iffy to make money from them ☝
Well, this alone is worth some money.. Thanks..
@crushed
Give him your approval and let the dev make money of this product for a better future for all of us
This sounds great! I still need to figure out the polyhymna generative part. Anyway cheers!
Thanks! I know people hate reading manuals, but just in case, here's a few details about PolyHymnia 😊
http://seven.systems/xequence2/en/manual/#sub-section-8-0
One hot take after the other, you're on a roll, mate 👌
Are you planning to implement probability/step repeats, etc in midi clips? This is a much-needed thing, has become so familiar in the sequencers, I would like to see it in updates.
It’s also a mistake to support all 128 MIDI notes for free; they should be sold in bundles of 12 for $1
This way we won’t have a huge list of notes we don't use cluttering our piano rolls, and you can make money from those advanced users who need the full range
Can you give me an example of how this would work and how you would like to see this implemented? I've seen the term "Probability" a lot related to sequencers but I'm not exactly sure what it should do.
One way to go so is either a global or per note probability. When the playhead is about to play a note, it generates a random 0..1 value "r" which is compared to the global or per note probability "p". If probability is 0, the note is never played and the opposite at 1. In-between, you can for instance check for "r < p" to determine if the note will be played or not.
Editing per note "p"would resemble editing velocity for instance.
OK thanks. I'm not sure how this would be used in practice? Wouldn't it be better and less convoluted to just introduce a selection tool for this (i.e. SELECT -> Random...) where you'd have a percentage slider, and then you'd just hit "Delete" or slide the velocity to zero?
This would have many advantages:
Or am I missing something?
In fact, the ideal option would be to implement this in the same way that velocity control is now implemented. In other programs this is implemented, the same slider as velocity, it is done in LK for example, it is just another parameter, which also acts only within the pattern. For example, in Drambo there are several mechanisms that create these pseudo-random events, such as retrig, cycle, probality. For example cycle condition, if you specify 1, 3, the first and third cycles of the pattern that note/notes will be active (with cycle option activated), the second does not, and so on. If we talk about probability, then visually you can do for example from 50 to 1, 50 - a note is always played, 25 is a state in which this note is played every once and a 0 - never played.
But what's the purpose? To get ideas? Wouldn't using PolyHymnia be a better bet?
Don't need different notes. There are other programs for them, like zoa. We are only talking about definite notes, which will either be played in the pattern or not. That defines the pattern and you don't have to clone the pattern a hundred times. You make one or three big patterns with drums for example, and the definition of it plays with a certain degree of randomness so it makes it more interesting. Yes, you can manually do 20 patterns where you can manually remove certain notes, but why do it when you have such elements as probability.
But I would be worried in this case that sometimes, the randomness just gives completely unmusical results. I can't imagine composing like that, i.e. with something I have absolutely no control over and which might give me a good song one time I press play, and a bad song the next.
But it appears to be a thing and so I'll see what I can do
A huge number of modern styles of music are built on pseudo-randomization or randomization. Otherwise these styles simply wouldn't exist ) From techno, idm, garage to experimental styles and modular music. Therefore, things like cycle / retrig / probability exist in almost all modern sequencers/DAW, both on the desktop, for example, in Ableton and bitwig, Logic Pro x, as well as separate auv3 or various DAWs on iOS. I gave examples above where and how this is implemented, I can provide you with a whole list of similar sequencers on iOS with these functions in the base.
You can listen to early jazz, like Louis Armstrong, for example, and you'll find that they often use pseudo-random notes, chord sequences, and so on. A lot of jazz is very free-form and that's sometimes be a difficult to the average listener. The same goes for classical music. Think about random Sharps/Flats in classical music, they are there too if it's done by a person and not a machine. The same pianist will play a classical piece at different times in different ways, he will make accents in different places, somewhere the length of the note will be higher, somewhere lower. This is what life is all about, and it's what distinguishes music played or written by a living person from machine code, which is clearly built algorithmically.
My suggestion would be multiple variable speed playheads, where each could be constrained to a specific section of the timeline and/or overlap as desired.
In my case, the purpose is something you're not considering: each time a pattern is played, it gives unpredictable results 😊 So the purpose isn't to get a random idea to reproduce in a sequence (as with PolyHymnia). This is something I often use in ambient to avoid strong repetitions, leading in different results each time.
That being said, there are other sequencers that can do that, so no specific need for xequence to handle that. If xequence should be viewed as it is now, i.e. a predictable sequencer, this is perfectly fine for me.
As you were asking for use cases and applications,I just wanted to give you some genres where this is useful 😊👍
OK, thanks for clarifying. Yes, this may be something that I don't see fit for Xequence's philosophy, which is more like "The MS Excel of Sequencers" if you will 😄 boring, but precise!
Good to have the discussion though, also thanks @soundsgoodbro for bringing it up.
I am a little surprised and amazed by this position, in the style of "If xequence should be viewed as it is now, i.e. a predictable sequencer, this is perfectly fine for me". With this position it turns out that there is no need to improve anything at all, let's leave it as it is, why do we need these innovations) as a result we come to the fact that the appstore is full of abandoned by developers software, including DAW’s, which for years are not updated and have no innovations in principle, because in the "opinion of developers" it is so good that it does not need anything. This is an absolutely dead-end development path in principle. Why limit a product to your personal philosophy when the product is made for people and their needs? Everyone uses AUM by default for the reason that it in its original version covered and opened iOS features to the maximum, developed a completely different philosophy of capabilities and potential, inspired a bunch of developers to make for it, including plug-ins and various tools. Until now, no DAW with a staff of developers can not even come close to the routing capabilities, convenience, development of internal midi and parameter management of plug-ins and third-party programs. Sorry for offtopic.