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
What's with the emoticon AudioGus? Don't act like you never been frustrated by apps that constantly cause grief because I'm sure you've been there before.
I was just sharing my own frustration at the situation.
Thanks for clearing that up. Sorry, I was a bit confused. I wouldn't understand why anyone would feel any other way. Attack Drums is a great app. I get very inspired by it. But at the same time, I get very put off by all of it's issues that prevent me from doing what I want with it. Being without it for 2 months waiting for an iOS 9 felt like an eternity. Then to see what's going on now with it was even more frustrating. I really hope they make it an IAA instrument at the very least. Stating that it's only a generator was a huge slap in the face. Turning it into an AU instrument would be more ideal, as I'm sick of all the issues of IAA. I should really spend more time with Gadget instead of trying to push a square peg into a round hole with Attack Drums, Cubasis, and any other IAA apps.
Yes the latest update does seem to be a step backward on the MIDI and IAA fronts. The MIDI out seems to be working which can make for some interesting layered sounds having 24 tracks of pattern based MIDI and audio tracks you can sync to. Can't get any hardware or apps to control Attack with MIDI.
Please raise a ticket with Waldorf, I have and think they are working on it, but they asked for a video of the problem happening with Cubasis which I don't have, but considering midi in is not working with anything I can't see how they can't replicate the bug with Cubasis or any other app.
@Carnbot just finished sending an email to their support. It seems like some programming oversight as the MIDI out from Attack works fine and the MIDI in is completely broken.
I think it would be hard to show this problem in a video other than configuring the settings in all of the various permutations with the resultant non-response from Attack. Perhaps Attack is suffering from MIDI burn out as it can dish it out, but can't take it anymore?
Am sure they'll fix it soon, midi in was half-working in the previous update so fingers crossed it's a quick fix!
While emailing Waldorf, make sure to let them know that Attack should become an IAA instrument as opposed to a generator, and also let them know that becoming an AU instrument would be even more ideal. It's important for all app developers to realize the demand for AU and the fact that it's more reliable.
AU is more reliable - is that a fact ?
From what I've read in the topic with iSEM running in Multitrack Studio, it certainly is a fact.
https://forum.audiob.us/discussion/10922/big-today-isem-update-audiounit-au-extension-added-11-19-2015/p1
Why an instrument? As a generator it lets you use the built in sequencer, as an instrument it would just be a sound module wouldn't it?
I'm still fairly new to IAA. I've only had my iPad for about 10 months. So I may be missing out on something here. Are you sure that if it were an instrument that it would'nt allow you to use it's internal sequencer?
@BiancaNeve as an IAA instrument you can put it into a host app (DAW for example) and record the midi generating the audio in Attack rather than the audio which takes up less space and can be edited. Many people have found this work flow to be more flexible when creating tracks. An AU is a way to do this and have multiple versions, rather than just one with IAA instrument, of Attack in a DAW project which will also remember all of the settings of the DAW and AU making it even easier to consistently recreate a setup before rendering a mix to audio. I'm not so sure that an app like Attack could work as an AU given the memory limits an AU has under Apple's iOS restrictions.
Errrrrrrr my understanding of an IAA instrument is that the host plays the midi and records the audio whereas a generator doesn't receive midi notes from the host just start stop and record.
Assuming it's working (which I haven't tested) it should be possible to record Attacks midi output via virtual midi.
@BiancaNeve With an IAA instrument, you can have a midi track in Cubasis and have the IAA app as the instrument for the track. When you hit play the midi from the Cubasis midi track is used to control the app. With an IAA generator, you put it as the instrument for an audio track which would create a wave file on the track when you go to record it. Yes you could assign the midi to a virtual midi port on an app and record it that way but the timing might not be as tight and if you had the IAA on the track and recorded, you'd get an audio recording. It would be possible to just name the midi track with the name of the app you're going to control it with but once again you'd have to launch the DAW and the generator app versus ideally it would launch all the IAA apps when you opened your project in your DAW.
You can certainly compose your song in Attack and record the midi out which could mean up to 24 channels of midi. This currently does work in Attack, you just can't play back the midi you've recorded from it into the DAW as the midi in is broken. Some people may prefer the work flow where they compose in the DAW and use individual midi tracks to control each element of the kit. The advantage of this approach is that they just learn how their DAW works and whatever midi controllers hardware and/or software they use to create their midi tracks in the DAW.
Some apps allow you to have the best of both worlds where you compose in the app and then you can import the midi into the DAW as separate tracks. Attack currently doesn't have this functionality But once again the issue becomes how well wil your Attack composition work in your mix with the other elements of your project?
If Attack doesn't get to be an IAA instrument, you could always setup a template of 24 midi tracks and just delete the ones you don't end up using in a particular project.
Recording many channels of midi into one midi track could be quite confusing and may overload the DAW with too much midi leading to crackling, stuck notes, etc. . . and might be why Waldorf is bailing on an IAA instrument implementation as recording the output from Attack to the DAW is relatively straight forward by comparison. Avoiding being blamed for poor audio because of how Attack is structured and how people choose to use it could be a headache Waldorf wants to nip in the bud.
There will of course be people who just want to use Attack like any of their other synths and want IAA instrument functionality rather than do the extra work of learning how to compose within Attack. Unlike traditional drum machines and groove apps which have a specific note assigned to each part of the kit, Attack has a midi channel for the first 16 and use the A and B midi ports to deal with going beyond the standard 16 midi channels with up to 24 hence why there may be some rough road ahead with Attack. One way around this would be to give users the option to turn on a more traditional midi note to kit option with one midi channel which their drums on channel 10 option might be for. Such a traditional approach will likely mean a lot of the detail and texture inherent in Waldorf's current setup could be lost and musicians may then bypass this designed functionality and start thinking, well what's so great about Attack?
@Paul Thanks for the in-depth thoughts and explanations also...very helpful/educative.
I open the app. And it works just fine.
Wait are ya'll still on about iOS, midi, sync, etc not working in this or that whatever app? Even after all these years? LMFAOO ow laawd....
That post wasn't really helpful I just realized. And I'm really sorry about it. Let's just change the subject, zebras. Zebras are awesome.
.
[Had an awesome gif of an awesome man/men in an awesome zebra costume doing an awesome soft-shoe shuffle. Srsly, it was awesome. But it wouldn't upload.]
Not awesome.