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.

SWAM Instruments & LP4i

2

Comments

  • SWAM French Horn + Bass Flute works fine, but as soon as I add SWAM Tenor Sax, LP4iOS crashes.

  • @HarlekinX said:

    @Samu said:
    Could this be one of those M1 vs M2 issues?

    No, tested also on my secondary iPad with A12X processor.
    Same behavior.

    I'm on M2 as well.

    Ok the plot thickens: no crashes on 17.1, but I just finished updating to 17.2 and it instantly crashed after loading up that same SWAM project and hitting play (CPU usage bar was pegged to the red).

  • I’ve also forwarded this thread to Audio Modelling

  • Surprise, surprise, the Cubasis 3 SWAM quartet works flawlessly. CPU was bored at 12% of usage, all instruments were automated.

  • @Samu said:
    Time to 'bombard' here until it gets fixed?
    https://www.apple.com/feedback/logic-pro/

    Done.

  • Just to let you all know, and especially @Luxthor that Audio Modelling have been in touch with me. They are able to reproduce the crash in LP4i and are actively working on a solution. Great news!

  • @BillS said:
    Just to let you all know, and especially @Luxthor that Audio Modelling have been in touch with me. They are able to reproduce the crash in LP4i and are actively working on a solution. Great news!

    Perfect, Thanks!

  • @BillS said:
    Just to let you all know, and especially @Luxthor that Audio Modelling have been in touch with me. They are able to reproduce the crash in LP4i and are actively working on a solution. Great news!

    Yes! I can’t wait. 🤞 Thank you!

  • I sent my project to Audio Modelling and got this response. Not done anything with it yet, as I’m not sure what steps are needed to get the menu in the image:

    _**I can see that both parameter automation and MIDI automation are applied to the same parameters (expression and vibrato).
    As workaround please try removing the parameter automation and keep only the MIDI automation (see the screenshot attached).

    Let me know if this can help.
    In the meanwhile we will try to improve the stability of out products.
    **_

    https://drive.google.com/file/d/1mW97-UHQ4C6SljYJfKS4PwJLN4evlIcp/view?usp=drivesdk

  • There should be a public release to fix this issue very soon. I have tested the beta version today and it is working perfectly for me in Logic Pro.

  • edited January 9

    @BillS said:
    There should be a public release to fix this issue very soon. I have tested the beta version today and it is working perfectly for me in Logic Pro.

    Great to hear. Thanks for keeping us posted.

  • @BillS said:
    There should be a public release to fix this issue very soon. I have tested the beta version today and it is working perfectly for me in Logic Pro.

  • edited January 21

    Any news on this front? I'm currently working on a song with violin and cello and it freezes every time I attempt to export.

  • @bluegroove yeah, I see on the App Store it’s still on version 3.7.2. I have the beta of 3.7.3 which has been working great since I downloaded it almost two weeks ago. I’m sure there’s a good reason why it’s not on public release but if you email them at [email protected] I’ve found them very helpful.

  • edited January 22

    @BillS said:
    @bluegroove yeah, I see on the App Store it’s still on version 3.7.2. I have the beta of 3.7.3 which has been working great since I downloaded it almost two weeks ago. I’m sure there’s a good reason why it’s not on public release but if you email them at [email protected] I’ve found them very helpful.

    Thank you, looking forward to that release.

  • It looks like everything is fine after the 3.7.3 update. My test project in LP4i is not crashing so far. 🤩

  • @Luxthor said:
    It looks like everything is fine after the 3.7.3 update. My test project in LP4i is not crashing so far. 🤩

    Ah, at long last it’s been released! My pre-release version of 3.7.3 has been working fine since January!

  • Best news I've heard in awhile!

  • It looks like SWAM instruments are unable to record automation from the SWAM interface in LP4i2. But it works just fine from the plugin tile.

    Then again, it works perfectly fine in Cubasis. 🫣

  • @Luxthor said:
    It looks like SWAM instruments are unable to record automation from the SWAM interface in LP4i2. But it works just fine from the plugin tile.

    Then again, it works perfectly fine in Cubasis. 🫣

    Yep, just tried the demo of LP4i for my workflow and the first thing I’ve got is the automation bug when LP4i doesn’t capture SWAM faders from their UI. Is there a possibility to add other parameters to the tile window as an ad hoc solution?

    P.S. I can’t understand why do iPad DAW developers concentrate their efforts on AI, billions sound libraries and built-in plugins instead of doing basic things well first.

    (At least Apple implemented tempo / time signature track from the very beginning. So we have at least hope that they will fix SWAM automations writing)

  • @vlaoladis said:

    @Luxthor said:
    It looks like SWAM instruments are unable to record automation from the SWAM interface in LP4i2. But it works just fine from the plugin tile.

    Then again, it works perfectly fine in Cubasis. 🫣

    Yep, just tried the demo of LP4i for my workflow and the first thing I’ve got is the automation bug when LP4i doesn’t capture SWAM faders from their UI. Is there a possibility to add other parameters to the tile window as an ad hoc solution?

    (At least Apple implemented tempo / time signature track from the very beginning. So we have at least hope that they will fix SWAM automations writing)

    I don’t think it’s only Apple’s fault, because for other AUv3 automations, the interface works perfectly. Here is an example of a KingB WAH pedal. 

    Plugin tiles are such a good feature, but they are implemented only to promote internal stock plugins. As far as I know, third-party developers can only choose access to the three key parameters, and that’s all.

    P.S. I can’t understand why do iPad DAW developers concentrate their efforts on AI, billions sound libraries and built-in plugins instead of doing basic things well first.

    Because of the marketing fanfare. 💰;)

  • edited June 2

    @Luxthor said:
    It looks like SWAM instruments are unable to record automation from the SWAM interface in LP4i2. But it works just fine from the plugin tile.

    Then again, it works perfectly fine in Cubasis. 🫣

    In LogicPro for iPad 2 set the Internal Midi to the Instrument Output of the Swam plug-in and it should record just fine.
    (This is how I record MPE from GeoShred).

    As for GeoShred they did overhaul the automation portion of the plug-in.

  • @Samu said:

    @Luxthor said:
    It looks like SWAM instruments are unable to record automation from the SWAM interface in LP4i2. But it works just fine from the plugin tile.

    Then again, it works perfectly fine in Cubasis. 🫣

    In LogicPro for iPad 2 set the Internal Midi to the Instrument Input of the Swam plug-in and it should record just fine.
    (This is how I record MPE from GeoShred).

    As for GeoShred they did overhaul the automation portion of the plug-in.

    I tried almost everything, this one was the first because of the v2 MIDI routing. SWAM only records the broken automation lane, no matter how much you tweak the control knob.
     
    I almost PM-ed you earlier, haha. Thank you!

  • @Luxthor said:

    I almost PM-ed you earlier, haha. Thank you!

    I made a booboo in my screenshot, naturally it's the output that has to be chosen otherwise the plug-is output will not be recorded to the track :)

  • @Samu said:

    @Luxthor said:

    I almost PM-ed you earlier, haha. Thank you!

    I made a booboo in my screenshot, naturally it's the output that has to be chosen otherwise the plug-is output will not be recorded to the track :)

    Yeah, but it’s the same thing regardless. It will not record automation from the interface.

  • @Luxthor said:

    Yeah, but it’s the same thing regardless. It will not record automation from the interface.

    Then it's like that they do not send release-events which are required by the AUv3 specification.
    Logic is very strict when it comes to AUv3 implementation...

    You can if you have the energy send this to the SWAM developers...

    "AUv3 automation recording doesn't work in many cases, because most AUv3s don't send AUParameterAutomationEventTypeTouch and Release events required by Audio Unit specification.

    https://developer.apple.com/documentation/audiotoolbox/auparameterautomationeventtype?language=objc

    So if you have a problem with your fav AUv3, inform developer please."

    Cheers!

  • Have you tried [email protected] ?

    They were very helpful and responsive when I contacted them a few months ago (as per my issue earlier in this thread)

  • @BillS said:
    Have you tried [email protected] ?

    They were very helpful and responsive when I contacted them a few months ago (as per my issue earlier in this thread)

    Personally I don't own any of their apps so I'll give @Luxthor the honor to contact them :sunglasses:

  • @Samu said:

    @Luxthor said:

    Yeah, but it’s the same thing regardless. It will not record automation from the interface.

    Then it's like that they do not send release-events which are required by the AUv3 specification.
    Logic is very strict when it comes to AUv3 implementation...

    You can if you have the energy send this to the SWAM developers...

    "AUv3 automation recording doesn't work in many cases, because most AUv3s don't send AUParameterAutomationEventTypeTouch and Release events required by Audio Unit specification.

    https://developer.apple.com/documentation/audiotoolbox/auparameterautomationeventtype?language=objc

    So if you have a problem with your fav AUv3, inform developer please."

    Cheers!

    I wanted to be sure it wasn't just me, so I sent my first message here on May 18. I also asked friends from the Discord groups. The first confirmation came today from @vlaoladis. So that’s that. 🫣

    BTW, did you try to record automation from the GeoShred interface, for example, vibrato control?

Sign In or Register to comment.