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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Attack update here

245

Comments

  • Here is a recording of the difference between playing back the demo track 'All I am is Digital' without IAA and then with IAA.
    (ios 8.4.1 in Cubasis 1.9.7)

  • How is the temple setting? That is too dramatical!

  • Update needs an update. Simples..

  • Same tempo in both Cubasis and Attack... I will try my iPad Mini, also running 8.4.1 and if it is still messed up I will update it to ios9 and see.

    Thanks for your tests!

    @Kaikoo said:
    How is the temple setting? That is too dramatical!

  • Come in Auria Pro, show me what you got!

  • edited November 2015

    I put some notes on your images...

  • @Kaikoo said:
    I have given my 5 stars rating to the store! This is my top drum and music machine. So meaningful for me, more than Korg Gadget for song writing purpose.

    I am looking forward to hearing one of your Attack song in a Song of the Month Club sometime soon :)

  • edited November 2015

    I get the same result on my ipad mini running 8.4.1 and 9.1 as I did on my ipad Air running 8.4. Simply put if I set up Attack as an IAA instrument in Cubasis and try to initiate playback in Cubasis or via the IAA Transport Panel the playback is really messed up. It is in sync, but messed up. Hitting the standard non-IAA play button in Attack does sound fine and the audio can be recorded but then you are not in sync.

    Any Auria folks able to test this? It is easy to try with the track 'All I am is Digital'. I am just hoping when I get Auria Pro it works. 8)

  • @AudioGus said:

    Hi, You need to contact Wardorf. I did a third test, this time I use Air1 ios9.1 to test. I fooled around the recording and played the recording. I pressed recording on Cubasis, I also pressed recording on IAA panel. All in good and excellent conditions. I know you do meet some hiccup, The last resort it to Wardorf for testing. Don't dispointed, cheer up.

  • Hmmm so you never press the #2 button?

    @Kaikoo said:

    @AudioGus said:

    Hi, You need to contact Wardorf. I did a third test, this time I use Air1 ios9.1 to test. I fooled around the recording and played the recording. I pressed recording on Cubasis, I also pressed recording on IAA panel. All in good and excellent conditions. I know you do meet some hiccup, The last resort it to Wardorf for testing. Don't dispointed, cheer up.

  • @AudioGus said:

    I always press Cubasis red button or IAA red button first, then I pressed Attack play button after, which you refer to #2 on the photo.

  • Right, yes that works for me too. But then it is not in sync. Try hitting the #1 play button and you will probably hear it is messed up.

    @Kaikoo said:

    @AudioGus said:

    I always press Cubasis red button or IAA red button first, then I pressed Attack play button after, which you refer to #2 on the photo.

  • @AudioGus said:

    Now I understand more what happened! You are not just record audio track to Cubasis. You actually send midi clock from Cubasis and use IAA to synch audio track. I do use midisetting to connect Cubasis. What's happening is the result like your recording sound.

  • @AudioGus

    I think you was trying record every sigle track, you may meet synching problem. You shouldn't mix up IAA with Midi synch. Because that is complicated.

  • @Kaikoo said:
    @AudioGus

    I think you was trying record every sigle track, you may meet synching problemj. You shouldn't mix up IAA with Midi synch. Because that is complicated.

    MTS developer says clearly, don't mix Midi with IAA in the setting for a track.

  • edited November 2015

    No I am not sending midi. I just want it to work like it should. It should work the same way Egoist or any other 'IAA Instrument' works. Attack seems fine as an 'IAA Generator' but does not work as an 'IAA Instrument' in Cubasis. Maybe it does in Auria.

    @AudioGus

    I think you was trying record every sigle track, you may meet synching problemj. You shouldn't mix up IAA with Midi synch. Because that is complicated.

    MTS developer says clearly, don't mix Midi with IAA in the setting for a track.

  • upgrade one of your pad to ios9.1 to try then. Hopefully everything well.

  • I like this guy's Attack shaking demo.

  • I tried. Did not work. Just emailed Waldorf.

    @Kaikoo said:
    upgrade one of your pad to ios9.1 to try then. Hopefully everything well.

  • Dear users, I have found out why the sound so quiet after loading presets!

    That is because most of the presets sounds have the amplifier velocity setting to too high after initial loading, that is the reason you have very quiet sound when you press your keyboard, so change them back to zero or even to negative.

    See photo, on what velocity button!

  • I'm having issues with the vocoder. iPad Air 2 9.1. When I first opened the app no issues. Later on I closed then reopened it...now when I try to type s a sentence in the box, the text box closes after a few seconds and don't let me type anything :(

  • @Noirflux said:
    I'm having issues with the vocoder. iPad Air 2 9.1. When I first opened the app no issues. Later on I closed then reopened it...now when I try to type s a sentence in the box, the text box closes after a few seconds and don't let me type anything :(

    Same specs, and I was just testing the update by typing obscenities, so re-opened it and didn't have any problems. Does it persist if you load a new song or sounds?

  • Some problems for me on iOS 8.3 can't get virtual midi or IAA to work for Attack with MTS except via channel 10 drum channel only....but virtual midi is working with some apps such as Patterning.

    Also I can't seem to get my midi keyboard working with it easily and it worked ok previously.

  • edited November 2015

    @Carnbot said:
    Some problems for me on iOS 8.3 can't get virtual midi or IAA to work for Attack with MTS excepts via channel 10 drum channel only.....

    True. iOS 9.1 too with MTS.

  • @Kaikoo said:

    On iOS 9 as well?

    Shame, I don't know why it won't work since its working fine with Patterning...Audiobus to the rescue again....

    I am looking forward to the day when I can sequence Attack via MTS, but that day is not here yet :)

  • Can not push too much. Attack is only good on its' own environment. Take times. I already satisfied enough.

  • It looks that parameter automation or Midi CC support hasn't arrived yet to Attack. At least I couldn't find any related info or setting in the app.

  • edited November 2015

    I will probably use the sequencer more again now that it has loop mode but prefer using it as a sound module via other apps.

    working with fugue machine via fugue machine midi out

    Definitely a step forward though, you can now tweak sounds whilst they are played via midi without any workarounds......midi learn hopefully isn't too far away

    Another weird thing midi channel 1 from patterning not recognised...

    Not sure what's going on with midi here....hopefully will be fixed

    Edit: virtual midi options are good too, "selected" mode means you can still change the designated track for the midi input by selecting by touch.

  • edited November 2015

    I sometimes got a crash after loading some factory wave files to tweak the env and velocity of oscillator. I therefore lose my song if I am not saving it. Attack still need more stability fix. IOS 9.1 Air2.

  • Thanks! I found out what the issue is. It doesn't ready my logitech keyboard when it's attached to my iPad. When I'm typing with just the Ipad it works fine.

    @oat_phipps said:

    Same specs, and I was just testing the update by typing obscenities, so re-opened it and didn't have any problems. Does it persist if you load a new song or sounds?

Sign In or Register to comment.