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.

Update: New Roland SH-101 and now MC-202 for Nanostudio 2

13»

Comments

  • @rs2000 said:

    @wim said:
    But if I was and I did then I would. ;)

    I shall call this "Wim's Assertion" of a (++well known) "Sampling Law".
    There are 8 permutations in all:

    "Does Sampling (a lot)?" + "Has a Mac?" + "Would Obtain Redmatica"

    111 = If I do and I do then I would (Wim's Assertion)
    110 = If I do and I do NOT then I would NOT
    101 = If I do and I do NOT then I would
    100 = If I do and I do NOT then I would NOT
    011 = If I do NOT and I do then I would
    010= If I do NOT and I do then I would NOT (McD's Conclusion)
    001 = If I do NOT and I do NOT then I would
    000 = If I do NOT and I do NOT then I would NOT

    This is my recollection of a TRUTH table from Boolean Logic class.
    You may declare any of the remaining 6 for your own branded "Sampling Law".

    ++ this is how you make meme's.

  • @rs2000 said:
    Here's a short rendered preview of a known piece by Lee Ritenour:
    Bass: SH-101 B
    Pads: P6-SoftLead
    Keys: 3x Rhodes Mk2 alpha version o:)
    Drums: Slate default kit

    Awesome job! Captain Fingers for the win!.

  • @wim said:
    It works with AudioLayer too!

    Really? I tried to add loop points in AudioLayer's editor and gave up.

  • @McD said:

    @wim said:
    It works with AudioLayer too!

    Really? I tried to add loop points in AudioLayer's editor and gave up.

    I meant, if you set loop points in Auditor, then import that saved sample into AudioLayer, AudioLayer recognizes and uses it.

  • I’m having difficulty getting click-free results in some samples though, Auditor makes a nice click-free looping region, but sometimes clicks when the playhead continues past the loop end.

    I guess the Auditor loop tool is more geared toward making standalone loops than loop regions within a sample.

  • edited November 2019

    @wim said:
    Cool! Once again BM3 sampler rulz. Man, an AU fork of the sampler would be a thing now, wouldn't it?

    No question!
    And yet another biggie inside the BM3 sampler: Does the button "Disk Streaming" really mean ... erm ... disk streaming??
    If so, I wonder why I'm still using AL ... ah, yes, it was the AUv3 :D

    @wim said:

    @McD said:

    @wim said:
    It works with AudioLayer too!

    Really? I tried to add loop points in AudioLayer's editor and gave up.

    I meant, if you set loop points in Auditor, then import that saved sample into AudioLayer, AudioLayer recognizes and uses it.

    Good to know. AL not only has its own loop editor however but also a crossfade function that does work quite well:

    @wim said:
    I’m having difficulty getting click-free results in some samples though, Auditor makes a nice click-free looping region, but sometimes clicks when the playhead continues past the loop end.

    That's the compromise with X-fade looping: You gotta crossfade some portion of the audio file. Either you bake-in the crossfade at the beginning of the loop (but then you get an audible transition at the beginning of the sustain loop) or you bake-in the crossfade at the end of the loop but then you naturally get an audible transition when the release portion is played (plus, with a longer sustain loop, you'll want the playhead to immediately play the release part upon releasing the key so it gets even worse).

    A positive way to use this effect is to implement release samples this way. Nanostudio has a very nifty feature in that you can use key release velocity to control e.g. oscillator volume. Voilá, the release samples implemented better than in AudioLayer.

    I guess the Auditor loop tool is more geared toward making standalone loops than loop regions within a sample.

    Hard to say. Some samples are nothing but a pita to loop, that's why Redmatica had these exotic loop modes that remind more of granular synthesis than traditional loop points.

  • @McD said:

    @rs2000 said:

    @wim said:
    But if I was and I did then I would. ;)

    I shall call this "Wim's Assertion" of a (++well known) "Sampling Law".
    There are 8 permutations in all:

    "Does Sampling (a lot)?" + "Has a Mac?" + "Would Obtain Redmatica"

    111 = If I do and I do then I would (Wim's Assertion)
    110 = If I do and I do NOT then I would NOT
    101 = If I do and I do NOT then I would
    100 = If I do and I do NOT then I would NOT
    011 = If I do NOT and I do then I would
    010= If I do NOT and I do then I would NOT (McD's Conclusion)
    001 = If I do NOT and I do NOT then I would
    000 = If I do NOT and I do NOT then I would NOT

    This is my recollection of a TRUTH table from Boolean Logic class.
    You may declare any of the remaining 6 for your own branded "Sampling Law".

    ++ this is how you make meme's.

    Haha, Mr. professeur mathématique, would you allow me to add the implementation of 66.6% data reduction by removal of the first two bits?
    Professor @McD giving logic classes for musicians would be a great matter to have @Lady_App_titude put her golden hands on ;)

  • @dendy said:
    ...
    Of course that are just my personal "rules" for building patches :) Not mandatory for anybody :)

    looking forward to your Rhodes madness ! :+1:

    I've almost finished my Rhodes patches but it seems that Obsidian always stores the same samples again with every new patch saved.
    Is there an easy way to consolidate these so 5 patches will all use the same samples and if so, anything to take care of when packing them to a ZIP collective?

  • no in simple way directly in NS... but i have in my mind concept which should work... i'm not at home right now (shopping with wife lol) but later will try it and will
    let you know...

  • @dendy said:
    no in simple way directly in NS... but i have in my mind concept which should work... i'm not at home right now (shopping with wife lol) but later will try it and will
    let you know...

    Cool, thanks and happy shopping!

  • PS: It seems to be possible to give a path to the sample name inside the obs XML file, like:
    <Zone File="/OSIAP/Instruments/Obsidian/FREE Launch Pack/BassWind.obs/SmoothBass-D1.wav"
    although I haven't tried that for user samples.

    But there must be a more straightforward way to do it ;)

  • edited November 2019

    there isn't straigtforward way... if you save patch, obsidian saves all samples insidide patch

    In theory, following concept should work. It takes advantage of fact, that if NS2 founds any samples in zipped package which are not inside patch, it unpacks those samples into

    /Library/Audio/Inbox/NameOfZipFile

    (It also preserves all subdirectories from zip file)

    • copy your patches to desktop into some directory
    • place all samples used in patches directly into same directory, so it will now contain all samples + all patches
    • remove samples from inside patch directories
    • replace paths inside patch XML files to

    /Library/Audio/Inbox/RS2K_Rhodes_Samples/nameofsample.wav

    • now zip both directories into zip file named "RS2K_Rhodes_Samples.zip"

    In theory (didn't tried it yet), when you now open such ZIP in NS2, NS unpacks it. It places all patches imto Obsidian patch library and all samples into /Libeary/Audio/Inbox/RS2K_Rhodes_Samples

    So relative paths saved in patch xml files will match samples location in library.

    However, this is a bit risky, because if user deletes samples in library or removes them into different folder, your patches will we dead...

    I'm not sure if it is worth that risk.

    Another way is to put all samples into one patch, name this patch like "SamplesContainer" and then link samples (again manually by editing XML files) from this patch.

    Also here is risk that deleting this one patch will render allmother patches unusable.

    I'm afaid that none of alternatove methods is safe enough. Or at least foolproof enough.

  • edited November 2019

    @dendy Thank you very much, that's at least some great info to work with.
    Another option is maybe to build only one or two patches and use the mod matrix to the max in order to map lots of parameters to the "8 meta controls page", so turning one knob maps to multiple parameters changing in a useful way. You've already mentioned it and I've found that these knobs can even be used as routing modifiers, something I only know from the Waldorf blofeld.

    I'll have to work on that because I like to find the very limits of apps :D

  • @rs2000 said:
    Haha, Mr. professeur mathématique, would you allow me to add the implementation of 66.6% data reduction by removal of the first two bits?

    Of Course.

    Wim would.
    I would not. (Finding an app that's no longer active is an exercise in frustration).
    Auto-sampling gets you close but great sample sets are a labor of love... like Salamander, etc.

  • Update: My red SH-101 now comes with 4 new presets, including funky lead synths.

    https://patchstorage.com/sh-101-red-patches/

Sign In or Register to comment.