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.8 update

24

Comments

  • dalton34grdalton34gr

    @bargale said:

    @dalton34gr said:

    @NeuM said:

    @dalton34gr said:
    Hi
    After Update I Managed To Run AudioLayer As Standalone It Worked Fine. Then I tried To Load It On AUM It Did Not Load I’ve RunThe App On The Background As Standalone And Try To Load It In AUM But No Luck I Went And Uninstalled The “last state”
    As Mentioned Above Again No Luck I Rebooted No Luck I Uninstalled The App And Reinstalled It Now It’s Not Running Either Way Not Standalone Nor As AUv3 Any Help Is Welcome
    Ps I Gave It A Try With Logic No Luck Also
    My iPad Model Is

    16.6.1
    iPad Pro (12.9-inch) (4th generation)WiFi
    256Gb

    Thank You !!!!!

    You did a full shutdown/force restart of your iPad Pro?

    Hi @NeuM
    Yes I Did
    I Managed to make AudioLayer Work Again by Coping The “las state” File of Xinematix into AudioLayer And Worked !!!
    Now Both work but AudioLayer Nit As AUv3 just Standalone Xinematix Work Fine Both Ways
    Thanks !!!

    How?

    With File Manager Navigate to Xinematix directory open the directory then hold on the “last file” file till the menu show make copy
    Navigate to the AudioLayer Directory Delete the old one and paste the file you just copied

  • NeuMNeuM

    @dalton34gr said:

    @bargale said:

    @dalton34gr said:

    @NeuM said:

    @dalton34gr said:
    Hi
    After Update I Managed To Run AudioLayer As Standalone It Worked Fine. Then I tried To Load It On AUM It Did Not Load I’ve RunThe App On The Background As Standalone And Try To Load It In AUM But No Luck I Went And Uninstalled The “last state”
    As Mentioned Above Again No Luck I Rebooted No Luck I Uninstalled The App And Reinstalled It Now It’s Not Running Either Way Not Standalone Nor As AUv3 Any Help Is Welcome
    Ps I Gave It A Try With Logic No Luck Also
    My iPad Model Is

    16.6.1
    iPad Pro (12.9-inch) (4th generation)WiFi
    256Gb

    Thank You !!!!!

    You did a full shutdown/force restart of your iPad Pro?

    Hi @NeuM
    Yes I Did
    I Managed to make AudioLayer Work Again by Coping The “las state” File of Xinematix into AudioLayer And Worked !!!
    Now Both work but AudioLayer Nit As AUv3 just Standalone Xinematix Work Fine Both Ways
    Thanks !!!

    How?

    With File Manager Navigate to Xinematix directory open the directory then hold on the “last file” file till the menu show make copy
    Navigate to the AudioLayer Directory Delete the old one and paste the file you just copied

    Interesting. I didn’t even realize it was possible to do this.

  • dalton34grdalton34gr

    I Hope That Harry Will Come Up With The Solution Fro AUv3 Problem He Always Does !!!

  • dalton34grdalton34gr

    Hi Everybody!!
    Good news AudioLayer is loading In AUM As AUv3 Synth And As MFx with Xinematix Loaded Too
    What I Did Is I tried To Load AudioLayer As Last State Choice in AUM And Try To Replace An Instrument Input Already Set With AudioLayer I Also Try To Load MFx On Master Channel Replacing An FX Too.I Think This Is What Made The App To Crash
    I Also Try To Load As New Instrument in Logic On An Already Song And The App Crashed There Too I Will Try To Load AudioLayer In Logic With A Fresh Song And I Will Let You Know The Results
    Please Try With A new Set In AUM To See If It Works For You
    Thanks

  • bargalebargale

    @dalton34gr said:
    Hi Everybody!!
    Good news AudioLayer is loading In AUM As AUv3 Synth And As MFx with Xinematix Loaded Too
    What I Did Is I tried To Load AudioLayer As Last State Choice in AUM And Try To Replace An Instrument Input Already Set With AudioLayer I Also Try To Load MFx On Master Channel Replacing An FX Too.I Think This Is What Made The App To Crash
    I Also Try To Load As New Instrument in Logic On An Already Song And The App Crashed There Too I Will Try To Load AudioLayer In Logic With A Fresh Song And I Will Let You Know The Results
    Please Try With A new Set In AUM To See If It Works For You
    Thanks

    Seems like you’re lucky
    I’m not able to run it not as standalone nor au after trashing the last state.
    Prior to last state file. Only standalone worked…

  • dalton34grdalton34gr

    @bargale said:

    @dalton34gr said:
    Hi Everybody!!
    Good news AudioLayer is loading In AUM As AUv3 Synth And As MFx with Xinematix Loaded Too
    What I Did Is I tried To Load AudioLayer As Last State Choice in AUM And Try To Replace An Instrument Input Already Set With AudioLayer I Also Try To Load MFx On Master Channel Replacing An FX Too.I Think This Is What Made The App To Crash
    I Also Try To Load As New Instrument in Logic On An Already Song And The App Crashed There Too I Will Try To Load AudioLayer In Logic With A Fresh Song And I Will Let You Know The Results
    Please Try With A new Set In AUM To See If It Works For You
    Thanks

    Seems like you’re lucky
    I’m not able to run it not as standalone nor au after trashing the last state.
    Prior to last state file. Only standalone worked…

    Where You Try To Run it as AUv3 ? Witch DAW

  • dalton34grdalton34gr


    It Works Ok In Logic !!

  • bargalebargale
    edited September 2023

    @dalton34gr said:

    @bargale said:

    @dalton34gr said:
    Hi Everybody!!
    Good news AudioLayer is loading In AUM As AUv3 Synth And As MFx with Xinematix Loaded Too
    What I Did Is I tried To Load AudioLayer As Last State Choice in AUM And Try To Replace An Instrument Input Already Set With AudioLayer I Also Try To Load MFx On Master Channel Replacing An FX Too.I Think This Is What Made The App To Crash
    I Also Try To Load As New Instrument in Logic On An Already Song And The App Crashed There Too I Will Try To Load AudioLayer In Logic With A Fresh Song And I Will Let You Know The Results
    Please Try With A new Set In AUM To See If It Works For You
    Thanks

    Seems like you’re lucky
    I’m not able to run it not as standalone nor au after trashing the last state.
    Prior to last state file. Only standalone worked…

    Where You Try To Run it as AUv3 ? Witch DAW

    Every daw I tried in.
    Wish I didn’t update lol

  • espiegel123espiegel123

    Running fine for me standalone and as AU instrument in Loopy Pro and AUM. iOS 16.6

  • dalton34grdalton34gr

    I Am At iOS 16.6.1

  • auxmuxauxmux

    @VirSyn The midi mapping feature in AudioLayer is not working. The drop-down for midi cc is appearing but it's not possible to select a specific midi cc.

  • VirSynVirSyn

    @auxmux said:
    @VirSyn The midi mapping feature in AudioLayer is not working. The drop-down for midi cc is appearing but it's not possible to select a specific midi cc.

    the MIDI mapping is not complete at the moment. That's the reason I didn't added it to the feature list/manual. Just forgot to remove the drop down menu...
    But now it's really in the last stages and planned for the next non-bug fix release.

  • auxmuxauxmux

    @VirSyn said:

    @auxmux said:
    @VirSyn The midi mapping feature in AudioLayer is not working. The drop-down for midi cc is appearing but it's not possible to select a specific midi cc.

    the MIDI mapping is not complete at the moment. That's the reason I didn't added it to the feature list/manual. Just forgot to remove the drop down menu...
    But now it's really in the last stages and planned for the next non-bug fix release.

    Cool, sounds good, thanks!

  • lukesleepwalkerlukesleepwalker

    @VirSyn said:

    @auxmux said:
    @VirSyn The midi mapping feature in AudioLayer is not working. The drop-down for midi cc is appearing but it's not possible to select a specific midi cc.

    the MIDI mapping is not complete at the moment. That's the reason I didn't added it to the feature list/manual. Just forgot to remove the drop down menu...
    But now it's really in the last stages and planned for the next non-bug fix release.

    Glad to hear this!

  • RockBottomRockBottom
    edited September 2023

    Can anybody tell me what kind of helper Audio Layer is expecting when it fails like it does below:

  • RockBottomRockBottom
    edited September 2023

  • RockBottomRockBottom
    edited September 2023

    this happens immediately when I try to open the plug-in — and restarting the machine does not help!

    Yet Audio Layer functions alright as a standalone application…

    iPad Pro (11-inch) (4th generation) iPadOS 16.6

  • SamuSamu

    @RockBottom said:
    this happens immediately when I try to open the plug-in, and restarting the machine does not help!

    What iPad and iPadOS version are you using?!

  • bargalebargale

    @RockBottom said:

    Fixed in beta, prolly out in a day or 2

  • RockBottomRockBottom

    thanks!

  • _ki_ki

    @VirSyn I just want to confirm that the updated AudioLayer v1.8.1 fixed the startup problem on my iPad Pro 10.5 / IOS 16.2, i also checked that the AUv3 is working again.

    Thanks a lot for the fast fix 👍🏼

  • VirSynVirSyn

    @_ki said:
    @VirSyn I just want to confirm that the updated AudioLayer v1.8.1 fixed the startup problem on my iPad Pro 10.5 / IOS 16.2, i also checked that the AUv3 is working again.

    Thanks a lot for the fast fix 👍🏼

    Thank you for your feedback!

  • dalton34grdalton34gr

    AudioLayer is loading fine now thanks for the update !!!!!

  • RockBottomRockBottom

    Thank you!

  • Paulo164Paulo164
    edited October 2023

    Hi @VirSyn,
    I think I have found an unexpected behavior with “round robin”.
    As I understand the feature, it is supposed to cycle (loop for each… in dev terms) between layers which has the option activated.
    However, you can try the following experiment :
    - create 1 layer
    - create a zone (for any keys) covering velocities from 1 to 100 with a sample
    - create another zone (same keys) covering velocities from 30 to 127
    - activate the round robin option for this layer
    => now when you play a note in the range of velocities 30 to 127, it will play alternatively the 2 zones while applying the cross faded volume, but for 1 zone at a time.
    The sonic result is very inconsistent.
    So maybe I am mistaking the original purpose of this feature but I think this is not what you intended to do 🤔
    Thank you very much !

    EDIT : to be clear, it also cycles through layers with activated round robin, but it cumulates this with the behavior described above. So it cycles from layer to layer and, within each layer, from zone to zone (only where velocities overlaps).
    If you have 2 layers, each one having 2 overlapping zones, then pressing 4 times in the overlapped area will produce a different tone each time.

  • VirSynVirSyn

    @Paulo164 said:
    Hi @VirSyn,
    I think I have found an unexpected behavior with “round robin”.
    As I understand the feature, it is supposed to cycle (loop for each… in dev terms) between layers which has the option activated.
    However, you can try the following experiment :
    - create 1 layer
    - create a zone (for any keys) covering velocities from 1 to 100 with a sample
    - create another zone (same keys) covering velocities from 30 to 127
    - activate the round robin option for this layer
    => now when you play a note in the range of velocities 30 to 127, it will play alternatively the 2 zones while applying the cross faded volume, but for 1 zone at a time.
    The sonic result is very inconsistent.
    So maybe I am mistaking the original purpose of this feature but I think this is not what you intended to do 🤔
    Thank you very much !

    EDIT : to be clear, it also cycles through layers with activated round robin, but it cumulates this with the behavior described above. So it cycles from layer to layer and, within each layer, from zone to zone (only where velocities overlaps).
    If you have 2 layers, each one having 2 overlapping zones, then pressing 4 times in the overlapped area will produce a different tone each time.

    @Paulo164 just tried this scenario and can confirm the weird behaviour. Added on my list, thanks.

  • Paulo164Paulo164

    @VirSyn said:

    @Paulo164 said:
    Hi @VirSyn,
    I think I have found an unexpected behavior with “round robin”.
    As I understand the feature, it is supposed to cycle (loop for each… in dev terms) between layers which has the option activated.
    However, you can try the following experiment :
    - create 1 layer
    - create a zone (for any keys) covering velocities from 1 to 100 with a sample
    - create another zone (same keys) covering velocities from 30 to 127
    - activate the round robin option for this layer
    => now when you play a note in the range of velocities 30 to 127, it will play alternatively the 2 zones while applying the cross faded volume, but for 1 zone at a time.
    The sonic result is very inconsistent.
    So maybe I am mistaking the original purpose of this feature but I think this is not what you intended to do 🤔
    Thank you very much !

    EDIT : to be clear, it also cycles through layers with activated round robin, but it cumulates this with the behavior described above. So it cycles from layer to layer and, within each layer, from zone to zone (only where velocities overlaps).
    If you have 2 layers, each one having 2 overlapping zones, then pressing 4 times in the overlapped area will produce a different tone each time.

    @Paulo164 just tried this scenario and can confirm the weird behaviour. Added on my list, thanks.

    Thank you
    🙏👍

  • SamuSamu

    @VirSyn Did something 'break' in the latest AudioLayer update (1.9.2) when it comes to reading loop-points embedded in *.wav files?

    Most of the samples I use have loop meta-data embedded in the 'smpl' chunk of the *.wav file and these seem to be ignored when imported into AudioLayer?!
    https://www.dropbox.com/s/sd2vv0yzg6xg5t0/SY85_2022.zip?dl=0

    I was just about to start creating some presets for AudioLayer based on my own samples...
    ...and noticed that the loops points were not imported at all :(

    In order to be able to use the same samples in multiple presets without duplicating them I copied them to iCloud Drive/Audio Layer/samples/

    Also noticed that after loading a new sample into a new preset it won't play before saving the preset and reloading it again?!

    Hopefully it's just a minor glitch in the matrix :sunglasses:

    Cheers!

  • BirdpieBirdpie
    edited November 2023

    got broken sfz imports after the last update.
    those instruments immediately chrash audiolayer when select.
    so sfz import is broken here, will test the other import options.

    hardreset doesn't change it.

  • BirdpieBirdpie

    audiolayer deletes the corresponding sample even when choosing no in the dialogue.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024