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.

BeatMaker 4 wish list

Hello.
I know I should post this on Intua forum...but lots of interest hopefully here...
Wish list:
1. Sampling..lazy chop.
2. Delete patterns in batches and not just individually.
3. Record into song sequencer direct from scenes.
4. Tempo track.
5. Time signature changes.

These are the main ones so far for me...will add more....

I love the duplicate tracks and flexible pattern length features added in recent updates...
What an amazing app BM3 is......looking forward to even better things in the foreseeable future..

Any suggestions welcome..thanks....

«1

Comments

  • edited January 2021

    BM3 is my favorite sequencer even more then any desktop sequencer like live or Logic.
    It’s so sad seeing BM3 becoming a living dead software.

  • 4.0?

    We hav’nt reached 3.1 yet!!

  • Universal

  • Interesting!
    When were versions 1 and 2 released?
    Wasn’t 3 around 2017?

  • Considering BM3 is currently a one-man-show it would take an absolute miracle to push out BM4 with all the gazillions of requests implemented and 100% bug-free in a short period of time...

    Let's just enjoy BM3 for what it is, a sampler still unbeaten on iOS/iPadOS!
    I've always compared it to the classic Roland W30 sampling workstation.

    Thankfully we have plenty of apps on iOS and I really enjoy using Koala to capture samples on the go.
    It's very easy to dump them samples over to BM3 when needed, either processed or raw.

    Sure I would love to see an uber-gizmo with NS2,BM3, Logic, Live, Cubasis, AUM & apeMatrix baked into one but it will likely never happen...

    2021 is still young and anything can happen B)

    As crazy as it sounds but I'm looking forward to what Apple does with iOS15/iPadOS15 even though they'll likely drop support for the iPad Air 2.

    Take Care,

  • I don't think it's living dead software...just a little quiet at times, but then a piece of magic happens and it keeps on rolling. I think there is still a strong future for it yet. Time signature changes would be nice. I'd like to see the ability to move the play marker inside a MIDI part like it was on the timeline...that would be nice. Then I wouldn't have to exit the MIDI part I'm working in to control where the playhead is....and yes, the same thing I would like with Cubasis - a master Solo button to cancel all solos at once, that would be nice. AP has it AUM has it...why is it so hard to incorporate such a simple handy feature? BM3 is still my favourite iPad DAW type app though...

  • @Samu said:
    Considering BM3 is currently a one-man-show it would take an absolute miracle to push out BM4 with all the gazillions of requests implemented and 100% bug-free in a short period of time...

    Let's just enjoy BM3 for what it is, a sampler still unbeaten on iOS/iPadOS!

    That was pretty much my first thoughts as I was reading this.

  • @arktek said:
    I don't think it's living dead software...just a little quiet at times, but then a piece of magic happens and it keeps on rolling. I think there is still a strong future for it yet. Time signature changes would be nice. I'd like to see the ability to move the play marker inside a MIDI part like it was on the timeline...that would be nice. Then I wouldn't have to exit the MIDI part I'm working in to control where the playhead is....and yes, the same thing I would like with Cubasis - a master Solo button to cancel all solos at once, that would be nice. AP has it AUM has it...why is it so hard to incorporate such a simple handy feature? BM3 is still my favourite iPad DAW type app though...

    Yah having a master solo button on the main out could be nice. Or even if just long pressing any solo button turned them all off.

  • Lets not jump to BM4 just yet. We didn’t even reach 3.1 😂😂😂😂

  • @AudioGus said:

    Yah having a master solo button on the main out could be nice. Or even if just long pressing any solo button turned them all off.

    Yes, a long hold would do the trick. Kind of like how Ableton and Bitwig use shift with a mouse click. How long did it take me to find that......

  • Ability to do easy busses
    MPE support
    Copy/ safe an effects chain
    Freeze tracks (this would be so nice)

  • @IOSSOS : No time signature switching on BM3? Ugh! Thanks for bringing that to my attention

  • Remove all the DAW stuff and make it AU. 🦀🦀🦀

  • ^this.

  • @BroCoast said:
    Remove all the DAW stuff and make it AU. 🦀🦀🦀

    ☝🏾This, with lazy chopping would be 🔥🔥🔥

  • @BroCoast said:
    Remove all the DAW stuff and make it AU. 🦀🦀🦀

    The ability to use a Beatmaker AU in Cubasis2/3, NS2, Garageband, etc would be so sweet. I already purchased BM3 back when it was first released, but I'd buy it all over again as an AU.

  • edited January 2021

    I see this debate about BM3 becoming an AUv3 sampler a lot, but here’s the thing...

    The fact that BM3 is it’s own host with a native sampler grants a large number of advantages that I don’t think are possible as an AUv3 plugin. Such as:

    1. Full control of, RAM, memory management and resource allocation. AUv3s are granted a small pool of RAM per instance.
    2. Full access to the host’s file browser and file storage.
    3. BM3’s midi patterns are uniquely suited to playing its multi-pad/multi-sample banks. AUv3 samplers are either limited to playing one sample per instance, or if they support multple samples (such as EG pulse) each sample can only be played at one pitch.

    I could be wrong (and I hope I am), but I’m just doubtful that any AUv3 sampler would ever be as flexible, powerful, CPU/RAM efficient, and quick to setup as one that is native to the host, like BM3.

  • wimwim
    edited January 2021

    @tk32 said:
    I see this debate about BM3 becoming an AUv3 sampler a lot, but here’s the thing...

    Being a host with a native sampler grants a large number of advantages that I don’t think are possible as an AUv3 plugin. Such as:

    1. Full control of, RAM, memory management and resource allocation. AUv3s are granted a small pool of RAM per instance.
    2. Full access to the host’s file browser and file storage.
    3. BM3’s midi patterns are uniquely suited to playing it’s multi-pad/multi-sample banks. AUv3 samplers are either limited to playing one sample per instance, or if they support multple samples (such as EG pulse) each sample can only be played at one pitch.

    I could be wrong (and I hope I am), but I’m just doubtful that any AUv3 sampler would ever be as flexible, powerful, CPU/RAM efficient, and quick to setup as one that is native to the host, like BM3.

    EG pulse and DigiStix are examples of an AUs that addresses most of what you mention, but just don't have quite the awesomeness of BM3's sampler. I think you over-estimate the challenges somewhat.

    I know it's not gonna happen. But it's fun to dream. And one can also hope that if it comes up over and over again, that some developer will say "yeah, I could do a sampler like that!"

  • @tk32 said:
    I see this debate about BM3 becoming an AUv3 sampler a lot, but here’s the thing...

    Being a host with a native sampler grants a large number of advantages that I don’t think are possible as an AUv3 slave plugin. Such as:

    1. Full control of, RAM, memory management and resource allocation. AUv3s are granted a small pool of RAM per instance.
    2. Full access to the host’s file browser and file storage.
    3. BM3’s midi patterns are uniquely suited to playing it’s multi-pad/multi-sample banks. AUv3 samplers are either limited to playing one sample per instance, or if they support multple samples (such as EG pulse) each sample can only be played at one pitch.

    Yah the whole sampling an internal track to a pad workflow too would be lost. You would need some jiggery pokery AU fx scenario but not have transport controls etc. Also, placing fx on pads is huge too. etc etc etc. I think a Cubasis Sampler track that Samu mentioned would be muchos killer and could be better than any AU sampler and maybe rival BM3. who knows?

  • Hahahahahahaha smh
    Better to wish in one hand and sh*t in the other

  • @tk32 said:
    I see this debate about BM3 becoming an AUv3 sampler a lot, but here’s the thing...

    The fact that BM3 is it’s own host with a native sampler grants a large number of advantages that I don’t think are possible as an AUv3 plugin. Such as:

    1. Full control of, RAM, memory management and resource allocation. AUv3s are granted a small pool of RAM per instance.
    2. Full access to the host’s file browser and file storage.
    3. BM3’s midi patterns are uniquely suited to playing its multi-pad/multi-sample banks. AUv3 samplers are either limited to playing one sample per instance, or if they support multple samples (such as EG pulse) each sample can only be played at one pitch.

    I could be wrong (and I hope I am), but I’m just doubtful that any AUv3 sampler would ever be as flexible, powerful, CPU/RAM efficient, and quick to setup as one that is native to the host, like BM3.

    So both, then.

  • edited January 2021

    With the current state of iOS/iPadOS an AUv3’s will never have a tight integration with the host allowing seamless access to session audio-files and eventual drag’n’drop btween host <-> plug-in.

    So the ‘I want BM3 as an AUv3’ would only cause workflow issues since we’d loose almost everything that makes the BM3 sampler unigue, remember AUv3’s can not host other AUv3’s and do not even have access to external audio inputs.

    AUv3’s can not even directly access files in the Files app but have to rely on their storage container which makes file management a hassle (and one of the reasons I no longer use 4P or EG apps for sampling).

    So before everyone goes nuts, study the limitations of iOS before requesting the almost impossible from the developers...

    These limitations are part of the reason why I’m pushing for better integrated samplers for the hosts as Plug-Ins on iOS would just be ‘crippled’ when it comes to workflow.

    I do get that for some users ‘Samplers’ are mainly used to play and chop up stuff made by others (ex. BeatHawk) instead of doing actual sampling and for those cases I understand it but as a ‘Sampling Workstation’ an AUv3 will with the current limitations be of limited use.

    Take Care,

  • I think it'd be best if BM3 would become an AUv3 sampler and just focus on sampling, file browsing and organization, audio manipulation etc... These are the best things about BM3, other features like sequencer, AU hosting etc are quite mediocre and would need quite a lot of work to catch up with other hosts and DAWs out there. Although I really love their scene mode, I think it's not used that much and it's a bit confusing, even if you get used to it.
    We really need such AUv3 sampler on iOS, BM3 could be the one. Even if it'd be an extra purchase, I wouldn't mind paying extra.

  • edited January 2021

    @arktek said:
    I'd like to see the ability to move the play marker inside a MIDI part like it was on the timeline...that would be nice. Then I wouldn't have to exit the MIDI part I'm working in to control where the playhead is....

    +1 That's a big one for me.

    Also, i wish we had the ability to add fades at the start/end of a pattern in the timeline.

  • wimwim
    edited January 2021

    @Samu , we clearly see different thing as unique and important about BM3’s Sampler. Nothing I wish for in it is impossible for an AU plugin. Nothing you mention as critical are things I care about all that much.

    Who’s going “nuts”? People just wishin’ out loud for stuff they want. No need to try to shut that down. It ain’t hurting anyone. B) ✌️

  • wimwim
    edited January 2021

    @Samu said:
    With the current state of iOS/iPadOS an AUv3’s will never have a tight integration with the host allowing seamless access to session audio-files and eventual drag’n’drop btween host <-> plug-in.

    Not a big deal to me. I don't feel particularly hampered by files workflow such as that is in Drambo, miRack, EG Pulse, DigiStix, AudioLayer, etc. OK, yes, in hosts with inflexible routing like Cubasis, session recordings are a challenge. But in a host like AUM the routing possibilities are endless and these issues go away. Maybe you're more DAW oriented than I am. I can kind of see your point there.

    So the ‘I want BM3 as an AUv3’ would only cause workflow issues since we’d loose almost everything that makes the BM3 sampler unigue, remember AUv3’s can not host other AUv3’s and do not even have access to external audio inputs.

    Don't care about AUv3 hosting in the sampler. No access to external audio inputs? What the heck u talkin' about?? Of course there is access just as anything else has access that is loaded in an FX slot in a host.

    AUv3’s can not even directly access files in the Files app but have to rely on their storage container which makes file management a hassle (and one of the reasons I no longer use 4P or EG apps for sampling).

    I know this is huge to you, but not something I care about all that much.

    So before everyone goes nuts, study the limitations of iOS before requesting the almost impossible from the developers...

    No one specifically requested the things you mention. Not one thing I want from a BM3 style sampler hasn't already been done in more than one AUv3. Just not all together in any one of them. :D

    These limitations are part of the reason why I’m pushing for better integrated samplers for the hosts as Plug-Ins on iOS would just be ‘crippled’ when it comes to workflow.

    Good luck with that.
    Never fear though. I'm sure iOS 19 will have greatly improved file management. Then I'm sure host developers will be more inclined to jump on board.

    I do get that for some users ‘Samplers’ are mainly used to play and chop up stuff made by others (ex. BeatHawk) instead of doing actual sampling and for those cases I understand it but as a ‘Sampling Workstation’ an AUv3 will with the current limitations be of limited use.

    I can usually make sense of what you're saying, but you really lost me there.

    (BTW, I will be incommunicado tomorrow, so feeling pretty smug about tossing a few hand grenades over the wall before I go. :D I hope to find a mountain of entertaining reading when I return. Please don't let me down peeps.)

  • @wim said:

    I can usually make sense of what you're saying, but you really lost me there.

    (BTW, I will be incommunicado tomorrow, so feeling pretty smug about tossing a few hand grenades over the wall before I go. :D I hope to find a mountain of entertaining reading when I return. Please don't let me down peeps.)

    If we take 'BeatHawk' as an example it's more or less a platform to sell IAPs rather than being an actual 'Sampler'.
    Sure, the stand-alone has very basic sampling capabilities but when used as an AUv3 it's more or less a sample/content-player.

    ReSlice has a good way to use 'Copy & Paste' from Files.app to import samples which is a workflow I can get used to.
    It could be expanded to allow copy & paste from Cubasis as well if Cubasis had an option to 'Copy as Audio' to the clipboard.

    What really 'irks' me is that I can do drag'n'drop from the Files.app pop-over to an AUv3 plug-in but not from the host that is hosting the plug-in like seriously?

    For example I can do 'drag'n'drop' of objects & content between Panges and Numbers in Split-View so it can be done.
    (On the desktop side I can run MPC Beats as an AU Plug-In in Logic and have full bi-directional drag'n'drop functionality)

    I also miss proper 'split-screen' support in AUM, slide-over works but then it covers part of the AUM UI.

    We have most of the functions available spread across multiple apps that often have issues communicating with each other :)

    I know iOS/iPadOS is still growing and that's partly why I always look forward to new iOS/iPadOS updates.

    And yes, most of the time I prefer integrated solutions as it helps me focus.

    Take Care & Enjoy some 'Off The Grid' Time :D

  • This sounds like a branding issue wrapped in consumer expectations more than anything.

    Sounds like you could totally make an AU sample player with same/similar features as the BM3 sampler (specifically, everything under the ‘sampler’ ‘layer fx’, ‘modulations’ and ‘mapping’ tab). You would however have to set the AU to either ‘pads’ or ‘notes’ mode though (as AU hosts can’t send pad number and notes, right?). You would also need to be able to host a copy of the AU in an fx slot for sampling (big BLECH from me on that one).

    Sure, I’d try it, maybe even love it in NS2. Non destructive sample ranges in NS2? Correction: I would totally love it. But no point in calling it the BM3 Sampler AU as it would be a totally different and restricted sampling experience to me.

    ———

    @samu are you saying that an AU that can record cannot have Files access and must use local storage? i guess that would explain why Spacecraft lost Files support. If this is the case then ugh, that is terrible. Having to use iCloud for gigs and gigs of sample management? Blech 2.

  • @AudioGus said:

    @samu are you saying that an AU that can record cannot have Files access and must use local storage? i guess that would explain why Spacecraft lost Files support. If this is the case then ugh, that is terrible. Having to use iCloud for gigs and gigs of sample management? Blech 2.

    An AUv3 can not directly access folders in the Files.app.
    It can import & export to/from a folder visible in Files.app but its manual labour.

    Most AUv3's use local storage containers to share files between stand-alone and AUv3 and their documents folder is usually not visible to Files.app unless the developer adds a storage provider extension or something similar.

    The kicker here is that 'storage containers' are locked to the developer.
    This is why AUM can have seamless integration with AudioShare but not other apps can...

    In those cases the app has a folder in Files.app the stand-alone has to be launched to sync the files between Plug-In and Stand-Alone (In most cases the content from Files.app folder gets copied into the apps storage container so the AUv3 can access the files).

    If you record samples into an AUv3 you have to export the files manually, they can not automagically appear in a folder in Files.app.

    So even though AUv3's are nice they do have limitations...

  • edited January 2021

    @Samu said:

    @AudioGus said:

    @samu are you saying that an AU that can record cannot have Files access and must use local storage? i guess that would explain why Spacecraft lost Files support. If this is the case then ugh, that is terrible. Having to use iCloud for gigs and gigs of sample management? Blech 2.

    An AUv3 can not directly access folders in the Files.app.

    Spacecraft at one point seemed to. I just had a regular Files folder that it loaded from. It did change at one point. Perhaps it was doing some 'import to local storage' on every load sort of thing so it just looked that way though. (Although maybe I am recalling when it was standalone only?)

    It can import & export to/from a folder visible in Files.app but its manual labour.

    Most AUv3's use local storage containers to share files between stand-alone and AUv3 and their documents folder is usually not visible to Files.app unless the developer adds a storage provider extension or something similar.

    The kicker here is that 'storage containers' are locked to the developer.
    This is why AUM can have seamless integration with AudioShare but not other apps can...

    In those cases the app has a folder in Files.app the stand-alone has to be launched to sync the files between Plug-In and Stand-Alone (In most cases the content from Files.app folder gets copied into the apps storage container so the AUv3 can access the files).

    If you record samples into an AUv3 you have to export the files manually, they can not automagically appear in a folder in Files.app.

    So even though AUv3's are nice they do have limitations...

    Thanks for the details!

Sign In or Register to comment.