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 1.6.0

13567

Comments

  • @kagamul said:

    1. When I load the sfz version of Sampletekks Rain Piano it plays but when I open the layer settings and scroll down Audiolayer crashes. Layer settings work fine with the factory instruments.

    For me also : a lot of crashes unless I load first a factory instrument, then only my instrument.

  • @swarmboy said:

    @VirSyn said:

    @swarmboy said:

    @VirSyn said:

    @swarmboy said:
    Fantastic update. Is there a way to move the local sample library to external storage?

    haven't tried this but...
    ...should be possible with the Instrument sharing option "Create Zip for Instrument+SampleFolder '/'"
    Take the generated zip file which contains all instruments and samples and unzip it to the new sample location.
    If it's too big to handle you have to zip the Instrument folders one by one.

    thanks. gave this a try but no luck. couldn't unzip in new location for folders or single instruments. might it be possible to add a "copy library to external media" function?

    hmm, just tried it here and it worked perfect. How big were the zip files ?

    the smallest was 37Mb. Will try again - probably something dumb I'm doing...

    managed to zip and unzip an instrument and place it on the external storage. however, the created ".instrument" folder contains separate folders for instruments, samples, etc and all in the original hierarchy they were in on the internal storage. it's possible to move things to the correct subfolders, but will be painful for a large library (>100Gb in my case). Could try zipping the whole library but that could also get tricky with storage.

    my own fault for not getting more storage...

  • @Paulo164 said:
    Hi,
    After some trials, it seems that my instrument created with the previous version can’t be fixed with the new version 1.6.0.
    I mean, the 2 layers are still bound together without possibility to set the parameters of each layer independently.
    Maybe if I create a new instrument from scratch it would be okay but no way to fix “corrupted” instrument… It would take a lot of time to do all again 😬
    @VirSyn , maybe I could send you my choir instrument so you can have a quick look, judge by yourself and see if there is a way to fix the file ? Thank you very much ! 😚

    That's the fastest way to fix it, send me your instrument as zip with instrument+samples

  • @kagamul said:
    I’ve got two other problems.

    1. When I load the sfz version of Sampletekks Rain Piano it plays but when I open the layer settings and scroll down Audiolayer crashes. Layer settings work fine with the factory instruments.

    2. I cannot manage to make Audiolayer import the samples for Sampletekks Vertikal (exs Version). I tried everything I could think of. It doesn’t find the files.

    I testet on iPad9 and iPad Pro 9.7, latest iOS version.

    I don’t have the Sampletekk here, but with other imported instruments I couldn’t reproduce this.
    Could you send me a screenshot of the Layer settings before scrolling ?

    The import of EXS files can be problematic if you import one exs file with the “Import” function.
    This only works if you copy all samples files and the exs file into the import folder of AudioLayer. Otherwise AudioLayer
    has no access rights.

  • @swarmboy said:

    @swarmboy said:

    @VirSyn said:

    @swarmboy said:

    @VirSyn said:

    @swarmboy said:
    Fantastic update. Is there a way to move the local sample library to external storage?

    haven't tried this but...
    ...should be possible with the Instrument sharing option "Create Zip for Instrument+SampleFolder '/'"
    Take the generated zip file which contains all instruments and samples and unzip it to the new sample location.
    If it's too big to handle you have to zip the Instrument folders one by one.

    thanks. gave this a try but no luck. couldn't unzip in new location for folders or single instruments. might it be possible to add a "copy library to external media" function?

    hmm, just tried it here and it worked perfect. How big were the zip files ?

    the smallest was 37Mb. Will try again - probably something dumb I'm doing...

    managed to zip and unzip an instrument and place it on the external storage. however, the created ".instrument" folder contains separate folders for instruments, samples, etc and all in the original hierarchy they were in on the internal storage. it's possible to move things to the correct subfolders, but will be painful for a large library (>100Gb in my case). Could try zipping the whole library but that could also get tricky with storage.

    my own fault for not getting more storage...

    100 GB ? uups :o
    Have put your request for a copy procedure on my list, but this may need a bit of time. Definitely not with the next update, sorry.

  • @VirSyn said:

    @kagamul said:
    I’ve got two other problems.

    1. When I load the sfz version of Sampletekks Rain Piano it plays but when I open the layer settings and scroll down Audiolayer crashes. Layer settings work fine with the factory instruments.

    2. I cannot manage to make Audiolayer import the samples for Sampletekks Vertikal (exs Version). I tried everything I could think of. It doesn’t find the files.

    I testet on iPad9 and iPad Pro 9.7, latest iOS version.

    I don’t have the Sampletekk here, but with other imported instruments I couldn’t reproduce this.
    Could you send me a screenshot of the Layer settings before scrolling ?

    The import of EXS files can be problematic if you import one exs file with the “Import” function.
    This only works if you copy all samples files and the exs file into the import folder of AudioLayer. Otherwise AudioLayer
    has no access rights.

    I can scroll as low as the sustain pedal tab - when I geh to the key switch, it crashes.
    Fir the exs import I followed the exact eInstructions: exs file and the samples in the sample folder both in the import folder.


  • @VirSyn said:

    @Paulo164 said:
    Hi,
    After some trials, it seems that my instrument created with the previous version can’t be fixed with the new version 1.6.0.
    I mean, the 2 layers are still bound together without possibility to set the parameters of each layer independently.
    Maybe if I create a new instrument from scratch it would be okay but no way to fix “corrupted” instrument… It would take a lot of time to do all again 😬
    @VirSyn , maybe I could send you my choir instrument so you can have a quick look, judge by yourself and see if there is a way to fix the file ? Thank you very much ! 😚

    That's the fastest way to fix it, send me your instrument as zip with instrument+samples

    That’s very kind from you ! Can I send it to [email protected] ?
    Thanks.

  • @Paulo164 said:

    @VirSyn said:

    @Paulo164 said:
    Hi,
    After some trials, it seems that my instrument created with the previous version can’t be fixed with the new version 1.6.0.
    I mean, the 2 layers are still bound together without possibility to set the parameters of each layer independently.
    Maybe if I create a new instrument from scratch it would be okay but no way to fix “corrupted” instrument… It would take a lot of time to do all again 😬
    @VirSyn , maybe I could send you my choir instrument so you can have a quick look, judge by yourself and see if there is a way to fix the file ? Thank you very much ! 😚

    That's the fastest way to fix it, send me your instrument as zip with instrument+samples

    That’s very kind from you ! Can I send it to [email protected] ?
    Thanks.

    yes Sir

  • @VirSyn said:

    @Paulo164 said:

    @VirSyn said:

    @Paulo164 said:
    Hi,
    After some trials, it seems that my instrument created with the previous version can’t be fixed with the new version 1.6.0.
    I mean, the 2 layers are still bound together without possibility to set the parameters of each layer independently.
    Maybe if I create a new instrument from scratch it would be okay but no way to fix “corrupted” instrument… It would take a lot of time to do all again 😬
    @VirSyn , maybe I could send you my choir instrument so you can have a quick look, judge by yourself and see if there is a way to fix the file ? Thank you very much ! 😚

    That's the fastest way to fix it, send me your instrument as zip with instrument+samples

    That’s very kind from you ! Can I send it to [email protected] ?
    Thanks.

    yes Sir

    Thanks. Just sent with File drop.
    Let me know in case you didn’t receive it.

  • @VirSyn said:

    @swarmboy said:

    @swarmboy said:

    @VirSyn said:

    @swarmboy said:

    @VirSyn said:

    @swarmboy said:
    Fantastic update. Is there a way to move the local sample library to external storage?

    haven't tried this but...
    ...should be possible with the Instrument sharing option "Create Zip for Instrument+SampleFolder '/'"
    Take the generated zip file which contains all instruments and samples and unzip it to the new sample location.
    If it's too big to handle you have to zip the Instrument folders one by one.

    thanks. gave this a try but no luck. couldn't unzip in new location for folders or single instruments. might it be possible to add a "copy library to external media" function?

    hmm, just tried it here and it worked perfect. How big were the zip files ?

    the smallest was 37Mb. Will try again - probably something dumb I'm doing...

    managed to zip and unzip an instrument and place it on the external storage. however, the created ".instrument" folder contains separate folders for instruments, samples, etc and all in the original hierarchy they were in on the internal storage. it's possible to move things to the correct subfolders, but will be painful for a large library (>100Gb in my case). Could try zipping the whole library but that could also get tricky with storage.

    my own fault for not getting more storage...

    100 GB ? uups :o
    Have put your request for a copy procedure on my list, but this may need a bit of time. Definitely not with the next update, sorry.

    that would be amazing. I'm doing it in big chunks and seeing how it goes - I think because it can zip higher level folders, it actually shouldn't be that bad.

    just to say, too, it's an incredible app - has revolutionised how I make music on the go, so thanks!

  • @Paulo164 said:

    @VirSyn said:

    @Paulo164 said:

    @VirSyn said:

    @Paulo164 said:
    Hi,
    After some trials, it seems that my instrument created with the previous version can’t be fixed with the new version 1.6.0.
    I mean, the 2 layers are still bound together without possibility to set the parameters of each layer independently.
    Maybe if I create a new instrument from scratch it would be okay but no way to fix “corrupted” instrument… It would take a lot of time to do all again 😬
    @VirSyn , maybe I could send you my choir instrument so you can have a quick look, judge by yourself and see if there is a way to fix the file ? Thank you very much ! 😚

    That's the fastest way to fix it, send me your instrument as zip with instrument+samples

    That’s very kind from you ! Can I send it to [email protected] ?
    Thanks.

    yes Sir

    Thanks. Just sent with File drop.
    Let me know in case you didn’t receive it.

    nothing here sorry

  • @VirSyn just want to make sure you’ve seen these posts regarding SSD performance 👇

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Knowing the SSD model, iPad model and connection method (using-c, cck, etc) would be good to know.

    @McD said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Can you share the model of SSD you're using? I'd like to research specs on SSD's when used with iPads. I wonder if moving instruments between external SSD and local storage before using is a potential workaround. I find the downloads from iCloud to be a total pain so I always use local in AudioLayer.

    I think, we either need to find an external SSD product that can service the needs of the app or find a workaround for swapping instruments in/out of local storage. We might need @virsyn's help on using the "swapping instruments" solution if it's not currently possible.

    Usb-C connection- direct and with a couple hubs. iPad Pro 2018. San disk extreme ssd

    @ipadbeatmaking said:

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Knowing the SSD model, iPad model and connection method (using-c, cck, etc) would be good to know.

    @McD said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Can you share the model of SSD you're using? I'd like to research specs on SSD's when used with iPads. I wonder if moving instruments between external SSD and local storage before using is a potential workaround. I find the downloads from iCloud to be a total pain so I always use local in AudioLayer.

    I think, we either need to find an external SSD product that can service the needs of the app or find a workaround for swapping instruments in/out of local storage. We might need @virsyn's help on using the "swapping instruments" solution if it's not currently possible.

    Usb-C connection- direct and with a couple hubs. iPad Pro 2018. San disk extreme ssd

    Just to follow up, the same hard drive is fast enough for all the gospel musicians apps (iPad) & heavy desktop virtual instruments. In both cases loading is snappy and there’s no dropouts or lag. So I’m confident the ssd itself isn’t the issue. The same patches also load fine on the internal drive, or using iCloud storage. The SSD option is the only one causing issues. The patches are around 300-400MB in size and are 3-4 velocities every 3 semi. Pretty hefty, but they worked fine prior.

  • @ipadbeatmaking said:
    @VirSyn just want to make sure you’ve seen these posts regarding SSD performance 👇

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Knowing the SSD model, iPad model and connection method (using-c, cck, etc) would be good to know.

    @McD said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Can you share the model of SSD you're using? I'd like to research specs on SSD's when used with iPads. I wonder if moving instruments between external SSD and local storage before using is a potential workaround. I find the downloads from iCloud to be a total pain so I always use local in AudioLayer.

    I think, we either need to find an external SSD product that can service the needs of the app or find a workaround for swapping instruments in/out of local storage. We might need @virsyn's help on using the "swapping instruments" solution if it's not currently possible.

    Usb-C connection- direct and with a couple hubs. iPad Pro 2018. San disk extreme ssd

    @ipadbeatmaking said:

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Knowing the SSD model, iPad model and connection method (using-c, cck, etc) would be good to know.

    @McD said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Can you share the model of SSD you're using? I'd like to research specs on SSD's when used with iPads. I wonder if moving instruments between external SSD and local storage before using is a potential workaround. I find the downloads from iCloud to be a total pain so I always use local in AudioLayer.

    I think, we either need to find an external SSD product that can service the needs of the app or find a workaround for swapping instruments in/out of local storage. We might need @virsyn's help on using the "swapping instruments" solution if it's not currently possible.

    Usb-C connection- direct and with a couple hubs. iPad Pro 2018. San disk extreme ssd

    Just to follow up, the same hard drive is fast enough for all the gospel musicians apps (iPad) & heavy desktop virtual instruments. In both cases loading is snappy and there’s no dropouts or lag. So I’m confident the ssd itself isn’t the issue. The same patches also load fine on the internal drive, or using iCloud storage. The SSD option is the only one causing issues. The patches are around 300-400MB in size and are 3-4 velocities every 3 semi. Pretty hefty, but they worked fine prior.

    sorry, the reason i forgot to comment this is that i already fixed it here :D

  • @VirSyn said:

    @Paulo164 said:

    @VirSyn said:

    @Paulo164 said:

    @VirSyn said:

    @Paulo164 said:
    Hi,
    After some trials, it seems that my instrument created with the previous version can’t be fixed with the new version 1.6.0.
    I mean, the 2 layers are still bound together without possibility to set the parameters of each layer independently.
    Maybe if I create a new instrument from scratch it would be okay but no way to fix “corrupted” instrument… It would take a lot of time to do all again 😬
    @VirSyn , maybe I could send you my choir instrument so you can have a quick look, judge by yourself and see if there is a way to fix the file ? Thank you very much ! 😚

    That's the fastest way to fix it, send me your instrument as zip with instrument+samples

    That’s very kind from you ! Can I send it to [email protected] ?
    Thanks.

    yes Sir

    Thanks. Just sent with File drop.
    Let me know in case you didn’t receive it.

    nothing here sorry

    It should be okay now.

  • Thoughts on au parameters? @VirSyn 🙏

  • I can play Pianobook files on this? Does this mean I never have to use Decent Sampler again? Say it is so!

  • @ghost_forests said:
    I can play Pianobook files on this? Does this mean I never have to use Decent Sampler again? Say it is so!

    Pianobook has a nice collection of EXS format samples and they import every time using the "Import Folder" approach. Importing "File" is hit or miss.

    For causal readers: Decent Sampler is free and there is a smaller collection of instruments at PianoBook that are in the Decent Sampler format. Many fail to install on IOS but seem to fare better on my Mac. The intersection of EXS and Decent Sampler instruments is in the 90% range I think.

    AudioLayer goes on sale periodically and like Ravenscroft 275 I recommend you go with the best in class but Decent Sampler will get you a nice collection for free if you can stand the buggy installs of many instruments. Decent Sampler is free but the developer does sell a handful of instruments in the app (like IAP's) to get some income from the effort.

  • Some Pianobook EXS24 instruments that had any controls for the sound, such as tone, attack, expression,etc. in my experience did not translate into AudioLayer. However, pianos from Pianobook all came in nicely from what I recall.
    I switched from AL to decent sampler just for the controls modwheel layer fading on Soft String Spurs. But decent sampler doesn’t load some large sample libraries for some reason. I need to try and import the ones that failed to import in Decent Sampler into AudioLayer. There are some good Christian Henson pianos I couldn’t get to work on DS that I may try now on AL :#

  • @VirSyn said:

    @ipadbeatmaking said:
    @VirSyn just want to make sure you’ve seen these posts regarding SSD performance 👇

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Knowing the SSD model, iPad model and connection method (using-c, cck, etc) would be good to know.

    @McD said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Can you share the model of SSD you're using? I'd like to research specs on SSD's when used with iPads. I wonder if moving instruments between external SSD and local storage before using is a potential workaround. I find the downloads from iCloud to be a total pain so I always use local in AudioLayer.

    I think, we either need to find an external SSD product that can service the needs of the app or find a workaround for swapping instruments in/out of local storage. We might need @virsyn's help on using the "swapping instruments" solution if it's not currently possible.

    Usb-C connection- direct and with a couple hubs. iPad Pro 2018. San disk extreme ssd

    @ipadbeatmaking said:

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Knowing the SSD model, iPad model and connection method (using-c, cck, etc) would be good to know.

    @McD said:

    @ipadbeatmaking said:
    @VirSyn so far the performance on SSD isn’t too good. Im getting a lot of crackling, and tracks aren’t freezing properly in hosts. With the internal HD this isn’t an issue but on a couple SSD’s i’ve tested, the issue is pretty consistent.

    Can you share the model of SSD you're using? I'd like to research specs on SSD's when used with iPads. I wonder if moving instruments between external SSD and local storage before using is a potential workaround. I find the downloads from iCloud to be a total pain so I always use local in AudioLayer.

    I think, we either need to find an external SSD product that can service the needs of the app or find a workaround for swapping instruments in/out of local storage. We might need @virsyn's help on using the "swapping instruments" solution if it's not currently possible.

    Usb-C connection- direct and with a couple hubs. iPad Pro 2018. San disk extreme ssd

    Just to follow up, the same hard drive is fast enough for all the gospel musicians apps (iPad) & heavy desktop virtual instruments. In both cases loading is snappy and there’s no dropouts or lag. So I’m confident the ssd itself isn’t the issue. The same patches also load fine on the internal drive, or using iCloud storage. The SSD option is the only one causing issues. The patches are around 300-400MB in size and are 3-4 velocities every 3 semi. Pretty hefty, but they worked fine prior.

    sorry, the reason i forgot to comment this is that i already fixed it here :D

    With action that fast, who needs words! Lol 😂

    Thanks, Looking forward to the update!

  • Very excited to try out the new external SSD option. Lifesaver for big sample libraries that just won’t fit (Sounds from Mars).
    Right now I’m copying about 50GB of samples/EXS to an external drive. I’m sort of confused by the root folder thing…. Here’s the scenario, hope someone can clarify:

    • I have a folder (/samples) on the external drive, containing all exs and samples in sub folders.
    • I’ll set audiolayer to use a (/audiolayer-instruments) folder in that same ssd as root.
    • Im supposed to batch import those with AudioLayer. Which I believe will copy all those samples over to the audiolayer root…
      That means I’ll have duplicated samples. Which in this case means a ton of space… Can’t I somehow just use one of the directories?.
      I assume there’s a hood reason why AudioLayer is not just linking to external files , and needs to import. But can’t I use that same audio layer root dir on the ssd to host the samples in case I want to remove the other (/samples) folder?.
      Ideally, if I could choose the folder with the samples already in it (//ssd/samples), AudioLayer would use that folder and existing samples without having to copy them all over.
      I believe my use case is pretty standard… Has anyone found a good method they can share?.
  • @VirSyn said:

    @espiegel123 said:

    @Poppadocrock said:
    Haven’t tried it yet but I’m curious… When using an SSD is there a specific way to name a folder so AL recognizes it? Or will it scan the drive looking for compatible presets? Or I guess I’m asking what’s the best way to set this up? Has anyone tried it yet. what’s the best way to set up the presets on a SSD?

    Do the same thing you would if putting files on your iPad. Create a parent folder for the stuff you wan to import. Move stuff into it. Do import folder and choose the parent folder you created.

    Things can get confusing now…
    The selection of a root storage folder for AudioLayer instrument and samples has nothing to do with the import of sample files or Sfz/exs instruments!

    You shouldn’t move any stuff inside the root storage folder! This has to be managed by AudioLayer.

    @tahiche . From the previous discussion, I believe the root folder on the SSD is a private folder, managed by AudioLayer. You can place the instrument samples anywhere, let AudioLayer import them, then you can delete your copy of the samples. You cannot place them in the AudioLayer root folder yourself.

  • @tahiche said:
    Very excited to try out the new external SSD option. Lifesaver for big sample libraries that just won’t fit (Sounds from Mars).
    Right now I’m copying about 50GB of samples/EXS to an external drive. I’m sort of confused by the root folder thing…. Here’s the scenario, hope someone can clarify:

    • I have a folder (/samples) on the external drive, containing all exs and samples in sub folders.
    • I’ll set audiolayer to use a (/audiolayer-instruments) folder in that same ssd as root.
    • Im supposed to batch import those with AudioLayer. Which I believe will copy all those samples over to the audiolayer root…
      That means I’ll have duplicated samples. Which in this case means a ton of space… Can’t I somehow just use one of the directories?.
      I assume there’s a hood reason why AudioLayer is not just linking to external files , and needs to import. But can’t I use that same audio layer root dir on the ssd to host the samples in case I want to remove the other (/samples) folder?.
      Ideally, if I could choose the folder with the samples already in it (//ssd/samples), AudioLayer would use that folder and existing samples without having to copy them all over.
      I believe my use case is pretty standard… Has anyone found a good method they can share?.

    Follow this video steps to share instruments.

  • Hi!
    So I tried importing from SSD. Here’s what’s happening.
    Ser the root folder to ssd

    Then I batch import from a Samples from mars directory on the same ssd but diff directory.

    I can see the samples . Means I can probably delete the original folder and use this one if I need to access those samples to import elsewhere. No?
    The key difference between the root folder on the ssd or local, seems to be that samples and instruments are visible on the audiolayer folder in the ssd. I might be wrong but I think they’re hidden in local storage.

  • @tahiche said:
    Hi!
    So I tried importing from SSD. Here’s what’s happening.
    Ser the root folder to ssd
    Then I batch import from a Samples from mars directory on the same ssd but diff directory.

    I can see the samples . Means I can probably delete the original folder and use this one if I need to access those samples to import elsewhere. No?
    The key difference between the root folder on the ssd or local, seems to be that samples and instruments are visible on the audiolayer folder in the ssd. I might be wrong but I think they’re hidden in local storage.

    Just want to confirm that this is exactly true B)

  • @VirSyn : can one have some instruments loaded locally and others from external drive?

  • @espiegel123 said:
    @VirSyn : can one have some instruments loaded locally and others from external drive?

    Not at the same from what I can see.

  • @VirSyn said:

    @tahiche said:
    Hi!
    So I tried importing from SSD. Here’s what’s happening.
    Ser the root folder to ssd
    Then I batch import from a Samples from mars directory on the same ssd but diff directory.

    I can see the samples . Means I can probably delete the original folder and use this one if I need to access those samples to import elsewhere. No?
    The key difference between the root folder on the ssd or local, seems to be that samples and instruments are visible on the audiolayer folder in the ssd. I might be wrong but I think they’re hidden in local storage.

    Just want to confirm that this is exactly true B)

    Works great. I now have my whole Samples From Mars lib on a external drive as AudioLayer instruments. I also copied the original EXS files in case I want to use it with a computer or something.
    I simply couldn’t use the SFM lib before, takes up too much space. Even tried a “minimized” version where instead of one sample per note I only had a sample per octave. Wouldn’t work as the root notes where all screwed up.
    So this is great 👍

    @VirSyn i do have one request, hope it’s not complicated… FAVS!!. Going through the SFM folders there’s hundreds of presets. I’d really like to mark the ones I like for easy recall. What I’m doing now is saving a copy of the instrument and then “move” to a FAV folder, but it’s not ideal and wouldn’t reflect any changes to the original. I’d love to be able to add tags and such but anything to make recalling those preferred sounds would be very welcome.
    Great job, thank u! 👏

  • @tahiche said:

    @VirSyn said:

    @tahiche said:
    Hi!
    So I tried importing from SSD. Here’s what’s happening.
    Ser the root folder to ssd
    Then I batch import from a Samples from mars directory on the same ssd but diff directory.

    I can see the samples . Means I can probably delete the original folder and use this one if I need to access those samples to import elsewhere. No?
    The key difference between the root folder on the ssd or local, seems to be that samples and instruments are visible on the audiolayer folder in the ssd. I might be wrong but I think they’re hidden in local storage.

    Just want to confirm that this is exactly true B)

    Works great. I now have my whole Samples From Mars lib on a external drive as AudioLayer instruments. I also copied the original EXS files in case I want to use it with a computer or something.
    I simply couldn’t use the SFM lib before, takes up too much space. Even tried a “minimized” version where instead of one sample per note I only had a sample per octave. Wouldn’t work as the root notes where all screwed up.
    So this is great 👍

    @VirSyn i do have one request, hope it’s not complicated… FAVS!!. Going through the SFM folders there’s hundreds of presets. I’d really like to mark the ones I like for easy recall. What I’m doing now is saving a copy of the instrument and then “move” to a FAV folder, but it’s not ideal and wouldn’t reflect any changes to the original. I’d love to be able to add tags and such but anything to make recalling those preferred sounds would be very welcome.
    Great job, thank u! 👏

    Samples from Mars are really well made. I've used them to test the importer - but also for just enjoying their high quality and lovely sounds.

    I put your request on my list...

  • @espiegel123 said:
    @VirSyn : can one have some instruments loaded locally and others from external drive?

    You can't use them at the same time - you have to switch the storage option before selecting a sound from one of them.

  • Hi,
    @Virsyn, in the same way as what pianobook is to Decent Sampler, it would be nice to have a kind of community who would contribute with original and free sample instruments (I mean free of any 3rd party copyright). Maybe the simplest solution would be to ask Pianobook owners to add the "AudioLayer" format to the list (they already have Kontakt, EXS24, SFZ, Noise and DS).

Sign In or Register to comment.