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
@cblomert Looking at the diagnostics, Modstep is reporting an EXC_RESOURCE / WAKEUPS exception type, but not a crash. However, DRC does indeed seem to be what crashed, so it looks like that might be the culprit.
I'd forgotten that I also attempted using MS in conjunction with Studiomux and the latter crashed. Will send the reports, along with the steps used, later.
DRC and Modstep should contact each other for solving the IAA problem.
A bit higher volume would be better for sampler, say another 5 - 10 db to entend the db knobs.
Cheers sleepless! That's what i'm seeing here, too - DRC behaves weird - it does not start after being loaded as an IAA - loading it manually from the iOS screen and afterwards tapping the DRC icon in modstep seems to work though.
If you do not need studiomux for its OSC capabilities, then you can just use modstep alone - it incorporates the exact same audio & midi via usb features and connects to the same server. It would still be great to get the crashlog and steps to reproduce - thank you!
Guys to fix the remaining issues with IAAs/AUs we need your help!
Would it be possible to compile a list of Apps that you are having issues with in modstep?
If possible including type of issue, steps to reproduce & if these apps run better in other hosts like AUM.
We'll work through them one by one and see if we can come up with fixes for the issues. This issue is stealing our sleep - we want our app to be as stable and pleasant to use as possible, and some of the workarounds you guys have to go through are definitely not what we intended!
Thank you!
about the sample volume issue:
Could you try and put the velocity of a note to 127 and see if it matches 0db in other apps?
The default velocity was 100 for notes entered via sequencer/piano roll/drum pads - i've just changed this to 127 to have them play at 100% volume.
Kaikoo: that might be the better idea. We'll add an adjustable +6 / +12db gain.
I should point out I was only incorporating Studiomux to test different workflows but realised straight away it wasn't necessary with Modstep.
@cblomert Should the new templates just be there? Circuit for example doesn't show up in the new update...
@cblomert,
You can ask us for help. Say each 2 days you ask us 5 consecutive alphabetical order on apps to work on IAA by re-awaking them after inserting them to Modstep. And re-sequencing the apps on piano roll for one time to test it is workable or not.
I think 6-7 threads for 14 days, we can roughly understand all the problematic apps. Then its your turn to contact with developers.
After these processes, I think no one should complain about the compatibility issues caused by Modstep inability for connections. It is then the apps' developers responsibility for maintenance.
So there must be a list for problematic apps. So everyones who owned Modstep should do the push on developers. It might be unfair to say all developers should compliant to Modstep. But it does good for any IAA apps users.
Hi @cblomert. Thank you for the response. Modstep doesn't crash, so hopefully I'll try to explain. 1: I open a new project & name it. 2: I choose on track 1(for example) drums on the internal sounds. 3: Arm the track, & the record button, Press play, then the track button & it records nicely, then disarm the track 4: add another track(track 2) & add another internal sound, & do the same as before..... Disarm the track.....No problem. 5: add track 3(as before).... Arm it, press play(making sure record button on the top is active, like normal.... ( I do exactly the same method, as I did in track 1). Now press to activate the track, now its not recording like the other tracks. 6: Stop play, then come out of Modstep(single home button press), then double press home button & swipe up to switch off in the background. 7: open Modstep up again, then make sure track 3 is armed. Press the play, then then track to activate it. Now I can record again. But, when I add another track(track 4) I have to do the same again....... Come out of Modstep, then double tap the home button, then swipe to turn it off complete, and so fourth. This has to be done every time(that's with the internal sounds within Modstep....... Adding IAA is the same problem to record as the internal sounds......... But, once I manage to record a track on a IAA & come out of Modstep to record another IAA track(same way as I recorded internal sounds method). Modstep loads up, then loads the IAA app, but no sound now comes out of the app(but did before), but it the sequence I've recorded is still in the recorded track. This happen all the time. I hope you understand what I've written? Or maybe I need to try and video it?(if I get chance. Lol.)
........ Sometimes I think, "Maybe it's me doing something wrong?".... Any help will appreciated.
Ah, for the IAA reason of no sound, I didn't press the midi out button in IO to the synth(bottom right) but I still have to close down Modstep(background)then restart it up again to record another track still.
@cblomert. I don't know what happened, or how? I deleted Modstep again, then did a hard reset. Then reinstalled Modstep. Now seems to be ok? If this problem happens again I'll video it then place it here. It's like going to a Dentist with a toothache, then when your at the Dentist, the Toothache goes away. You go home, Toothache starts up again, so you go back to the Dentist.......... Guess what, the the pain goes away...... If you get my drift?
I just did a quick and very unscientific test. It seems to me that a few FX apps don't work as expected but most do. For AU's the Blamsoft work fine. RP-1 works fine except when you hit Sync. For IAA's many of the ones I have work fine. Some instruments are more stable than others as well. If they don't "just work" then I'd say the issue is with the app and not ModStep.
I don't think it has to do with being compliant with ModStep but rather the problem apps are not fully compliant with AU or IAA specs. With all the devs involved, some are likely to have taken approaches to their programming that are not quite what they should be.
I think a good idea is a list of problem apps as mentioned.
Hmmmm just uninstalled to try and get hold of the Circuit template and I'm being charged £14.99 to reinstall, that can't be right surely??!
Could you share your audioBus preset?
****> @gonekrazy3000 said:
sure. any particular IAA's you want ? i only own Gadget,Im1,Terasynth,Lorentz,Moog model 15,Fm4, elastic Drums, Thumbjam(its pretty much muted. i only use it for appregiator processing), StepPolyArp(same as Thumbjam),Fuguemachine and Aufx(all 4). rest of my apps don't really support midi in Like Blocs and Patterning.
FM4 kind of makes everything go haywire. It resets all the midi outs to FM4 and then just stops making sound. It might matter that this the fourth IAA app added.
When using RP-1 Delay as an AU in ModStep, selecting Sync shuts down audio. When using RP-1 in AUM it works as expected.
In ModStep or AUM it works as expected as an IAA.
Yes, I'd love to see that too. So Modstep routes the midi where? Where does this chain of wonder end?
To everything. It's kept separate from Aum and audiobus. But it sends its midi to everything.
I guess what I mean is: from instrument to end product, what is the path? I can't escape the idea that all the instruments must somehow travel to a giant Studer two-track for a final mix. It's a metaphor that is both unhelpful and resilient.
@ExAsperis99, you're going to continually stumble until you learn to separate MIDI and Audio in your thinking once and for all.
ModStep routes the MIDI wherever you tell it to.
The Audio routing is dependent on what is hosting the instrument.
Hope that helps...
I don't see that behavior in my testing. Any chance you could send a screenshot of the ModStep io settings?
I did see that FM4 was picking up more MIDI channels than I wanted. To get past that, go to FM4's midi settings and select just one channel rather than omni. You c also disable all devices except ModStep if that still isn't enough.
midi doesnt need a path. just modstep=>app port
example modstep track1=>gadget channel 1. even if gadget is hosted in AUM its the same.
Audio and midi are seperate. please stop thinking they're the same. Audiobus,Aum. its only for audio.
midi can jump directly to the apps ports. irrespective if the app is hosted in an App like Aum or audiobus or even if the app is running by itself.
@Nerk_, @cblomert
Thanks for the update and all your hard work.
One bug: The option "Auto start IAA apps" is not working. ModStep auto loads all the IAA's on startup regardless of how this is set.
I've yet to take the plunge to get ModStep and will honestly wait until we can use soundfonts/samples (preferably record and edit them too) as an oscillator in the synth to play samples across the keyboard.
I've however grown pretty fond of the sequencer built-into NTBYF and love the fact that it's possible to play multiple patterns on the same track at once (Think different drum-sounds in individual patterns for easy on/off for fills etc.).
The 'bigger brother' (Infinite Looper) also has a nice way to chain selected patterns into a song.
So the question is. Is it possible to play multiple patterns on the same track at the same time?
(ModSTEP seems to be too 'scene-focused' to obviously allow this).
As I've understood ModStep does not yet have a 'song mode'. Is a song-mode in the works?
Sorry for hijacking the thread...
nope. its basically ableton live. you can technically do the same by having multiple tracks sending their midi to the same synth. example track1,2,3,4,5,6 all sending midi to gadget port 1 hosting darwin or something polyphonic. then when you trigger clips on each of the track its creates rhythmic complex patterns.
Ouch! This practically means that if we have an app as IAA-Instrument inside ModSTEP the patterns have to be duplicated for each 'combination' of sounds. (This is a 'limitation' I don't like about Ableton Live Lite either).
Who knows maybe a future update will enable this functionality as it's something that is pretty darn handy.
Instead of duplicating a pattern just add or drop layer(s) on top of it. (Too used for 'Folder Tracks' in Logic).
MidiLooper does this perfectly but is limited to 6 tracks
I know it's cumbersome. But both Live suite and modstep have infinite tracks. So it isn't really a problem. Just create 1 track with all the patterns you want and then duplicate the track itself as many times as you want.
I do modular midi processing this way all the time so I guess I'm used to it. For example in ableton I once had 8 instances of cthulhu accepting the same chord sequence but playing 8 different sequences with different time signatures and swing all feeding into 1 synth. It creates stuff you will never believe is basically appregiators....
Yeah that's my setup too. But it feels heavy, like I shouldn't have to have three "hosts" running. Not sure what the future holds but I think at some point we won't need all three.