DM10 - Drum & Synth Machine by Fingerlab (Released)

EdZAB · March 18

The TestFlight version is looking good for me today. 🙂

Has anyone tried recording MIDI out from DM10 loaded as an instrument in Logic Pro for iPad? I've tried both the current release version 2.0 and the beta version from today, and I'm not able to get it to record MIDI to the track. If I replace DM10 (by using the Replace button in the instrument slot) with another instrument such as Riffler Flow on the same track, it records correctly, which seems to indicate I have the track recording set up correctly. Since there is no MIDI FX version of DM10 available in Logic Pro for iPad (it doesn't show in the list), that's not an option either.

I can create a video of it in action as described above, if needed.

Tentype · March 18

Tested most things on the list with no issues.

A few things i noticed though:

it would be great to have parity between the list of midi mappable controls, and the list of exposed parameters
it would be really handy to have a dedicated midi cc for muting each channel. In the app you can double click a track header to Mute a track, but no way to Mute by midi.
you added a midi parameter for pattern select which is awesome, but currently is a little challenging to use. Right now it spreads out the selection of 45 patterns over 127 values possible on a dial. That means that turning a mapped knob up 2.82 changes to the next pattern. It works, but it makes for a lot of math if i want to create a button that when pressed Will take me to an exact pattern number. it makes me curious if there was a particular reason that you chose 45 patterns as the maximum? if you upped it to 63 patterns for example it would make selecting a particular pattern by midi cc much easier.

Thank you thank you thank you for offering this app, I'm extremely impressed by its great sound, and intuitive simplicity. 🙏🏽💕

relpot · March 19

@Tentype said:
Tested most things on the list with no issues.

A few things i noticed though:

it would be great to have parity between the list of midi mappable controls, and the list of exposed parameters

it would be really handy to have a dedicated midi cc for muting each channel. In the app you can double click a track header to Mute a track, but no way to Mute by midi.

you added a midi parameter for pattern select which is awesome, but currently is a little challenging to use. Right now it spreads out the selection of 45 patterns over 127 values possible on a dial. That means that turning a mapped knob up 2.82 changes to the next pattern. It works, but it makes for a lot of math if i want to create a button that when pressed Will take me to an exact pattern number. it makes me curious if there was a particular reason that you chose 45 patterns as the maximum? if you upped it to 63 patterns for example it would make selecting a particular pattern by midi cc much easier.

Thank you thank you thank you for offering this app, I'm extremely impressed by its great sound, and intuitive simplicity. 🙏🏽💕

Thanks for your feedback, here are my comments:
-About parity between the list of midi mappable controls, and the list of exposed parameters, it's not possible to have the same list because midi mappable controls and exposed parameters does not work the same way. Indeed, with midi mappable controls it's possible to have one-action control, meaning control that not change a parameter but tell the app to do something. For example "song rewind", "previous pattern", "next pattern", ... But it's not possible to do that with exposed parameters as exposed parameters are meant to change parameters values only. This is why the two list are not the same.

-About track mute with midi, yes indeed you are right, it's currently missing, I will add that.

-About the pattern select midi parameter, yes indeed it could be better. I think the simple solution would be to have one CC value per pattern, meaning cc value 1 would be pattern 1, cc value 2 would be pattern 2, and so on from 1 to 45 cc value. After that it will repeat, meaning 46 cc value will be pattern 1, 47 cc value will be pattern 2, and so on... what do you think ?
About the 45 patterns as the maximum, it's an arbitrary choice, there is no particuliar reason. We wanted the users to have enough patterns to make complex songs, but not too much to keep the app intuitive and easily understandable.

Tentype · March 19

@relpot said:

@Tentype said:
Tested most things on the list with no issues.

A few things i noticed though:

it would be great to have parity between the list of midi mappable controls, and the list of exposed parameters

it would be really handy to have a dedicated midi cc for muting each channel. In the app you can double click a track header to Mute a track, but no way to Mute by midi.

you added a midi parameter for pattern select which is awesome, but currently is a little challenging to use. Right now it spreads out the selection of 45 patterns over 127 values possible on a dial. That means that turning a mapped knob up 2.82 changes to the next pattern. It works, but it makes for a lot of math if i want to create a button that when pressed Will take me to an exact pattern number. it makes me curious if there was a particular reason that you chose 45 patterns as the maximum? if you upped it to 63 patterns for example it would make selecting a particular pattern by midi cc much easier.

Thank you thank you thank you for offering this app, I'm extremely impressed by its great sound, and intuitive simplicity. 🙏🏽💕

Thanks for your feedback, here are my comments:
-About parity between the list of midi mappable controls, and the list of exposed parameters, it's not possible to have the same list because midi mappable controls and exposed parameters does not work the same way. Indeed, with midi mappable controls it's possible to have one-action control, meaning control that not change a parameter but tell the app to do something. For example "song rewind", "previous pattern", "next pattern", ... But it's not possible to do that with exposed parameters as exposed parameters are meant to change parameters values only. This is why the two list are not the same.

-About track mute with midi, yes indeed you are right, it's currently missing, I will add that.

-About the pattern select midi parameter, yes indeed it could be better. I think the simple solution would be to have one CC value per pattern, meaning cc value 1 would be pattern 1, cc value 2 would be pattern 2, and so on from 1 to 45 cc value. After that it will repeat, meaning 46 cc value will be pattern 1, 47 cc value will be pattern 2, and so on... what do you think ?
About the 45 patterns as the maximum, it's an arbitrary choice, there is no particuliar reason. We wanted the users to have enough patterns to make complex songs, but not too much to keep the app intuitive and easily understandable.

Thanks for the responses!

Understandable about parity issues because of differences between the 2 control methods
Great news about Mute control
Mapping patterns 1 to 45 to value 1 to 45 on a given cc would be ideal for me because I'm using highly configurable knobs and buttons. One issue i can see though is that someone mapping a standard endless encoder to the pattern select parameter would get to value 127 (which would be pattern 37) and then it would jump to pattern 1 from there. I feel like that's a small price to pay though and i would go for it.

sigma79 · March 20

@Tentype said:
Tested most things on the list with no issues.

A few things i noticed though:

it would be great to have parity between the list of midi mappable controls, and the list of exposed parameters

it would be really handy to have a dedicated midi cc for muting each channel. In the app you can double click a track header to Mute a track, but no way to Mute by midi.

you added a midi parameter for pattern select which is awesome, but currently is a little challenging to use. Right now it spreads out the selection of 45 patterns over 127 values possible on a dial. That means that turning a mapped knob up 2.82 changes to the next pattern. It works, but it makes for a lot of math if i want to create a button that when pressed Will take me to an exact pattern number. it makes me curious if there was a particular reason that you chose 45 patterns as the maximum? if you upped it to 63 patterns for example it would make selecting a particular pattern by midi cc much easier.

Thank you thank you thank you for offering this app, I'm extremely impressed by its great sound, and intuitive simplicity. 🙏🏽💕

Thanks for your feedback, here are my comments:
-About parity between the list of midi mappable controls, and the list of exposed parameters, it's not possible to have the same list because midi mappable controls and exposed parameters does not work the same way. Indeed, with midi mappable controls it's possible to have one-action control, meaning control that not change a parameter but tell the app to do something. For example "song rewind", "previous pattern", "next pattern", ... But it's not possible to do that with exposed parameters as exposed parameters are meant to change parameters values only. This is why the two list are not the same.

-About track mute with midi, yes indeed you are right, it's currently missing, I will add that.

-About the pattern select midi parameter, yes indeed it could be better. I think the simple solution would be to have one CC value per pattern, meaning cc value 1 would be pattern 1, cc value 2 would be pattern 2, and so on from 1 to 45 cc value. After that it will repeat, meaning 46 cc value will be pattern 1, 47 cc value will be pattern 2, and so on... what do you think ?
About the 45 patterns as the maximum, it's an arbitrary choice, there is no particuliar reason. We wanted the users to have enough patterns to make complex songs, but not too much to keep the app intuitive and easily understandable.

I think a left and right curser would be best. A cc message triggers the curser. It would work with Drambo because you switch patterns via midi curser with Drambo. A must syncing patterns across ipads and probably ideal with one ipad, if using drum machines that dont trigger its patterns by a host sequencer note.

You have a pattern structure as your app.

May as well utilise the pattern structure of a host that has a pattern structure and a midi mappable curser of left and right.

You listen to song.

You want to go back a pattern .

All the song needs to sync.

May as well add the loop thing from Drambo, where you loop a pattern or progress.

Drambo does have different sync options though, like instant switch or end of pattern ( after the midi trigger )

How would you actually control song mode, if a drum app goes through patterns with a cc knob. Using any host that dosent work the same way ( a cc knob ) ?

relpot · March 20

@sigma79 said:

@Tentype said:
Tested most things on the list with no issues.

A few things i noticed though:

it would be great to have parity between the list of midi mappable controls, and the list of exposed parameters

it would be really handy to have a dedicated midi cc for muting each channel. In the app you can double click a track header to Mute a track, but no way to Mute by midi.

you added a midi parameter for pattern select which is awesome, but currently is a little challenging to use. Right now it spreads out the selection of 45 patterns over 127 values possible on a dial. That means that turning a mapped knob up 2.82 changes to the next pattern. It works, but it makes for a lot of math if i want to create a button that when pressed Will take me to an exact pattern number. it makes me curious if there was a particular reason that you chose 45 patterns as the maximum? if you upped it to 63 patterns for example it would make selecting a particular pattern by midi cc much easier.

Thank you thank you thank you for offering this app, I'm extremely impressed by its great sound, and intuitive simplicity. 🙏🏽💕

Thanks for your feedback, here are my comments:
-About parity between the list of midi mappable controls, and the list of exposed parameters, it's not possible to have the same list because midi mappable controls and exposed parameters does not work the same way. Indeed, with midi mappable controls it's possible to have one-action control, meaning control that not change a parameter but tell the app to do something. For example "song rewind", "previous pattern", "next pattern", ... But it's not possible to do that with exposed parameters as exposed parameters are meant to change parameters values only. This is why the two list are not the same.

-About track mute with midi, yes indeed you are right, it's currently missing, I will add that.

-About the pattern select midi parameter, yes indeed it could be better. I think the simple solution would be to have one CC value per pattern, meaning cc value 1 would be pattern 1, cc value 2 would be pattern 2, and so on from 1 to 45 cc value. After that it will repeat, meaning 46 cc value will be pattern 1, 47 cc value will be pattern 2, and so on... what do you think ?
About the 45 patterns as the maximum, it's an arbitrary choice, there is no particuliar reason. We wanted the users to have enough patterns to make complex songs, but not too much to keep the app intuitive and easily understandable.

I think a left and right curser would be best. A cc message triggers the curser. It would work with Drambo because you switch patterns via midi curser with Drambo. A must syncing patterns across ipads and probably ideal with one ipad, if using drum machines that dont trigger its patterns by a host sequencer note.

You have a pattern structure as your app.

May as well utilise the pattern structure of a host that has a pattern structure and a midi mappable curser of left and right.

You listen to song.

You want to go back a pattern .

All the song needs to sync.

May as well add the loop thing from Drambo, where you loop a pattern or progress.

Drambo does have different sync options though, like instant switch or end of pattern ( after the midi trigger )

How would you actually control song mode, if a drum app goes through patterns with a cc knob. Using any host that dosent work the same way ( a cc knob ) ?

I'm not sure to understand what is your point and what you mean.
If you want a CC Midi mapping for "Pattern Previous" and "Pattern Next", there are already available in DM10.

sigma79 · March 20

@relpot said:

@sigma79 said:

@Tentype said:
Tested most things on the list with no issues.

A few things i noticed though:

it would be great to have parity between the list of midi mappable controls, and the list of exposed parameters

it would be really handy to have a dedicated midi cc for muting each channel. In the app you can double click a track header to Mute a track, but no way to Mute by midi.

you added a midi parameter for pattern select which is awesome, but currently is a little challenging to use. Right now it spreads out the selection of 45 patterns over 127 values possible on a dial. That means that turning a mapped knob up 2.82 changes to the next pattern. It works, but it makes for a lot of math if i want to create a button that when pressed Will take me to an exact pattern number. it makes me curious if there was a particular reason that you chose 45 patterns as the maximum? if you upped it to 63 patterns for example it would make selecting a particular pattern by midi cc much easier.

Thank you thank you thank you for offering this app, I'm extremely impressed by its great sound, and intuitive simplicity. 🙏🏽💕

Thanks for your feedback, here are my comments:
-About parity between the list of midi mappable controls, and the list of exposed parameters, it's not possible to have the same list because midi mappable controls and exposed parameters does not work the same way. Indeed, with midi mappable controls it's possible to have one-action control, meaning control that not change a parameter but tell the app to do something. For example "song rewind", "previous pattern", "next pattern", ... But it's not possible to do that with exposed parameters as exposed parameters are meant to change parameters values only. This is why the two list are not the same.

-About track mute with midi, yes indeed you are right, it's currently missing, I will add that.

-About the pattern select midi parameter, yes indeed it could be better. I think the simple solution would be to have one CC value per pattern, meaning cc value 1 would be pattern 1, cc value 2 would be pattern 2, and so on from 1 to 45 cc value. After that it will repeat, meaning 46 cc value will be pattern 1, 47 cc value will be pattern 2, and so on... what do you think ?
About the 45 patterns as the maximum, it's an arbitrary choice, there is no particuliar reason. We wanted the users to have enough patterns to make complex songs, but not too much to keep the app intuitive and easily understandable.

I think a left and right curser would be best. A cc message triggers the curser. It would work with Drambo because you switch patterns via midi curser with Drambo. A must syncing patterns across ipads and probably ideal with one ipad, if using drum machines that dont trigger its patterns by a host sequencer note.

You have a pattern structure as your app.

May as well utilise the pattern structure of a host that has a pattern structure and a midi mappable curser of left and right.

You listen to song.

You want to go back a pattern .

All the song needs to sync.

May as well add the loop thing from Drambo, where you loop a pattern or progress.

Drambo does have different sync options though, like instant switch or end of pattern ( after the midi trigger )

How would you actually control song mode, if a drum app goes through patterns with a cc knob. Using any host that dosent work the same way ( a cc knob ) ?

I'm not sure to understand what is your point and what you mean.
If you want a CC Midi mapping for "Pattern Previous" and "Pattern Next", there are already available in DM10.

Thanks.

Thats cool.

Il check out the app before requests lol.

Cambler · March 22

Apologies if this has been covered, but is there a way to do pattern change via midi?

Tentype · March 23

@Cambler said:
Apologies if this has been covered, but is there a way to do pattern change via midi?

Yes. There is the ability to map a midi cc to change to the next pattern, the previous pattern, and also to map a cc to a "pattern select" parameter where every value corresponds to a pattern.
For example you map "pattern select" to channel 1, cc30, and send it value 1 you get pattern 1 etcetera. After value 45 it circles back to pattern 1.

Cambler · March 23

@Tentype said:

@Cambler said:
Apologies if this has been covered, but is there a way to do pattern change via midi?

Yes. There is the ability to map a midi cc to change to the next pattern, the previous pattern, and also to map a cc to a "pattern select" parameter where every value corresponds to a pattern.
For example you map "pattern select" to channel 1, cc30, and send it value 1 you get pattern 1 etcetera. After value 45 it circles back to pattern 1.

Thanks so much for the response @Tentype. I must admit to never really having used cc so I think I have some learning to do. Currently working in Cubasis so I assume I need to use automation. Funnily enough I’m thinking of moving back to Logic as I find Cubasis automation flaky and awkward to work with. Can’t see any values for DM10 when I open automation in Cubasis. I must admit I do like the option to change patterns by midi note for its ease of setup.

sigma79 · March 28

Hello sir.

What are the kit names you added recently.

Thanks.

Overreach · March 28

@sigma79 said:
Hello sir.

What are the kit names you added recently.

Thanks.

Read the Version History https://apps.apple.com/gb/app/dm10-drum-synth-machine/id982224575

sigma79 · March 29

@Overreach said:

@sigma79 said:
Hello sir.

What are the kit names you added recently.

Thanks.

Read the Version History https://apps.apple.com/gb/app/dm10-drum-synth-machine/id982224575

Thanks.

Tentype · April 29

Wow, version 3 is in beta and what a perfectly straightforward and feature rich machine this app is now. 💕

@relpot
I haven't come across any issues so far. Is there a better way to contact you for any issues, or is posting on this public forum fine?

The only other thing I'd love to see in this app is a way to shift each drums pattern left or right.
The randomizers are wonderful and can produce interesting stuff, but sometimes the downbeat of the whole rhythm needs to be shifted. It would be great to have a way to do that without having to rebuild the whole rhythm.

relpot · April 29

@Tentype said:
Wow, version 3 is in beta and what a perfectly straightforward and feature rich machine this app is now. 💕

@relpot
I haven't come across any issues so far. Is there a better way to contact you for any issues, or is posting on this public forum fine?

The only other thing I'd love to see in this app is a way to shift each drums pattern left or right.
The randomizers are wonderful and can produce interesting stuff, but sometimes the downbeat of the whole rhythm needs to be shifted. It would be great to have a way to do that without having to rebuild the whole rhythm.

Thanks for your feedback! You can contact me directly at [email protected] or send me a PM on this forum if you want, but posting on this public forum is also ok too.

About steps shift, yes I can add that, it's technically easy to do but I have to find now a good place to add it in the UI, I will think about it for next update.

boberto · April 29

Another humble repeat request to @relpot -
Not for this release but…

it sure would be nice to do the glitchy 16th/32nd/64ths beyond the current triplets…

UI - put a number on the square instead of trying to visually subdivide (because there ain’t no way someone’s gonna see that )
To access - do a long hold on the “new” triplet button and pick from a pop up sub-menu?

One random’s idea.
Great app as it is though.

garden · April 30

I find myself not using the sequencer so much, but its library of classic machines is great, so I use it a lot these days as module driven by Octachron, for example.

robosardine · April 30

Is it just me or is anyone else not getting decent results with the track randomiser? I think we need an option to only randomise selected instruments. I mean if you want four on the floor pretty consistently it’s gone every time you randomise & that’s a big pain in the hoop.

audiomike · April 30

@robosardine said:
Is it just me or is anyone else not getting decent results with the track randomiser? I think we need an option to only randomise selected instruments. I mean if you want four on the floor pretty consistently it’s gone every time you randomise & that’s a big pain in the hoop.

I’ve had very poor unmusical results with the randomiser.

oceansinspace · May 1

Yeah , the way dm2 had the many subdivisions. That way there is more variety in the ratchet or rap hi hats. We need like 4 diff speed blasts if u know I’m saying. Works well besides that.mcheers.

robosardine · May 1

Yes if you could apply the step randomiser to specific tracks like in the mixer that would be much better.

relpot · May 2

@robosardine said:
Yes if you could apply the step randomiser to specific tracks like in the mixer that would be much better.

Yes indeed, I will add that for the next update!

robosardine · May 2

@relpot said:

@robosardine said:
Yes if you could apply the step randomiser to specific tracks like in the mixer that would be much better.

Yes indeed, I will add that for the next update!

Nice! I think that will make a big difference. I think if you were to work on various randomisation options then this would make the app truly stellar. It really would
As an example - It would also be useful if it was possible to nominate specific steps that remained unaffected by randomising action in the selected track.
There are many options worth exploring along this line - I’m convinced doing this would elevate the app into a leading classic.
What do others think?

Loopy Pro: Create music, your way.

DM10 - Drum & Synth Machine by Fingerlab (Released)

Comments