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.

Steel Guitar Pro - annoying (and loud) pops at load...

Using Steel Guitar Pro in setups and each time it loads, a rather loud and annoying dblk click/pop sound happens. Once it's loaded it's fine, just at load.

Anyone else had this, and if so, a fix?

Comments

  • Wow… that’s taking guitar emulation to a new level. There was a physical guitar cable that had a mechanism to avoid the “plugging in” pop.

    I will test when I get home. I love Steel Guitar Pro’s sound through a good amp sim like TH-U with all the FX modules applied. It can be made to sound like most tones that way and not just pedal steel. The FX’es and Amos in SGO just scrape the surface if what’s possible.

  • @pax-eterna said:
    Using Steel Guitar Pro in setups and each time it loads, a rather loud and annoying dblk click/pop sound happens. Once it's loaded it's fine, just at load.

    Anyone else had this, and if so, a fix?

    I've not had that problem. Are you using the standalone, or the AUv3 plugin?

  • @pax-eterna said:
    Using Steel Guitar Pro in setups and each time it loads, a rather loud and annoying dblk click/pop sound happens. Once it's loaded it's fine, just at load.

    Anyone else had this, and if so, a fix?

    Yes, I have experienced this but don’t have a fix for you. I mute the channel in the host to avoid it.

  • Looks like it happens when it loads on a preset that uses the reverb. That’s the only time I can replicate. So I saved an init patch for it to load upon opening and the issue stopped.

  • @McD said:
    Wow… that’s taking guitar emulation to a new level. There was a physical guitar cable that had a mechanism to avoid the “plugging in” pop.

    I will test when I get home. I love Steel Guitar Pro’s sound through a good amp sim like TH-U with all the FX modules applied. It can be made to sound like most tones that way and not just pedal steel. The FX’es and Amos in SGO just scrape the surface if what’s possible.

    :D

  • @wim said:

    @pax-eterna said:
    Using Steel Guitar Pro in setups and each time it loads, a rather loud and annoying dblk click/pop sound happens. Once it's loaded it's fine, just at load.

    Anyone else had this, and if so, a fix?

    I've not had that problem. Are you using the standalone, or the AUv3 plugin?

    both

  • @lukesleepwalker said:

    @pax-eterna said:
    Using Steel Guitar Pro in setups and each time it loads, a rather loud and annoying dblk click/pop sound happens. Once it's loaded it's fine, just at load.

    Anyone else had this, and if so, a fix?

    Yes, I have experienced this but don’t have a fix for you. I mute the channel in the host to avoid it.

    thanks - that was what I was thinking too - but in my case, I would probs forget to unmute while I'm playing (solo) and then either make a mad scramble to fix it, or just go without hahaha!

  • @HotStrange said:
    Looks like it happens when it loads on a preset that uses the reverb. That’s the only time I can replicate. So I saved an init patch for it to load upon opening and the issue stopped.

    Nice!! Would it be possible for you to share that patch, or is it pretty easy to setup? Although I'm not sure how it would work as I'd need to set it in the host, and then somehow auto load another preset???

  • @pax-eterna said:

    @HotStrange said:
    Looks like it happens when it loads on a preset that uses the reverb. That’s the only time I can replicate. So I saved an init patch for it to load upon opening and the issue stopped.

    Nice!! Would it be possible for you to share that patch, or is it pretty easy to setup? Although I'm not sure how it would work as I'd need to set it in the host, and then somehow auto load another preset???

    It might be easier to turn off the built-in reverb and use a separate AUv3 reverb after SG.

  • @uncledave said:

    @pax-eterna said:

    @HotStrange said:
    Looks like it happens when it loads on a preset that uses the reverb. That’s the only time I can replicate. So I saved an init patch for it to load upon opening and the issue stopped.

    Nice!! Would it be possible for you to share that patch, or is it pretty easy to setup? Although I'm not sure how it would work as I'd need to set it in the host, and then somehow auto load another preset???

    It might be easier to turn off the built-in reverb and use a separate AUv3 reverb after SG.

    Ah, yes. I just opened an old Loopy project and I can see that this is how I worked around the problem in this project. Turned off reverb in SG and added separate reverb.

  • edited January 2024

    @uncledave said:

    @pax-eterna said:

    @HotStrange said:
    Looks like it happens when it loads on a preset that uses the reverb. That’s the only time I can replicate. So I saved an init patch for it to load upon opening and the issue stopped.

    Nice!! Would it be possible for you to share that patch, or is it pretty easy to setup? Although I'm not sure how it would work as I'd need to set it in the host, and then somehow auto load another preset???

    It might be easier to turn off the built-in reverb and use a separate AUv3 reverb after SG.

    Very nice, thanks Dave, that was one of those "....why didn't I think of that" things hahahaha!

  • @lukesleepwalker said:

    @uncledave said:

    @pax-eterna said:

    @HotStrange said:
    Looks like it happens when it loads on a preset that uses the reverb. That’s the only time I can replicate. So I saved an init patch for it to load upon opening and the issue stopped.

    Nice!! Would it be possible for you to share that patch, or is it pretty easy to setup? Although I'm not sure how it would work as I'd need to set it in the host, and then somehow auto load another preset???

    It might be easier to turn off the built-in reverb and use a separate AUv3 reverb after SG.

    Ah, yes. I just opened an old Loopy project and I can see that this is how I worked around the problem in this project. Turned off reverb in SG and added separate reverb.

    Cool, thanks!

  • @pax-eterna said:

    @HotStrange said:
    Looks like it happens when it loads on a preset that uses the reverb. That’s the only time I can replicate. So I saved an init patch for it to load upon opening and the issue stopped.

    Nice!! Would it be possible for you to share that patch, or is it pretty easy to setup? Although I'm not sure how it would work as I'd need to set it in the host, and then somehow auto load another preset???

    Sorry for the delay but all I did was create a new patch, hit init, and then named it/saved it. You may have to do it per host but it worked in AUM and Nodes for me.

Sign In or Register to comment.