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.

AudioLayer by VirSyn - The mobile Sampling Solution for iOS

14243444547

Comments

  • Thank you all. That was the info i was looking for.
    I wished they had added their great MSEG´s from Tera Synth :)

  • @rs2000 said:
    @Clueless
    No curves.
    Still I would say AL is the best you can get on iOS.
    Working with iOS means accepting limitations or finding workarounds all the time, if you want it better then go Win or Mac.

    Obsidian in Nanostudio 2 has such envelopes but it clearly lacks the disk streaming facility and the support for an insane amount of samples both in key and velocity ranges.

    Thank´s. I was sure Audio Layer is the best on iOS.
    Workarounds? Yes but these are options i call standard ;)
    I mean it might sound simple but having just the attack and attack curve as modulation source can make such a huge different and can make a simple one sample per note instrument so much more dynamic and expressive.
    Well, at least it has envelopes which are the most important thing for me in a sampler or any sample player engine (but still many lacks this standard feature for some reason).

  • I am experiencing consistent crashing of the AudioLayer auv3 instrument in Cubasis 3.1.3 (and Beatmaker 3) after updating to iPadOS14.

    I first observed the crashing of Cubasis 3.1.3 on opening of several of my projects but wasn't able to pinpoint the cause of the crash due to my projects having so many auv3s, and since testing all auv3's separately and confirming them to instantiate fine in Cubasis 3 and also reopen fine when closing and opening projects. After experimenting with different test projects, I believe I have found the culprit to be AudioLayer, specifically when using large sized instruments (in my case imported Drum Drops acoustic multisample drumkits). These have been working flawlessly and stably regardless of their size prior to iPadOS14, but now they will crash the host (Cubasis 3 and Beatmaker 3 tested). Smaller sized AudioLayer instruments don't seem to cause a problem.

    Has anyone else observed similar behaviour and what do you @VirSyn think is the issue?

  • @gosnote said:
    I am experiencing consistent crashing of the AudioLayer auv3 instrument in Cubasis 3.1.3 (and Beatmaker 3) after updating to iPadOS14.

    I first observed the crashing of Cubasis 3.1.3 on opening of several of my projects but wasn't able to pinpoint the cause of the crash due to my projects having so many auv3s, and since testing all auv3's separately and confirming them to instantiate fine in Cubasis 3 and also reopen fine when closing and opening projects. After experimenting with different test projects, I believe I have found the culprit to be AudioLayer, specifically when using large sized instruments (in my case imported Drum Drops acoustic multisample drumkits). These have been working flawlessly and stably regardless of their size prior to iPadOS14, but now they will crash the host (Cubasis 3 and Beatmaker 3 tested). Smaller sized AudioLayer instruments don't seem to cause a problem.

    Has anyone else observed similar behaviour and what do you @VirSyn think is the issue?

    I'd recommend reporting to both Steinberg and Virsyn via their preferred support channels. While they do check in here from time to time, they are more likely to see the information if you send directly to them.

  • @AudioGus said:
    Sweet! Very curious how this will workflow with Cubasis...

    We certainly have a few videos using Audiolayer including the video called How To Slide 808s in Cubasis 3 :)

  • In AUM AudioLayer exposes 8 assignable parameters for midi control.
    Anyone know how to map/assign these to a parameter in AudioLayer?

  • @soundtemple said:
    In AUM AudioLayer exposes 8 assignable parameters for midi control.
    Anyone know how to map/assign these to a parameter in AudioLayer?

    Same! I don't think anyone has figured this out.

  • @auxmux ah ok bummer... appreciate the update. thanks.

    maybe @VirSyn can tell us? ^^

  • Wow, loads of new (free) instruments in this release. The orchestra library is good imo

  • @naturalefx said:
    Sorry for the repeated message but it seemed that the system did not send it. Visit the new Patch Demo Download Page of my new site (https://nefx78.wixsite.com/website/audiolayer-samples-audio-demo?lang=en) and give me a feedback, it's important for me, THX!!

    Hi, I downloaded the Keys of Paradise demo and was able to import it into AudioLayer without problems. Sounds very nice, many thanks.

  • This is a nice update, wondering if we'll see the AU parameter function enabled any time soon too :)

  • @Carnbot said:
    This is a nice update, wondering if we'll see the AU parameter function enabled any time soon too :)

    I imagine that to get this on the radar, a number of people would need to contact @Virsyn -- probably via email.

  • @espiegel123 said:

    @Carnbot said:
    This is a nice update, wondering if we'll see the AU parameter function enabled any time soon too :)

    I imagine that to get this on the radar, a number of people would need to contact @Virsyn -- probably via email.

    Yes, this would be great. Last thing keeping this app from being perfect. Need to able to modulate those filters.

  • @soundtemple said:
    In AUM AudioLayer exposes 8 assignable parameters for midi control.
    Anyone know how to map/assign these to a parameter in AudioLayer?

    Same question here. I couldn't figure out how to assign those "assignable parameters".

  • Does this ever go on sale? I keep hearing about this app being used, but never really looked at it. Worth the 30 clams?

  • @Intrepolicious said:
    Does this ever go on sale? I keep hearing about this app being used, but never really looked at it. Worth the 30 clams?

    It occasionally goes on sale. If you need a velocity-layered sampler or sampler that streams from disk so that it doesn't need all samples in memory it is well worth the price as there isn't another one that I know of that is an AU.

  • @Ali_Göktürk said:

    @soundtemple said:
    In AUM AudioLayer exposes 8 assignable parameters for midi control.
    Anyone know how to map/assign these to a parameter in AudioLayer?

    Same question here. I couldn't figure out how to assign those "assignable parameters".

    I think this is coming in a future update but maybe not this next one.

  • Hello, I have a specific issue with Audiolayer that I would like to share in hopes of someone having an idea on how to tackle it.

    This is related to acoustic drum multisample libraries (www.drum-drops.com), which I have been using successfully in the AL auv3 within Cubasis 3. Recent DD libraries come with an EXS patch, but some older ones also include SFZ patches for the full kit, and all kit pieces, which is a super useful workaround in Cubasis 3 without auv3 multiout capability. My issue is with one of the newest libraries, Neo Soul Kit, which does not include the SFZ patches, so I need to import the EXS (full kit) patch into AudioLayer.

    In this case, importing the EXS file into AL that according to Drum Drops has been generated by the newest Logic Pro 10.6 Sampler, the resulting AL instrument only contains part of the whole drumkit (hihats) on one layer and nothing else. EXS files of older libraries have apparently been generated using an older version of the Logic sampler and the imported EXS file in AL results in the whole kit being imported correctly, with kit pieces on different layers.

    Since I don't have Logic or Mainstage I am not able to open the EXS file to try to understand how it is built, and make possible edits to the mapping. Drum Drops weren't very keen on helping out except for mentioning that this EXS was generated with the latest Sampler in Logic Pro, and the issue might be related to this.

    I am wondering, what tools do there exist to e.g. convert the EXS file to SFZ for AudioLayer, or edit the EXS patch so that it would import the whole kit into AudioLayer? Or could this be an issue with the EXS import in AudioLayer?

    Thanks for any insights!

  • @gosnote said:
    Hello, I have a specific issue with Audiolayer that I would like to share in hopes of someone having an idea on how to tackle it.

    This is related to acoustic drum multisample libraries (www.drum-drops.com), which I have been using successfully in the AL auv3 within Cubasis 3. Recent DD libraries come with an EXS patch, but some older ones also include SFZ patches for the full kit, and all kit pieces, which is a super useful workaround in Cubasis 3 without auv3 multiout capability. My issue is with one of the newest libraries, Neo Soul Kit, which does not include the SFZ patches, so I need to import the EXS (full kit) patch into AudioLayer.

    In this case, importing the EXS file into AL that according to Drum Drops has been generated by the newest Logic Pro 10.6 Sampler, the resulting AL instrument only contains part of the whole drumkit (hihats) on one layer and nothing else. EXS files of older libraries have apparently been generated using an older version of the Logic sampler and the imported EXS file in AL results in the whole kit being imported correctly, with kit pieces on different layers.

    Since I don't have Logic or Mainstage I am not able to open the EXS file to try to understand how it is built, and make possible edits to the mapping. Drum Drops weren't very keen on helping out except for mentioning that this EXS was generated with the latest Sampler in Logic Pro, and the issue might be related to this.

    I am wondering, what tools do there exist to e.g. convert the EXS file to SFZ for AudioLayer, or edit the EXS patch so that it would import the whole kit into AudioLayer? Or could this be an issue with the EXS import in AudioLayer?

    Thanks for any insights!

    Two things:

    • please report to @Virsyn ...the email address is on their web site
    • There is an app that translates between different sampler formats that can translate EXS to SFZ called AWAVE Studio and it can run in trial mode for 30 days.

    If the samples are well-named, you can use AudioLayer’s auto-mapping.

  • Thanks @espiegel123 for the tip on AWAVE Studio. Gotta try it out. I will also contact VIrsyn.

  • @gosnote said:
    Hello, I have a specific issue with Audiolayer that I would like to share in hopes of someone having an idea on how to tackle it.

    This is related to acoustic drum multisample libraries (www.drum-drops.com), which I have been using successfully in the AL auv3 within Cubasis 3. Recent DD libraries come with an EXS patch, but some older ones also include SFZ patches for the full kit, and all kit pieces, which is a super useful workaround in Cubasis 3 without auv3 multiout capability. My issue is with one of the newest libraries, Neo Soul Kit, which does not include the SFZ patches, so I need to import the EXS (full kit) patch into AudioLayer.

    In this case, importing the EXS file into AL that according to Drum Drops has been generated by the newest Logic Pro 10.6 Sampler, the resulting AL instrument only contains part of the whole drumkit (hihats) on one layer and nothing else. EXS files of older libraries have apparently been generated using an older version of the Logic sampler and the imported EXS file in AL results in the whole kit being imported correctly, with kit pieces on different layers.

    Since I don't have Logic or Mainstage I am not able to open the EXS file to try to understand how it is built, and make possible edits to the mapping. Drum Drops weren't very keen on helping out except for mentioning that this EXS was generated with the latest Sampler in Logic Pro, and the issue might be related to this.

    I am wondering, what tools do there exist to e.g. convert the EXS file to SFZ for AudioLayer, or edit the EXS patch so that it would import the whole kit into AudioLayer? Or could this be an issue with the EXS import in AudioLayer?

    Thanks for any insights!

    update on this ^ issue:

    I tried a couple of EXS to SFZ conversions with the help of @espiegel123 and @jazzmess (thank you) which unfortunately didn't work but the free EXS2SFZ converter worked: importing the resulting SFZ produced an Audiolayer instrument with the previously only visible "Hats" layer and everything else on another layer. The converter is https://www.bjoernbojahr.de/exs2sfz.html.

  • is there any way to make the ModWheel to Layer A/B crossfade work in NS2 when using audio layer is an AU?
    Or any other way to crossfade layers manually?

  • @jo92346 said:
    is there any way to make the ModWheel to Layer A/B crossfade work in NS2 when using audio layer is an AU?
    Or any other way to crossfade layers manually?

    That's quite easy:
    In the list of Layers you can go to the Layer settings tapping the ">" on Layer A
    Then set "Articulation" to "mod wheel up"
    Make the same with Layer B but this time set "mod wheel down"

  • I did that, it's working perfectly in audio layer as a standalone, but not in NS2 as an AU. it's like the mod wheel cc is not transmitted at all.

  • @jo92346 said:
    I did that, it's working perfectly in audio layer as a standalone, but not in NS2 as an AU. it's like the mod wheel cc is not transmitted at all.

    Just tried this and it's not working here too. I'm not firm with NS2 maybe someone knowing NS2 better can shed some light?
    In AUM it works perfectly.

  • it is also working in garageband. I guess this is an NS2 issue.

  • @VirSyn said:

    @jo92346 said:
    I did that, it's working perfectly in audio layer as a standalone, but not in NS2 as an AU. it's like the mod wheel cc is not transmitted at all.

    Just tried this and it's not working here too. I'm not firm with NS2 maybe someone knowing NS2 better can shed some light?
    In AUM it works perfectly.

    talking of audio layer, I don't know if it was already asked by someone, but I really need a cc that can be set up to select a layer based on its value (example cc 16 = 0 to 32 play layer 1, cc=33 to 64 play layer 2, cc 50 to 127 play layer 3 -- with crossfade if needed) . The mod wheel is too limited and I'd prefer to assign the CC I want to a knob or a fader on my controller.

  • @jo92346 said:

    @VirSyn said:

    @jo92346 said:
    I did that, it's working perfectly in audio layer as a standalone, but not in NS2 as an AU. it's like the mod wheel cc is not transmitted at all.

    Just tried this and it's not working here too. I'm not firm with NS2 maybe someone knowing NS2 better can shed some light?
    In AUM it works perfectly.

    talking of audio layer, I don't know if it was already asked by someone, but I really need a cc that can be set up to select a layer based on its value (example cc 16 = 0 to 32 play layer 1, cc=33 to 64 play layer 2, cc 50 to 127 play layer 3 -- with crossfade if needed) . The mod wheel is too limited and I'd prefer to assign the CC I want to a knob or a fader on my controller.

    just put this on the AudioLayer list.

  • edited October 2022
    The user and all related content has been deleted.
Sign In or Register to comment.