DK+: Collect Items for Feature Poll

[liqih]

One idea for a next feature in DK+ 2.0

what you think of an "Extract hits from loops" tools, it would work this way:

you drag&drop a drum loop, or even not a loop, let's say and audio file of percussions, it could be wav, mp3 or ogg,
so you drag&drop it on DK+ GUI, and smartly the first 24 usable hits (single shot samples) would be extracted and mapped to the DK+ pads,

thus creating a new kit on the fly, with 24 single shot samples extracted from the source file,

nice?

[midiboss]

One idea for a next feature in DK+ 2.0

what you think of an "Extract hits from loops" tools, ......

This would be a really nice feature that would fit many's work flow!
To do this also with REX would be really handy.

[midiboss]

Hi all,
I see what you mean but I think we have a different use of DK+, to me the DK+ sequencer is nothing more than ah handy tool inside the plugin to quickly layout drum patterns and NOT a way (even though possible) to compose a whole song.

Me also don't use DK+ sequencer extensively, but for a lot of guys I know this is a must. They prepare a pallet of grooves, that they trigger via midi note (recorded or even live!!). The thing is that by changing/improving the grooves in DK+ sequencer automatically applies to the whole triggered song (if it triggers that specific loop, of course). Kind of linked loop, that Reaper, for example, doesn't have, yet.
I don't know if this is already a possible (I'm not at home to try), but triggering more than 1 loop at the time would be great.
Going this path, would take a lot of efforts from Luigi (major rework of the sequencer segment), but would expand potential user base.
But DK+'s basic functionality as a drum sampler should not suffer because of this. You know what I mean

[tomg]

Hi all, I see what you mean but I think we have a different use of DK+, to me the DK+ sequencer is nothing more than ah handy tool inside the plugin to quickly layout drum patterns and NOT a way (even though possible) to compose a whole song.

[AKJ]

I kkep on tying:

don't forget:
one should be able to define probability per step in the step sequencer (for randomisation)

cheers, ajk

[liqih]

I kkep on tying:

don't forget:
one should be able to define probability per step in the step sequencer (for randomisation)

cheers, ajk

Actually I need that too, but I don't like a setting per step, too much time consuming, moreover pure randomization
doesn't give good results IMHO, as far as my experience goes with Cubase.

[AKJ]

Hi,

thanks for anwering. But if one can set a probabilty per step this means that the user has a lot of control on the randomisation. For example you create a pattern and want that some additional acceents occur from time to time, then you can set the probabilit per step for each of these accents to, say, 50 or 30% (while the rest has probability 100% which means: always played), and thus create a randomisation which will give very good results.

With the power of modern cpus I do not think that it will be too much time consuming.

cheers, akj

[liqih]

as time consuming, I mean user programming time, sorry for the confusion,
what I would like is something which doesn't require to program per step and could give about the same results

[AKJ]

Hi,

implement it like this: default: probability 100% (equals play always)

thus, randomisation just takes place if the users wants and takes the time to set it.

akj