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 3 July 15th.

1…6970727475…77

Comments

  • [Deleted User][Deleted User]

    @wim said:

    @InfoCheck said:
    @wim thanks for the info., hitting the start button in the Module app really doesn't work for me as I'm trying to use BM3 to control Module via MIDI. I can record by generating sequences from within Module. The recorder on each pad is a much easier way to record directly to a bank than exporting the song as I'd suggested earlier. I think apps that are only IAA generators can not be controlled automatically via BM3's transport controls or at the very least it's a different setup I'm not aware of. I suspect there may be MIDI control possibilities to initiate/stop recordings though I haven't gotten that far yet. . .

    I didn't mean hitting start within Module. I meant hit start in the BM3 keyboard sampler, and play in BM3 to play the pattern. If you have midi set up correctly, it will play Module just fine.

    You are clearly ahead of me with BM3 and MIDI which I haven't really delved into at all. Good to know that the suspected MIDI solutions for these sorts of issues are workable once you learn them.

    I've been going after the low hanging fruit first so being able to sample relying upon IAA host sync for controlling transport from within BM3 to automatically create perfectly sliced loops and to put them on pads has been my goal. I plan to explore all aspects of BM3 and it's options before investing a lot of time trying to create music with it as some aspects of the app are different than what I'm used to.

    Once I've gone through this process, I anticipate being able to make some more rational decisions about how to approach music creation incorporating BM3. At this point it's not always clear to me what are bugs versus simply not knowing how to use the app as envisioned by the developer. It has become increasingly clear to me that perceived bugs are most frequently due to an insufficient understanding on my part. BM3 has many context sensitive layers and my aptitude for keeping these sequences in my head is relatively low. Repeated use and developing an understanding of how the parts function within the whole may be a slower yet worthwhile process for me.

  • [Deleted User][Deleted User]

    @mireko_2 said:

    @MonzoPro said:

    @boone51 said:

    @ALB said:
    It sucks to lose something, even a fragment, when it feels inspired. I myself am just waiting for the update before doing anything "serious" as I don't want to lose anything that I like.

    I have to say, for me, and I realize thats just my own isolated experience, but the crashes were only startling at first. By that I mean that since then, I can kind of predict where the trouble might happen. I save a lot to avoid losing anything for now. Granted, would be much cooler if it auto saved correctly on an interval, but I’ve mitigated the lost work by saving manually. I come from the PC world, so this didn’t represent a learning curve for me.

    It's not a learning curve for me. The thing is, the app didn't crash, and I saved regularly during making the song and before closing. What's happened is there is an issue with the saving mechanism. My own guess is the numerous auto-saves it's doing are getting jumbled with the actual saves and resulting in lost work.

    Yeah I've been having problems with saving too, opened up the first song I made today and it cannot find the samples even though they are all there in the browser. Honestly has me hovering over the refund button. I don't mind paying full price later once it's stable, but kind of bummed paying $30 for something that doesn't even save properly. It's like I paid $30 for early access to the beta

    One approach I've been using is to save my samples with the banks. There are similar options for saving projects too. I have experienced the issue of banks not finding their samples if I've moved sample storage locations after creating the bank.

    I agree the developer and his users would have benefited from having a larger and more diverse population of beta testers to iron out the many practical use issues many people have been experiencing with BM3. While a smaller beta test group may be easier to manage and appropriate in earlier stages, the final product should run the gauntlet of a more inclusive group of testers with different expectations, use cases, and that do not have a long development history with the app so they don't know how to use it the first time they test it.

    I can appreciate how many users are not happy with a product that isn't meeting their expectations and is too difficult for them to learn how to use because the developer didn't go far enough in the testing phase to iron things out. With a complex app like BM3, getting deeper insights into how users will interact with your app seems critical to its success.

  • brambosbrambos

    I am planning to use the upcoming summer vacation to get really comfortable with BM3. It's such a fun app that I really want to learn how to get the most out of it and it will be a nice alternative way of working to Cubasis.

    By the time it's fully stable I'll be ready to get cracking! :)

  • mireko_2mireko_2

    @InfoCheck said:

    @mireko_2 said:

    @MonzoPro said:

    @boone51 said:

    @ALB said:
    It sucks to lose something, even a fragment, when it feels inspired. I myself am just waiting for the update before doing anything "serious" as I don't want to lose anything that I like.

    I have to say, for me, and I realize thats just my own isolated experience, but the crashes were only startling at first. By that I mean that since then, I can kind of predict where the trouble might happen. I save a lot to avoid losing anything for now. Granted, would be much cooler if it auto saved correctly on an interval, but I’ve mitigated the lost work by saving manually. I come from the PC world, so this didn’t represent a learning curve for me.

    It's not a learning curve for me. The thing is, the app didn't crash, and I saved regularly during making the song and before closing. What's happened is there is an issue with the saving mechanism. My own guess is the numerous auto-saves it's doing are getting jumbled with the actual saves and resulting in lost work.

    Yeah I've been having problems with saving too, opened up the first song I made today and it cannot find the samples even though they are all there in the browser. Honestly has me hovering over the refund button. I don't mind paying full price later once it's stable, but kind of bummed paying $30 for something that doesn't even save properly. It's like I paid $30 for early access to the beta

    One approach I've been using is to save my samples with the banks. There are similar options for saving projects too. I have experienced the issue of banks not finding their samples if I've moved sample storage locations after creating the bank.

    I agree the developer and his users would have benefited from having a larger and more diverse population of beta testers to iron out the many practical use issues many people have been experiencing with BM3. While a smaller beta test group may be easier to manage and appropriate in earlier stages, the final product should run the gauntlet of a more inclusive group of testers with different expectations, use cases, and that do not have a long development history with the app so they don't know how to use it the first time they test it.

    I can appreciate how many users are not happy with a product that isn't meeting their expectations and is too difficult for them to learn how to use because the developer didn't go far enough in the testing phase to iron things out. With a complex app like BM3, getting deeper insights into how users will interact with your app seems critical to its success.

    This is the problem though, I haven't moved any samples at all. The linking between the project and samples broke at some point, and I think it is because of auto save.

    And it's not that difficult to learn imo, it's just that there are some serious bugs.

    Another bug I've had is loading a project and all notes are missing from patterns.

    Show stopping bugs, because I don't want to work on a track only to load it and all that work is gone, or have to go through a project and manually relink all the projects samples to their pads (which is what I did with the first project since the samples were still in the same place)

  • [Deleted User][Deleted User]

    @mireko_2 said:

    @InfoCheck said:

    @mireko_2 said:

    @MonzoPro said:

    @boone51 said:

    @ALB said:
    It sucks to lose something, even a fragment, when it feels inspired. I myself am just waiting for the update before doing anything "serious" as I don't want to lose anything that I like.

    I have to say, for me, and I realize thats just my own isolated experience, but the crashes were only startling at first. By that I mean that since then, I can kind of predict where the trouble might happen. I save a lot to avoid losing anything for now. Granted, would be much cooler if it auto saved correctly on an interval, but I’ve mitigated the lost work by saving manually. I come from the PC world, so this didn’t represent a learning curve for me.

    It's not a learning curve for me. The thing is, the app didn't crash, and I saved regularly during making the song and before closing. What's happened is there is an issue with the saving mechanism. My own guess is the numerous auto-saves it's doing are getting jumbled with the actual saves and resulting in lost work.

    Yeah I've been having problems with saving too, opened up the first song I made today and it cannot find the samples even though they are all there in the browser. Honestly has me hovering over the refund button. I don't mind paying full price later once it's stable, but kind of bummed paying $30 for something that doesn't even save properly. It's like I paid $30 for early access to the beta

    One approach I've been using is to save my samples with the banks. There are similar options for saving projects too. I have experienced the issue of banks not finding their samples if I've moved sample storage locations after creating the bank.

    I agree the developer and his users would have benefited from having a larger and more diverse population of beta testers to iron out the many practical use issues many people have been experiencing with BM3. While a smaller beta test group may be easier to manage and appropriate in earlier stages, the final product should run the gauntlet of a more inclusive group of testers with different expectations, use cases, and that do not have a long development history with the app so they don't know how to use it the first time they test it.

    I can appreciate how many users are not happy with a product that isn't meeting their expectations and is too difficult for them to learn how to use because the developer didn't go far enough in the testing phase to iron things out. With a complex app like BM3, getting deeper insights into how users will interact with your app seems critical to its success.

    This is the problem though, I haven't moved any samples at all. The linking between the project and samples broke at some point, and I think it is because of auto save.

    And it's not that difficult to learn imo, it's just that there are some serious bugs.

    Another bug I've had is loading a project and all notes are missing from patterns.

    Show stopping bugs, because I don't want to work on a track only to load it and all that work is gone, or have to go through a project and manually relink all the projects samples to their pads (which is what I did with the first project since the samples were still in the same place)

    Those are very significant bugs, I encourage you to report this to the developer. My suggestion to try saving samples to banks or projects was to see if they'd act as a backup. Naturally when you save a project it should save the project without having to do other things in case the project isn't saved correctly or becomes corrupted later on.

    For me, the app isn't so easy to learn due to my own personal experiences and cognitive abilities. In app context sensitive help would facilitate my learning process.

  • CarnbotCarnbot

    So I'm only just getting my head around the sequencer. Is there a way to import one long sample, eg a mixdown to an audio track?

  • mireko_2mireko_2

    @InfoCheck said:

    @mireko_2 said:

    @InfoCheck said:

    @mireko_2 said:

    @MonzoPro said:

    @boone51 said:

    @ALB said:
    It sucks to lose something, even a fragment, when it feels inspired. I myself am just waiting for the update before doing anything "serious" as I don't want to lose anything that I like.

    I have to say, for me, and I realize thats just my own isolated experience, but the crashes were only startling at first. By that I mean that since then, I can kind of predict where the trouble might happen. I save a lot to avoid losing anything for now. Granted, would be much cooler if it auto saved correctly on an interval, but I’ve mitigated the lost work by saving manually. I come from the PC world, so this didn’t represent a learning curve for me.

    It's not a learning curve for me. The thing is, the app didn't crash, and I saved regularly during making the song and before closing. What's happened is there is an issue with the saving mechanism. My own guess is the numerous auto-saves it's doing are getting jumbled with the actual saves and resulting in lost work.

    Yeah I've been having problems with saving too, opened up the first song I made today and it cannot find the samples even though they are all there in the browser. Honestly has me hovering over the refund button. I don't mind paying full price later once it's stable, but kind of bummed paying $30 for something that doesn't even save properly. It's like I paid $30 for early access to the beta

    One approach I've been using is to save my samples with the banks. There are similar options for saving projects too. I have experienced the issue of banks not finding their samples if I've moved sample storage locations after creating the bank.

    I agree the developer and his users would have benefited from having a larger and more diverse population of beta testers to iron out the many practical use issues many people have been experiencing with BM3. While a smaller beta test group may be easier to manage and appropriate in earlier stages, the final product should run the gauntlet of a more inclusive group of testers with different expectations, use cases, and that do not have a long development history with the app so they don't know how to use it the first time they test it.

    I can appreciate how many users are not happy with a product that isn't meeting their expectations and is too difficult for them to learn how to use because the developer didn't go far enough in the testing phase to iron things out. With a complex app like BM3, getting deeper insights into how users will interact with your app seems critical to its success.

    This is the problem though, I haven't moved any samples at all. The linking between the project and samples broke at some point, and I think it is because of auto save.

    And it's not that difficult to learn imo, it's just that there are some serious bugs.

    Another bug I've had is loading a project and all notes are missing from patterns.

    Show stopping bugs, because I don't want to work on a track only to load it and all that work is gone, or have to go through a project and manually relink all the projects samples to their pads (which is what I did with the first project since the samples were still in the same place)

    Those are very significant bugs, I encourage you to report this to the developer. My suggestion to try saving samples to banks or projects was to see if they'd act as a backup. Naturally when you save a project it should save the project without having to do other things in case the project isn't saved correctly or becomes corrupted later on.

    For me, the app isn't so easy to learn due to my own personal experiences and cognitive abilities. In app context sensitive help would facilitate my learning process.

    I should mention the app was pretty straightforward to me because I've spent years using hardware samplers like Mpc's and software like Geist and Battery so the structure of the app and the sample editing and seq is pretty familiar.

    I can imagine it would be pretty overwhelming coming from not using the machines this app emulates, hopefully they release more in depth tutorials soon. It took me ages to get my head around my first Mpc (mpc2000).

    I was very excited for this app because it really is pretty revolutionary if it was stable and bug free, I guess I thought after all the delays it would launch stable but it wasn't to be.

    I have no problem paying full price when it is stable, but I think I will refund for now, same as I did with Mpc pro (which is still waiting on bug fixes how many years after release?)

  • [Deleted User][Deleted User]

    @mireko_2 said:

    @InfoCheck said:

    @mireko_2 said:

    @InfoCheck said:

    @mireko_2 said:

    @MonzoPro said:

    @boone51 said:

    @ALB said:
    It sucks to lose something, even a fragment, when it feels inspired. I myself am just waiting for the update before doing anything "serious" as I don't want to lose anything that I like.

    I have to say, for me, and I realize thats just my own isolated experience, but the crashes were only startling at first. By that I mean that since then, I can kind of predict where the trouble might happen. I save a lot to avoid losing anything for now. Granted, would be much cooler if it auto saved correctly on an interval, but I’ve mitigated the lost work by saving manually. I come from the PC world, so this didn’t represent a learning curve for me.

    It's not a learning curve for me. The thing is, the app didn't crash, and I saved regularly during making the song and before closing. What's happened is there is an issue with the saving mechanism. My own guess is the numerous auto-saves it's doing are getting jumbled with the actual saves and resulting in lost work.

    Yeah I've been having problems with saving too, opened up the first song I made today and it cannot find the samples even though they are all there in the browser. Honestly has me hovering over the refund button. I don't mind paying full price later once it's stable, but kind of bummed paying $30 for something that doesn't even save properly. It's like I paid $30 for early access to the beta

    One approach I've been using is to save my samples with the banks. There are similar options for saving projects too. I have experienced the issue of banks not finding their samples if I've moved sample storage locations after creating the bank.

    I agree the developer and his users would have benefited from having a larger and more diverse population of beta testers to iron out the many practical use issues many people have been experiencing with BM3. While a smaller beta test group may be easier to manage and appropriate in earlier stages, the final product should run the gauntlet of a more inclusive group of testers with different expectations, use cases, and that do not have a long development history with the app so they don't know how to use it the first time they test it.

    I can appreciate how many users are not happy with a product that isn't meeting their expectations and is too difficult for them to learn how to use because the developer didn't go far enough in the testing phase to iron things out. With a complex app like BM3, getting deeper insights into how users will interact with your app seems critical to its success.

    This is the problem though, I haven't moved any samples at all. The linking between the project and samples broke at some point, and I think it is because of auto save.

    And it's not that difficult to learn imo, it's just that there are some serious bugs.

    Another bug I've had is loading a project and all notes are missing from patterns.

    Show stopping bugs, because I don't want to work on a track only to load it and all that work is gone, or have to go through a project and manually relink all the projects samples to their pads (which is what I did with the first project since the samples were still in the same place)

    Those are very significant bugs, I encourage you to report this to the developer. My suggestion to try saving samples to banks or projects was to see if they'd act as a backup. Naturally when you save a project it should save the project without having to do other things in case the project isn't saved correctly or becomes corrupted later on.

    For me, the app isn't so easy to learn due to my own personal experiences and cognitive abilities. In app context sensitive help would facilitate my learning process.

    I should mention the app was pretty straightforward to me because I've spent years using hardware samplers like Mpc's and software like Geist and Battery so the structure of the app and the sample editing and seq is pretty familiar.

    I can imagine it would be pretty overwhelming coming from not using the machines this app emulates, hopefully they release more in depth tutorials soon. It took me ages to get my head around my first Mpc (mpc2000).

    I was very excited for this app because it really is pretty revolutionary if it was stable and bug free, I guess I thought after all the delays it would launch stable but it wasn't to be.

    I have no problem paying full price when it is stable, but I think I will refund for now, same as I did with Mpc pro (which is still waiting on bug fixes how many years after release?)

    I think Intua will follow through and fix the deficiencies in the app whether they're bugs or functionality issues. I'd check back in a few months to see how stable it is. I am surprised the app wasn't more polished and bug free after the development and beta testing over an extended period of time.

    The Intua BM3 forum is very active. Hopefully the release feedback will help them to get on track and nail down the bugs. I can only speculate that because they had a relatively small beta testing pool and didn't actually beta test the released version (from what I understand) they failed to catch the issues users are now experiencing.

  • [Deleted User][Deleted User]
    edited July 2017

    Still on sale? I thought the intro price would be over now.
    However, i think if you might like an Abelton Live workflow it might be the right tool but since Live would be the last DAW i would ever use and i´m more a fan of the "normal" timeline sequencer i´m sure this version is not my thing.
    Maybe v3.1. will do.
    But the sampler is really (even in v2) the best still on iOS (but i have the feeling NanoStudio 2 will offer something here too).
    At least i can now finally forgot about the hype and looking forward to the next 2 most awaited things on iOS......that said other DAW and Zeeon which might be the first iOS synth to offer me really desktop class analog sound :)
    Preferences, preferences.
    I still think BM3 is a great app and will have success. So i wish Intua good luck and all the best with it. Competition is needed.

  • [Deleted User][Deleted User]

    @mireko_2 said:

    @InfoCheck said:

    @mireko_2 said:

    @MonzoPro said:

    @boone51 said:

    @ALB said:
    It sucks to lose something, even a fragment, when it feels inspired. I myself am just waiting for the update before doing anything "serious" as I don't want to lose anything that I like.

    I have to say, for me, and I realize thats just my own isolated experience, but the crashes were only startling at first. By that I mean that since then, I can kind of predict where the trouble might happen. I save a lot to avoid losing anything for now. Granted, would be much cooler if it auto saved correctly on an interval, but I’ve mitigated the lost work by saving manually. I come from the PC world, so this didn’t represent a learning curve for me.

    It's not a learning curve for me. The thing is, the app didn't crash, and I saved regularly during making the song and before closing. What's happened is there is an issue with the saving mechanism. My own guess is the numerous auto-saves it's doing are getting jumbled with the actual saves and resulting in lost work.

    Yeah I've been having problems with saving too, opened up the first song I made today and it cannot find the samples even though they are all there in the browser. Honestly has me hovering over the refund button. I don't mind paying full price later once it's stable, but kind of bummed paying $30 for something that doesn't even save properly. It's like I paid $30 for early access to the beta

    One approach I've been using is to save my samples with the banks. There are similar options for saving projects too. I have experienced the issue of banks not finding their samples if I've moved sample storage locations after creating the bank.

    I agree the developer and his users would have benefited from having a larger and more diverse population of beta testers to iron out the many practical use issues many people have been experiencing with BM3. While a smaller beta test group may be easier to manage and appropriate in earlier stages, the final product should run the gauntlet of a more inclusive group of testers with different expectations, use cases, and that do not have a long development history with the app so they don't know how to use it the first time they test it.

    I can appreciate how many users are not happy with a product that isn't meeting their expectations and is too difficult for them to learn how to use because the developer didn't go far enough in the testing phase to iron things out. With a complex app like BM3, getting deeper insights into how users will interact with your app seems critical to its success.

    This is the problem though, I haven't moved any samples at all. The linking between the project and samples broke at some point, and I think it is because of auto save.

    And it's not that difficult to learn imo, it's just that there are some serious bugs.

    Another bug I've had is loading a project and all notes are missing from patterns.

    Show stopping bugs, because I don't want to work on a track only to load it and all that work is gone, or have to go through a project and manually relink all the projects samples to their pads (which is what I did with the first project since the samples were still in the same place)

    That's exactly the same issue I've had, missing notes.

    Definitely something weird going on with this auto-save malarkey. The auto-save list is pretty useless anyway as there's just an identical list with no dates or times.

  • TrueyorkyTrueyorky

    @ErrkaPetti said:

    @wim - now I have made all above in the right order, although I made a bigger and longer pattern (all 88 keys with long sustain)...

    Everything went well, but, there's a but, when I save the 88 slices to layer all went well again, but, it ends with pads or key-instrument in monophonic behavior - I can't take a chord, only play one single pad/key at once...?

    I'll try again and see what's missing in some of the samplers settings...

    88 slices - WOW. Did you change the polyphony on each one maybe that is why they are playing monophonic? I would be tempted to test a fewer number of samples before taking on such a project. Good luck.

  • ErrkaPettiErrkaPetti
    edited July 2017

    @Carnbot said:
    So I'm only just getting my head around the sequencer. Is there a way to import one long sample, eg a mixdown to an audio track?

    It's a piece of cake to add long (or short) wavefiles into the sequencer!

    Create an Audiotrack with the Plus sign.
    Drag'n'drop the wavefile from the filebrowser onto the new track called "1" is this case...
    Voila!



  • CarnbotCarnbot
    edited July 2017

    @ErrkaPetti said:

    Ah brilliant, that's great thanks :)

  • ErrkaPettiErrkaPetti
    edited July 2017

    @ErrkaPetti said:

    @wim said:

    @InfoCheck said:
    Unfortunately BM3 has issues with IAA and sometimes you can get around this by using Audiobus or AUM but this isn't working for Module. You could host Module in another app to record the audio and import it into BM3 for slicing.

    I was able to host Module in Audiobus 3 and record the output of a MIDI file output into AudioShare, trim it to the beat and import the sample into BM3. The slicing to pads worked well in BM3.

    I'm not sure I understand how you guys are doing it, but this worked just fine for me:

    • Load module into a pad. Make sure you hear sound when you play the keyboard in BM3. Midi has to be set right, and you may have to switch over to Module and go to the settings tab once to get sound.
    • Make a pattern playing the chromatic scale (I only did 16 notes for brevity). Each note a quarter note, and tempo set at 30bpm, velocity set to the layer velocity you're targeting.
    • Show the plugin so that the keyboard sampler shows.
    • Select Start at the bottom left, then Play
    • Play the pattern through, then press Stop and Recording to finish the recording. I forgot to stop recording at first, and wondered why I got no wave sample.
    • Check that you now have a wav file in the sample tab. If so then you can unload Module.
    • Set Snap to grid then trim the sample to remove any space. The new length should be only the number of beats that you want to slice (16, 32, 64, etc.).
    • Select slice mode, set slice to the number of notes.
    • On the save menu, select slice to a single layer and be sure to select the starting note.

    Now if you go to keys you can play the samples. I'm pretty sure you can repeat this process with different velocities and save to a different layer, but you're on your own there.

    One last thought. You're planning to sample all keys at 3 velocities. However, unless you've read it somewhere, module may not even be using that many samples itself. To save space, romplers often play fewer notes, then pitch them up or down over ranges of keys.

    Also, I noticed even at 30bpm, several samples hadn't finished sustaining by the next note. That could mean needing to do longer samples, or fading them out manually if they don't sound right when sustained.

    Good luck.

    @wim - now I have made all above in the right order, although I made a bigger and longer pattern (all 88 keys with long sustain)...

    Everything went well, but, there's a but, when I save the 88 slices to layer all went well again, but, it ends with pads or key-instrument in monophonic behavior - I can't take a chord, only play one single pad/key at once...?

    I'll try again and see what's missing in some of the samplers settings...

    Hmmm... Answer myself here...

    I gave up sampling Korg Module Ivory Grand into Beatmaker 3 :-(
    After many hours testing it seems that I can't have the piano polyphonic...?
    I can just play one pad/key at once, and that make it impossible to make chords etc...
    Can't understand what's wrong here... But the 88 sampled keys is the and everything around is pretty ok...

    I took the advice someone here gave me: bought the Acoustic Grand Piano as an IAP into Beathawk 2.x and use that as an AUv3 instrument in Beatmaker 3 instead...
    UVI:s Acoustic Grand Piano sounds really amazing! Very very very good for 10 bucks!!! Recommended!

  • JohnnyGoodyearJohnnyGoodyear

    @5pinlink said:

    Do you just want a real quick run through of all the features and what they do, or something specific ?

    Best place/thing to look at to get a decent grounding as people seem to be very much in favor.

  • wimwim
    edited July 2017

    @ErrkaPetti said:

    Everything went well, but, there's a but, when I save the 88 slices to layer all went well again, but, it ends with pads or key-instrument in monophonic behavior - I can't take a chord, only play one single pad/key at once...?

    I'll try again and see what's missing in some of the samplers settings...

    Hmmm... Answer myself here...

    I gave up sampling Korg Module Ivory Grand into Beatmaker 3 :-(
    After many hours testing it seems that I can't have the piano polyphonic...?
    I can just play one pad/key at once, and that make it impossible to make chords etc...
    Can't understand what's wrong here... But the 88 sampled keys is the and everything around is pretty ok...

    I found it. B)
    You need to set max polyphony (its in the sample settings) to more than one. Then you will be able to play chords.

    That said ... BeatHawk piano is the way to go. I was gonna suggest that, but you made it clear you wanted to give sampling a go. I'm glad you did because I learned a lot along the way too.

    One last discovery too ... when setting up the pattern to grab the sounds, be sure to leave a gap of an eighth note or more between notes. This will then pick up the instrument's own release curve and avoid having to fade out samples that overlapped each other.

  • boone51boone51
    edited July 2017

    @Trueyorky said:

    @boone51 said:
    great. Now can someone tell me s simple way to rearrange the pads?

    Editor view - three dots - pad copy paste. That works :D

    You cheeky #^*~

    Obviously. So walk me though the process of moving the kick from the first and third pads to thee second and fourth when all the pads are full. Without it taking three hundred and fourty eight steps. There should be a simple way to rearrange those, and it's honestly kind of surprising nobody else asked for that.

    Yeah yeah, I know...go to their forum. I'll do that.

    The Intua BM3 forum is very active. Hopefully the release feedback will help them to get on track and nail down the bugs. I can only speculate that because they had a relatively small beta testing pool and didn't actually beta test the released version (from what I understand) they failed to catch the issues users are now experiencing.

    There is no derivative of the space/time continuum that allows for all bugs to be caught. Anyone who is complaining about bugs just doesn't understand how the development of an incredibly sprawling complex app like this works. And that's ok. I wish it was perfect too, but I promise you that Intua wants that more than all of us.

    @JohnnyGoodyear said:

    Sorry, no time today to read through the 500 odd posts here, but have we found/seen a straightforward sampler explanation/video? I too bought a few of the IAPs and didn't get on with them (happens) so feel to get the most here I think I should at least give the sampler a real go.

    Hit me up in a PM. I'd suggest not buying any more iap's. Those are for people who own less than 300 music apps they can sample from like we do.

  • gonekrazy3000gonekrazy3000
    edited July 2017

    @boone51 said: fourty

    This number intruiges me. Is it similar to forty ?

  • [Deleted User][Deleted User]
    edited July 2017

    @boone51 said:

    @Trueyorky said:

    @boone51 said:
    great. Now can someone tell me s simple way to rearrange the pads?

    Editor view - three dots - pad copy paste. That works :D

    You cheeky #^*~

    Obviously. So walk me though the process of moving the kick from the first and third pads to thee second and fourth when all the pads are full. Without it taking three hundred and fourty eight steps. There should be a simple way to rearrange those, and it's honestly kind of surprising nobody else asked for that.

    Yeah yeah, I know...go to their forum. I'll do that.

    The Intua BM3 forum is very active. Hopefully the release feedback will help them to get on track and nail down the bugs. I can only speculate that because they had a relatively small beta testing pool and didn't actually beta test the released version (from what I understand) they failed to catch the issues users are now experiencing.

    There is no derivative of the space/time continuum that allows for all bugs to be caught. Anyone who is complaining about bugs just doesn't understand how the development of an incredibly sprawling complex app like this works. And that's ok. I wish it was perfect too, but I promise you that Intua wants that more than all of us.

    @JohnnyGoodyear said:

    Sorry, no time today to read through the 500 odd posts here, but have we found/seen a straightforward sampler explanation/video? I too bought a few of the IAPs and didn't get on with them (happens) so feel to get the most here I think I should at least give the sampler a real go.

    Hit me up in a PM. I'd suggest not buying any more iap's. Those are for people who own less than 300 music apps they can sample from like we do.

    With respect to comments about the how beta testers can help improve an app, I don't think it's hard to imagine how having a larger pool of beta testers in the later stages of development would have helped to identify more bugs which could have been addressed before the app was released:

    1. More devices being used.
    2. A wider variety of apps used for testing.
    3. A wider variety of workflows.
    4. Better insight into how new users will interact with the app.

    In general, a larger pool of beta testers will better simulate how users will experience the app when it's released. From what developers on this forum have said, a very significant proportion of sales occur during the initial period after the app has been released. If this understanding is accurate, that would seem to be a significant motivation for developers to squash as many bugs as they reasonably can before release.

    I'd also recognize the limitations of a small development team with limited resources. A complex app would require a lot more feedback and commitment on the part of beta testers and the developers than for an app with fewer options and complexity.

    This all assumes that the beta testers didn't collectively bring the bugs users have been experiencing to the developer's attention which they very well may have. Perhaps the developers felt it'd be less damaging to release the app in it's current state than to delay releasing the app as is? Their familiarity with the app may have led them to believe the app would be less problematic than it is or perhaps there are significantly more users who see this as par for the course with respect to music app development?

    I was surprised that a developer who had already done BM, and BM2, and had spent years developing BM3 would release an app with significant bugs. Does it mean I think they'll fail to address the bugs or other issues with the app? No, I'm confident they will. Will all users share my confidence? I don't think so. How will their decision to release the app when they did and as it is effect their bottom line? I have no idea.

    I do think they're doing the right thing by actively collecting user feedback to address both bugs fixes and feature requests.

    The people who have been using music apps for several years will already know the score. They can wait for reviews and feedback from early adopters or take their chances based upon their confidence in Intua with respect to how they've developed and supported their previous versions of BeatMaker. They can also wait to hear feedback from other users about how they use BM3 to see if it matches up with how they create music or would like to.

    My decision to purchase early was based upon Intua's track record and the excitement from beta testers such as @samu. I don't feel betrayed or let down by them and even though I'm far from understanding how to use the app, I can already see how I'll use the app for making music even in it's current state where there's room for significant improvement (IMO). To be totally honest, I'm a sucker for an app sale especially when I believe the developer will make good on their commitment to make the app fully functional. I recognize others will be significantly less or more enthusiastic about the app and its potential for them.

  • JunebugJunebug

    @lukesleepwalker said:

    @Trueyorky said:
    This works brilliantly and actually goes one better. Drag the sample into the mapping area and hold it, then drag up and down and you will see it mapped to a note, an octave or the whole keyboard range. Then drag another sample into the area and map that in the same way - keep doing until all mapped. Fantastic and so so quick :)

    WHOA! Dude, this just made my day and makes resampling so much easier. What a great tip...

    +1 for this !!

    HUGE time saver for me! Thank you :)

  • mireko_2mireko_2

    Well I've changed my mind again, definitely keeping bm3. Just hooked it up to the digitakt and a match made in heaven. They work so well together. Even down to the eight banks and eight Midi tracks on the digitakt

    Plus don't need to worry about song mode because the digitakt is doing all the sequences now

  • mireko_2mireko_2

    here's digitakt + BM3

  • JohnnyGoodyearJohnnyGoodyear

    @boone51 said:

    @JohnnyGoodyear said:

    Sorry, no time today to read through the 500 odd posts here, but have we found/seen a straightforward sampler explanation/video? I too bought a few of the IAPs and didn't get on with them (happens) so feel to get the most here I think I should at least give the sampler a real go.

    Hit me up in a PM. I'd suggest not buying any more iap's. Those are for people who own less than 300 music apps they can sample from like we do.

    Yeah, figured that (finally) on the IAPs, which is what led me -if nothing else- to thinking I need to master the sampler. I am going to hold off for a bit and let Intua do their house-cleaning and then will revisit. Thanks to you (and @5pinlink) for your upnods....

  • [Deleted User][Deleted User]

    @JohnnyGoodyear said:

    @boone51 said:

    @JohnnyGoodyear said:

    Sorry, no time today to read through the 500 odd posts here, but have we found/seen a straightforward sampler explanation/video? I too bought a few of the IAPs and didn't get on with them (happens) so feel to get the most here I think I should at least give the sampler a real go.

    Hit me up in a PM. I'd suggest not buying any more iap's. Those are for people who own less than 300 music apps they can sample from like we do.

    Yeah, figured that (finally) on the IAPs, which is what led me -if nothing else- to thinking I need to master the sampler. I am going to hold off for a bit and let Intua do their house-cleaning and then will revisit. Thanks to you (and @5pinlink) for your upnods....

    Have you got iMaschine Boss? It's pretty easy to get sounds from that one across, and similarly Blocs is good for exporting. Drag the iMaschine samples to pads of your choice, and you can open the Blocs file in the sampler, select your chops and save them to pads.

  • JohnnyGoodyearJohnnyGoodyear

    @MonzoPro said:

    @JohnnyGoodyear said:

    @boone51 said:

    @JohnnyGoodyear said:

    Sorry, no time today to read through the 500 odd posts here, but have we found/seen a straightforward sampler explanation/video? I too bought a few of the IAPs and didn't get on with them (happens) so feel to get the most here I think I should at least give the sampler a real go.

    Hit me up in a PM. I'd suggest not buying any more iap's. Those are for people who own less than 300 music apps they can sample from like we do.

    Yeah, figured that (finally) on the IAPs, which is what led me -if nothing else- to thinking I need to master the sampler. I am going to hold off for a bit and let Intua do their house-cleaning and then will revisit. Thanks to you (and @5pinlink) for your upnods....

    Have you got iMaschine Boss? It's pretty easy to get sounds from that one across, and similarly Blocs is good for exporting. Drag the iMaschine samples to pads of your choice, and you can open the Blocs file in the sampler, select your chops and save them to pads.

    Thanks for the nudge. I do have iMaschine (dusty and unused, but therefore very low mileage :) ). Will drag it out later and have a cack-handed fiddle. Have to say I have spent my spare hour this morning remembering (again) how good many apps can be, but how we think of them otherwise because we haven't mastered them yet. Running a nice Sample Tank guitar via a written Navichord sequence into Blocs gave me something more pretty/useful/song-like in ten minutes than all sorts of stewing elsewhere. Just hadn't tried it before....every day in every way etc etc. Thanks again.

  • [Deleted User][Deleted User]

    @JohnnyGoodyear said:

    @MonzoPro said:

    @JohnnyGoodyear said:

    @boone51 said:

    @JohnnyGoodyear said:

    Sorry, no time today to read through the 500 odd posts here, but have we found/seen a straightforward sampler explanation/video? I too bought a few of the IAPs and didn't get on with them (happens) so feel to get the most here I think I should at least give the sampler a real go.

    Hit me up in a PM. I'd suggest not buying any more iap's. Those are for people who own less than 300 music apps they can sample from like we do.

    Yeah, figured that (finally) on the IAPs, which is what led me -if nothing else- to thinking I need to master the sampler. I am going to hold off for a bit and let Intua do their house-cleaning and then will revisit. Thanks to you (and @5pinlink) for your upnods....

    Have you got iMaschine Boss? It's pretty easy to get sounds from that one across, and similarly Blocs is good for exporting. Drag the iMaschine samples to pads of your choice, and you can open the Blocs file in the sampler, select your chops and save them to pads.

    Thanks for the nudge. I do have iMaschine (dusty and unused, but therefore very low mileage :) ). Will drag it out later and have a cack-handed fiddle. Have to say I have spent my spare hour this morning remembering (again) how good many apps can be, but how we think of them otherwise because we haven't mastered them yet. Running a nice Sample Tank guitar via a written Navichord sequence into Blocs gave me something more pretty/useful/song-like in ten minutes than all sorts of stewing elsewhere. Just hadn't tried it before....every day in every way etc etc. Thanks again.

    Whenever I open Blocs I always wonder why I'm not using it more often, it's a wonderful thing. BM3 adds another layer to this though - you could import your Blocs clips into BM3 for easy sequencing into a finished song, or if you're feeling adventurous - chop them up for further playing and mucking about.

    The advantage with BM3 over Auria (for me anyway), is having an easy option to either trigger a sample or play it as an instrument.

    I reckon once you get the hang of BM3 you'll be using it as much as Blocs. When they clean up the bugs.

  • ErrkaPettiErrkaPetti
    edited July 2017

    @wim said:

    @ErrkaPetti said:

    Everything went well, but, there's a but, when I save the 88 slices to layer all went well again, but, it ends with pads or key-instrument in monophonic behavior - I can't take a chord, only play one single pad/key at once...?

    I'll try again and see what's missing in some of the samplers settings...

    Hmmm... Answer myself here...

    I gave up sampling Korg Module Ivory Grand into Beatmaker 3 :-(
    After many hours testing it seems that I can't have the piano polyphonic...?
    I can just play one pad/key at once, and that make it impossible to make chords etc...
    Can't understand what's wrong here... But the 88 sampled keys is the and everything around is pretty ok...

    I found it. B)
    You need to set max polyphony (its in the sample settings) to more than one. Then you will be able to play chords.

    That said ... BeatHawk piano is the way to go. I was gonna suggest that, but you made it clear you wanted to give sampling a go. I'm glad you did because I learned a lot along the way too.

    One last discovery too ... when setting up the pattern to grab the sounds, be sure to leave a gap of an eighth note or more between notes. This will then pick up the instrument's own release curve and avoid having to fade out samples that overlapped each other.

    Voila!!!!
    Fantastic, now it's working as it should!
    Thanks mr @wim !

    Poly set to 64 makes everything (poly set to example 12 doesn't work)!

    But, it feels good to support UVI when I bought the fabolous Beathawk Acoustic Grand for only 10 buck...

    And, this journey has learn me a lot of the whole app (Beatmaker 3)...

    Thanks again!

  • TrueyorkyTrueyorky

    EXTENDED SALE! #BeatMaker3 will continue to be on sale until Friday 28th! Last chance to benefit from the intro price! @AppStore

  • [Deleted User][Deleted User]

    @JohnnyGoodyear @MonzoPro
    BlocsWave is great and straightforward for instrumental arranging. BM3 seems the perfect companion to mixdown or add some extra layer via AU if you want to tweak later things (instead record them into audio).
    I have BM3 and opened few times ATM (I should research in remixing cappabilities but I can wait until some updates) but Blocs/Launchpad are my first choice for music making/enjoy. :wink:

  • [Deleted User][Deleted User]
    edited July 2017

    @5pinlink said:
    It is definitely not for you just yet DubbyLabby, it cant match the Blocs>Launchpad workflow

    I'm agree. There are few things I will need that aren't still there but I hope in some moment Intua address them. It will be good to have their roadmap to know when are going to land...

Sign In or Register to comment.

© Vanilla Keystone Theme 2025