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.

GigFast Lite by ArteraDSP (Released)

1234568

Comments

  • pbelgiumpbelgium

    Congrats on the 1st anniversary @ArteraDSP! And thanks for the 75% off both GigFast Lite and NAM XT - very generous!

  • KrupaKrupa

    @ArteraDSP said:

    @Krupa said:
    Are there many of these parametric NAM captures out in the wild?

    Not publicly disclosed except Steven's overdrive and new preamp saturation plugin by Submission Audio. Some of them probably using hybrid approaches, but I don't want to get into details about their workflow unless they choose to do so.

    Regards
    Emrah - Co-Founder

    Cheers Emrah, I only recently got nam xt, but I’ll give this one a whirl and see if my crabby old ears can tell the difference 😅

  • filo01filo01

    @wim said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    Attn: @Michael , @espiegel123

    I dug a little bit deeper and here is my findings.
    1. I'm able to unlock/lock Presence and and Resonance knobs by recalling of saved Loopy Pro patches. Not every time, but at least once in 10 tries for sure. Here's a screen from Flo's video where he uses the VAC-036 model and both mentioned knobs are disabled. My GigFast app in Loopy Pro screen is in the middle. Both knobs are enabled.

    Here is a video demonstration:
    https://youtube.com/watch?v=e4G2Wmqz14I
    2. In this example I'm recalling of saved Loopy Pro patch with MJM model and the sound changes significantly in several cases:
    https://youtube.com/watch?v=IFIuG5P1Qr4
    I hope this can be fixed, @ArteraDSP . If there's anything I can do to help, please let me know.

  • jacoujacou

    @wim said:
    If I've purchased GigFast Lite, is there any reason I would also need NamXT?

    I can imagine once the NAM XT mono compatibility update is out it might use less CPU than Gigfast

  • ArteraDSPArteraDSP

    @filo01 said:

    @wim said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    Attn: @Michael , @espiegel123

    I dug a little bit deeper and here is my findings.
    1. I'm able to unlock/lock Presence and and Resonance knobs by recalling of saved Loopy Pro patches. Not every time, but at least once in 10 tries for sure. Here's a screen from Flo's video where he uses the VAC-036 model and both mentioned knobs are disabled. My GigFast app in Loopy Pro screen is in the middle. Both knobs are enabled.

    Here is a video demonstration:
    https://youtube.com/watch?v=e4G2Wmqz14I
    2. In this example I'm recalling of saved Loopy Pro patch with MJM model and the sound changes significantly in several cases:
    https://youtube.com/watch?v=IFIuG5P1Qr4
    I hope this can be fixed, @ArteraDSP . If there's anything I can do to help, please let me know.

    Thanks for reporting, saving the presets to GigFast's own library and recalling them is our recommended solution currently. We will check and see if we can fix this.

  • ArteraDSPArteraDSP

    @jacou said:

    @wim said:
    If I've purchased GigFast Lite, is there any reason I would also need NamXT?

    I can imagine once the NAM XT mono compatibility update is out it might use less CPU than Gigfast

    No, GigFast is already already handling the inputs in that way.

  • ArteraDSPArteraDSP

    @pbelgium said:
    Congrats on the 1st anniversary @ArteraDSP! And thanks for the 75% off both GigFast Lite and NAM XT - very generous!

    Thanks a lot 🤘🏻

  • jacoujacou

    @ArteraDSP said:

    @jacou said:

    @wim said:
    If I've purchased GigFast Lite, is there any reason I would also need NamXT?

    I can imagine once the NAM XT mono compatibility update is out it might use less CPU than Gigfast

    No, GigFast is already already handling the inputs in that way.

    Oh that's good to know. Thanks for the info.

  • bangzerobangzero

    @ArteraDSP said:
    Thanks for reporting, saving the presets to GigFast's own library and recalling them is our recommended solution currently. We will check and see if we can fix this.

    pretty sure the same problem will occur when loading a Loopy Pro project & GigFast instances will not restore correctly. fwiw, i reported a similiar issue in MacOS/Reaper by email a few months back.

  • espiegel123espiegel123

    @bangzero said:

    @ArteraDSP said:
    Thanks for reporting, saving the presets to GigFast's own library and recalling them is our recommended solution currently. We will check and see if we can fix this.

    pretty sure the same problem will occur when loading a Loopy Pro project & GigFast instances will not restore correctly. fwiw, i reported a similiar issue in MacOS/Reaper by email a few months back.

    Do you have a set of steps that you could describe?

  • bangzerobangzero

    @espiegel123 said:

    @bangzero said:

    @ArteraDSP said:
    Thanks for reporting, saving the presets to GigFast's own library and recalling them is our recommended solution currently. We will check and see if we can fix this.

    pretty sure the same problem will occur when loading a Loopy Pro project & GigFast instances will not restore correctly. fwiw, i reported a similiar issue in MacOS/Reaper by email a few months back.

    Do you have a set of steps that you could describe?

    my trial period has expired so i can't verify, but iirc: w new Reaper project, new instance of GigFast; set an extreme tone setting, save Reaper project, quit & reopen. GigFast would visually show the extreme tone setting but actually had default values in effect until the tone knobs were manually tweaked. this was w GigFast Lite 2.2, Reaper 7.30 with MacOS 14.4 on an M2 Macbook Air.

  • espiegel123espiegel123

    @bangzero said:

    @espiegel123 said:

    @bangzero said:

    @ArteraDSP said:
    Thanks for reporting, saving the presets to GigFast's own library and recalling them is our recommended solution currently. We will check and see if we can fix this.

    pretty sure the same problem will occur when loading a Loopy Pro project & GigFast instances will not restore correctly. fwiw, i reported a similiar issue in MacOS/Reaper by email a few months back.

    Do you have a set of steps that you could describe?

    my trial period has expired so i can't verify, but iirc: w new Reaper project, new instance of GigFast; set an extreme tone setting, save Reaper project, quit & reopen. GigFast would visually show the extreme tone setting but actually had default values in effect until the tone knobs were manually tweaked. this was w GigFast Lite 2.2, Reaper 7.30 with MacOS 14.4 on an M2 Macbook Air.l

    I misunderstood. I thought you were having a problem with Gigfast Lite not loading correctly in Loopy Pro.

  • bangzerobangzero
    edited May 2025

    @espiegel123 said:
    I misunderstood. I thought you were having a problem with Gigfast Lite not loading correctly in Loopy Pro.

    sorry. that was @filo01. i thought my similar experience on MacOS might be relevant. & i do think @filo01's problem will also occur when loading Loopy Pro projects. using GigFast presets is not an alternative in that case.

  • filo01filo01

    @ArteraDSP said:

    @filo01 said:

    @wim said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    Attn: @Michael , @espiegel123

    I dug a little bit deeper and here is my findings.
    1. I'm able to unlock/lock Presence and and Resonance knobs by recalling of saved Loopy Pro patches. Not every time, but at least once in 10 tries for sure. Here's a screen from Flo's video where he uses the VAC-036 model and both mentioned knobs are disabled. My GigFast app in Loopy Pro screen is in the middle. Both knobs are enabled.

    Here is a video demonstration:
    https://youtube.com/watch?v=e4G2Wmqz14I
    2. In this example I'm recalling of saved Loopy Pro patch with MJM model and the sound changes significantly in several cases:
    https://youtube.com/watch?v=IFIuG5P1Qr4
    I hope this can be fixed, @ArteraDSP . If there's anything I can do to help, please let me know.

    Thanks for reporting, saving the presets to GigFast's own library and recalling them is our recommended solution currently. We will check and see if we can fix this.

    Thank you, fingers crossed.

  • filo01filo01
    edited May 2025

    @bangzero said:

    @espiegel123 said:
    I misunderstood. I thought you were having a problem with Gigfast Lite not loading correctly in Loopy Pro.

    sorry. that was @filo01. i thought my similar experience on MacOS might be relevant. & i do think @filo01's problem will also occur when loading Loopy Pro projects. using GigFast presets is not an alternative in that case.

    I've tested loading of project with GigFast (GF) app inside in Loopy Pro on several scenarios and I cannot confirm any issues there.
    Init: Open LP, new project, add GigFast app, set extreme settings, save LP project.
    1. Close and reopen LP - sound corresponds to extreme GF settings.
    2. Switch to different project and back - sound corresponds to extreme GF settings.
    3. Switch to different project, close and reopen LP, switch to GF project - sound corresponds to extreme GF settings.

    So it looks like the problem is only with saving/recalling Loopy Pro GF preset, not when loading the whole Loopy Pro project.

  • bangzerobangzero

    @filo01 said:
    So it looks like the problem is only with saving/recalling Loopy Pro GF preset, not when loading the whole Loopy Pro project.

    thanks for checking that out @filo01. MacOS/IOS maybe different, & things may have changed since my trial back in January.

  • MichaelMichael

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    FYI this should be sorted in the latest 2.0 beta

  • filo01filo01

    @Michael said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    FYI this should be sorted in the latest 2.0 beta

    Thank you Michael for dealing with this. I'm on beta b.661 and the problem still persists.

  • espiegel123espiegel123

    @filo01 said:

    @Michael said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    FYI this should be sorted in the latest 2.0 beta

    Thank you Michael for dealing with this. I'm on beta b.661 and the problem still persists.

    @filo01 can you post a project, demonstration and instructions on the Slack?

  • filo01filo01

    @espiegel123 said:

    @filo01 said:

    @Michael said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    FYI this should be sorted in the latest 2.0 beta

    Thank you Michael for dealing with this. I'm on beta b.661 and the problem still persists.

    @filo01 can you post a project, demonstration and instructions on the Slack?

    Wouldn't a YT video with a description be enough? I don't know anything about Slack, I'd have to learn how to use it first.

  • espiegel123espiegel123

    @filo01 said:

    @espiegel123 said:

    @filo01 said:

    @Michael said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    FYI this should be sorted in the latest 2.0 beta

    Thank you Michael for dealing with this. I'm on beta b.661 and the problem still persists.

    @filo01 can you post a project, demonstration and instructions on the Slack?

    Wouldn't a YT video with a description be enough? I don't know anything about Slack, I'd have to learn how to use it first.

    If you don’t want to join the slack, that would be fine. (FWIW, using slack doesn’t have much learning curve)

  • VaultnaemsaeVaultnaemsae

    @ArteraDSP -- Wow, what a great deal on a superb application for guitarists! Thank you for offering this.

  • filo01filo01

    @espiegel123 said:

    @filo01 said:

    @espiegel123 said:

    @filo01 said:

    @Michael said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    FYI this should be sorted in the latest 2.0 beta

    Thank you Michael for dealing with this. I'm on beta b.661 and the problem still persists.

    @filo01 can you post a project, demonstration and instructions on the Slack?

    Wouldn't a YT video with a description be enough? I don't know anything about Slack, I'd have to learn how to use it first.

    If you don’t want to join the slack, that would be fine. (FWIW, using slack doesn’t have much learning curve)

    Not unless it's absolutely necessary. FB groups, several Forums, Discord groups, WhatsApp, Teams ... I'm too socialized. :smile:
    Here is a video example: https://youtube.com/watch?v=1iyfVyAeZYs

  • ArteraDSPArteraDSP

    @Vaultnaemsae said:
    @ArteraDSP -- Wow, what a great deal on a superb application for guitarists! Thank you for offering this.

    Thanks for your kind words, we hope you enjoy GigFast :)

  • espiegel123espiegel123

    @filo01 said:

    @espiegel123 said:

    @filo01 said:

    @espiegel123 said:

    @filo01 said:

    @Michael said:

    @filo01 said:
    @ArteraDSP
    I found something I think you should know about running GigFast in Loopy Pro and hopefully it can be resolved. I had the same problem with the ShimmerFX app from 4 Pockets and Paul was able to fix the error.
    What it is: When saving the current GigFast settings to the Loopy Pro preset, an action occurs in the background that causes everything to be visually OK when the preset is reloaded, but not data-wise - the position of the knobs doesn't correspond with what I'm hearing.
    It's easy to test this by, for example, pulling back the bass completely, and you can hear the sound suddenly change when the preset is saving into Loopy Pro. Then, when you recall the preset you just saved, you see the bass knob pulled back, but the sound doesn't match it.

    Here's what Paul from 4Pockets wrote to me about this issue:
    "It is supposed to save the settings as saved as part of the session in the host which is does properly in AUM for instance.
    It looks like you are running in Loopy Pro, and there is a known issue with AUv3’s not being properly restoring under Loopy which I’ve reported to Michael many times. It seems for some reason Loopy is also trying to set a preset during the session save. I’ve seen this many times and not sure why he is doing it."

    FYI this should be sorted in the latest 2.0 beta

    Thank you Michael for dealing with this. I'm on beta b.661 and the problem still persists.

    @filo01 can you post a project, demonstration and instructions on the Slack?

    Wouldn't a YT video with a description be enough? I don't know anything about Slack, I'd have to learn how to use it first.

    If you don’t want to join the slack, that would be fine. (FWIW, using slack doesn’t have much learning curve)

    Not unless it's absolutely necessary. FB groups, several Forums, Discord groups, WhatsApp, Teams ... I'm too socialized. :smile:
    Here is a video example: https://youtube.com/watch?v=1iyfVyAeZYs

    @ArteraDSP : I don't know if this is a Loopy issue or an GigfastLite issue -- you might be able to tell easily from your side. It looks like what is happening is that when Loopy Pro restores the the state and the model changes that EQ params don't restore unless one re-selects the channel.

  • ArteraDSPArteraDSP

    Hi everyone. Autumn is ahead of us so “end of summer sale” has started. You can have GIGFAST LITE for $19.99 till the end of September. You can download it from the AppStore.

  • filo01filo01
    edited September 2025

    @ArteraDSP Any plans to make Gigfast Lite and NAM XT less CPU hungry?

  • ArteraDSPArteraDSP

    @filo01 said:
    @ArteraDSP Any plans to make Gigfast Lite and NAM XT less CPU hungry?

    We might have maybe one or two options that we have not tried to further improve the CPU usage but for the most part our processing is as good as it gets. That is why we don't see many native NAM supporting hardwares at tonex price point.

  • AileromAilerom
    edited September 2025

    @ArteraDSP Has anything come of the Cubase crash issue I am having with Gigfast?

  • ArteraDSPArteraDSP

    @Ailerom said:
    @ArteraDSP Has anything come of the Cubase crash issue I am having with Gigfast?

    Yes, along with some iOS 18 fixes and new models.

Sign In or Register to comment.