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
Nice one!
I'm turning blue, though, waiting for MIDI channel selection, ideally MIDI Port and channel per destination, but at least AUM Virtual MIDI In port with channel selection per inserted thingy. No pressure. I like to jam and use MIDI channel on keyboard to select which synth I'm playing. For now checking and unchecking in the routing panel is sort of useable but not as tactile. Or as immediate.
How does one get rid of an empty channel?
+1 For skinny channel mode
I like detailed VU. How about skinny stereo VUs showing input left of the fader, output right, same height as fader, inside the existing outline?
I found something I thought was a bug, then did't, then maybe it is a bug but it's useful: IAA synths show up in the MIDI routing panel even after they have been removed from their inputs. Turned out that is true for IAA synths that go zombie when removed. Now we can no longer view processes lists, this is a way to see what zombies ar running so we can kill them properly. Module and Thor both did this. After I loaded and quit them manually they disappeared from the routing panel.
I like both of these ideas (Logic and Reaper also do the 'busses only', 'inputs only'... type views). Maybe the simplest for now would be the ability to toggle that zoomed out view you get when you drag a channel down?
88.2 kHz? Why not a more common 96khz?
If 44.1 is the destination format, 88.2k is (traditionally, anyway) your friend.
88.2k to 44.1k is a simple 2:1. Simple math.
96k is to 44.1k is 2.176870748299319727891156462585:1. That's a lot of decimal places per sample to contend with.
That said, I'm not sure how relevant this is anymore. Computers are stupid fast and most of the sample rate conversion algorithms out there have been tuned and tuned for a long time. @Tarekith is 88.2 > 96 (for 44.1 final) still a thing?
Would need the ability to solo just a bus with this though, at the moment have to solo the tracks going into the bus as well. Thought it was a big but that's how it's meant to work
Found a confusing one. I have faders, mutes, and solos mapped from my Samson Graphite 49. When I reorder channel strips, the assignments reorder with them. Sounds like a nice idea, but my visual cortex has problems. I expect fader 1 to operate the leftmost channel strip, not the one that used to be there but is now in position three.
OTOH I can envision other use cases where keeping the asigment with the instrument makes more sense, especially once you get notes observing MIDI channel numbers too like your CC learns do now (yay for that btw!). e.g. a different physical controller for each instrument.
Maybe a preference checkbox?
No, that's an old wives tale that never dies. These days any sort of proper sample rate conversion will be oversampling many times anyway, there's no such thing as simple math for SRC anymore (if there ever was).
I'm listening to everything you say here, and taking notes
This is an interesting idea, but a lot of work, but I will certainly keep it in mind.
Yeah, IAA in itself doesn't have state saving. That's why Audiobus added it in their SDK! Audio Unit extensions does, however. So for IAA, route them through Audiobus, or save the presets internally in each app too.
And yes, the idea is to use mix busses if you need a mix for recording or applying effects to a whole mix, or to have a mix fader. AUM makes no difference of a main mix, submix, or effect send, or signal splitting by receiving on multiple busses, etc..
Thanks! A nice but simple non-destructive audio editor is something I've been wanting to do for a long time, and will hopefully jump into it some day in the future
Yes! That would be great!
Thanks! I was worried you might have missed it :-)
I'll add another 4 if there's a demand for this. So far you're the only one
(Perhaps I should add some kind of voting feature request list on my forum!)
Actually I've never even seen an audio interface with 88.2 kHz sample rate. I could easily add that, but I don't know if iOS/CoreAudio supports it and since I have no audio interface that supports it I can't test it.
You should email the developers and ask them to implement an IAA host transport panel, or at least an IAA switch-to-host button.
It's coming in the next update! It will be a channel filter per destination, regardless of which MIDI ports are selected as sources for it.
http://kymatica.com/aum#faq
I decided to only have one detailed VU, at the top, to keep CPU demands low for the user interface. But you can tap it and choose what you want to see there, any hardware input/output, mix bus or Audiobus/IAA output port.
That's correct. Unfortunately it doesn't help for IAA apps that has no MIDI ports. Personally I make a habit of always switching to an IAA app at some point, so that it appears in the multi tasking view. And then swipe them out to terminate when done with them.
And for developers, here's a way to make your IAA apps go zombie much less likely: http://lijon.github.io/iaa_quirks.html
Yeah I can see that this might look confusing. The idea is that channel strips are independent, and that their visual order is not important. It would be confusing if a user sets up a channel strip to be controlled, and then inserts another channel and suddenly it has changed its mappings! Also note that each control can have different MIDI channels, controlling different parts of a single channel strip.
But I can see your point of view too. It would need some sort of "auto MIDI channel" option, to discard the user setting and use MIDI channel == visual channel strip order.
Another idea is to add a simple way to set the same MIDI channel for all parameters of a channel strip in one go. So after reordering, it would be just a few taps.
Would it be possible to add more busses in the future? There's only 8, so let's say you use one for your master, two for Aux sends, 4 sub groups, and one for monitoring, and you've run out. You might want to add another sub group, or another Aux send or two. For small projects 8 is OK, but if you want to do something more ambitious it's not really enough, especially since they have multiple purposes (Master, Aux, Sub group etc.).
For example they're really useful for parallel processing: you can send a channel out to two Busses, one that has effects on it and another that's dry, and blend between the two with the faders (great for compression for example). But with a limited number of busses this kind of thing is harder to do.
Yes, this is possible, and will do that if there's a strong demand!
Just making sure you have plenty to do and do not get bored
I am getting used to AUM now after a full evening of using it and it really is the missing Link (no pun) for me
It has removed a lot of the back and forth between apps and exporting that I previously had in my workflow.
If you have AUM, ModStep and some good AU's/IAA's you really don't need much else
Woa, what??
+1 for your and @dwarman's auto midi mode as an option or quick toggle. That's the way most DAW mixers work (your HUI is ambivalent to what is on the 3rd channel but the third fader will always control it). Definitely lots of reasons to keep the current incarnation but hopefully their is room for both.
Yeah, will definitely give this some thought. If I ever get a Mackie HUI controller, it would make totally sense to always map it as visual. But it's a bit different for any non-mixer-like controller: Perhaps the user has a controller with only 4 knobs, mapped to filter cutoffs on channel 12,13,14, and 15. Then re-arranges his channels inserting one before them, and voila everything is messed up. So it really needs to be a separate and optional mode, perhaps like a special channel setting (as 0 now gives OFF).
@j_liljedahl more then 8Busses would make sense in BigProjects YES +1
but the PopUp Listoption should not be crowded (maybe in OPTIONS how much Busses could be used, like n loopy how much Tracks...)
(+ maybe if you zoomed out, there is space maybe could be rows? just a thought....)
Studiomux is the only option to get 8 IAA buses into Windows..the full glory of AUM is not realized with the 4 bus limit
Yes, the entire Echo Audiofire range support 88.2kHz as does the DBX Quantum Mastering Processor. Probably not a priority for you, but nice to have at some point of AUM's long future
Thanks for providing the wording of what we should be asking App Devs for.
It is very difficult to see what could work here. All controllers are different in terms of controls and how those controls work, some use different CCs for each function on each mixer channel, some use different Midi channel for each mixer channel and same CC's for each function, some are user configurable, also the selected inserts and mapped controls to those inserts will be different for everyone, so knowing what controller is attached and what was mapped to what would need to be known in order to decide what to do for AUTO, I think there would be far too many possible combinations to be able to deal with them reliably.
Perhaps just auto swap the controls that are common across all channels, level, mute, solo and rec
@j_liljedahl Just thought I'd mention what appears to be an issue. I do occasionally get a brief slow down warping bug on a loop playing in the file player when I'm doing something else in AUM or in another app. doesn't appear to be always the same thing which causes it. Stabilizes again afterwards.
Will try and replicate.
That's the file player's re-adjusting/catching up after a buffer drop-out (CPU overload) or after AUM's latency compensation changed (added/removed a lookahead limiter or AUFX effect with limiter enabled).
Ok, I just tried with my Focusrite 6i6, and 88.2 kHz seems to work just fine! So I see no reason not to add that option in the next update
Awesome...thanks @j_liljedahl
Ok thanks, I'll look out for the cpu usage
I'm sorry if this has been already answered but how do I midi route multiple AU's loaded in AUM to multiple tracks in sequencers like Genome or Modstep?
https://forum.audiob.us/discussion/12383/channel-selection-in-aum-with-midiflow
MIDI channel filtering will be added in AUM 1.0.1!
Don't have Midiflow I think I'll wait for the update. Thanks.