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
sorry, never mind... I completely forgot that this iPad runs IOS 8.1.3 ...
in fact background audio doesn't work at all, can't even send midi from another app
(results in the typical non-synced distortion that apps produce when they 'think' the interface lost connection)
no need to track that one down
but DRC definitely fills a gap in the sound palette with it's very own character
on the midi page it looks like you select a control and it waits for incoming data for assignment
(which seems to be a common practice today)
I'd much appreciate a simple entry box to type in the value manually
for obviois reasons the current method is quite tricky if the controller is sent by software
cheers, Tom
You really should upgrade to iOS 9.32. It's better than iOS 8 in every way for audio and midi. iOS 7 is still better for 32 bit devices but even on them iOS 9 is better than 8.
tnx for the hint, but I actually have another iPad running 9.3.2
the one under IOS 8 is my recording device and first of all 'conserves' a specific version of BIAS/JamUp
you'll never know with what crap Positive Grid may spoil the party via an 'update'
(in the past they did several times - and people already complained about BIAS FX quality)
yet I found it cool the 'old' device recognized the iConnectAudio's io-ports and simply worked
(except some background/idle stuff as mentioned above)
usually this iPad is connected to an Audient ID22 for tracking guitar/vocals
the ID22 is class compliant, but not specifically supported by it's manufacturer
(which means all io is active and usable, but lacks routing configuration under IOS, no biggie...)
but the ID22 has outstanding microphone/instrument preamp stages
clearly a class above the iCA4+, at least 10dB less noise effectively, which is huge with acoustic sources
otherwise I really love the iCA's functionality and it's perfectly ok with line level input and monitor out
to be honest:
the ID22's output is so uncompromisingly dry and precise, that the somewhat flattering iCA is more pleasing
(my main headphones are classic AKG K501s, so this would be just too much analytics...)
cheers, Tom
I have a question. I have recently implemented program change (CC0). Should this CC be available for midi assignment or not? What is your experience? What would you expect? Thanks!
no own experience, but it may be a crucial feature for those controlling their rig via software like Onsong...
cheers, Tom
Being able to assign CC 0 or not?
I don't use that much midi - just notes from an entry device/sequencer and CC
didn't even know that CC0 can be used for program change
(and considered PC a dedicated midi command)
but it's certainly useful to have an option to select a preset via PC
at least it's frequently mentioned by people who control their stage gear remotely
(in virtual amp simulations the feature often is not present, so they complain)
cheers, Tom
DRC 1.0.5 released:
Wow, Nuno thanks a lots.
Thank you, sir!
Always great to see a developer on the case....thanks for the update. Particularly happy about 'last preset state' being saved.
Awesome update, awesome app. 5 stars. Thanks again.
Thank you for the update:). The velocity control of amplitude and filter are now working for me with TC-Data.
@sinosoidal
Still crashes upon loading in Cubasis...
@Littlewoodg @sinosoidal I was able to open DRC and play in Cubasis 1.9.9 on an iPad Air 2 running iOS 9.3.2 using the DRC keyboard and the built-in Cubasis MIDI keyboard without any issues. I closed and opened Cubasis and the setup worked again.
Weird- Ima hafta keep deleting and reinstalling. The beta was doing the same thing.
Nope. Deleted Cubasis, (pita, 12 kits to save elsewhere and reinstall) deleted DRC, reinstalled..."open" DRC, device goes to home screen, DRC unreachable from Cubasis, delete DRC and close from background, select again in Cubasis, same cycle starts again...
Anyone else using DRC in Cubasis?
Or Modstep (IAA glitches there too, DRC reboots when selected from Modstep home screen after set into a track)
The 'workaround' for getting DRC to work with Cubasis is to start DRC first and then load it up in Cubasis...
If none of the apps are running and a project uses DRC launch DRC first and then start up Cubasis.
Don't know if Cubasis 2.0 will have 'improved' way of loading IAA nodes so we'll have to wait and see until it's released
Tried workarounds (open DRC first, also route audio track from DRC, send midi "no instrument" style. Still no luck.
In software doesn't work is relative. There are too many variables. We need to find a pattern. Something that could lead us to a conclusion on why it works on some scenarios and others don't. Let's start with iOS device model, iOS version, apps version.
For iOS audio I'm relying on The Amazing Audio Engine, which is a audio lib created by the same guys of Audiobus. It is a standardised way of creating inter-app audio ports, handling with audio things, etc. I don't have many things to to play with besides the initialisation of the lib and when it starts or stops. For instance, on the first versions of DRC I was starting it even more late and it was giving problems loading within Cubasis. Since I moved the initialisation of the ports to a place more close to the beginning of the program, it started working. This also depends on how the host has programmed the inter-app audio support inside.
Everyone who is experiencing problems, please answer the following questions. I will build a table with the answers. Let's see if we can find anything mean-full.
Use DRC as IAA-Instrument...
First class synth with amazing support.
Strangely Im not a big fan of DRC to be honest. It' s a decent synth but too EDM or Indus for me .I would prefer something like TF7 or ipolysix or ns1 , i think Im stuck in the 80's However Im only 40 y.o
@Samu ,is it the same process for the others synth in cubasis ? Cause a lot of IAA dont appear in the list of midi instrument like Ielectribe, ipolysix ,ims20 and many others.That's a big problem with cubasis
Yepp! That's one of the 'best' work-arounds that works for almost any IAA-App.
Even apps like AUM can not load all IAA-Synths and recommend this work-around for those that do not work directly.
AUs on the other hand do not suffer from this and that's why many are requesting AU updates to existing apps to work around the problems caused by IAA.
The IAA 'error' handling is up to the host that loads the IAA-Node and there is very little an app-developer can do other than try the best they can to follow 'best practices' (http://lijon.github.io/inter-app-audio.html).
No
No
Cubasis, AUM, mod step / latest versions
Air One / latest
Is it supposed to be an IAA instrument? Or just a generator?
IAA-Instrument.
Did do (thought I said that, sorry) and also loaded it using a workaround that works for IAA apps that are instruments that Cubasis doesn't list as instruments...which involves a trick learned from @sirdavidabraham in which the offending app is loaded as IAA audio source, and a midi channel ("no instrument") is set up to send midi notes to it via virtual midi, or by name...nada
Me: No, No, Cubasis latest. Air 2 latest
Additional info: during DRC beta, in Modstep beta build, DRC loaded, wouldn't rains to its own I/o from Modstep, but could be used with a workaround in which the "in" was set as Modstep rather than DRC. This worked unless I used another app at the same time that required the same workaround (seperate channel assignments don't help, though the same workaround with other apps the channel assignment is effective in keeping info flowing to discrete apps)
OK. After an excellent evening with DRC — and using what appeared to be a kind of transport in the top left corner of the app! — DRC is now pulling shenanigans.
It simply won't load in modstep. Tried to load song from last night. Didn't work.
Restarted iPad. Opened modstep (apps include Yahmaha AN15, Sunrizer, ThumbJam, DRC). All make sound (except DRC) but the tempo of the AN15 arpeggio is wonky, and I realize DRC is bleeding into it. Delete DRC from track, and the arpeggio is correct again.
Delete all apps; restart iPad.
Open DRC first.
Open modstep and all the apps appear in their correct tracks, but now the tempo is at 120! (This is the default DRC tempo.) No sound from DRC. Clicking on the app icon in modstep simply spins the wheel but doesn't bring up DRC. Manually open DRC and check midi info. The "transport" from the previous evening is gone! Modstep is listed in the midi options with a checkmark listed next to it. But back in modstep the app will not load.
Delete all apps; restart iPad.
Open DRC first. Set tempo to 106. Open modstep track, and now the tempo is the correct 106, so obviously if DRC is open first it is somehow governing modstep. Tried to get DRC to play in modstep; failed.
Deleted it from track and replaced it with Laplace, which works fine.
Very weird, I know. Especially the phantom transport! But I swear I tapped a back-arrow-looking thing that sent me to modstep. You've go to believe me, Officer!