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…6869717374…77

Comments

  • ErrkaPettiErrkaPetti
    edited July 2017

    @5pinlink said:
    Personally i wouldn't bother with sampling velocities on a piano from a korg rompler either, seems like overkill to me.

    You are such a positive guy :-)
    Sure, I agree with you, but, I see this little project to sample Korg Module Ivory Grand into Beatmaker 3 as an educational thing...
    This project may learn me a lot of the positive/negative side of Beatmaker 3...

    It seems to be difficult to make this pattern/song/export to Wavefiles with Korg Module (and other IAA apps)...

  • wimwim

    @MonzoPro said:
    I have to say, after all the praise - BM3 in its current state is pretty fucked up. I just created a simple two bank track with a couple of patterns, saved and quit. When I reopened the song, the patterns I'd created using one of the banks (using the free IAP drum kit, so no external samples) are now completely blank. Work lost. As I've said before, the saving functionality is currently screwed and I'm guessing its this constant auto-save crap.

    That. Pisses. Me. Off.

    Regardless of potential that will make me hit the refund button if it's not fixed very quickly.

    Maybe just to be sure ... go to the song tab and hit the "pattern helper" at the top of left to expose all of the patterns? Just checking whether maybe you have a different, empty, pattern selected.

  • boone51boone51

    @ErrkaPetti said:
    I miss a really good piano into Beatmaker 3!
    Sure, I could pay another 40$ to get UVI:s new AUv3 piano app (Ravencroft or what they call it)...

    But, just now I have sooooo many other great pianos in my iPads, so, I thinking that it could be sampled into Beatmaker 3...

    But, I can't get my head around the workflow to sample Korg Modules Ivory Grand into Beatmaker 3 and make a bank out of it...?
    It's pretty easy to sample a few notes here and there, but, to sample all 88 keys into several velocity value take a little while...
    And, how can you map 88 keys x3 different velocities? That's 264 samples...

    Anyone got any suggestions?

    I’ll kindly ask you not to mention any other 40 dollar apps that I apparently cant live without...

  • [Deleted User][Deleted User]

    I highly recommend the BeatHawk grand piano and it's AUv3 so it works perfectly inside BM3 and many instances too!

    @ErrkaPetti said:

    @wim said:

    @ErrkaPetti said:
    I miss a really good piano into Beatmaker 3!
    Sure, I could pay another 40$ to get UVI:s new AUv3 piano app (Ravencroft or what they call it)...

    But, just now I have sooooo many other great pianos in my iPads, so, I thinking that it could be sampled into Beatmaker 3...

    But, I can't get my head around the workflow to sample Korg Modules Ivory Grand into Beatmaker 3 and make a bank out of it...?
    It's pretty easy to sample a few notes here and there, but, to sample all 88 keys into several velocity value take a little while...
    And, how can you map 88 keys x3 different velocities? That's 264 samples...

    Anyone got any suggestions?

    If you have good pianos, why not just load one of them onto a pad through IAA or AUv3?

    Oh, excuse my uncleared demand into Beatmaker 3...
    But, I don't have any AUv3 piano, and, all the pianos I've got is IAA only, and, the IAA technology is so shitty and unstable in Bestmaker 3... That's why I want to test and sample perhaps Korg Modules Ivory Grand into a instrument bank in Beatmaker 3, so I can avoid the crappy IAA that Apple has forgotten to improve over time... :-(

    But, how's the best workflow for that?

  • ALBALB

    @MonzoPro said:
    I have to say, after all the praise - BM3 in its current state is pretty fucked up. I just created a simple two bank track with a couple of patterns, saved and quit. When I reopened the song, the patterns I'd created using one of the banks (using the free IAP drum kit, so no external samples) are now completely blank. Work lost. As I've said before, the saving functionality is currently screwed and I'm guessing its this constant auto-save crap.

    That. Pisses. Me. Off.

    Regardless of potential that will make me hit the refund button if it's not fixed very quickly.

    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.

  • [Deleted User][Deleted User]

    @ErrkaPetti said:

    @InfoCheck said:

    @ErrkaPetti said:

    @wim said:

    @ErrkaPetti said:
    I miss a really good piano into Beatmaker 3!
    Sure, I could pay another 40$ to get UVI:s new AUv3 piano app (Ravencroft or what they call it)...

    But, just now I have sooooo many other great pianos in my iPads, so, I thinking that it could be sampled into Beatmaker 3...

    But, I can't get my head around the workflow to sample Korg Modules Ivory Grand into Beatmaker 3 and make a bank out of it...?
    It's pretty easy to sample a few notes here and there, but, to sample all 88 keys into several velocity value take a little while...
    And, how can you map 88 keys x3 different velocities? That's 264 samples...

    Anyone got any suggestions?

    If you have good pianos, why not just load one of them onto a pad through IAA or AUv3?

    Oh, excuse my uncleared demand into Beatmaker 3...
    But, I don't have any AUv3 piano, and, all the pianos I've got is IAA only, and, the IAA technology is so shitty and unstable in Bestmaker 3... That's why I want to test and sample perhaps Korg Modules Ivory Grand into a instrument bank in Beatmaker 3, so I can avoid the crappy IAA that Apple has forgotten to improve over time... :-(

    But, how's the best workflow for that?

    1. You could create a bank and add Korg Module as the IAA instrument.
    2. Create a pattern and add MIDI notes for the samples you want.
    3. Allow enough time between notes so they decay sufficiently.
    4. Save the bank along with the pattern. You can change pianos and use same pattern.
    5. Add the pattern to your song.
    6. Export the song.
    7. Create a bank for your samples.
    8. Rename the song you exported to something that makes sense.
    9. Add the song sample to the first pad.
    10. Use auto slice to cut up the song sample into one slice per note.
    11. Save slices to pads in the bank.
    12. Save the bank with the slices.
    13. Set the hold area for each sample in the bank so sustained notes sound reasonable.
    14. Repeat steps but just change the piano in the IAA module bank.

    There are some other issues such as assigning the samples to a pad associated with its note which I'm not too sure about how to navigate through yet which would be good to know in terms of playability.

    I was able to record an Alchemy synth on an iPad 2 using this method and transfer the bank by exporting/importing the zip file to BM3 on my iPad Air 2. This could be a method for sampling IAA apps that don't make it to iOS 11.

    This process is similar to creating a sound font with similar limitations and concerns. If the IAA setup should ever be stable enough to meet your needs, that would seem to be an easier and more flexible method unless you have some very specific uses for piano. Trying to recreate the range of piano sounds offered by Ivory Grand would not be a very practical task to take on. The layering, effects, and other BM3 effects do make this an appealing consideration if these sorts of sound transformations are of interest.

    Creating percussive banks seems more straight forward as you'd just use one shot mode and could have a standardized setup for which pads correspond to which parts of your kit.

    Ok, thanks for this tips!

    But, unfortunate, I have done exactly as you written doen here, but, when I export the Midi-pattern-song (with the notes from A0 to C7) I've got an empty (quiet) 250 MB wavefiles...?
    I tried with several setups, without any luck :-((

    But, as I can remember from a thread from the Auria Pro forum, Rim (the developer of Auria Pro) said it was problem with bouncing tracks with IAA-synth, especially with high speed....
    Perhaps this is the issue with the empty wavefile?

    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.

  • boone51boone51

    @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.

  • ErrkaPettiErrkaPetti

    @5pinlink said:

    @ErrkaPetti said:

    @5pinlink said:
    Personally i wouldn't bother with sampling velocities on a piano from a korg rompler either, seems like overkill to me.

    You are such a positive guy :-)
    Sure, I agree with you, but, I see this little project to sample Korg Module Ivory Grand into Beatmaker 3 as an educational thing...
    This project may learn me a lot of the positive/negative side of Beatmaker 3...

    It seems to be difficult to make this pattern/song/export to Wavefiles with Korg Module (and other IAA apps)...

    Ok well i was only giving advice from the point of view of the last 5 years i have been making sample content for a developer hahaha.

    I might do a video tutorial to show how to do it, is that positive enough ?

    As we say in Sweden: Kalas!
    If you make a video, we're pleased enough!

  • ErrkaPettiErrkaPetti

    @InfoCheck said:

    @ErrkaPetti said:

    @InfoCheck said:

    @ErrkaPetti said:

    @wim said:

    @ErrkaPetti said:
    I miss a really good piano into Beatmaker 3!
    Sure, I could pay another 40$ to get UVI:s new AUv3 piano app (Ravencroft or what they call it)...

    But, just now I have sooooo many other great pianos in my iPads, so, I thinking that it could be sampled into Beatmaker 3...

    But, I can't get my head around the workflow to sample Korg Modules Ivory Grand into Beatmaker 3 and make a bank out of it...?
    It's pretty easy to sample a few notes here and there, but, to sample all 88 keys into several velocity value take a little while...
    And, how can you map 88 keys x3 different velocities? That's 264 samples...

    Anyone got any suggestions?

    If you have good pianos, why not just load one of them onto a pad through IAA or AUv3?

    Oh, excuse my uncleared demand into Beatmaker 3...
    But, I don't have any AUv3 piano, and, all the pianos I've got is IAA only, and, the IAA technology is so shitty and unstable in Bestmaker 3... That's why I want to test and sample perhaps Korg Modules Ivory Grand into a instrument bank in Beatmaker 3, so I can avoid the crappy IAA that Apple has forgotten to improve over time... :-(

    But, how's the best workflow for that?

    1. You could create a bank and add Korg Module as the IAA instrument.
    2. Create a pattern and add MIDI notes for the samples you want.
    3. Allow enough time between notes so they decay sufficiently.
    4. Save the bank along with the pattern. You can change pianos and use same pattern.
    5. Add the pattern to your song.
    6. Export the song.
    7. Create a bank for your samples.
    8. Rename the song you exported to something that makes sense.
    9. Add the song sample to the first pad.
    10. Use auto slice to cut up the song sample into one slice per note.
    11. Save slices to pads in the bank.
    12. Save the bank with the slices.
    13. Set the hold area for each sample in the bank so sustained notes sound reasonable.
    14. Repeat steps but just change the piano in the IAA module bank.

    There are some other issues such as assigning the samples to a pad associated with its note which I'm not too sure about how to navigate through yet which would be good to know in terms of playability.

    I was able to record an Alchemy synth on an iPad 2 using this method and transfer the bank by exporting/importing the zip file to BM3 on my iPad Air 2. This could be a method for sampling IAA apps that don't make it to iOS 11.

    This process is similar to creating a sound font with similar limitations and concerns. If the IAA setup should ever be stable enough to meet your needs, that would seem to be an easier and more flexible method unless you have some very specific uses for piano. Trying to recreate the range of piano sounds offered by Ivory Grand would not be a very practical task to take on. The layering, effects, and other BM3 effects do make this an appealing consideration if these sorts of sound transformations are of interest.

    Creating percussive banks seems more straight forward as you'd just use one shot mode and could have a standardized setup for which pads correspond to which parts of your kit.

    Ok, thanks for this tips!

    But, unfortunate, I have done exactly as you written doen here, but, when I export the Midi-pattern-song (with the notes from A0 to C7) I've got an empty (quiet) 250 MB wavefiles...?
    I tried with several setups, without any luck :-((

    But, as I can remember from a thread from the Auria Pro forum, Rim (the developer of Auria Pro) said it was problem with bouncing tracks with IAA-synth, especially with high speed....
    Perhaps this is the issue with the empty wavefile?

    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.

    Ok!
    I'll try this instead... Thanks!

  • ExAsperis99ExAsperis99

    @InfoCheck said:

    @ExAsperis99 said:

    @InfoCheck said:
    This works well for me with samples that aren't bpm aligned:

    1. Load in a sample.
    2. Use zero crossing detection and scissors to select where to cut slice.
    3. Repeat step 2 until you've set all your slices.
    4. Save slices.

    Here's a screenshot of a 3 second voice sample sliced.

    A quick question about No. 4. Where are you saving them? Must they be sent to a Bank immediately? Also, let's say you wanted to take that 3-second vocal sample and remove it for later use. Can you just send it to a folder on its own? To a different Bank?

    There are several options for step 4. When you save to pads, you can select which bank, on which pad to start. You can create a new bank too.

    @wim said:

    @AudioGus said:
    This sounds super cool, but I don't see how to do it. Could you circle on a screenshot " If you touch one of the patterns in the list at the left as the sequence is playing,"...?

    • Get to Song view, set a loop section over the area you want to work with and turn on looping.

    • Make sure no banks are darkened out due to being under Scene control. If they are then touch the little play button at the top right of the timeline area.

    • Expose the patterns by touching the area at the upper left where it says PLAYING SONG. I forget what they call this ... the "Pattern helper" or something.

    • Things should now look like the screenshot below, with the patterns you've created listed down the left.
    • Press play to begin looping through the section. Now, touch a pattern at the left and it will begin to play instead of the pattern that's in the timeline. You'll see a "pacman" pie shape indicating the position within the loop, and the row will be shaded.
    • You can switch between banks using the bank letters just to the right of the patterns. You can fire up as many "override" loops as you want.
    • The currently playing pattern for each bank is highlighted, but is also shown in the "Pattern helper" at the top left. This can save some scrolling around if you have a lot of patterns. (Don't forget you can name patterns too if it makes things easier.)
    • Touch the play button at the far right of the bank row to stop the override for that bank. Touch the play button at the top right to turn off all overrides.
    • When you can still edit the patterns in the timeline while this is going on, so it's easy to delete and replace any patterns as you go. Just tap the pattern, delete it, then drag another into it's place. This works whether the bank is shaded (under pattern control) or not (under song control).

    I hope that's clearer than my other explanation.

    Cheers

    Gold star for robot boy!

  • wimwim
    edited July 2017

    @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.

  • wimwim

    Oh, and you might want to turn of FX in Module so that the samples come in as dry as possible for the most flexibility.

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

    @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. . .

  • MayoMayo

    I can't wait for BM4 :neutral:

  • wimwim

    @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.

  • philowerxphilowerx

    @Mayo said:
    I can't wait for BM4

    Gadget 14 with IAA, AB, AU instrument and effects support!

  • raindroraindro

    When the pads are on screen and there's the side bar that says keys and select and mute and scene etc:

    Wouldn't have the ability to switch patterns with the pads be much more useful then a global scene switch?

  • jn2002dkjn2002dk

    So has anyone found a remotely efficient way of importing midi files?

    The only way i've found is to drag the file from the import folder into the song timeline but that leaves me with all the midi tracks in the same bank. This means i either have to assign instruments to each pad but that means a lot of extra fiddling in the mixer when applying fx, or i have to do it for as many banks as there are tracks and manually disable or delete the other pads in each bank

    Why oh why can't i just press load file and have it create a bank for each track in the midi file?

  • gonekrazy3000gonekrazy3000

    @wim said:

    @ErrkaPetti said:

    @wim said:
    I have a few ideas, but others will be way better at answering your sampling question.

    For me, I would just load it as an IAA, record to an audio track as soon as the pattern is good, then unload the IAA if you feel like it's going to crash your project. Rinse and repeat.

    Good idea!
    But, I rather have a complete sampled piano instrument (Korg Module) into Beatmaker 3...

    I wish you luck with that. Making good multi-layered sound banks is difficult. The really good ones have carefully crafted loop points in each sample, for sustain. Apps can also sometimes swap in random samples, and add additional things like key-hammer sounds in slightly varying loudnesses.

    Even Intua failed. Their piano bank is a mess from what I've read. And they supposedly know what they're doing. With time and skill I guess you can get there though! I hope it works out.

    I feel like the process is going to involve creating a pattern of all 64 notes (to get to 88 I think you need more than one bank?), at low velocity. Then play it back at a slow enough tempo for each note to ring out (this will need to be really slow for the lower notes). Then play it and save to an audio file. Next load that sample to a pad and slice it up with auto-slice set to 64. Finally, save to a layer, setting the starting note to the lowest note of your pattern.

    Copy the original pattern, select all notes and change to medium velocity, and repeat the above, saving to a new layer. (I'm not sure at this time how to set the velocity range for a layer.)

    Repeat the above with a pattern at high velocity.

    banks can have 128 pads. so theoretically it can be done on 1 bank.

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

    @wim said:

    @MonzoPro said:
    I have to say, after all the praise - BM3 in its current state is pretty fucked up. I just created a simple two bank track with a couple of patterns, saved and quit. When I reopened the song, the patterns I'd created using one of the banks (using the free IAP drum kit, so no external samples) are now completely blank. Work lost. As I've said before, the saving functionality is currently screwed and I'm guessing its this constant auto-save crap.

    That. Pisses. Me. Off.

    Regardless of potential that will make me hit the refund button if it's not fixed very quickly.

    Maybe just to be sure ... go to the song tab and hit the "pattern helper" at the top of left to expose all of the patterns? Just checking whether maybe you have a different, empty, pattern selected.

    Nah I checked, the correct pattern is in the timeline, but both patterns I created are blank.

    This is what happened:

    Created new song 'Donkey'

    Added own sample, sliced to pads in Bank 1, made two patterns, added to timeline.

    Added a second bank, used an internal drum pack, created two patterns and added to timeline.

    Played song through, it sounded fantastic, hit 'save session' and closed app.

    When I reopened the app the usual list of auto saves are there - about three 'Donkey (Auto-saved)', which I don't want, so instead I selected the 'Open session' link in the left, found 'Donkey' and opened it. When I did this it queried whether I wanted to do this, as saved changes would be lost. Since this was the version I'd saved, right before closing, I carried on and opened 'Donkey'.

    Result: the correct patterns for Bank 2 are in the timeline, the drum pack is still loaded, but the patterns are empty.

  • [Deleted User][Deleted User]

    @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.

  • wimwim

    @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.

    That's a tough one for sure since there is no indication of what circumstances caused it to fail. Developers need to be able to recreate an issue in order to fix it. Sorry about that one man, it must be really frustrating.

  • ElGregoLocoElGregoLoco
    edited July 2017

    @gonekrazy3000 said:

    @ElGregoLoco said:

    @srcer said:

    @ElGregoLoco said:
    I still have regular crashes on my side (like every 5-6 hours of use) and I identified many odd behaviors when playing with audio files/pattern (like when you slice a pattern on a audio file and then want to edit it, the ending loop marker is not at the right place, etc), but after more than 30hrs on the app I can now confirm that it is (or will be in fact) wonderful... I will now probably wait until the 'public beta' is over i.e. wait for a few updates before I use it again (in the current state it is not stable enough for me to build a full project in... Too risky IMO), but I'm really looking forward to be able to use it correctly...
    Peace.

    Perhaps @mathieugarcia should add you to his beta team so you can test the forthcoming code before it's released :)

    Don't ... Just don't... I begged to be in the beta when it was opened and they rejected my proposal in a 'not very nice' way... That's why I made jokes back then to say it was a VIB (Very Important Beta)...
    I really wish I could have been part of the beta as it seems that most beta testers have not really used the thing given the instable state it is in right now...
    Yesterday night I spent 6 hours working on a project, I thought everything was fine and then I tried to save a sliced loop to AIFF so that I could reload it in the same bank on the second page of pads to slice it again with a new effect on (HP filter to make the intro, would have been good). At first it seemed to worked but once sliced to pad on the second page of the bank, the app crash completly everytime I touch pad... Another 6 hours to the trash can I guess (I already lost about 40hrs on the app trying to finalize at least one simple project, but I was never able to because of the instability of the app)... Right now, I'm very frustrated and feel like back when I was believing in Retronyms... Sad

    @Tritonman said:
    Can I delete a sound from a pad once it is put there? Is there an actual manual with an index yet?

    It seems sometimes you can and sometimes you can't... Probably linked to the fact that the sample is currently playing or not I guess... Sometimes when I cannot delete a pad, I close the app and restart it and I can then delete it ...
    The same goes with files/folders that you delete from the library on 'Edit' mode... You have to quit the app and restart it to see them disappear from the lib...
    What a good beta tested app... For sure...

    PS : Sorry for being so sarcastic and negative... But given the teasing and the first feed back from beta testers, I admit I really thought this app would be the holy grail for me.. .And therefore, I am very disapointed today...
    I still love what the app intend to propose and the functionnalities it tries to achieve... But the fact that it is so buggy and instable make it impossible to finish a project...
    I mean, it's supposed to be really more suited to my sample based music style than Gadget (for which it take me hours to put to the right tempo and slice loops outside the app before I load in Bilbao) but at least, Gadget has never crashed on me, has always been supa stable on my iPad Air2 and allows me to finalize music projects (it does less than BM3 regarding samples, but at least it does it correctly).

    Its getting a bit old with you constantly stating the fact that they turned you down from the beta. i think i personally have seen at-least 10+ posts now. you're bitter that they turned you down. we get it. but please stop posting it again and again.

    Yes. the app is a mess. no i am not a tester. that being said the release branch isn't the betas the testers have. its atleast a couple versions behind. so many of these bugs have already been fixed. I'm just going to patiently wait till the broken stuff gets fixed. but even in its broken state this is the best sampler on IOS. I'm having a blast tinkering around in it for the challenge @JangoMango created.

    I understand why you say that, but I don't think I complained about not being part of the beta for weeks now...
    And here, I was just replying to someone suggesting that it would be a good idea if I was part of the beta given the love I got for the app, the time I spend on it and the number of bugs I identify... That's it, I was not trying to complain more about the beta on my side.

    Plus, the last 2 pages of the thread make me feel a bit better as at least 3-4 other people, including you, confirm that the app is a bug fiesta in its current state and cannot be used to make complete projects as is...
    I admit that I completly misunderstood the devs communication before release then... I really thought that they delayed the release for months several times and asked 'fans' to be patient about it because they intended to release something fully ironed and stable... That's why I'm disappointed.
    But at least, now, experiencing that much bugs and crashes, I feel like I'm part of the beta... Lol

    Peace and sorry again for bothering you man.

  • JohnnyGoodyearJohnnyGoodyear

    @lukesleepwalker said:

    @gonekrazy3000 said:

    @rhizome said:
    So, I went and got the piano IAP, on the strength of the free Summer Keys samples. It sounds awful. Everything is out of tune - the keys, the scales, the chords. Sounds like they sampled a piano prepared by John Cage.

    I could probably use it if I were making an experimental track exploring dissonance, but other than that, it is money wasted.

    I can't believe they charged a premium price for this. Has anyone else got these problems, or am I missing something here?

    Honestly at this point I'd suggest you just sample your own instruments. I'm currently making multisampled instruments from both iOS apps/au and also some of the sample libraries I have and having a blast!

    Totally agree. Hopefully someone will do a good primer video on sampling (or I should get off my Duff and figure out how to make videos myself) because this sampler is a thing of beauty.

    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.

  • [Deleted User][Deleted User]

    @wim 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.

    That's a tough one for sure since there is no indication of what circumstances caused it to fail. Developers need to be able to recreate an issue in order to fix it. Sorry about that one man, it must be really frustrating.

    Thanks. I think for now I'll concentrate on learning how to use the app (your tips are very helpful), and leave song-making for after the bug fixes.

  • ErrkaPettiErrkaPetti

    @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.

    Thanks guy for so many tips and suggestions around piano sampling into Beatmaker 3!

    I've try some of them and will return with an report how it's going...

    @wim I think Korg Modules Ivory samples got 3 different velocity layers (it's a 1.2GB samplelibrary)...

  • JohnnyGoodyearJohnnyGoodyear
    edited July 2017

    @wim said:

    • 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.

    Good stuff for those of us at the back of the class.

  • ErrkaPettiErrkaPetti
    edited July 2017

    @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...

  • mireko_2mireko_2

    @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

  • mireko_2mireko_2

    I've was considering just holding onto it to use the time stretch with my sp404. Going to give that a go tomorrow and see how it goes but if not then I will just rebuy it once it's stable

Sign In or Register to comment.

© Vanilla Keystone Theme 2025