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.

Koala sampler update!!!!!

135

Comments

  • @CapnWillie said:
    I hope Elf ignores most of the feature requests and sticks to his winning visions for his app. Frequently on ABF folks overwhelm the most engaged Devs for tons of “upgrades” that take brilliant apps into complicated zone.

    Grooverider comes to mind. Probably an excellent app, but way too many features make it look over complicated. Hardly ever hear it mentioned around here anymore after the natives spent launch and months thereafter hounding the Dev for new feature after new feature. When’s the last time you saw a new Grooverider thread? Yeah. Right.

    Koala brilliance is in simplicity and speed. AU this, AU that....dude, it’s a sampler. Sample your AUs. If you can’t be bothered with that...Bm3.

    It’s hilarious to me that naysayers say Bm3 is too much.🤦🏽‍♂️ Same folks want fast and simple Kaola to be Bm3 apparently. I don’t get it.lol

    Yeah, let’s add more complexity and work for Elf because his own vision isn’t what we all love already.

    Stick to doing your thing @elf_audio

    PLEEEEEAAAAAAAAASE.

    We DEFINITELY don’t need Kaola to host AU so we can hear the same users complain about it crashing and lack of stability (As they do unfairly with Bm3).

    Kaola is near perfect as is. Please stay YOUR course sir. 🙏🏽

    End of rant.

    Agree 100%

  • @espiegel123 said:

    @RajahP said:

    @espiegel123 said:

    @RajahP said:

    @CapnWillie said:
    I hope Elf ignores most of the feature requests and sticks to his winning visions for his app. Frequently on ABF folks overwhelm the most engaged Devs for tons of “upgrades” that take brilliant apps into complicated zone.

    Grooverider comes to mind. Probably an excellent app, but way too many features make it look over complicated. Hardly ever hear it mentioned around here anymore after the natives spent launch and months thereafter hounding the Dev for new feature after new feature. When’s the last time you saw a new Grooverider thread? Yeah. Right.

    Koala brilliance is in simplicity and speed. AU this, AU that....dude, it’s a sampler. Sample your AUs. If you can’t be bothered with that...Bm3.

    It’s hilarious to me that naysayers say Bm3 is too much.🤦🏽‍♂️ Same folks want fast and simple Kaola to be Bm3 apparently. I don’t get it.lol

    Yeah, let’s add more complexity and work for Elf because his own vision isn’t what we all love already.

    Stick to doing your thing @elf_audio

    PLEEEEEAAAAAAAAASE.

    We DEFINITELY don’t need Kaola to host AU nor really be AU so we can hear the same users complain about it crashing and lack of stability (As they do unfairly with Bm3).

    Kaola is near perfect as is. Please stay YOUR course sir. 🙏🏽

    End of rant.

    You do know that iaa will be (what do they call it) ‘depreciated’ in the near future? Like it or not, AU is the future.. Anyway... GrooveRider is as complex as you make it.. Updated a couple days ago...

    Edit.. Jesus.. this thing is so nice.. will really love to have 2-3 instances going in a project... state saving.. etc.. the things that Au is known for... bless..

    Re "deprecated". No one knows how soon or far off that will have any impact. Deprecated APIs have sometimes remained suppprted for many years. Michael has said that he will find a way to make Audiobus work if/when IAA gets pulled from the OS.

    I personally hope Koala stays a strong standalone for maximum usability and stability.

    Seeing the export features now. Ableton Live export, etc. Loving it.. still, multi instances, state saving will be nice..

    Sure it would be nice: if it doesn't come at the expense of usability and stability and the development isn't so time-consuming that it comes at the expense of other refinements and doesn't require one to have the latest and greatest iPad or iPhone.

    Getting this all to work nicely as an AUv3 (particularly if one tends to fill up a project with a full-complement of samples) seems like a much bigger task than people imagine.

    One would think that future iOS updates will address the ‘limitations’ for Au that some folks mention here.. I’m not a programmer.. I can only speak from a user’s perspective..and Multi instances will be nice, state saving and all the good stuff Au is known for..

  • @Lil_Stu07 said:

    @CapnWillie said:
    I hope Elf ignores most of the feature requests and sticks to his winning visions for his app. Frequently on ABF folks overwhelm the most engaged Devs for tons of “upgrades” that take brilliant apps into complicated zone.

    Grooverider comes to mind. Probably an excellent app, but way too many features make it look over complicated. Hardly ever hear it mentioned around here anymore after the natives spent launch and months thereafter hounding the Dev for new feature after new feature. When’s the last time you saw a new Grooverider thread? Yeah. Right.

    Koala brilliance is in simplicity and speed. AU this, AU that....dude, it’s a sampler. Sample your AUs. If you can’t be bothered with that...Bm3.

    It’s hilarious to me that naysayers say Bm3 is too much.🤦🏽‍♂️ Same folks want fast and simple Kaola to be Bm3 apparently. I don’t get it.lol

    Yeah, let’s add more complexity and work for Elf because his own vision isn’t what we all love already.

    Stick to doing your thing @elf_audio

    PLEEEEEAAAAAAAAASE.

    We DEFINITELY don’t need Kaola to host AU so we can hear the same users complain about it crashing and lack of stability (As they do unfairly with Bm3).

    Kaola is near perfect as is. Please stay YOUR course sir. 🙏🏽

    End of rant.

    Agree 100%

    Plus 1

  • @supadom said:

    @Lil_Stu07 said:

    @CapnWillie said:
    I hope Elf ignores most of the feature requests and sticks to his winning visions for his app. Frequently on ABF folks overwhelm the most engaged Devs for tons of “upgrades” that take brilliant apps into complicated zone.

    Grooverider comes to mind. Probably an excellent app, but way too many features make it look over complicated. Hardly ever hear it mentioned around here anymore after the natives spent launch and months thereafter hounding the Dev for new feature after new feature. When’s the last time you saw a new Grooverider thread? Yeah. Right.

    Koala brilliance is in simplicity and speed. AU this, AU that....dude, it’s a sampler. Sample your AUs. If you can’t be bothered with that...Bm3.

    It’s hilarious to me that naysayers say Bm3 is too much.🤦🏽‍♂️ Same folks want fast and simple Kaola to be Bm3 apparently. I don’t get it.lol

    Yeah, let’s add more complexity and work for Elf because his own vision isn’t what we all love already.

    Stick to doing your thing @elf_audio

    PLEEEEEAAAAAAAAASE.

    We DEFINITELY don’t need Kaola to host AU so we can hear the same users complain about it crashing and lack of stability (As they do unfairly with Bm3).

    Kaola is near perfect as is. Please stay YOUR course sir. 🙏🏽

    End of rant.

    Agree 100%

    Plus 1

    Plus 10x. With update of piano roll so I can finally make sure to hit the damn downbeat: F'in perfection for my workflow.

  • [Okay, well... I could do with multi-file simultaneous import 😇]

  • @boberto said:
    [Okay, well... I could do with multi-file simultaneous import 😇]

    Huh?

    Disable the AudioShare import in the settings and use the document picker to select multiple files for import 😎

  • @supadom said:

    @Lil_Stu07 said:

    @CapnWillie said:
    I hope Elf ignores most of the feature requests and sticks to his winning visions for his app. Frequently on ABF folks overwhelm the most engaged Devs for tons of “upgrades” that take brilliant apps into complicated zone.

    Grooverider comes to mind. Probably an excellent app, but way too many features make it look over complicated. Hardly ever hear it mentioned around here anymore after the natives spent launch and months thereafter hounding the Dev for new feature after new feature. When’s the last time you saw a new Grooverider thread? Yeah. Right.

    Koala brilliance is in simplicity and speed. AU this, AU that....dude, it’s a sampler. Sample your AUs. If you can’t be bothered with that...Bm3.

    It’s hilarious to me that naysayers say Bm3 is too much.🤦🏽‍♂️ Same folks want fast and simple Kaola to be Bm3 apparently. I don’t get it.lol

    Yeah, let’s add more complexity and work for Elf because his own vision isn’t what we all love already.

    Stick to doing your thing @elf_audio

    PLEEEEEAAAAAAAAASE.

    We DEFINITELY don’t need Kaola to host AU so we can hear the same users complain about it crashing and lack of stability (As they do unfairly with Bm3).

    Kaola is near perfect as is. Please stay YOUR course sir. 🙏🏽

    End of rant.

    Agree 100%

    Plus 1

    Yes!! This update is absolute brilliant. Wouldn’t want to lose any of the flow due to AU making it crash - recording from Audiobus into it is good for me. Using it split screen with Documents app as the sample browser, drag multiple samples over at the same time.

    And man, Beats time stretching mode in a sampler?!?! Does anyone know of anything besides Ableton simpler that has this, Kontakt isn’t quite the same. Absolute killing. Can’t believe how fast you can lay down ideas and experiment with this - then export to Ableton if needed.

    Love the Dilla mixed with Japanese minimalism aesthetic as the foundation for this, my new favorite app by a mile @elf_audio ! Seriously nice work.

  • Koala gurus, can individual samples be exported as wav?

  • @aleyas said:
    Koala gurus, can individual samples be exported as wav?

    Yes
    Tap ‘Export’ then ‘Current Sample’

  • @robosardine said:

    @aleyas said:
    Koala gurus, can individual samples be exported as wav?

    Yes
    Tap ‘Export’ then ‘Current Sample’

    Cool, thanks!

    With split screen drag and drop from files, and the 'add sample to end' merge function, this can be a very useful tool for building up samples for other 'slicer' apps like sEGments, Flexi and Egoist.

  • @kdogg said:

    @supadom said:

    @Lil_Stu07 said:

    @CapnWillie said:
    I hope Elf ignores most of the feature requests and sticks to his winning visions for his app. Frequently on ABF folks overwhelm the most engaged Devs for tons of “upgrades” that take brilliant apps into complicated zone.

    Grooverider comes to mind. Probably an excellent app, but way too many features make it look over complicated. Hardly ever hear it mentioned around here anymore after the natives spent launch and months thereafter hounding the Dev for new feature after new feature. When’s the last time you saw a new Grooverider thread? Yeah. Right.

    Koala brilliance is in simplicity and speed. AU this, AU that....dude, it’s a sampler. Sample your AUs. If you can’t be bothered with that...Bm3.

    It’s hilarious to me that naysayers say Bm3 is too much.🤦🏽‍♂️ Same folks want fast and simple Kaola to be Bm3 apparently. I don’t get it.lol

    Yeah, let’s add more complexity and work for Elf because his own vision isn’t what we all love already.

    Stick to doing your thing @elf_audio

    PLEEEEEAAAAAAAAASE.

    We DEFINITELY don’t need Kaola to host AU so we can hear the same users complain about it crashing and lack of stability (As they do unfairly with Bm3).

    Kaola is near perfect as is. Please stay YOUR course sir. 🙏🏽

    End of rant.

    Agree 100%

    Plus 1

    Yes!! This update is absolute brilliant. Wouldn’t want to lose any of the flow due to AU making it crash - recording from Audiobus into it is good for me. Using it split screen with Documents app as the sample browser, drag multiple samples over at the same time.

    And man, Beats time stretching mode in a sampler?!?! Does anyone know of anything besides Ableton simpler that has this, Kontakt isn’t quite the same. Absolute killing. Can’t believe how fast you can lay down ideas and experiment with this - then export to Ableton if needed.

    Love the Dilla mixed with Japanese minimalism aesthetic as the foundation for this, my new favorite app by a mile @elf_audio ! Seriously nice work.

    Also let’s not forget that this is universal so one can continue messing with it virtually anywhere and all the export options let one moving projects between devices with ease.

    If there was one thing I’d like is the effects to be automated in the sequencer but tbh with midi learn I expect they can be assigned to an external midi sequencer like Drambo.

  • Mmm, I just tried to map AUMs keyboard notes to functions in koala but it isn’t working, unless I’m doing something wrong. @elf_audio does koala need to be in the foreground for midi learn? I can’t think of something else being the reason. I have AUMs keyboard rooted to koala in settings.

  • @aleyas said:

    >

    With split screen drag and drop from files, and the 'add sample to end' merge function, this can be a very useful tool for building up samples for other 'slicer' apps like sEGments, Flexi and Egoist.

    great idea and workflow! I hadn't considered this as a tool for making sample chains...my Flexi Sampler thanks you :)

  • @drewinnit said:

    @aleyas said:

    >

    With split screen drag and drop from files, and the 'add sample to end' merge function, this can be a very useful tool for building up samples for other 'slicer' apps like sEGments, Flexi and Egoist.

    great idea and workflow! I hadn't considered this as a tool for making sample chains...my Flexi Sampler thanks you :)

    wait... what? is there a ‘add sample to end’ merge thing? i haven’t found that in Koala and i would very much like to.. hints?

  • Drag a sample on top of another sample and you get the prompt ;)

  • @supadom said:
    Mmm, I just tried to map AUMs keyboard notes to functions in koala but it isn’t working, unless I’m doing something wrong. @elf_audio does koala need to be in the foreground for midi learn? I can’t think of something else being the reason. I have AUMs keyboard rooted to koala in settings.

    Most of the time when I use Koala with AUM I use it in slide-over view since AUM doesn't support proper split-screen.
    That might be worth a try?

  • @Samu said:

    @supadom said:
    Mmm, I just tried to map AUMs keyboard notes to functions in koala but it isn’t working, unless I’m doing something wrong. @elf_audio does koala need to be in the foreground for midi learn? I can’t think of something else being the reason. I have AUMs keyboard rooted to koala in settings.

    Most of the time when I use Koala with AUM I use it in slide-over view since AUM doesn't support proper split-screen.
    That might be worth a try?

    Yes, that did it, thanks. So I’ve mapped pads to Drambo’s pads and Drambo’s CC mapped to effects but it seems that the effects only work with internal koala sequences as despite visually responding to CC messages they cannot be heard. @elf_audio ?

  • @drewinnit said:
    Drag a sample on top of another sample and you get the prompt ;)

    ahhh! you have to do it with the pads!! i was looking at all the import audio things and trying drag & drop from files etc..... thanks for clearing that up.... actually very quick to drag a handful of boinks from files in one go onto pads then assemble a long cutup dragging on top..

  • @supadom said:
    If there was one thing I’d like is the effects to be automated in the sequencer but tbh with midi learn I expect they can be assigned to an external midi sequencer like Drambo.

    Yes, MIDI learn works but it's fiddly (at best) on the iPhone when I'm on the go. While I recognize that others use this on their iPad and are interested in AUv3 support (either as host or plug in) I like Koala as a standalone thing. As such, it would best support "getting in the flow" to be able to record the FX. My two cents.

  • edited February 2021

    Trying to understand if Auv3 will ‘replace’ Standalone/IAA.. or will Auv3 just be an add-on (as GrooveRider)? 😧🥱

  • edited February 2021

    @RajahP said:
    Trying to understand if Auv3 will ‘replace’ Standalone/IAA.. or will Auv3 just be an add-on (as GrooveRider)? 😧🥱

    [This is completely off topic, but yes, the good people in Cupertino do seem to be pushing for AUs to become their new(est 🙄) standard and broadly speaking they do make for a smooth workflow inside host apps (AB, AUM) As for replacing? Well, only time will tell...]

    I’ve got a BUG REPORT for @elf_audio that maybe someone else can confirm?. I trigger pads with an external controller. When I’m in Piano-Grid view and recording, while my new notes are recorded and play back, they do not show up on the grid unless I exit the grid view and then reopen it. Anyone else having this issue?

  • @boberto said:

    @RajahP said:
    Trying to understand if Auv3 will ‘replace’ Standalone/IAA.. or will Auv3 just be an add-on (as GrooveRider)? 😧🥱

    [This is completely off topic, but yes, the good people in Cupertino do seem to be pushing for AUs to become their new(est 🙄) standard and broadly speaking they do make for a smooth workflow inside host apps (AB, AUM) As for replacing? Well, only time will tell...]

    I’ve got a BUG REPORT for @elf_audio that maybe someone else can confirm?. I trigger pads with an external controller. When I’m in Piano-Grid view and recording, while my new notes are recorded and play back, they do not show up on the grid unless I exit the grid view and then reopen it. Anyone else having this issue?

    yes , i’ve noticed this too yesterday... had forgotten about it... not checked in this update though..

  • @RockySmalls said:

    @boberto said:

    @RajahP said:
    Trying to understand if Auv3 will ‘replace’ Standalone/IAA.. or will Auv3 just be an add-on (as GrooveRider)? 😧🥱

    [This is completely off topic, but yes, the good people in Cupertino do seem to be pushing for AUs to become their new(est 🙄) standard and broadly speaking they do make for a smooth workflow inside host apps (AB, AUM) As for replacing? Well, only time will tell...]

    I’ve got a BUG REPORT for @elf_audio that maybe someone else can confirm?. I trigger pads with an external controller. When I’m in Piano-Grid view and recording, while my new notes are recorded and play back, they do not show up on the grid unless I exit the grid view and then reopen it. Anyone else having this issue?

    yes , i’ve noticed this too yesterday... had forgotten about it... not checked in this update though..

    to be honest though , i didn’t see it as a bug, just a ‘finesse’ elf-audio hadn’t got around to yet.. after all you can’t even see the piano roll when inputting notes internally in Koala ,, you always have to open the piano roll sequence afterwards ,, which must be when it draws the notes.. on the other hand it does draw the notes when using those sidebar keys...

  • @supadom said:

    @kdogg said:

    @supadom said:

    @Lil_Stu07 said:

    @CapnWillie said:
    I hope Elf ignores most of the feature requests and sticks to his winning visions for his app. Frequently on ABF folks overwhelm the most engaged Devs for tons of “upgrades” that take brilliant apps into complicated zone.

    Grooverider comes to mind. Probably an excellent app, but way too many features make it look over complicated. Hardly ever hear it mentioned around here anymore after the natives spent launch and months thereafter hounding the Dev for new feature after new feature. When’s the last time you saw a new Grooverider thread? Yeah. Right.

    Koala brilliance is in simplicity and speed. AU this, AU that....dude, it’s a sampler. Sample your AUs. If you can’t be bothered with that...Bm3.

    It’s hilarious to me that naysayers say Bm3 is too much.🤦🏽‍♂️ Same folks want fast and simple Kaola to be Bm3 apparently. I don’t get it.lol

    Yeah, let’s add more complexity and work for Elf because his own vision isn’t what we all love already.

    Stick to doing your thing @elf_audio

    PLEEEEEAAAAAAAAASE.

    We DEFINITELY don’t need Kaola to host AU so we can hear the same users complain about it crashing and lack of stability (As they do unfairly with Bm3).

    Kaola is near perfect as is. Please stay YOUR course sir. 🙏🏽

    End of rant.

    Agree 100%

    Plus 1

    Yes!! This update is absolute brilliant. Wouldn’t want to lose any of the flow due to AU making it crash - recording from Audiobus into it is good for me. Using it split screen with Documents app as the sample browser, drag multiple samples over at the same time.

    And man, Beats time stretching mode in a sampler?!?! Does anyone know of anything besides Ableton simpler that has this, Kontakt isn’t quite the same. Absolute killing. Can’t believe how fast you can lay down ideas and experiment with this - then export to Ableton if needed.

    Love the Dilla mixed with Japanese minimalism aesthetic as the foundation for this, my new favorite app by a mile @elf_audio ! Seriously nice work.

    Also let’s not forget that this is universal so one can continue messing with it virtually anywhere and all the export options let one moving projects between devices with ease.

    If there was one thing I’d like is the effects to be automated in the sequencer but tbh with midi learn I expect they can be assigned to an external midi sequencer like Drambo.

    True, effect automation would be pretty killer. Yeah Airdropping sessions from iPad to iPhone is sweet. Resampling some wild processing with the FX hold button down and bringing that back in the mix is so cool, of course these things can all be done easily on desktop daws but there is something about the speed and improvised flow of using this that is amazing. I always feel so much more planned in my approach in Ableton or Cubase, this is yield some very fun sessions so far coming up with stuff I couldn’t even imagine I would have made on Ableton for instance.

  • @elf_audio the iap restore purchase is actually fine on iphone6 I get the pop up screen (can’t connect to itunes pay etc) i press ok and all works in airplane mode So its just the pop up screen that comes up when in airplane mode. Not a major issue thus far

  • I think I will probably do a AUv3 plugin of koala, although I see it as not essential for koala whilst there's IAA - I can see the multiple instance case, but it always feels a bit like square peg round hole.

    There are many steps towards an AUv3 for Koala

    1. Koala uses OpenGL which uses a lot of RAM, and is deprecated by Apple (thanks Apple) - I'm moving it to Metal at the moment which should help

    2. Koala has 64 sample slots (and potentially a lot more in future), people load tonnes and tonnes of samples in there, AUv3 has a 300MB limit, which if you count koala's resources plus the actual sample data, plus the cached timestretch samples, is not very much for a heavy session. So how to manage that scenario

    3. Koala's design is sort of monolithic - it's supposed to be used by itself. I think a different design would be more conducive to an environment where you can have lots of samples - like a split design - a midi sequencing AUv3 (I'm sure that already exists), a sampling AUv3 with multiple outs (I'm sure alternatives exist, but I think that's where the koala magic is), and a koala effects AUv3 - well that definitely exists!

    Basically, my workload is a bit crazy at the moment, there's still so much to improve and fix with SAMURAI and there are other things that I think are ESSENTIAL for koala before it gets AUv3, that would outweigh the AUv3 benefit. ALSO, I have several related products/projects that need to get released, that could be as interesting to you lot as koala but in a different way, but I would say AUv3 definitely in the pipeline - one big motivator is that if I can get it to work as an AUv3, VST is a no-brainer (I will use a library called iPlug2 - I've ported koala fx to that, but not yet released)

    Ok back to the wheel! Also, thx for everyone's support and kind words, makes me so happy to hear all the wonderful music coming out with koala!

  • edited February 2021

    @elf_audio said:
    I think I will probably do a AUv3 plugin of koala, although I see it as not essential for koala whilst there's IAA - I can see the multiple instance case, but it always feels a bit like square peg round hole.

    There are many steps towards an AUv3 for Koala

    1. Koala uses OpenGL which uses a lot of RAM, and is deprecated by Apple (thanks Apple) - I'm moving it to Metal at the moment which should help

    2. Koala has 64 sample slots (and potentially a lot more in future), people load tonnes and tonnes of samples in there, AUv3 has a 300MB limit, which if you count koala's resources plus the actual sample data, plus the cached timestretch samples, is not very much for a heavy session. So how to manage that scenario

    3. Koala's design is sort of monolithic - it's supposed to be used by itself. I think a different design would be more conducive to an environment where you can have lots of samples - like a split design - a midi sequencing AUv3 (I'm sure that already exists), a sampling AUv3 with multiple outs (I'm sure alternatives exist, but I think that's where the koala magic is), and a koala effects AUv3 - well that definitely exists!

    Basically, my workload is a bit crazy at the moment, there's still so much to improve and fix with SAMURAI and there are other things that I think are ESSENTIAL for koala before it gets AUv3, that would outweigh the AUv3 benefit. ALSO, I have several related products/projects that need to get released, that could be as interesting to you lot as koala but in a different way, but I would say AUv3 definitely in the pipeline - one big motivator is that if I can get it to work as an AUv3, VST is a no-brainer (I will use a library called iPlug2 - I've ported koala fx to that, but not yet released)

    Ok back to the wheel! Also, thx for everyone's support and kind words, makes me so happy to hear all the wonderful music coming out with koala!

    @elf_audio cheers for all the above You have done a brilliant job. Personally Auv3 no rush cos you have given us Export options and I like the independant vibe Koala is. The Sp404 inspiration within Koala is brilliant. Less is more and make it happen with what the user has. Please stick to this concept. Koala has filters etc built in. Only thing I so would appreciate is pad mute /solos & record count ins. Thanks for adding the Export Current sequence/stems. Looking forward to the fix today (ish). Having said that though when I go into the piano roll I vision a similar screen for an audio track or 2 (iap) Can drop an acapella in there :)

  • edited February 2021

    @elf_audio forgot to mention a lock screen scroll (vertical&horizontal) in piano roll & cycle markers in piano roll would be a welcome addition. (Very handy when editing notes within a sequence in piano roll)

  • @elf_audio said:
    I think I will probably do a AUv3 plugin of koala, although I see it as not essential for koala whilst there's IAA - I can see the multiple instance case, but it always feels a bit like square peg round hole.

    There are many steps towards an AUv3 for Koala

    1. Koala uses OpenGL which uses a lot of RAM, and is deprecated by Apple (thanks Apple) - I'm moving it to Metal at the moment which should help

    2. Koala has 64 sample slots (and potentially a lot more in future), people load tonnes and tonnes of samples in there, AUv3 has a 300MB limit, which if you count koala's resources plus the actual sample data, plus the cached timestretch samples, is not very much for a heavy session. So how to manage that scenario

    3. Koala's design is sort of monolithic - it's supposed to be used by itself. I think a different design would be more conducive to an environment where you can have lots of samples - like a split design - a midi sequencing AUv3 (I'm sure that already exists), a sampling AUv3 with multiple outs (I'm sure alternatives exist, but I think that's where the koala magic is), and a koala effects AUv3 - well that definitely exists!

    Basically, my workload is a bit crazy at the moment, there's still so much to improve and fix with SAMURAI and there are other things that I think are ESSENTIAL for koala before it gets AUv3, that would outweigh the AUv3 benefit. ALSO, I have several related products/projects that need to get released, that could be as interesting to you lot as koala but in a different way, but I would say AUv3 definitely in the pipeline - one big motivator is that if I can get it to work as an AUv3, VST is a no-brainer (I will use a library called iPlug2 - I've ported koala fx to that, but not yet released)

    Ok back to the wheel! Also, thx for everyone's support and kind words, makes me so happy to hear all the wonderful music coming out with koala!

    no hurry :). btw I LOVE Koala FX ... especially the xy pad bit.. is there any rumours about XY or maybe just the “reorder FX” capabilities coming to big Koala?

  • @elf_audio said:
    I think I will probably do a AUv3 plugin of koala, although I see it as not essential for koala whilst there's IAA - I can see the multiple instance case, but it always feels a bit like square peg round hole.

    There are many steps towards an AUv3 for Koala

    1. Koala uses OpenGL which uses a lot of RAM, and is deprecated by Apple (thanks Apple) - I'm moving it to Metal at the moment which should help

    2. Koala has 64 sample slots (and potentially a lot more in future), people load tonnes and tonnes of samples in there, AUv3 has a 300MB limit, which if you count koala's resources plus the actual sample data, plus the cached timestretch samples, is not very much for a heavy session. So how to manage that scenario

    3. Koala's design is sort of monolithic - it's supposed to be used by itself. I think a different design would be more conducive to an environment where you can have lots of samples - like a split design - a midi sequencing AUv3 (I'm sure that already exists), a sampling AUv3 with multiple outs (I'm sure alternatives exist, but I think that's where the koala magic is), and a koala effects AUv3 - well that definitely exists!

    Basically, my workload is a bit crazy at the moment, there's still so much to improve and fix with SAMURAI and there are other things that I think are ESSENTIAL for koala before it gets AUv3, that would outweigh the AUv3 benefit. ALSO, I have several related products/projects that need to get released, that could be as interesting to you lot as koala but in a different way, but I would say AUv3 definitely in the pipeline - one big motivator is that if I can get it to work as an AUv3, VST is a no-brainer (I will use a library called iPlug2 - I've ported koala fx to that, but not yet released)

    Ok back to the wheel! Also, thx for everyone's support and kind words, makes me so happy to hear all the wonderful music coming out with koala!

    Loving this Gem and discovering it’s deep features.. Export is mighty.. So much to chew on until Auv3 is born.. Thanks..

Sign In or Register to comment.