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.
MODSTEP not recording ext MIDI consistently [EDIT] Simple work around found
I am able to trigger elastic drums and animoog with my qunexus through modatep. But modstep isn't recording the notes.
I do have the tracks armed and also the record enabled in the transport. And the LEDS in the modstep I/O screen verify that my qunexus key presses are making it into modstep, which in turn is routed out to elastic and animoog. What gives?
Comments
The pattern you want to record into needs to be "playing" as well. Be sure you've touched it as you would to get it playing if it had notes in
Oops, just read better, you have the track armed. Has to be something in either the track midi input, or in the global settings for midi input. The keyboard and the modstep input are on the same midi channel?
Yes clip was playing @wim
@Processaurus Global settings, device settings, and MIDI channels are all straight away. I verify this from triggering from qunexus and hearing ED or Animoog, depending on which channel i select from QN.
I then unarm the respective channel in ModStep and i no longer hear the instrument. This prooves that modstep is receiving and sending, and me not directly triggering ED or Animoog from qunexus.
I should also mention when recording, i can see the notes appearing in the track, but as soon as i release the keys, they dissapear.
Thanks for your reponse guys
You might be experiencing a bug I had a month ago. Try resetting the iPad completely. Also do the ram trick. (Hold power till slide to power off shows up. Then hold home till it gets you back to the home screen)
It has definetely worked with an earlier version - you may watch my video on that:
I will check with the current version asap
I'm having this issue too. I set up an app using iaa, then send midi from another app sequencer to modstep, modstep then sends the midi to the iaa synth and that works, but it won't record the midi. Disappointing as that's the main thing I bought if for.
Ok so reset the ipad and did the ram thing but no luck.
I emailed modstep support last night, EST.
Yep @RCM , i watched your video just to make sure i didn't overlook something simple, but that is not the case, thanks.
I appreciate you volunteering the time to try again with the later version.
@Blipsford_Baubie - My pleasure
I have tried now with the latest version 1.1.1.0 - and connected an xkey via Modstep to Sunrizer - and it simply works like expected - all notes are recorded as played.
With Animoog it also works, BUT I had to select Midi All Inputs instead of XKey, which isn't obvious of course - perhaps you may try that as well (sorry if my video misleads in that case)
With ED it is important to check the channel (which is usually 10) and also you might have to midi learn the different drum-triggers before you can start playing.
Unfortunately I couldn't confirm with qunexus, because I don't own one.
Have you tried with another Synth - but I don't think that really matters.
Could you try it with another midi device?
Hope that helps - if not I may post another video on the weekend - just tell me
I appreciate your input, but maybe you didn't fully read my original post. I'm having no problems triggering either instrument. It's the recording of the notes. Cheers.
Perhaps I didn't mention that - but - of course I have managed to record as well - sorry if that doesn't turn out of my explanation
Just to prove that it's working here - Animoog recorded with Modstep:
Same here...
Ok I've managed to confirm that it's a bug.
First, I ditched my complicated set-up to test MS with only ED and animoog. Still not recording ext midi.
I then deleted MS and DL'ed it again, and had success with recording midi with the simple setup above!
But when I tried my complicated setup again, MS went back to not being able to record midi again.
Finally I loaded the simple setup that just previously worked, only to find it not recording again.
My more complicated setup consists of AB hosting AUM as an input and Blocs Wave as the output. AUM is hosting ED and Animoog, which is routed to a buss going to Blocks, with another input in AUM coming from Blocks, which then routes to my headphones.
I realize all these variables introduced can quickly become problematic, but let's start with the basics:
I made sure all apps were set to the same buffer size.
Deleted MS again, and worked as expected again after downloading and keeping a basic setup.
This time I created my complicated AB setup from scratch, as opposed to loading the saved template, but still no luck. And again, when closed everything to create the basic setup that just worked...not working again.
its possible that it might be a bug thats been fixed in the betas. we're not allowed to discuss the betas
but i guess its ok to say that my Keith Mcmillan K-board seems to record midi with no issue.
i guess you'll just have to wait for the update to go public. which should be soon i'm guessing....
...and where is Modstep in that complicated setup?
Would love to try that out.
@RCM
Modstep is in the AB input for no other reason than having a quicker way of switching to and from the app and startup. It could just as well work outside of AB for my needs. I realize modtep is capable of much more, but i prefer using modstep as a dedicated midi sequencer and midi recorder since it's the only app that has can have odd numbers of steps AND record midi. Please tell me otherwise if I'm wrong.
I also wanted a dedicated sampler, and I've waited a long time for a sampler than can live sample in sync such as Blocs wave. The Samplr app was the first but sync is unreliable.
But your question gave me an idea to take modstep out of the AB equation to see if i can get it to work.
@gonekrazy3000
Kind of embarrassing, but i completely forgot that I was an early beta tester; before modstep even went on itunes.
I need to check my Test Flight status to see if I can still report bugs that way. I'm sure that'd me faster, cause It's been 3 or 4 days and i still haven't heard back from them since I've reported the bug via their website.
Forget anything I mentioned regarding a complicated setup. I am able to repeatedly recreate the bug using only modstep, elastic drums, and Animoog; where modstep will only record external midi on my first session after deleting and reinstalling modstep. When I close all apps and relaunch again, unable to record ext midi. For consistency I always launch apps in the same order.
Fortunately I never deleted Test Flight from being an early beta tester, so I just sent a more proper report to MS. I had foolishly assumed beta testing ends once an app goes public on the store. So thanks @gonekrazy3000 !
This actually worked for me momentarily for the first time. However I saw that midi in was displayed as coming from my Blofeld, when it was actually Step poly arp app. So I changed it to display correctly and then nothing. Changed it back and then still nothing. Have to restart my iPad to get it to work it seems. This app only works properly for 5 minutes if I'm lucky, it's unless in its current state. And I'm not doing anything at all complex. Another bug I assume...
Yes, i did encounter exactly this as well.
@PMPM. On the new beta version i got yesterday, I'm able to fix the problem by momentarily selectecting ALL for midi input, maybe send a note, then reselect your hardware controller again for input. See if it works on your current version.
@RCM Now that I'm joyously able to record ext midi, can you tell me if you're encountering the following problem?
No external midi is required, for i can do this using the internal keyboard. If the SPEED of the clip is set to anything slower than 1, the keypresses run ahead of the transport, resulting in longer notes being recorder. If speed is set to faster than 1, the keypresses lag behind the transport, resulting in shorter notes being recorded.
@Blipsford_Baubie : Can you summarize again for your first use case? Trying to figure out how exactly it is set up.
Cheers!
Hi Nerk, I'm not sure i understand your question.
Hi @Blipsford_Baubie, just a step-by-step summary for your midi in issues with all associated external hardware and/or apps.
I have experienced problems recording chords from my Alesis Q25 & MicroKorg, via the iConnectMIDI4. Will try it tonight with the nanokey Studio to see if it was merely some feedback issue to do with the iConnect's needlessly over complicated MIDI routing.
hi sleepless , we've met before over this issue .
I'll bet the problem is not your iConnect , as I posted in the Modstep workaround thread , the issue is usb midi in Modstep. I proved this to myself by connecting my same
(modstep only)"problematic" keyboards from their midi din plug instead of direct usb , via my emu 1x1 usb midi interface & suddenly no more stuck notes .
at first I thought this was due to the filtering on the 1x1 , as I knew it filtered active sensing.
however , new info @Nerk_ , I have just also tested with that ubiquitous el cheapo usb midi device I normally wouldnt recommend :
https://www.amazon.co.uk/Proster-MIDI-Interface-Cable-Adapter/dp/B00EYYWGRI/ref=sr_1_2?ie=UTF8&qid=1470673081&sr=8-2-spons&keywords=usb+midi+cable&psc=1
& guess what ..even that stops the stuck notes !
Somehow Modstep prefers receiving midi from the din out of the keyboard , via an external usb midi interface , rather than direct usb thru the CCK .
^^^ so as iconnect has midi dins , try connecting any midi din keyboards via those ,
& let us know .
Ok Nerk. I discovered that I'm also able to recreate the bug with a very simple setup actually. For example, only using modstep and any ios synth or drum app, and in my case quenexus as the controller.
I don't wish to go into detail only cause I'm not a noob, i know how to route midi, and I've been using modstep since before it went public. I realize only a handful of people are encountering this problem, but it is real, and is not a result of forgetting to arm a track, not launching the clip, or improper global settings like most here seem to suggest.
I do realize everybody who has posted here, the only intention is to help, and that suggesting obvious things before real trouble shooting makes sense. I appreciate this, and am merely venting at modsteps inability to perform core sequencing functions while prematurely becoming complicated with AUs and sampling and stuff.
For me, recording external midi will only record when the app is deleted and reinstalled. After that, as in closing the app and relaunching, ext midi still triggers, but only records with the following simple work around: If you select ALL for midi in, and then reselecting your hardware. But i dunno if that will work for the others or on the latest public release.
Also, there is a seperate issue NOT related to external midi with the note length recording not matching the speed of the clip if it's set to anything other than 1. If the clip is playing slower than one, i can see the key press running ahead of the transport bar, resulting in longer than desired recorded notes. If the clip plays faster than 1, keypresses lag behind the transport bar, resulting in shorter than desired recorded notes.
And regarding changing speed, the speed change usually takes effect once i select the clip. I assume this is the intended behavior but doesn't always work. Sometimes my touch doesn't respond with numerous tries. At this point i have to stop the main transport and start again in order to get a response.
I also apologize if any of this has already been discussed in the other thread i just noticed yesterday, Modstep workaround.
Uh oh. Sincerest apologies to @Nerk , for i just took the time to read through the other thread "modstep workaround ". I quoted from there:
"One thing to the betatesters: please do not discuss betas and their bugs here, it is not helping this thread (which is about the current released version) and it is not very fair to us. Please report those bugs to us directly so we can fix them in the next beta"
Being a beta tester who hasn't become proactive until recently, I was not aware of this etiquette. Also, I was unaware i was speaking to a dev. I apologize for being snarky. Kudos to you guys for taking on such an ambitious feat.
@Blipsford_Baubie : No problem, it is just to keep the thread (which is about the released version) useful for people who have the release version. Some people were complaining about bugs that are beta bugs, that´s all. In general it definitely helps to have the easiest description and to check again, if everything is set up correctly (i force myself to do this all the time, because it happens to everyone). So don´t feel offended when i ask those things in order to be able to understand and reproduce
In a nutshell: it´s great to get all the feedback and to be able to squash the bugs, but reporting them directly is still the fastest way to get there.