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.

Weird issue in Ripplemaker and BB17

2»

Comments

  • Fear2StopFear2Stop

    @wim said:
    Is it possible you just didn't apply a GarageBand update until recently?

    No…I check for app updates twice daily. And since I use GarageBand every day, I definitely would’ve done it immediately

  • wimwim

    I'm stumped then. There's no possible cause I can think of that could have changed that recently.

  • dendydendy
    edited January 23

    @brambos said:

    @dendy said:

    @uncledave said:

    @CracklePot said:
    I messed with Ripplemaker in GarageBand. It’s the mod wheel in GarageBand that is overriding the LFO rate.

    I tested this in AUM. It looks like Mod Wheel (CC1) is permanently connected to LFO Rate in Ripplemaker. There appears to be no way to turn off this connection.

    I suppose the Frequency control in BB17 is similarly connected to Mod Wheel.

    It sounds like Garage Band is sending the current Mod Wheel position on Play. Not sure if this is right or wrong, since any controlled parameter will jump as soon as the wheel is moved.

    Ooo very cool … that explains EVERYTHING … also reason why on project load it is reseted to zero in NS - that is defsult modwheel position in AU instrument interface ..

    @brambos i guess, this should be easy to fix in Ripplemaker just by adding switch in options to remove this connection.

    Well no, because I don't have options or settings panels in my apps. That's a hard design principle.

    You can't put it to system settings ? Noticed that APP can have global settings accessible directly in iOS app settings section (saw it in some apps) ...

    Or just remove that functionality for AUv3 plugin, it's accessible via AU parameter in AU host anyway so to have it hard linked to Midi CC is not much needed anyway .. Yeah maybe few % of users will complain but i think for majority it will be solution ... 80/20 rule ;)

    @Fear2Stop said:
    Yes, because I use Ripplemaker quite often…it’s one of my favorite apps.

    yeah, still for me one of best synths ever made or ios .. simple but sonically very powerfull.. i am very sad i can't really use it in my NS2 projects because of this problem for years, if this was not there i would use it literally in every single track, it's kind of beauty.

    Here i got some hope for Bram finding some way to fix this :smile: That would be amazing. Would even pay for fix as IAP lol :-D

  • lisacastillolisacastillo

    Try removing and reinstalling the affected AUv3 synths. This can sometimes resolve issues related to corrupted plugin files. Delete the apps, restart your device, and then reinstall them.

  • Fear2StopFear2Stop

    @lisacastillo said:
    Try removing and reinstalling the affected AUv3 synths. This can sometimes resolve issues related to corrupted plugin files. Delete the apps, restart your device, and then reinstall them.

    If I do that would I lose my presets? Asking because there are some my wife made before we separated and they’re kind of important to me 😞

  • brambosbrambos

    Reinstalling will certainly not solve this issue. I would not recommend it :)

  • uncledaveuncledave

    @Fear2Stop said:

    @lisacastillo said:
    Try removing and reinstalling the affected AUv3 synths. This can sometimes resolve issues related to corrupted plugin files. Delete the apps, restart your device, and then reinstall them.

    If I do that would I lose my presets? Asking because there are some my wife made before we separated and they’re kind of important to me 😞

    I believe you're talking to a bot here. The problem with Ripplemaker and Mod Wheel is a design feature, not caused by corruption.

  • Fear2StopFear2Stop

    @brambos said:
    Reinstalling will certainly not solve this issue. I would not recommend it :)

    Gotcha ..:good thing I checked first lol > @uncledave said:

    @Fear2Stop said:

    @lisacastillo said:
    Try removing and reinstalling the affected AUv3 synths. This can sometimes resolve issues related to corrupted plugin files. Delete the apps, restart your device, and then reinstall them.

    If I do that would I lose my presets? Asking because there are some my wife made before we separated and they’re kind of important to me 😞

    I believe you're talking to a bot here. The problem with Ripplemaker and Mod Wheel is a design feature, not caused by corruption.

    A bot with my last name, coincidentally enough lol

  • wimwim
    edited January 23

    @brambos - The Ripplemaker manual lists CC 31, not CC 1 (mod wheel) as the control for LFO speed. It seems to me like you could just remove the mod wheel linkage altogether?

    It would break some projects where a person or two stumbled on the undocumented LFO speed link to mod wheel.

    I understand and respect not bowing to pressure to modify your apps because of stupid host behavior, but in this case it's an undocumented feature in Ripplemaker's case anyway. At the least, maybe the documentation should be updated. 😉

  • Fear2StopFear2Stop

    Is it sad that I didn’t even know GarageBand had a mod wheel? Lol

  • brambosbrambos

    @wim said:
    @brambos - The Ripplemaker manual lists CC 31, not CC 1 (mod wheel) as the control for LFO speed. It seems to me like you could just remove the mod wheel linkage altogether?

    It would break some projects where a person or two stumbled on the undocumented LFO speed link to mod wheel.

    I understand and respect not bowing to pressure to modify your apps because of stupid host behavior, but in this case it's an undocumented feature in Ripplemaker's case anyway. At the least, maybe the documentation should be updated. 😉

    Yeah... let me look into that. It has been 7 years since I wrote the MIDI implementation :)

    That would be a sweet solution!

  • Fear2StopFear2Stop

    @brambos said:

    @wim said:
    @brambos - The Ripplemaker manual lists CC 31, not CC 1 (mod wheel) as the control for LFO speed. It seems to me like you could just remove the mod wheel linkage altogether?

    It would break some projects where a person or two stumbled on the undocumented LFO speed link to mod wheel.

    I understand and respect not bowing to pressure to modify your apps because of stupid host behavior, but in this case it's an undocumented feature in Ripplemaker's case anyway. At the least, maybe the documentation should be updated. 😉

    Yeah... let me look into that. It has been 7 years since I wrote the MIDI implementation :)

    That would be a sweet solution!

    If that fixes it, I would be happier than anyone would believe. I have kind of an emotional attachment to Ripplemaker as it brings back happy memories of my wife making patches with it. I miss her so much

  • Fear2StopFear2Stop

    Update: the BB developer found the source of the problem and is working on the fix!

  • brambosbrambos

    @Fear2Stop said:

    @brambos said:

    @wim said:
    @brambos - The Ripplemaker manual lists CC 31, not CC 1 (mod wheel) as the control for LFO speed. It seems to me like you could just remove the mod wheel linkage altogether?

    It would break some projects where a person or two stumbled on the undocumented LFO speed link to mod wheel.

    I understand and respect not bowing to pressure to modify your apps because of stupid host behavior, but in this case it's an undocumented feature in Ripplemaker's case anyway. At the least, maybe the documentation should be updated. 😉

    Yeah... let me look into that. It has been 7 years since I wrote the MIDI implementation :)

    That would be a sweet solution!

    If that fixes it, I would be happier than anyone would believe. I have kind of an emotional attachment to Ripplemaker as it brings back happy memories of my wife making patches with it. I miss her so much

    Just sent a fix to Apple for review.

  • Fear2StopFear2Stop

    @brambos said:

    @Fear2Stop said:

    @brambos said:

    @wim said:
    @brambos - The Ripplemaker manual lists CC 31, not CC 1 (mod wheel) as the control for LFO speed. It seems to me like you could just remove the mod wheel linkage altogether?

    It would break some projects where a person or two stumbled on the undocumented LFO speed link to mod wheel.

    I understand and respect not bowing to pressure to modify your apps because of stupid host behavior, but in this case it's an undocumented feature in Ripplemaker's case anyway. At the least, maybe the documentation should be updated. 😉

    Yeah... let me look into that. It has been 7 years since I wrote the MIDI implementation :)

    That would be a sweet solution!

    If that fixes it, I would be happier than anyone would believe. I have kind of an emotional attachment to Ripplemaker as it brings back happy memories of my wife making patches with it. I miss her so much

    Just sent a fix to Apple for review.

    Awesome possum! You rock 😎

  • Fear2StopFear2Stop

    Ripplemaker is fixed 🥰 Thank you @brambos !!!!

Sign In or Register to comment.

© Vanilla Keystone Theme 2024