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.

Are you planning to avoid iOS 11.2.2 ?

I’m at 11.2.1 and just noticed the 11.2.2 update is available, which is supposed to patch up the spectre vulnerability. I’m thinking about avoiding this update ; for one, it’ll keep the option to jailbreak on the table. Also, I’ve heard the vulnerability fix may slow down the CPU — I need to do some research., but I think I’ll take my chances and keep my tablet where its at - everything runs great now and so many previous iOS 11 patches ended up temporarily screwing up certain audio apps or combinations of apps.

Just wondering if you guys are staying put as well, or upgrading?

«1

Comments

  • Upgraded, working fine here on Pro 10.5.

  • I already took the plunge and did a Geekbench benchmark for you to assess the damage :)

    https://forum.audiob.us/discussion/23905/ios-11-2-2#latest

  • I never avoid updates. Prefer my phone to have a reasonable stab at being secure.

  • No. All devices updated. All fine.

  • @brambos said:
    I already took the plunge and did a Geekbench benchmark for you to assess the damage :)

    https://forum.audiob.us/discussion/23905/ios-11-2-2#latest

    Thanks for this.

    @AnimalHeadSpirit said:
    I’m at 11.2.1 and just noticed the 11.2.2 update is available, which is supposed to patch up the spectre vulnerability. I’m thinking about avoiding this update ; for one, it’ll keep the option to jailbreak on the table. Also, I’ve heard the vulnerability fix may slow down the CPU — I need to do some research., but I think I’ll take my chances and keep my tablet where its at - everything runs great now and so many previous iOS 11 patches ended up temporarily screwing up certain audio apps or combinations of apps.

    Just wondering if you guys are staying put as well, or upgrading?

    In this instance I'd rather be secure, even if there is a hit on performance or compatibility - though feedback seems to suggest everything's ok with this one.

  • edited January 2018

    I'll keep my Air-2 in IOS 9 as it works and any 'current' OS will come with a new purchase anyway.
    So called 'possible vulnerabilities' are a mega hype today. Check if your personal situation and real use of the device even apply to it.
    We all know that a hit from a 10 mile block from out of space can happen anytime and mean the end of the world as we know it ;)

  • @Telefunky said:
    I'll keep my Air-2 in IOS 9 as it works and any 'current' OS will come with a new purchase anyway.
    So called 'possible vulnerabilities' are a mega hype today. Check if your personal situation and real use of the device even apply to it.

    Good luck with that!

    https://react-etc.net/entry/exploiting-speculative-execution-meltdown-spectre-via-javascript

  • those bugs existed for a decade without causing havoc, but of course now all self-proclaimed-security bimbos jump the train. What a bore.
    If you dig deep enough 'everything' can be attacked, particularly in those bloated systems as used today.
    The exploits mentioned aren't of the easy kind for an effective real world attack. It's only easy to demonstrate the principle ;)
    If I had significant transaction processes on an internet connected machine, this box would be dedicated to just this task. It would connect to (say) Paypal or online banking services via a direct link and never be used for browsing.

  • Thanks! I'll add "self-proclaimed-security bimbo" to my personal honorifcs.

  • Patches against meltdown already exist in 11.2 so we’re already running some of them. Would like to see a render speed test before and after though.

  • I updated on my iPad Pro. Like it’s reallt gonna matter I never finish off a song anyway. If I’m good for an 8 bar loop then rock on!

  • Reading through the gumpf it seems that impact on newer devices is basically zero but I’m more concerned about my desktop and laptop which have older chips. Pre 2016 intel chips supposedly have noticeable performance hit. Will need to see some benchmarks of these.

  • edited January 2018

    @Telefunky said:
    those bugs existed for a decade without causing havoc, but of course now all self-proclaimed-security bimbos jump the train. What a bore.

    Yep, but now every angry spotty teenage hacker gimp from Llanbadarn Fnydd to Shintotsukawa knows about them.

    @Carnbot said:
    Reading through the gumpf it seems that impact on newer devices is basically zero but I’m more concerned about my desktop and laptop which have older chips. Pre 2016 intel chips supposedly have noticeable performance hit. Will need to see some benchmarks of these.

    I'm doing minimal online PC stuff until desktop's with the new chip are released. This one's 8 years old so I'm due an update anyway.

  • edited January 2018

    @Carnbot said:
    Reading through the gumpf it seems that impact on newer devices is basically zero but I’m more concerned about my desktop and laptop which have older chips. Pre 2016 intel chips supposedly have noticeable performance hit. Will need to see some benchmarks of these.

    +1
    (Edit) Updated Air 2 to 10.2.2, and all seems fine. Negligable difference in Geekbench scores, before & after update.

  • edited January 2018

    @lnikj said:
    Thanks! I'll add "self-proclaimed-security bimbo" to my personal honorifcs.

    Hilarious!

  • edited January 2018

    @Carnbot I'm no compiler expert, but 'guessing instruction chains' might not be that relevant for straight DSP code - on which most of us depend.
    For office apps ? Who cares about 'speed' of them anyway ? ;)

  • edited January 2018

    @Iso said:

    @Carnbot said:
    Reading through the gumpf it seems that impact on newer devices is basically zero but I’m more concerned about my desktop and laptop which have older chips. Pre 2016 intel chips supposedly have noticeable performance hit. Will need to see some benchmarks of these.

    +1

    Well YMMV but i didn't notice any step back at all on my windows laptop. Just played back a mix inside Ableton on 64 buffer/96khz/24 bit featuring a demanding piano library and the CPU/Ram activity is exactly the same as it was before the update.

  • @Keepitsimple said:

    @Iso said:

    @Carnbot said:
    Reading through the gumpf it seems that impact on newer devices is basically zero but I’m more concerned about my desktop and laptop which have older chips. Pre 2016 intel chips supposedly have noticeable performance hit. Will need to see some benchmarks of these.

    +1

    Well YMMV but i didn't notice any step back at all on my windows laptop. Just played back a mix inside Ableton on 64 buffer/96khz/24 bit featuring a demanding piano library and the CPU/Ram activity is exactly the same as it was before the update.

    Have you noticed any increase in latency?

  • @Iso said:

    @Keepitsimple said:

    @Iso said:

    @Carnbot said:
    Reading through the gumpf it seems that impact on newer devices is basically zero but I’m more concerned about my desktop and laptop which have older chips. Pre 2016 intel chips supposedly have noticeable performance hit. Will need to see some benchmarks of these.

    +1

    Well YMMV but i didn't notice any step back at all on my windows laptop. Just played back a mix inside Ableton on 64 buffer/96khz/24 bit featuring a demanding piano library and the CPU/Ram activity is exactly the same as it was before the update.

    Have you noticed any increase in latency?

    That i have a to test today and report back. Like i said, it was a playback, just watching the activity.

  • Thats great thanks.........

  • My air 2 gets updated and pro on 10.3 goes off line.

  • edited January 2018

    @Telefunky said:
    @Carnbot I'm no compiler expert, but 'guessing instruction chains' might not be that relevant for straight DSP code - on which most of us depend.
    For office apps ? Who cares about 'speed' of them anyway ? ;)

    More of a concern for me as I do video moving image/animation and graphics for a living so any performance hit will affect this noticeably even though GPU's won't be affected.

    This will push me to upgrade soonish I expect if the hit is a big one.

    edit: just updated my Laptop with KB4056892 Spectre patch and benchmarked before and after. Lost only 44 Geekbench points and no multicore loss on my i7 from 2012 so looks like it's pretty minimal hopefully all round. Be aware though that some users are having issues with the patch looking at Google...esp AMD chips

  • I just upgraded, loaded and played back my last composition. Auria, multiple tracks, multiple fab filter plugins running on pretty much every track. Never broke a sweat. Is it more than it was before? I can’t tell, but CPU never cracked 50%. No pauses, latency, audio issues, de nada. That’s a pretty quick test, but good enough for me to feel comfortable, because nothing else I do comes close to breaking my iPad like this kind of a mix.

    iPad Pro 9.7”.

  • I also just loaded up the video for the same project in Lumafusion. Didn’t do any editing, but it ran from start to finish without issue.

  • edited January 2018

    Just updated and benched my Xeon desktop and lost 3 or 4% CPU power, that's acceptable and I can get that back from overclocking a little more anyway.

    edit: Ok so did the test again and back to normal so the last bench was just when the Pc was still starting up. So it seems there's no performance hit at all yet unless the patches aren't all rolled out yet.

  • @Telefunky said:
    those bugs existed for a decade without causing havoc, but of course now all self-proclaimed-security bimbos jump the train. What a bore.

    but (almost) nobody knew bout them..

    now every fucking kid can, using javascript, hack into your device.. because it is welll known and easy to reproduce, everybody will try it to found people who give a shit on security updates ...

    i would not risk it..

  • @Telefunky said:
    I'll keep my Air-2 in IOS 9 as it works and any 'current' OS will come with a new purchase anyway.
    So called 'possible vulnerabilities' are a mega hype today. Check if your personal situation and real use of the device even apply to it.
    We all know that a hit from a 10 mile block from out of space can happen anytime and mean the end of the world as we know it ;)

    I absolutely agree on that one. The risk is definitely over hyped; it’s quite minimal for most people, depending on individual circumstances. I’m certainly not a high value target ;)

    I’m usually not overly concerned with protecting iPad ..or even my iPhone for that matter. I keep iOS 10 on my iPhone 6plus and Air 2 , as I’m also not ready to give up all my 32bit apps.

    I’m glad to hear that 11.22 seems to be working great for everyone. I’ll probably wait a while b4 updating my 2017 iPad Pro, making sure no unforseen issues arrise after a few weeks of use;

  • All is well here.

  • OT: Speaking of upgrades, I finally abandoned my long lived & stable Win 7 install, for Windows 10 on my desktop ..Put it off ‘till the last minute , as it appears Microsoft is planning to shut down the free upgrade paths soon .. no regrets though , it seems snappier than 7 on my 3770k quad. Reason 10 seems rock solid stable on it as well.

  • @brambos said:
    I already took the plunge and did a Geekbench benchmark for you to assess the damage :)

    https://forum.audiob.us/discussion/23905/ios-11-2-2#latest

    I appreciate that., thanks.. I’ll probably do the same before I update .. may try a couple different benchmarks on a freshly rebooted 2017 iPad Pro 512., before and after 11.2.2 .. It already looks like my concern with the potential for degraded performance is unfounded.
    -cheers

Sign In or Register to comment.