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.

I'm Not Making Any More DrumPerfect Pro Tutorials

245

Comments

  • @gilbert Thanks for your generous advice. I really appreciate it.

    My issue with appending patterns: If I have a two bar pattern and add another two bar pattern -- no problem.
    If I have a two bar pattern and then want to append a one bar pattern to it-- DPP crashes on me.

  • I've been unable to save my DrumPerfect songs so they look the way they did when I shut the program. Let me explain.

    Here's a current page. As you can see I have arranged patterns I have created (grayed out) in the grid to click and play while I select the ones I like to put into my song. (then they are in color).

    Why do I set it up like this? Because when you load patterns on the Pattern Page, you have to be very careful that they don't come up on a spot where a pattern already exists. If you do that, it will change the patterns in your song.

    So you need to be very, very, very careful. Setting things up like this is the only way I have found to not screw up my song. It's my work process.

    The only problem is that when I go back sometimes, DrumPerfect will load up with their standard 64 patterns.

    So I load my song again. It looks like what you see below.. My DrumPerfect song only saves the patterns that have been put into my song. In all the other spots it keeps the patterns from the previous song loaded.

    So... not only have I lost my work, the page is a big mess.

    So I hit the "clear all" button, clear all the patterns, and load my song again. Now it's nice and clean but all you see are the patterns that I have already placed into my song.

    I've gone to the effort of doing this to make a feature request.

    Please have DrumPerfect songs load up looking the same way they did when they were saved! :)

  • @Reid said:
    Please have DrumPerfect songs load up looking the same way they did when they were saved! :)

    A lot of effort but a very important thing...

  • edited March 2016

    What I do is take midi patterns from Addictive Drums and just play the midi to DPP and record them right in there, it's great way to quickly build up your pattern banks inside DPP. Of course, you can do this with any desktop drum vst that has a built in bank of midi patterns. Recording the patterns in this way seems easier than importing the midi files which I couldn't figure out an easy way to do, plus I would have to export each midi file through my DAW first, much easier to just play it and record it.

  • Importing midi files into DP is very easy. I keep my midi files in Dropbox or Audioshare so I open a midi file and click on the icon that takes you to "Open in" (what do you call that icon, share?) and then select Drum Perfect as your destination. It seems to copy the midi file into whatever song is already open so you may want to create a new blank song first. I just realized I have only ever imported midi drum files so I'm not sure what would happen if a multitrack midi file was imported.

  • edited March 2016

    .

    Why do I set it up like this? Because when you load patterns on the Pattern Page, you have to be very careful that they don't come up on a spot where a pattern already exists. If you do that, it will change the patterns in your song.

    So you need to be very, very, very careful. Setting things up like this is the only way I have found to not screw up my song. It's my work process.

    The only problem is that when I go back sometimes, DrumPerfect will load up with their standard 64 patterns.

    >

    So I load my song again. It looks like what you see below.. My DrumPerfect song only saves the patterns that have been put into my song. In all the other spots it keeps the patterns from the previous song loaded.

    So... not only have I lost my work, the page is a big mess.

    So I hit the "clear all" button, clear all the patterns, and load my song again. Now it's nice and clean but all you see are the patterns that I have already placed into my song.

    I've gone to the effort of doing this to make a feature request.

    Please have DrumPerfect songs load up looking the same way they did when they were saved! :)

    Hi Reid,
    and others fellows that might find a bit puzzling the management of patterns and songs, ( perhaps kits ) in DPP...

    You see, DPP is perhaps one of the rare drum app that offer such an extensive range of import/export of data, and with these numerous possibilities come a little price; we make mistakes and at the beginning, feel often wondering what to do to achieve a particular goal.
    So let's look at these points one at a time.
    Usually, before building a song it is recommended to know which patterns are required and have them ready in the library. ( intro, verse, fills, bridge and ending for a standard structure. )
    If there are many variations of a pattern you will have noticed the automatic renaming of the variations after the main pattern. That simplify and make much easier the tedious task of naming individually each pattern, specially when they are similar ( variations ). Another appreciable feature is the possibility to save ALL the patterns in one go, at any time, to update and make sure that no change will be lost. I don't know if it is well documented but you can achieve that by long pressing the save button ( a confirmation box will appear yes/no )
    After all required patterns of the song are done, they can, for the sake of clarity, be grouped in a newly created category with perhaps the name of the song. At that point we can audition each of them in the pattern library, in their category. If something need to be changed it is possible to load the pattern and make the changes. Once patterns are ready, they will be loaded in one go ( again ) by multiple selection ( turn on the blue switch in the pattern library ) then select all in the category and close. they will be placed from THE FIRST SLOT selected prior to loading. If you have cleared all patterns from the song, the first slot will automatically be selected. Then just build the song, choosing colors before inserting or copying patterns, at your convenience. Once the song sounds good, save and it will be recalled exactly the same when reloaded.
    Now if you make new patterns in empty slots and add them to the song they will be present when the song is reloaded, ONLY if they have been saved as patterns before. Saving a song doesn't save any pattern. It just save a list of the patterns used. It's why the save all patterns, I mentioned above, is so important to make sure that every pattern is indeed saved.
    Next, if you decide to load additional patterns to the ones already chosen for the song, make sure to select the first EMPTY slot BEFORE loading them. Because they will be loaded from there and not overwrite the first batch loaded.

    Normally DPP will restart with the latest state we have been working on. We will find everything as we left it. But if one clear the cache in settings, it will reinitialize the state with the factory PatBank64. A safe best practice is therefore to make sure that all patterns and current song are saved before shutting down the app. Just 2 buttons to press. Longpress "save" to save all patterns and save song. Done.

    Three more useful hints to simplify life ( with DPP that is... )
    Longpress " Clear all " in song mode will clear EVERYTHING! Patterns/song/kits. Great to start afresh for a new project.
    Long press " Clear " in kit mode will clear ALL kits.
    Longpress " Load " in Song mode will insert in one go, all the patterns currently in the pattern bank in their respective order. Not only that will save time, if you have your patterns in the correct order without repetition ( repeating some patterns will be very easy after, using copy and paste ) but it is a safe way to save a song just as a BANK OF PATTERNS , nothing else. We can create of course as many pattern banks ( PatBank ) as wished and recall them for specific work.
    Therefore no need to reload each of the patterns ( imagine the work if they belong to different categories! ) from the pattern view. A kind of playlist of patterns ( max 64 ). Then clear the "song", and start building a real song or experimenting combination of patterns, etc...
    Try longpress on each button and see on some of them what is " hidden "........

    There are so many ways to input/output data in DPP that it would almost require a huge manual ( or videos on which I am working presently ) to go in depth/detail about each way.
    DPP is a real digital musical instrument for both performance ( touch sensitive pads ) and composition ( sequencer ). ( and practice too! ). As one dig it everyday, amazing possibilities are revealed.

    A bit long reply but no other way to go in details, here...

    Great that users can share here their discoveries, particular workflows, and... questions.

    Good luck, good work.

  • I'm kind of lost on this one. I have my midi patterns from EZ drummer but my PC is not working right now. I did manage to load them into the iPad when I had ifunbox. Sso I have them all in Aufioshare. Wonder I there's an easy way to send the data to DP like you mentioned.

    Question,
    Is there a way to optimize DP to not take too much Ram? What should I do?> @Judochopjames said:

    What I do is take midi patterns from Addictive Drums and just play the midi to DPP and record them right in there, it's great way to quickly build up your pattern banks inside DPP. Of course, you can do this with any desktop drum vst that has a built in bank of midi patterns. Recording the patterns in this way seems easier than importing the midi files which I couldn't figure out an easy way to do, plus I would have to export each midi file through my DAW first, much easier to just play it and record it.

  • Wow!!! So awesome. Thanks for the tips. I wanna get Audiobus remote to launch the midi clips in DP is this possible?

    @Gilbert said:
    .

    Why do I set it up like this? Because when you load patterns on the Pattern Page, you have to be very careful that they don't come up on a spot where a pattern already exists. If you do that, it will change the patterns in your song.

    So you need to be very, very, very careful. Setting things up like this is the only way I have found to not screw up my song. It's my work process.

    The only problem is that when I go back sometimes, DrumPerfect will load up with their standard 64 patterns.

    >

    So I load my song again. It looks like what you see below.. My DrumPerfect song only saves the patterns that have been put into my song. In all the other spots it keeps the patterns from the previous song loaded.

    So... not only have I lost my work, the page is a big mess.

    So I hit the "clear all" button, clear all the patterns, and load my song again. Now it's nice and clean but all you see are the patterns that I have already placed into my song.

    I've gone to the effort of doing this to make a feature request.

    Please have DrumPerfect songs load up looking the same way they did when they were saved! :)

    Hi Reid,
    and others fellows that might find a bit puzzling the management of patterns and songs, ( perhaps kits ) in DPP...

    You see, DPP is perhaps one of the rare drum app that offer such an extensive range of import/export of data, and with these numerous possibilities come a little price; we make mistakes and at the beginning, feel often wondering what to do to achieve a particular goal.
    So let's look at these points one at a time.
    Usually, before building a song it is recommended to know which patterns are required and have them ready in the library. ( intro, verse, fills, bridge and ending for a standard structure. )
    If there are many variations of a pattern you will have noticed the automatic renaming of the variations after the main pattern. That simplify and make much easier the tedious task of naming individually each pattern, specially when they are similar ( variations ). Another appreciable feature is the possibility to save ALL the patterns in one go, at any time, to update and make sure that no change will be lost. I don't know if it is well documented but you can achieve that by long pressing the save button ( a confirmation box will appear yes/no )
    After all required patterns of the song are done, they can, for the sake of clarity, be grouped in a newly created category with perhaps the name of the song. At that point we can audition each of them in the pattern library, in their category. If something need to be changed it is possible to load the pattern and make the changes. Once patterns are ready, they will be loaded in one go ( again ) by multiple selection ( turn on the blue switch in the pattern library ) then select all in the category and close. they will be placed from THE FIRST SLOT selected prior to loading. If you have cleared all patterns from the song, the first slot will automatically be selected. Then just build the song, choosing colors before inserting or copying patterns, at your convenience. Once the song sounds good, save and it will be recalled exactly the same when reloaded.
    Now if you make new patterns in empty slots and add them to the song they will be present when the song is reloaded, ONLY if they have been saved as patterns before. Saving a song doesn't save any pattern. It just save a list of the patterns used. It's why the save all patterns, I mentioned above, is so important to make sure that every pattern is indeed saved.
    Next, if you decide to load additional patterns to the ones already chosen for the song, make sure to select the first EMPTY slot BEFORE loading them. Because they will be loaded from there and not overwrite the first batch loaded.

    Normally DPP will restart with the latest state we have been working on. We will find everything as we left it. But if one clear the cache in settings, it will reinitialize the state with the factory PatBank64. A safe best practice is therefore to make sure that all patterns and current song are saved before shutting down the app. Just 2 buttons to press. Longpress "save" to save all patterns and save song. Done.

    Three more useful hints to simplify life ( with DPP that is... )
    Longpress " Clear all " in song mode will clear EVERYTHING! Patterns/song/kits. Great to start afresh for a new project.
    Long press " Clear " in kit mode will clear ALL kits.
    Longpress " Load " in Song mode will insert in one go, all the patterns currently in the pattern bank in their respective order. Not only that will save time, if you have your patterns in the correct order without repetition ( repeating some patterns will be very easy after, using copy and paste ) but it is a safe way to save a song just as a BANK OF PATTERNS , nothing else. We can create of course as many pattern banks ( PatBank ) as wished and recall them for specific work.
    Therefore no need to reload each of the patterns ( imagine the work if they belong to different categories! ) from the pattern view. A kind of playlist of patterns ( max 64 ). Then clear the "song", and start building a real song or experimenting combination of patterns, etc...
    Try longpress on each button and see on some of them what is " hidden "........

    There are so many ways to input/output data in DPP that it would almost require a huge manual ( or videos on which I am working presently ) to go in depth/detail about each way.
    DPP is a real digital musical instrument for both performance ( touch sensitive pads ) and composition ( sequencer ). ( and practice too! ). As one dig it everyday, amazing possibilities are revealed.

    A bit long reply but no other way to go in details, here...

    Great that users can share here their discoveries, particular workflows, and... questions.

    Good luck, good work.

  • edited March 2016

    @Gilbert I have been digging into DrumPerfect bit by bit, making hundreds of mistakes, as I try to figure out how to make my song. I appreciate all this help enormously. I hope you will listen to me. We are talking about user interface. The reasons you used to make the app the way you did are fine, but if in practice I am trying something, it loses my work, try again it loses my work,. try again, it loses my work.... and onward for dozens and dozens of times--maybe there are some things you could reconsider. You have one of the best music apps ever, but I have read more than one person on this forum say that they have set it aside and don't use it because of the user interface.

    I have read the manual a few times and I am pursuing this very seriously. I refuse to give up and won't give up. And I hope to make a video someday to share what I am learning the hard way. These posts I'm making on this page aren't really helpful to everybody else, but I am learning and maybe I will be able to put it together in a simple way someday. From the user's perspective.

    Usually, before building a song it is recommended to know which patterns are required and have them ready in the library. ( intro, verse, fills, bridge and ending for a standard structure. )

    Yeah... well that might work fine for some people, but not for me. I don't know what I"m going to do before I'm doing it. And I create a workspace on the song page so I can assemble my song.

    And when I set that workspace up--I want it to stay there.

    If there are many variations of a pattern you will have noticed the automatic renaming of the variations after the main pattern. That simplify and make much easier the tedious task of naming individually each pattern, specially when they are similar ( variations ). Another appreciable feature is the possibility to save ALL the patterns in one go, at any time, to update and make sure that no change will be lost. I don't know if it is well documented but you can achieve that by long pressing the save button ( a confirmation box will appear yes/no )

    I must differ on automatic renaming. I believe that it is better to give each pattern a name that identifies it as you make it--and I think it is also important that it be filed away in a folder where you can find it. Housekeeping is good. Anything the program can do to remind you to do that and help you do it, is a plus. Maybe it shouldn't let you save a pattern unless you give it a folder, and then put everything in that folder until you tell it not to.

    One thing I particularly don''t like is what happens if you create a new song. You auto-name all the patterns based on the name of the song. It's MUCH easier to work with numbers.

    I do know about saving all the patterns at once--and that's great.

    After all required patterns of the song are done, they can, for the sake of clarity, be grouped in a newly created category with perhaps the name of the song. At that point we can audition each of them in the pattern library, in their category. If something need to be changed it is possible to load the pattern and make the changes. Once patterns are ready, they will be loaded in one go ( again ) by multiple selection ( turn on the blue switch in the pattern library ) then select all in the category and close. they will be placed from THE FIRST SLOT selected prior to loading. If you have cleared all patterns from the song, the first slot will automatically be selected.

    Didn't catch the blue switch thing. Thank you! That will definitely save me time.
    [Note: tried this today. Use with caution! Caused me a lot of errors that I had to fix. Any lingering patterns that you forget to deselect get put into the grid. Covering up the ones that were there, of course. ]

    Then just build the song, choosing colors before inserting or copying patterns, at your convenience. Once the song sounds good, save and it will be recalled exactly the same when reloaded.

    Gilbert, people don't finish their songs in one go, and in particular, songs that offer the complexity of DPP. When I hit the save button on any app of any kind--music, graphic, whatever--I expect it to look exactly the same when I reload it. And it took me a ton of experimentation to figure out why and how it was changing.

    You know what I do now? I make a frame grab. And I go into my photo library to find out how to reload my patterns. To me that's a lot to ask.

    Please consider changing this in a future version. You can say "this is the way it works--learn it," or you can try to make it easier. Little alterations like this can make a big difference.

    Now if you make new patterns in empty slots and add them to the song they will be present when the song is reloaded, ONLY if they have been saved as patterns before. Saving a song doesn't save any pattern. It just save a list of the patterns used. It's why the save all patterns, I mentioned above, is so important to make sure that every pattern is indeed saved.
    Next, if you decide to load additional patterns to the ones already chosen for the song, make sure to select the first EMPTY slot BEFORE loading them. Because they will be loaded from there and not overwrite the first batch loaded.

    Normally DPP will restart with the latest state we have been working on. We will find everything as we left it. But if one clear the cache in settings, it will reinitialize the state with the factory PatBank64. A safe best practice is therefore to make sure that all patterns and current song are saved before shutting down the app. Just 2 buttons to press. Longpress "save" to save all patterns and save song. Done.

    Will do. But you are aware that there is no save button in apps like Auria Pro. Log out and it is the same when you come back. It becomes second nature and it's understandable if people expect that. If you can add this functionality in a future version it will be mean that your users will be much happier.

    Three more useful hints to simplify life ( with DPP that is... )
    Longpress " Clear all " in song mode will clear EVERYTHING! Patterns/song/kits. Great to start afresh for a new project.
    Long press " Clear " in kit mode will clear ALL kits.

    Those two things are clear from the Quick Start.

    Longpress " Load " in Song mode will insert in one go, all the patterns currently in the pattern bank in their respective order. Not only that will save time, if you have your patterns in the correct order without repetition ( repeating some patterns will be very easy after, using copy and paste ) but it is a safe way to save a song just as a BANK OF PATTERNS , nothing else. We can create of course as many pattern banks ( PatBank ) as wished and recall them for specific work.
    Therefore no need to reload each of the patterns ( imagine the work if they belong to different categories! ) from the pattern view. A kind of playlist of patterns ( max 64 ). Then clear the "song", and start building a real song or experimenting combination of patterns, etc...
    Try longpress on each button and see on some of them what is " hidden "........

    The 64Bank is also a song. That's how I've been loading them. That's intuitive.

    There are so many ways to input/output data in DPP that it would almost require a huge manual ( or videos on which I am working presently ) to go in depth/detail about each way.
    DPP is a real digital musical instrument for both performance ( touch sensitive pads ) and composition ( sequencer ). ( and practice too! ). As one dig it everyday, amazing possibilities are revealed.

    I agree! I love it! I hope someday to help others use it, and I wouldn't be able to do that without your help. I'm sure I will have many more questions in the future. I am very grateful for your generosity in taking the time to help me.

  • @Reid said:

    @Gilbert

    Usually, before building a song it is recommended to know which patterns are required and have them ready in the library. ( intro, verse, fills, bridge and ending for a standard structure. )

    Yeah... well that might work fine for some people, but not for me. I don't know what I"m going to do before I'm doing it. And I create a workspace on the song page so I can assemble my song.

    And when I set that workspace up--I want it to stay there.

    As a blundering n00b I appreciate your dedication Mister Reid and also your desire to explain and help Mister Gilbert. However, from the very long and useful posts I must tell you(Mister Gilbert) that as soon as I saw this response from Mister Reid I said aloud 'Exactly!'.

  • edited March 2016

    I also agree with @Reid, except that (even in Auria or other apps) what would make my life SO MUCH easier would be to have a REAL BLANK PROJECT at every opening of the app.
    I often start new projects then set them apart for a couple of days, then return to them... and the simple possibility to open an app and simply press an "open" button to load the exact same project at the exact same state with the exact same configuration on any panel/window all over the app would be a dream becoming true.

  • edited March 2016

    @Gratouilli Or the Logic way where you establish in Settings what you want it to do when you load it up.

  • @Gilbert Some features that would be MEGA-SUPER-DUPER-USEFUL on the Song Page:

    The ability to clear a single pattern or selected patterns on the Song Page.
    The ability to load a pattern or pattern(s) to a selected open spot on the Song Page.
    The ability to copy and paste a pattern or selected on the Song Page

    If I had those buttons, the issues I'm having would take 10% of the time to deal with.

    Another thing that would be great would be to make it harder to over-write patterns.

    DPP asks you if you're SURE you want to clear a pattern.
    But it doesn't ask you if you're SURE you want to load a pattern into a spot where a pattern already exists.
    Seeing how those spots are on a different page from where you're loading patterns, all users will do this dozens of times. (Unless they dumb like me, where they will do it several times a day)

    And if you over-write a pattern that is already in your song--then you change the song.

    That's when you are surprised to discover that your basic pattern has mysteriously transformed into a continuous tom solo .

    Of course, that's if you're really lucky and you only change one pattern.

    An "Are You Sure" question before you save anything that's not on a blank numbered spot would be very helpful.

  • edited March 2016

    @Reid said:
    @Gratouilli Or the Logic way where you establish in Settings what you want it to do when you load it up.

    You're right... To be clearer, I'd like iOS music apps to behave (at opening) like Photoshop or Indesign or Illustrator... etc. on my Mac. When I launch them, I can create something REALLY new or open a project in the exact same state I've saved it.
    Perhaps that's asking too much on iOS ?
    For exemple, one other app I really like but drives me crazy in it's way to manage presets it's Elastic Drums... Why the hell the dev doesn't allow us to erase all the supplied default presets which I just don't need/care about (and there's a BUNCH !) ?

  • @Reid said:
    @Gilbert Some features that would be MEGA-SUPER-DUPER-USEFUL on the Song Page:

    The ability to clear a single pattern or selected patterns on the Song Page.
    The ability to load a pattern or pattern(s) to a selected open spot on the Song Page.
    The ability to copy and paste a pattern or selected on the Song Page

    If I had those buttons, the issues I'm having would take 10% of the time to deal with.

    Another thing that would be great would be to make it harder to over-write patterns.

    DPP asks you if you're SURE you want to clear a pattern.
    But it doesn't ask you if you're SURE you want to load a pattern into a spot where a pattern already exists.
    Seeing how those spots are on a different page from where you're loading patterns, all users will do this dozens of times. (Unless they dumb like me, where they will do it several times a day)

    And if you over-write a pattern that is already in your song--then you change the song.

    That's when you are surprised to discover that your basic pattern has mysteriously transformed into a continuous tom solo .

    Of course, that's if you're really lucky and you only change one pattern.

    An "Are You Sure" question before you save anything that's not on a blank numbered spot would be very helpful.

    Good points Reid, I am sure Marinus will do something about it. It will be beneficial to all of us.

  • edited March 2016

    @JohnnyGoodyear said:

    @Reid said:

    @Gilbert

    Usually, before building a song it is recommended to know which patterns are required and have them ready in the library. ( intro, verse, fills, bridge and ending for a standard structure. )

    Yeah... well that might work fine for some people, but not for me. I don't know what I"m going to do before I'm doing it. And I create a workspace on the song page so I can assemble my song.

    And when I set that workspace up--I want it to stay there.

    As a blundering n00b I appreciate your dedication Mister Reid and also your desire to explain and help Mister Gilbert. However, from the very long and useful posts I must tell you(Mister Gilbert) that as soon as I saw this response from Mister Reid I said aloud 'Exactly!'.

    Hi Mister Johnny,
    appreciate your comments on this forum, but not sure I got the full meaning of this one. ( I am new here and need to be used to each form of expression, and English is not my native language... ). You meant "response FROM Mister Reid", and not "TO Mister Reid"? So you would prefer to build songs, assembling patterns in a more experimental workflow, like Mr Reid do ?

  • @Reid said:

    Gilbert, people don't finish their songs in one go, and in particular, songs that offer the complexity of DPP. When I hit the save button on any app of any kind--music, graphic, whatever--I expect it to look exactly the same when I reload it. And it took me a ton of experimentation to figure out why and how it was changing.

    I can feel the passion! Of not giving up despite the many challenges.
    Yes, that's right, a song is generally not finished in one go. Though it may happen the day we will master DPP.... Things will certainly be simplified and made safer in next updates.

    You know what I do now? I make a frame grab. And I go into my photo library to find out how to reload my patterns. To me that's a lot to ask.

    That's a creative idea! Perhaps some kind of snapshot feature could be added to DPP, to refresh our ( human ) memory when in need.

  • edited March 2016

    @Gilbert said:
    Hi Mister Johnny,
    appreciate your comments on this forum, but not sure I got the full meaning of this one. ( I am new here and need to be used to each form of expression, and English is not my native language... ). You meant "response FROM Mister Reid", and not "TO Mister Reid"? So you would prefer to build songs, assembling patterns in a more experimental workflow, like Mr Reid do ?

    Forgive me if I was unclear. I very much agree with Mister @Reid. I never know what music I am going to make or how I am going to make it. I may have an emotion. I often have words (even if they are confusing!), but the music, the rhythm, the atmosphere as it develops, shows me the way.

  • @JohnnyGoodyear said:

    Forgive me if I was unclear. I very much agree with Mister @Reid. I never know what music I am going to make or how I am going to make it. I may have an emotion. I often have words (even if they are confusing!), but the music, the rhythm, the atmosphere as it develops, shows me the way.

    Thanks, got it!

  • Any plans to make more Rock oriented drum patterns sort of what Rock Drum Machine puts out? I like RDM but I have to record it as audio, where as DP is midi. Thanks!

  • @Gilbert Question about the export page. When I select "Render Song" I am able to render separate files of the entire song without issues.

    But when I deselect "Render Song" andthen put in, for example, 16 measures, it just gives me 16 measures of the pattern that happens to be currently selected in the pattern bank. Any suggestions? v

  • @Gilbert Am I correct in that the position of the probability and Time Shift sliders an't be saved in patterns? That it just stays in that place for a song?

    If that's the case, I guess that's the reason why the Link feature is necessary. Otherwise you could just select a probability of 1 and you would know that pattern A would always play the same.

    The A/B JAM, 2-Hand, Humanize, and Swing settings do save in patterns.

    I am planning a video so I want to know what I'm talking about.

  • please videos

    @Reid said:

    @Gilbert Am I correct in that the position of the probability and Time Shift sliders an't be saved in patterns? That it just stays in that place for a song?

    If that's the case, I guess that's the reason why the Link feature is necessary. Otherwise you could just select a probability of 1 and you would know that pattern A would always play the same.

    The A/B JAM, 2-Hand, Humanize, and Swing settings do save in patterns.

    I am planning a video so I want to know what I'm talking about.

  • @Tones4Christ said:
    Any plans to make more Rock oriented drum patterns sort of what Rock Drum Machine puts out? I like RDM but I have to record it as audio, where as DP is midi. Thanks!

    Would buy these too.

  • Is there a way to batch load a bunch or folder of GM mid drum files into DPP? Currently I can only load one at a time, but would love to load my whole set from audioshare. I love the fact that they are working perfectly now in DPP. I'm using some Groovemonkey midi drum loops that were offered for free which sound really great!

    Any idea if it is possible? I'm trying to load by using iFunbox, but i guess now in IOS 9.3.1 it isnt possible is it?

  • edited April 2016

    Well, was finally able to add all my Groove Monkee free Midi files into DPP via Copy Trans beta as ifunbox doesn't work. Only thing is that I can only add them via the song instead of patterns or midi files. But if I add them via the song I can only add a midi file pattern at a time. Bummer but what I really loved about DPP is that you can select Audition in the screen and you can select each midi file and it will auto playback allowing you to hear if its a beat or style you wanna use in your song. I was really pleasantly surprised to be able to do that. IOS 9.3.1

    Is there a way to turn my midi drum loops into DPP patterns? Like a batch convert so I don't have to do them one at a time?

  • This is the most amazing realistic sounding drum app...im so glad I bought it! Will be leaving great review on the store.

    Question:
    Are there any plans to add Audiobus remote features to DPP? With Remote would love to trigger other patterns in DPP like in patterning. Thanks!

  • Not a tip or feature request, but a pack request: I love the sound of brushes and would really love a kit that offered mostly many lovely brush sounds. Twin Peaks style jazziness. It's the one drum thing I still look for on iOS. Existing kits/packs I know of feature only 2-3 different brush strokes/hits and then lots of other drum sounds. Possibly a minority interest, but I'd love a kit with just brushes. It would be easy to then do the other drum sounds on other tracks.

  • I really hope we can get updated on DPP, unless Apple bought them up already.

Sign In or Register to comment.