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.

Have Kaspar? Please help me test an issue I'm having.

Recently AUM and BM3 were updated to get around an issue where instanced AU3 plugins were crashing after instantiating X amount of times. That number seemed to vary depending on model of iPad. Both applications were updated with a work around that I believe loads the interface in the background and allows you to get around this ios bug. It works for me except for one app, Kaspar. I'm hoping that others can help me by reporting how many instances of Kaspar they can load. I'm running a new 10.5" iPad Pro and I can load four instances in AUM and BM3 before crashing on the fifth. I still have plenty of ram available when this happens. Previously there was a thread going about the new iPad Pro's having odd latency and distortion issues. That thread kind of split up into people talking about this instantiating problem along with the latency/distortion issue coming from headphones. In my case the behavior I see doesn't differentiate between headphones or internal speakers. What's really odd is that when the crash happens my audio output gets corrupt. What I mean by that is say I have another app playing audio (not using audiobus or IAA, just something like a streaming music app) that audio will get distorted on the fifth instance of Kaspar until I kill the app that was hosting the AU3.

tldr; How many instances of Kaspar AU3 can you load in your app of choice? Please report back the number of instances, your hardware, hosted app and ios version.

Thanks for your time!

Comments

  • edited September 2017

    Just had time to test this for you before calling it a night. Zzzzzzzzzzz

    Crapped out on 4 instances. 12.9 iPAD PRO (2017)

    :(

    • in AUM
  • edited September 2017
    The user and all related content has been deleted.
  • @SpookyZoo said:
    Just had time to test this for you before calling it a night. Zzzzzzzzzzz

    Crapped out on 4 instances. 12.9 iPAD PRO (2017)

    :(

    • in AUM

    Thanks for testing! What version of IOS?

  • @tja said:
    As curious.

    I tried this slow and secure on an iPad Pro 9.7 with 2 GB RAM.
    Adding the 4th Kaspar, all of them crashed!

    And I too time to select all of them, add keyboard input, change the preset and play something before adding the next:

    Well, I guess it's not an isolated issue with the new models of iPad Pro. I don't think it's related to free RAM either as the 10.5" has 4GB like the 12.9". What version of IOS? If it's a bug in Kaspar I can't wrap my head around how it triggers when instantiated. I guess they share file resources. I'm thinking this is more of an issue with AU3 but I've never developed a plugin. Maybe a developer could chime in on what they think could be going on.

  • edited September 2017
    The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • edited September 2017

    10.3.2

    @rezidue said:

    @SpookyZoo said:
    Just had time to test this for you before calling it a night. Zzzzzzzzzzz

    Crapped out on 4 instances. 12.9 iPAD PRO (2017)

    :(

    • in AUM

    Thanks for testing! What version of IOS?

  • @tja said:
    I think it is memory related.

    There are two types of such Apps!
    One type seems to think there is lots of free RAM, while the other seems to be more accurate:

    Thinks there are 1,5 GB free, which i think is wrong (AUM with 3 Kaspar):

    This seems to be more accurate:

    Here you can see, that RAM is at nearly 100%

    That top line in your first graph is the amount of memory used which is almost at 100% so I think it matches up with your other screenshots. Your crash could really just be memory usage. On my iPad I have about 34% free before the fifth instance crashes. It was surprising to see that with no apps running my iPad was using about 2GB of memory.

  • The user and all related content has been deleted.
  • @tja said:
    I needed to sort the images to fit them to my text, please read again above ;-)

    Haha, I see now! Sorry about that. Weird how it could report that. Which app are you using? I'm using System Status which I think your first couple 'more accurate' screenshots are from.

  • The user and all related content has been deleted.
  • BTW, the AUM developer suggested using iConsole to view the device logs so I'm going to do that when I can get on my laptop. He said it should be obvious if it's a memory problem because it will spit out Memory Warning messages. Who knows, might find something else useful in there as well.

  • Same here, 4 Kaspars good, adding a 5th ghost brings the house down in AUM. 12" Pro / 10.3.3

  • The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • 4 are fine on Air 2, 5 crashes

  • New iPad 9.7 on iOS 10.3.3

    Crapped out on the 5th instance in AUM, AB3, & BM3.

    Cubasis made it to 8 somehow, but had to reload the 4th instance.

  • The user and all related content has been deleted.
  • Usage after crashing on the fifth instance of Kaspar:

    Usage after crashing on the tenth instance of Kaspar:

  • I was able to find some interesting events happening when I monitored the console log.

    Below is what is happening when I load Kaspar and start having issues that eventually crash on the fifth instance. I mainly grabbed the iap2d and UIKit logs because it eliminated a lot of the noise:

    Sep 17 21:15:20 rezidues-iPad iap2d[644] <Notice>: process com.yonac.kaspar.kasparAU is now running the foreground
    Sep 17 21:15:38 rezidues-iPad KASPAR AU(UIKit)[3058] <Notice>: Received memory warning.
    Sep 17 21:15:43 rezidues-iPad KASPAR AU(UIKit)[3058] <Notice>: Received memory warning.
    Sep 17 21:15:50 rezidues-iPad BeatMaker 3(UIKit)[3056] <Notice>: viewServiceDidTerminateWithError:: Error Domain=_UIViewServiceInterfaceErrorDomain Code=3 "(null)" UserInfo={Message=Service Connection Interrupted}
    Sep 17 21:15:50 rezidues-iPad BeatMaker 3(UIKit)[3056] <Notice>: viewServiceDidTerminateWithError:: Error Domain=_UIViewServiceInterfaceErrorDomain Code=3 "(null)" UserInfo={Message=Service Connection Interrupted}
    Sep 17 21:15:50 rezidues-iPad iap2d[644] <Notice>: process com.yonac.kaspar.kasparAU is now suspending
    Sep 17 21:15:51 rezidues-iPad iap2d[644] <Notice>: process com.yonac.kaspar.kasparAU is now terminated
    

    Once Kaspar is suspended my audio goes nuts (includes all audio, not just the main host) and I find these messages spamming non stop until I kill the host app:

    Sep 17 21:15:50 rezidues-iPad mediaserverd(CoreAudio)[25] <Notice>: HALS_IOContext.cpp:1496:IOWorkLoop_HandleOverload:  HALS_IOContext::IOWorkLoop_HandleOverload: Overload on context 1271 current time: 2872614 deadline: 2872596
    Sep 17 21:15:50 rezidues-iPad mediaserverd(CoreAudio)[25] <Notice>: HALS_IOContext.cpp:1496:IOWorkLoop_HandleOverload:  HALS_IOContext::IOWorkLoop_HandleOverload: Overload on context 1271 current time: 2873180 deadline: 2873160
    Sep 17 21:15:50 rezidues-iPad mediaserverd(CoreAudio)[25] <Notice>: HALS_IOContext.cpp:1496:IOWorkLoop_HandleOverload:  HALS_IOContext::IOWorkLoop_HandleOverload: Overload on context 1271 current time: 2874771 deadline: 2874752
    Sep 17 21:15:50 rezidues-iPad mediaserverd(CoreAudio)[25] <Notice>: HALS_IOContext.cpp:1496:IOWorkLoop_HandleOverload:  HALS_IOContext::IOWorkLoop_HandleOverload: Overload on context 1271 current time: 2875327 deadline: 2875316
    Sep 17 21:15:50 rezidues-iPad mediaserverd(CoreAudio)[25] <Notice>: HALS_IOContext.cpp:1496:IOWorkLoop_HandleOverload:  HALS_IOContext::IOWorkLoop_HandleOverload: Overload on context 1271 current time: 2875887 deadline: 2875872
    

    I'm a bit confused why memory warnings are received if I have over a gig free but it helps explain why all the plugins are killed and why my audio output goes crazy until I kill the host.

  • also on an old mini ipad 1st gen: 4 kaspar instances max
    ios 10.3.3. ram and cpu are NOT maxed out when it happens

  • edited September 2017

    @rezidue said:
    I'm a bit confused why memory warnings are received if I have over a gig free

    I haven't read the whole thread, but IIRC plugin extensions get a maximum amount of RAM allotted to them. I'm beginning to suspect this is 'per app' and not 'per instance'. My plugins barely use any memory so I've never been able to reach that limit (it would take many dozens of instances), but it would mean that once you've filled up your share of the RAM, it goes poof.

    As with anything that has to do with the internals of iOS, I can't be 100% sure, but if I had to guess, this would be it.

  • iPad Pro 9.7 on iOS 11, crashes loading 5th instance. brambo’s hypothesis seems reasonable.

  • @brambos said:

    @rezidue said:
    I'm a bit confused why memory warnings are received if I have over a gig free

    I haven't read the whole thread, but IIRC plugin extensions get a maximum amount of RAM allotted to them. I'm beginning to suspect this is 'per app' and not 'per instance'. My plugins barely use any memory so I've never been able to reach that limit (it would take many dozens of instances), but it would mean that once you've filled up your share of the RAM, it goes poof.

    As with anything that has to do with the internals of iOS, I can't be 100% sure, but if I had to guess, this would be it.

    I've been thinking the same with the way that the iap2d logs only mention a single Kaspar for starting up and terminating. Each instance might just be a fork? Thanks for your input.

  • @TheMediocritist said:
    iPad Pro 9.7 on iOS 11, crashes loading 5th instance. brambo’s hypothesis seems reasonable.

    Darn, I was wondering if the behavior will change once I upgrade to 11.

Sign In or Register to comment.