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.

(removed)

edited March 2023 in General App Discussion

removed

«1345

Comments

  • Thanks so much for the pre-release demos. This is a great series. Congratulations.

  • I don’t usually do Pre-orders but I have some credits now and I may NOT on the 12th so.

    Yamaha, Kawai. I hope there’s a decent Casio too. Oh… real pianos. Never mind.

  • edited March 2023

    jason said:

    The “try before buy” version is here: https://testflight.apple.com/join/6CrAr8yb
    It is binary identical with the release.

    That version works well on my iPad 9th gen, on my 8th gen as expected it has some troubles. On my MacBook Pro it works perfectly as a standalone but there is no sound in GarageBand as a plugin.

  • I think when used as a plugin in GarageBand your piano doesn’t receive the midi from GB. In the standalone there is a setting to select my midi keyboard that I had to activate. This setting doesn’t show up in GarageBand.

  • edited March 2023

    It is interesting’ on the 8th gen iPad it works at first, no glitches, but it is like randomly some notes go into some kind of loop, then it makes a weird noise, and then it either crashes or resume to normal.

  • I have absolutely no idea what this means. It works great on 9th gen so I’ll just wait for it to work on my MacBook and pay full price which is still pretty inexpensive for a good iOS piano.

  • jason said:

    @jo92346 said:
    I have absolutely no idea what this means. It works great on 9th gen so I’ll just wait for it to work on my MacBook and pay full price which is still pretty inexpensive for a good iOS piano.

    ps. you should download the other models too. I think the Imperior and the Xcelsior will fit you.
    The links are in another … wait I will copy here …

    TESTFLIGHT (super universal macOS / iOS):

    JAX Superior Grand: https://testflight.apple.com/join/n0dXotQk
    JAX Emporeor Grand: https://testflight.apple.com/join/6CrAr8yb
    JAX Imperior Grand: https://testflight.apple.com/join/WkQFo2JP
    JAX Xcelsior Grand: https://testflight.apple.com/join/aUpmFrmD
    JAX Xperior Grand: https://testflight.apple.com/join/bcxhol3D
    TRY BEFORE BUY!
    We do not like returns (for what reason ever) at all.
    Please note that TestFlight apps are time limited.

    Awesome, can’t wait to try these out. Big fan of your apps and Superior Grand, I’m sure these will be just as great.

  • Have to say, I am EXTREMELY impressed with the sound and responsiveness of this Emporeor piano, especially with a bit of tweaking of the volume, release etc and added sustain. Preordered. Blows the Pure Piano apps into the dust imo. 👏 👏 👏

  • edited March 2023

    Well my 9th gen iPad is just good enough to play very simple things. As soon as I let my left hand do something a bit frantic and use the sustain pedal my poor iPad shows he is not up to the task. Guess I’ll have to buy a new one to really enjoy these pianos.

    It works perfectly in the MacBook Pro though. Gonna work on some demos for the emporeor.

  • If there was ever an app that will get me to finally upgrade my iPad, this'll probably be it. Sounds great and doesn't take up too much space. I should be able to get rid of enough other pianos to make it a wash. But too much polyphony puts the CPU usage over the top. That's understandable and I'd rather have the quality even if it means committing to audio more often.

    One thing on the beta though. In AUM too much polyphony just causes under-runs. But in Loopy Pro (my main host) it dies an unhappy death. Audio cuts out and does not come back until I restart Loopy.

    Still pre-ordering though. 👍🏼

  • wimwim
    edited March 2023

    I'm on a decrepit old iPad Air 2, A8X chip. I don't expect it to hold up or you to support it. I'm just providing data for you, and also pointing out the difference when using Loopy Pro as a host.

    It's pretty rare that I can successfully play with more than three fingers at a time anyway.

  • wimwim
    edited March 2023

    jason said:
    I really hope, I can improve the performance for older devices. A similar problem was reported with MIDI Module&Player. But this one is just using Apples own frameworks under the hood. So I am really wondering why this uses so much CPU on older devices…

    This is why developers should always be issued only old equipment. ;)

    The better stuff they have the less efficient their apps become. I know. I supported developers for 35 years. Needless to say, I wasn't the most popular IT Director in the world whenever I would half jokingly point this out. 😂

    Since I'm such a good guy, I'll offer to swap devices with you if that'll help.

  • I wouldn’t recommande the A12 as absolute minimum. My 8th gen iPad can only play very simple things before showing its limits.
    A13 is the absolute minimum in my opinion for live play on the standalone app.

    I’ll have to order a pro to really work with your piano on iPad if I want to do something else than live playing. In a multitrack composition the A13 is also not powerful enough.

    That is the price to pay to have one of the best pianos.

  • jason said:
    The Emporeor was by the way our ‚problem child‘.

    I was just long time not satisfied with the sound. It was, that the typical Yamaha sound is extraordinary difficult to emulate satisfactory. But I think for the release we did our best. We still will improve all the timbres with version 2 of the collections.

    That is interesting because after testing them all the emporeror is definitely my favorite despite my personal taste going for more somber tones.

    Is it a perfect Yamaha emulation? Of course not. The only way to have perfect Yamaha emulation is to buy a C series at least. Which is barely more expensive…… Does your app (costing 1/1000th of a C6) sound 1000 times worse than a C6? Definitely not.

    You did an impressive job.

  • @wim said:

    jason said:
    I really hope, I can improve the performance for older devices. A similar problem was reported with MIDI Module&Player. But this one is just using Apples own frameworks under the hood. So I am really wondering why this uses so much CPU on older devices…

    This is why developers should always be issued only old equipment. ;)

    The better stuff they have the less efficient their apps become. I know. I supported developers for 35 years. Needless to say, I wasn't the most popular IT Director in the world whenever I would half jokingly point this out. 😂

    Since I'm such a good guy, I'll offer to swap devices with you if that'll help.

    We definitely need a "humor" font. The "smileys" tend to be ignored.

    Considering the usual complaints about "planned obsolescence as Apple continues to upgrade chips, busses and it's OS'ed I'm pretty happy with Apple's ability to provide new
    platforms that kick ass while supporting a lot of apps created years ago. I do still have
    1 older iPads to run "BeatMaker 1" and some other inbetween app that got kicked off my
    M1 iPad. Roland SoundCanvas might be in that category. I have SoundCanvas on my iPhone still so owning it won't give me access on the M1 iPad in the App Store. Too bad. That Roland app is an ideal target for General Midi stuff... KQ Sampei is a great alternative along with the steady BS-16i.

  • edited March 2023

    just downloaded test flight to try this out !! Real good so far... was waiting for pianoteq but, must say that after a few mins i preordered. will upload an example in a few

    posted here

    https://forum.audiob.us/discussion/54686/screen-kiss-thomas-dolby-jax-emporeor-grand-piano#latest

  • jason said:

    @McD said:

    @wim said:

    jason said:
    I really hope, I can improve the performance for older devices. A similar problem was reported with MIDI Module&Player. But this one is just using Apples own frameworks under the hood. So I am really wondering why this uses so much CPU on older devices…

    This is why developers should always be issued only old equipment. ;)

    The better stuff they have the less efficient their apps become. I know. I supported developers for 35 years. Needless to say, I wasn't the most popular IT Director in the world whenever I would half jokingly point this out. 😂

    Since I'm such a good guy, I'll offer to swap devices with you if that'll help.

    We definitely need a "humor" font. The "smileys" tend to be ignored.

    Oh. then I misunderstood this?

    I think each of the statements was "tongue in cheek" with an opposite meaning of the words used:

    This is why developers should always be issued only old equipment. ;)

    @wim is a programmer so he knows the benefits of using the most current gear due to
    Moore's Law of 2 x performance at the same (usually) price.

    The better stuff they have the less efficient their apps become. I know. I supported developers for 35 years. Needless to say, I wasn't the most popular IT Director in the world whenever I would half jokingly point this out. 😂

    Now this is a true statement: better performing gear takes the pressure off the developer to
    optimize the code.

    Since I'm such a good guy, I'll offer to swap devices with you if that'll help.

    and back to a proposal only an idiot would accept.

    Carry on.

  • wimwim
    edited March 2023

    jason said:

    @McD said:

    @wim said:

    jason said:
    I really hope, I can improve the performance for older devices. A similar problem was reported with MIDI Module&Player. But this one is just using Apples own frameworks under the hood. So I am really wondering why this uses so much CPU on older devices…

    This is why developers should always be issued only old equipment. ;)

    The better stuff they have the less efficient their apps become. I know. I supported developers for 35 years. Needless to say, I wasn't the most popular IT Director in the world whenever I would half jokingly point this out. 😂

    Since I'm such a good guy, I'll offer to swap devices with you if that'll help.

    We definitely need a "humor" font. The "smileys" tend to be ignored.

    Oh. then I misunderstood this?

    Yes. I was just playing with you. B)

    But there is a small grain of truth to it. If all you had was an Air 2 to work with or that was the latest available, your development outlook would be undeniably different. I don't say that is a good thing. Because then we wouldn't have such a Superior (pun intended) sounding piano available to us.

  • jason said:

    @McD said:

    jason said:

    @McD said:

    @wim said:

    jason said:
    I really hope, I can improve the performance for older devices. A similar problem was reported with MIDI Module&Player. But this one is just using Apples own frameworks under the hood. So I am really wondering why this uses so much CPU on older devices…

    This is why developers should always be issued only old equipment. ;)

    The better stuff they have the less efficient their apps become. I know. I supported developers for 35 years. Needless to say, I wasn't the most popular IT Director in the world whenever I would half jokingly point this out. 😂

    Since I'm such a good guy, I'll offer to swap devices with you if that'll help.

    We definitely need a "humor" font. The "smileys" tend to be ignored.

    Oh. then I misunderstood this?

    I think each of the statements was "tongue in cheek" with an opposite meaning of the words used:

    This is why developers should always be issued only old equipment. ;)

    @wim is a programmer so he knows the benefits of using the most current gear due to
    Moore's Law of 2 x performance at the same (usually) price.

    The better stuff they have the less efficient their apps become. I know. I supported developers for 35 years. Needless to say, I wasn't the most popular IT Director in the world whenever I would half jokingly point this out. 😂

    Now this is a true statement: better performing gear takes the pressure off the developer to
    optimize the code.

    Since I'm such a good guy, I'll offer to swap devices with you if that'll help.

    and back to a proposal only an idiot would accept.

    Carry on.

    ...

    I mean, I did grow up with Assembler language and did optimize many of my DSP codes manually in my entire life... But Apples development platform is different. It is in fact generally such a closed and opaque framework mess, that nobody really is even able to optimize something with that at all. So you just are forced to use that and keep with the latest updates and the supposed devices.

    Well, in fact @giku_beepstreet does exactly that in his Drambo app: Optimized ARM assembly code for the most relevant DSP parts, so large projects will still run on iDevices that cannot go beyond iOS 12 for example.
    Somehow he must have managed to go through the "framework mess" ;)

  • @rs2000 said:

    jason said:
    ...
    I mean, I did grow up with Assembler language and did optimize many of my DSP codes manually in my entire life... But Apples development platform is different. It is in fact generally such a closed and opaque framework mess, that nobody really is even able to optimize something with that at all. So you just are forced to use that and keep with the latest updates and the supposed devices.

    Well, in fact @giku_beepstreet does exactly that in his Drambo app: Optimized ARM assembly code for the most relevant DSP parts, so large projects will still run on iDevices that cannot go beyond iOS 12 for example.
    Somehow he must have managed to go through the "framework mess" ;)

    There is truth there though. There is little financial incentive for Apple to make it easier to support older hardware. Of course they're going to subtly drive both developers and consumers toward needing newer equipment. That's to be expected.

  • Tested all of them out for a while today and man they’re all excellent sounding. I did have trouble getting them to work in Audiobus but it worked just fine in AUM and standalone.

  • edited March 2023

    @wim said:

    @rs2000 said:

    jason said:
    ...
    I mean, I did grow up with Assembler language and did optimize many of my DSP codes manually in my entire life... But Apples development platform is different. It is in fact generally such a closed and opaque framework mess, that nobody really is even able to optimize something with that at all. So you just are forced to use that and keep with the latest updates and the supposed devices.

    Well, in fact @giku_beepstreet does exactly that in his Drambo app: Optimized ARM assembly code for the most relevant DSP parts, so large projects will still run on iDevices that cannot go beyond iOS 12 for example.
    Somehow he must have managed to go through the "framework mess" ;)

    There is truth there though. There is little financial incentive for Apple to make it easier to support older hardware. Of course they're going to subtly drive both developers and consumers toward needing newer equipment. That's to be expected.

    Definitely. And that makes me value apps that still support older iDevices even more.

    Anyway, you've built a wonderful app jason.

  • I've noticed that playing one of the built-in MIDI files can make radical changes to the sound of the instrument. These are not reflected in the on-screen knobs. The only way to get back to "normal" is to restart (or reload) the app. We need to be sure we're testing a clean copy of the app.

  • This is already available on the store, and sounding great

  • @szczyp said:

    Sounds great! 👏🏾👏🏾

  • @ninobeatz yes! And there are many different models inside the app, I still feel like on first date with beauty, I dont know her deep yet but I ❤️

  • edited March 2023

    If you had made app in 2018. Or whenever ipads with the 12 or 13 chip were made.

    Would the cpu usage be the same etc.

    Is this the required chip for pianos in general because piano needs a low buffer setting ?

  • Is the Xcelsior already available for presale?

  • @sigma79 said:
    If you had made app in 2018. Or whenever ipads with the 12 or 13 chip were made.

    Would the cpu usage be the same etc.

    Is this the required chip for pianos in general because piano needs a low buffer setting ?

    Question is not to me, but I have iPad Pro 4-th so chip is it M1, and I use 128 buffer (smallest in Drambo).

This discussion has been closed.