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

1212224262748

Comments

  • You know an update has to be coming to fix the local/iCloud loading issue and hopefully to allow SFZ instrument imports.
    Worst case there will be IAP's of tested Sampled Instrument or 3rd party IAPs like Scarbee. Right?

  • I bought 2 great BeatHawk instrument sets but when I tried them in a DAW they crackled like crazy. Sometimes, AUv3 support helps sell a product but it's just not practical.

    If I could sample them into an AudioLayer instrument I'd get more done. I'd just like a programmer to consider the effort involved and automate as much as possible. So, I'm going to wait before spending days making my own sample sets.

    I have all the time in the world since no one is waiting for me to make anything. My most precious commodity is time and I don't want to waste it if something better is around the corner to make life easier. I think it is...

    Someone should start a Patreon service for users to share presets, sampes, loops, etc. I'd pay something every month to post and download files of value to the community. Would you?
    Otherwise, we'll just get more IAP upsells which is OK but sharing our work is better for those without unlimited budgets for purchasing.

  • @McDtracy said:
    You know an update has to be coming to fix the local/iCloud loading issue and hopefully to allow SFZ instrument imports.
    Worst case there will be IAP's of tested Sampled Instrument or 3rd party IAPs like Scarbee. Right?

    Import and export please. I personally don't care too much if it's EXS24 or SFZ, both would be Ok for me, but I understand the big advantages of an open and human-readable format.

  • @rs2000 said:
    Import and export please.

    Got it. You want fries with that?

  • @McDtracy said:

    @rs2000 said:
    Import and export please.

    Got it. You want fries with that?

    yes.

  • is this like a simplified version of beatmaker 3s sampling / pad slicing ?

  • edited September 2018

    @reasOne said:
    is this like a simplified version of beatmaker 3s sampling / pad slicing ?

    Not really, it's rather a sampler with high polyphony and disk streaming capability so you can build, load and play huge instruments.
    You can sample, do basic edits (start/end/loop/XFade) but no slicing. It's not multi-timbral, layers cannot be set to receive on different MIDI channels, you cannot switch presets except manually loading inside the app.
    You also cannot export your work to any other known format but it does import EXS + WAV files including a custom filename-to-key-and-velocity-mapping structure.
    I've built my own grand piano and vibraphone libs for it so far. When layering both, the size is about 1.3GB with about 900 samples, and they play very well. This app really has potential if you want large-scale instruments.
    For beatmaking, you're better off with BM3 for sure, a fairly different concept.

  • @reasOne said:
    is this like a simplified version of beatmaker 3s sampling / pad slicing ?

    @VirSyn has a slicing App called ReSlice that does slice and dice of audio "samples". This is a user programmable "Rompler" like capability similar to what you'd find in a Stage Piano from Nord or Korg except you get to decide what to put in the "ROM". How long to sustain and loop/no loop the sample and how many layers and what happens when you life the key and what Modulations to apply and whether you should overlap ranges when a key is pressed and if so should they be weighted linearly or by summing and .... you get the idea. A lot of controls and decisions to tweak a perfect digeridoo over 127 values of MIDI. Ultra high digeridoo sounds just like a Bee 2 inches from your ear. You can also sample powertools and play them with MIDI.

  • @rs2000 said:
    You can sample, do basic edits (start/end/loop/XFade) but no slicing. It's not multi-timbral, layers cannot be set to receive on different MIDI channels, you cannot switch presets except manually loading inside the app.

    You can change presets via midi pc if you put them in the setlist folder.

  • @Multicellular said:

    @rs2000 said:
    You can sample, do basic edits (start/end/loop/XFade) but no slicing. It's not multi-timbral, layers cannot be set to receive on different MIDI channels, you cannot switch presets except manually loading inside the app.

    You can change presets via midi pc if you put them in the setlist folder.

    Cool, thanks! Haven't seen that in the manual ;)

  • edited September 2018

    @VirSyn
    When it comes to AudioLayer, its full SFZ support or bust for me. SFZ import is not good enough. EXS24 support is not good enough. I have Zero interest in your .instruments. I'm highly against iAPs, never have bought one, and never will. With that being said: @VirSyn if you go the iAP and .instrument focused route... I'll be disappointed, but I'll understand.

    In other news...
    @AudioKit , and I have been in contact multiple times this past month, and I don't know if this is public knowledge yet, but...

    So a SFZ AUv3 is coming. I'm actually developing and ActionRPG for iOS, and have a full developer account. So even if I have to do it myself... Soon.
    Hopefully AudioLayer update type of soon, but soon either way.

  • @Lithalean said:
    @VirSyn
    When it comes to AudioLayer, its full SFZ support or bust for me. SFZ import is not good enough. EXS24 support is not good enough. I have Zero interest in your .instruments. I'm highly against iAPs, never have bought one, and never will. With that being said: @VirSyn if you go the iAP and .instrument focused route... I'll be disappointed, but I'll understand.

    In other news...
    @AudioKit , and I have been in contact multiple times this past month, and I don't know if this is public knowledge yet, but...

    So a SFZ AUv3 is coming. I'm actually developing and ActionRPG for iOS, and have a full developer account. So even if I have to do it myself... Soon.
    Hopefully AudioLayer update type of soon, but soon either way.

    Why would you be disappointed if they go with IAP?not everyone is good with sound design.why can’t we ask for both IAp and SFZ?and if they make all over wishes come true then we are all happy.✌️😀

  • @Paa89 said:

    @Lithalean said:
    @VirSyn
    When it comes to AudioLayer, its full SFZ support or bust for me. SFZ import is not good enough. EXS24 support is not good enough. I have Zero interest in your .instruments. I'm highly against iAPs, never have bought one, and never will. With that being said: @VirSyn if you go the iAP and .instrument focused route... I'll be disappointed, but I'll understand.

    In other news...
    @AudioKit , and I have been in contact multiple times this past month, and I don't know if this is public knowledge yet, but...

    So a SFZ AUv3 is coming. I'm actually developing and ActionRPG for iOS, and have a full developer account. So even if I have to do it myself... Soon.
    Hopefully AudioLayer update type of soon, but soon either way.

    Why would you be disappointed if they go with IAP?not everyone is good with sound design.why can’t we ask for both IAp and SFZ?and if they make all over wishes come true then we are all happy.✌️😀

    Making SFZ support an IAP doesn't make sense if @Virsyn decides to switch from .instrument to .SFZ format. It's going to be a change in the instrument data representation format anyway (although the instrument definition held in memory will most likely remain unchanged) so it doesn't make much sense to add SFZ as an option on top.

  • I do feel that support for SFZ & SF2 files is the way to go without having to 'convert' them to yet another 'custom' format. Last time I checked *.SFZ was a standard zip-archive with an accompanying 'text-file' specifying the mapping of the *.wav files so there should be no need to 'convert' the patch, just add the extra headers to the accompanying xml/txt file keeping the compatibility of the SFZ file open.

    I do get that in order to 'stream' content from a *.zip/sfz archive it would need to be extracted to avoid extra overhead of having to uncompress the files from the archives every time they are used.

    Personally I chose to let Logic Pro X 'convert' all my SF2 files to EXS24 programs so I can easily access the individual samples when needed in order to be able to create custom programs by collecting samples from the various SF2 archives.

    I thought I'd be using AudioLayer a lot more for pure sampling and patch creation but the lack of preview during trimming of the recordings and simple edit tools for fade in &out and normalise keep me distant at the moment.

    I do hope features from ReSlice find it's way into AudioLayer.

  • edited September 2018

    We need to be patient...

    I’ve asked @VirSyn several months ago for Reslice fullscreen in AU mode, they asked it will be added but it’s still not there :'(

    They must be busy... SFZ?

    What I don’t understand however is that they were very responsive here at AudioLayer launch, and it seems to me they haven’t post any answers about SFZ progression since a while... Reminds me Intua/BM3 update, and some others. Communication is always appreciated when users put some money in an app, even if it’s an iOS price tag. Asking for answers in pretty legitime IMO. Refund is only possible 2 weeks... I barely use AL and only wait for SFZ support to start really using it. Creating a whole instrument is too much time consuming, and no easy EXS creation as a W10 user.

  • edited September 2018

    @Paa89 said:
    Why would you be disappointed if they go with IAP?not everyone is good with sound design.why can’t we ask for both IAp and SFZ?and if they make all over wishes come true then we are all happy.✌️😀

    I was talking about as in just supporting .instrument, and not .SFZ I 100% agree with you that sound design is not everyones thing. Although, because of SFZ's simplicity, it's extremely easy to learn. Also, because of an iDevice's mobility, ...
    1.) Audio Layer with Full .SFZ support.
    2.) ReSlice as a AUv3, and the ability to export as .SFZ
    ... people that never thought they'd be interested in sound design would fall in love with it.

    @rs2000 said:
    Making SFZ support an IAP doesn't make sense if @Virsyn decides to switch from .instrument to .SFZ format. It's going to be a change in the instrument data representation format anyway (although the instrument definition held in memory will most likely remain unchanged) so it doesn't make much sense to add SFZ as an option on top.

    I never said switch. They both can coexist. In fact, .instrument will support features .sfz won't, and also work with AudioLayer's more complex GUI controls. @Virsyn already said "they" as in his team, use a .SFZ importer to convert to the .instrument format (unless I misunderstood). So, I don't really think I need to convince "them" of why it would be an amazing thing. What I'm hoping is they have faith that they can make .instrument so polished and preconfigured/easy to use, that they won't view SFZ as a threat to revenue.

  • edited September 2018

    @Samu said:
    I do feel that support for SFZ & SF2 files is the way to go without having to 'convert' them to yet another 'custom' format. Last time I checked *.SFZ was a standard zip-archive with an accompanying 'text-file' specifying the mapping of the *.wav files so there should be no need to 'convert' the patch, just add the extra headers to the accompanying xml/txt file keeping the compatibility of the SFZ file open.

    I do get that in order to 'stream' content from a *.zip/sfz archive it would need to be extracted to avoid extra overhead of having to uncompress the files from the archives every time they are used.

    Personally I chose to let Logic Pro X 'convert' all my SF2 files to EXS24 programs so I can easily access the individual samples when needed in order to be able to create custom programs by collecting samples from the various SF2 archives.

    I do hope features from ReSlice find it's way into AudioLayer.

    Again, .SFZ over .SF2/.EXS24 anyday, SFZ is a OPEN format. Both .EXS24 and .SF2 have licensing/contractual issues. On top of that you'll need a desktop to create/edit the instruments. SFZ could be made, edited, and saved all from the iDevice.



    @Janosax said:
    We need to be patient...

    I’ve asked @VirSyn several months ago for Reslice fullscreen in AU mode, they asked it will be added but it’s still not there :'(

    Agreed! Its hard.
    @VirSyn
    1. AudioLayer with full .SFZ support (Create / Edit / Save)
    2. ReSlice as a AUv3 (with the ability to export to AudioLayer as a .SFZ)

    Please, and Thank You!

  • @VirSyn said:
    We're just on reworking the file management cloud and local to have more flexibility.
    We're here preparing orchestral libraries to get a substantial amount of content to help increasing the sales and it's done with an alpha version of our sfz importer and i think this will find it's way into AudioLater hopefully soon.

    So, the next update will likely address:

    The Local/iCloud storage issues - high probability

    Orchestral Libraries are coming - high probability (revenue)

    An SFZ Importer is in Alpha and being used as an internal tool to prepare new instruments - long way from Alpha to a product.

    Wait. So, many apps to play with. Try not to take it personally when code and product re-design takes time.

    If you don't have this App buy it to show how much we need an AUv3 Sampler with these new features added in an update.

    Can Doug (@thesoundtestroom) host EXS24 instruments on his Patreon site to give us a repository for the bigger instruments?

  • @Lithalean: Yes, that's what it could look like!

    BTW, being able to set a MIDI receive channel per layer would help live performance a lot using the standalone version. Currently I cannot have a multi-timbral instrument, except I'm missing something.

    @Samu said:
    I do feel that support for SFZ & SF2 files is the way to go without having to 'convert' them to yet another 'custom' format. Last time I checked *.SFZ was a standard zip-archive with an accompanying 'text-file' specifying the mapping of the *.wav files so there should be no need to 'convert' the patch, just add the extra headers to the accompanying xml/txt file keeping the compatibility of the SFZ file open.

    I have yet to find one property of AudioLayer instrument parameters that wouldn't be supported by SFZ, and if so, I guess we're ready to discuss about solutions :)

    I do get that in order to 'stream' content from a *.zip/sfz archive it would need to be extracted to avoid extra overhead of having to uncompress the files from the archives every time they are used.

    Streaming from zip is probably much like decompressing .wv (AudioKit) or FLAC files on-the-fly. May become problematic with high polyphony. Native Instruments developed their own "NCW" lossless-compressed audio file format that is not as efficient as FLAC but has better performance when decompressing on-the-fly.

    I thought I'd be using AudioLayer a lot more for pure sampling and patch creation but the lack of preview during trimming of the recordings and simple edit tools for fade in &out and normalise keep me distant at the moment.

    Yes, the lack of many editing tools doesn't help when trying to create a multi-sample instrument, samples cannot even be cropped or faded-in/out once saved.
    Having done a few instruments now I've found a workflow in which I do all the sample preparation on the laptop (including auto-naming, normalizing to RMS levels, cutting, fading/envelopes ...) and just auto-import the set of prepared WAV files in AudioLayer.
    That reduced AL to be a ROMpler more or less, but at least if the imported files match the naming syntax suggested by @Virsyn, they import and map properly so far.
    And I have to say that AL on an iPhone in my pocket with wired headphones attached and me wandering around the house playing a Yamaha grand piano on my keytar over bluetooth MIDI is a lot of fun :wink:

  • So much fun...

    I removed AudioLayer and re-installed it selecting Local Files so I can load the large Instruments quickly.

    I have upgraded to IOS 12 as well.

    Yesterday I could use AudioLayer in Cubasis as an AUv3 and freeze tracks to make an audio file.

    After the upgrade and re-install of the product thre Freezing of AUv3 the Salamander Piano instrument in Cubasis doesn't produce any audio.

    I'm guessing IOS 12 broke it.

    Hoping for an update. I guess I should submit a bug report. I've just always waited and moved on to other projects because they usually ask you to some work to solve the problem and I quit work.

  • edited September 2018

    @McDtracy said:
    So much fun...

    I removed AudioLayer and re-installed it selecting Local Files so I can load the large Instruments quickly.

    I have upgraded to IOS 12 as well.

    Yesterday I could use AudioLayer in Cubasis as an AUv3 and freeze tracks to make an audio file.

    After the upgrade and re-install of the product thre Freezing of AUv3 the Salamander Piano instrument in Cubasis doesn't produce any audio.

    I'm guessing IOS 12 broke it.

    Hoping for an update. I guess I should submit a bug report. I've just always waited and moved on to other projects because they usually ask you to some work to solve the problem and I quit work.

    You can choose local or iCloud on AL install? Can’t be changed after install?

    I just don’t use that app, waiting for SFZ...

  • @Janosax said:
    You can choose local or iCloud on AL install?

    You can toggle between the two settings. I wanted to clean out a lot of poorly made samples and re-import good instruments from Mainstage. So, I backed up the folders on iCloud and deleted the App. Then I re-installed. Slected Local Storage and imported the large Salamander Piano that was giving me grief
    downloading from iCloud. It installs quickly now.

    But IOS 12 seems to have broken the DAW's convert to audio in Cubasis and Auria Pro. So, more work for Virsyn (or maybe the DAW's) to stabilize the AUv3 instance. I also triad the IAA Instrument version and it also fails to convert to audio in both DAW's. It worked in IOS 11. Can't go back now. So, I'll have to wait for updates.

    Can’t be changed after install?

    When you toggle the instruments installed in that mode are visible. For me the DEMO Instruments are in the Local File system. I think Virsyn intends to let you pick the target at import
    in the next update based upon something they wrote here.

    I just don’t use that app, waiting for SFZ.

    I think there are some excellent SF2's but that option requires a Mac. When you have a Mac the $30 Mainstage provides all the sampled instruments you can get with Logic Pro X and there's some nice instruments there.

    I haven't found a lot of free SFZ's so I'm not excited by that possibility as other seem to be. Where are the SFZ's? I know Auria Pro can import them

    What might be nice is to see WaveMachine Labs break Lyra out of Auria Pro and stand it up as an SF2/SFZ capable sampler product. I think @VirSyn has a first provider advantage if they can execute on this update.

    It's likely they will add packages of Sampled Instruments to increase product uptake and tested stability.

    I hope this IOS 12 Update doesn't set the whole platform back months making a lot of Apps unstable in DAWs.

  • edited September 2018

    @McDtracy @VirSyn

    I’ve disabled iCloud storage in the app and I’ve lost all my files... they have come back after enabling the setting again.... risky!! :*

    Since iOS12 update, GarageBand AudioLayer merging/export sometimes makes GarageBand crashes. Rendered audio file always have sound issues with audio cracking. AL itself often crashes in GarageBand. GB is very stable with all AU, and GB never crashes. So it’s a bit unusual. iOS12/iPhone 7 Plus. Need to be fixed!!! :)

  • @Janosax said:
    I’ve disabled iCloud storage in the app and I’ve lost all my files... they have come back after enabling the setting again.... risky!! :*

    The application looks for these 2 directories:
    instruments
    samples

    They can be on iCloud or Local Storage. Any instruments and associated samples will be put in one of the other. Changing the iCloud/Local setting will make it appear as if these directories are empty but changing it back and the contents will re-appear.

    The directory "import" is always from iCloud (without regard to the Local/iCloud setting) to import EXS Instruments.

    It appears moving instruments from Local to iCloud or back isn't in the current version.

    Then theres the recordings directory and I'll wager it keeps 2 directories and the contents seems to change with the iCloud/Local setting.

    I'm going to stick with Local to make everything fast. I was hoping to move old backed up instruments in but I don't see a way to do that. Just import EXS Instruments and create instruments manually.

  • I was really excited to consider getting more AU's in DAW's working and my #1 AU was going to be AudioLayer. So, I've been knocked off my path.

    I think I'll spend the time waiting by using IOS as a sound module for my Mac and Logic Pro X and learning which EXS24 instruments are great.

    I imported the String+ EXS24 into AudioLayer and realized the transfer has a lot of issues. All the articulations are mapped to Layers but every Layer is activated by "Key Down" so it's got tremolos layered with legato, etc. So, it need a lot of manual work stripping out articulations into distinct instruments.

    There are long term solutions:

    1. Sharing instruments (not sure about sample ownership issues)
    2. Stable instrument packs as IAP's (tested and supported for bugs)
    3. Standardized instrument format (import/export) that leverage 1 and 2

    So, like most IOS App Users... we wait for improved stability.

  • @McDtracy said:
    I was really excited to consider getting more AU's in DAW's working and my #1 AU was going to be AudioLayer. So, I've been knocked off my path.

    I think I'll spend the time waiting by using IOS as a sound module for my Mac and Logic Pro X and learning which EXS24 instruments are great.

    I imported the String+ EXS24 into AudioLayer and realized the transfer has a lot of issues. All the articulations are mapped to Layers but every Layer is activated by "Key Down" so it's got tremolos layered with legato, etc. So, it need a lot of manual work stripping out articulations into distinct instruments.

    There are long term solutions:

    1. Sharing instruments (not sure about sample ownership issues)
    2. Stable instrument packs as IAP's (tested and supported for bugs)
    3. Standardized instrument format (import/export) that leverage 1 and 2

    So, like most IOS App Users... we wait for improved stability.

    I do hope that @VirSyn will be committed enough to refine and improve AudioLayer continuously. This app has potential!

  • AudioLayer crashing for me quite regularly in apeMatrix and AUM, no real change from iOS 11 though, seems fine with some instruments but other samples can more often cause a crash.

  • @McDtracy @Janosax @rs2000 @Carnbot @Samu

    https://musical-artifacts.com/artifacts?q=Lithalean
    1. Steinway Model B (SFZ)
    2. Vintage Kit (SFZ)
    3. Church Organ (SFZ)
    4. Accordion (SFZ)
    5. Upright Bass (SFZ)
    6. Classical Acoustic Guitar (SFZ)
    7. Marimba (SFZ)

    @WaveMachineLabs
    @VirSyn

    No BS paywall. Not locked behind some DAW.
    100% open and non-monolithic!
    Samples, beautifully out in the open, and uncompressed.
    Instruments or individual samples - Creatable / Editable / Sharable - by anyone!
    Music!

  • @Lithalean said:
    @McDtracy @Janosax @rs2000 @Carnbot @Samu

    https://musical-artifacts.com/artifacts?q=Lithalean
    1. Steinway Model B (SFZ)
    2. Vintage Kit (SFZ)
    3. Church Organ (SFZ)
    4. Accordion (SFZ)
    5. Upright Bass (SFZ)
    6. Classical Acoustic Guitar (SFZ)
    7. Marimba (SFZ)

    @WaveMachineLabs
    @VirSyn

    No BS paywall. Not locked behind some DAW.
    100% open and non-monolithic!
    Samples, beautifully out in the open, and uncompressed.
    Instruments or individual samples - Creatable / Editable / Sharable - by anyone!
    Music!

    This is excellent, thanks! You may want to change the info for the Upright Bass section though, it’s talking about classical guitar...

Sign In or Register to comment.