MTPOWER DrumKit2: included grooves don't follow project tempo

[SteffHell]

Hello,
I just made my first attempts to use MTPOWER DrumKit 2 in Waveform.

Goal:
I wanted to find suitable drum grooves for a given chord track.
For this, I created two tracks, 1 with a chord progression, 2 with the drumkit and was clicking through the drum grooves included in the drumkit.

Problem:
To my surprise the drum grooves were never in sync with the chord progression. They seem to have a fixed tempo and do not automatically adjust to the project tempo.
The only way (that I found) to sync them was to first drag the grooves into the "composer" field in the drumkit.

Questions:
Is this like that? Is there no way to click through the grooves with them in sync?
I was hoping to see an option like "follow project tempo" and/or "automatically start groove at beginning of loop".

[mikoatkvr]

From what I can see it looks like MTPower Drumkit is just free-rolling with it's own internal MIDI clock start sync, it behaves the same way on FL_Studio too. It does however adhere to tempo change in both WF and FL ( Albeit out of sync as you have stated ).

I'm not sure if MTPD can accept some kind of MIDI CC to reset it's internal clock to reset to the start of it's patterns, but I know that Waveform is definetely sending these commands as it works in a few plugins that i have, one that comes to mind is Glitch2, but there are others.

[Watchful]

When dragging the clip from the plugin into your track, Waveform will ask you if you want to keep or ignore the clip's tempo. You want to have Waveform's BPM override. You'll need to do this for every clip you drag in.

[SteffHell]

You'll need to do this for every clip you drag in.

Okay, so it is not possible to browse grooves within the context of the song and with the project's tempo. That groove section seemed like a nice way to do that.

[Watchful]

No, that's a limitation of the plugin. It doesn't read in BPM from the DAW. I suspect each clip is nothing more than a hard-coded MIDI file.

I know what you're describing, though: I have a number of plugins that can play presets and patterns in their browsers, in time with the project as well as in key. It pulls that info in from Waveform, as Milo noted above.

[SteffHell]

I also asked at the producer's website and received helpful information. I was given permission to share and so here it is...


My question:
Hi,
is there a chance to pre-listen the grooves from the groove section and hear them in sync with the tempo of the project?
If I try that and simultaniously play a song and click a groove, they have different tempos.
To hear the groove in sync with the song's tempo I have to first drag it into the project or into the "composer" section.
Is this a given limitation?
Still a great plugin, though, just asking ;.)


Their answer:
Hello.
The plugin does sync its tempo to the current project. So if the project is set to 60 bpm, the plugin will also play in 60 bpm.

But that applies only to the tempo. What the plugin does NOT do is playing the grooves in sync with the DAWs timeline. So while it plays in the same tempo, it does not automatically play in sync. So the beats might sound off, if you don't start the playback manually at the exact right time.

That's because the purpose of the plugins built in grooves player i.e. the composer is to only prelisten / audition the grooves and then dragging them into the DAW to construct the whole song there. But I understand that there are situations where you would want to play your DAW timeline and the plugin in sync. That's why we plan to add this feature in a future version. But that might take a while, since it's going to be a bigger update with many more features.

If you feel that the grooves of the plugin not only aren't playing in sync with the DAWs timeline, but also indeed at different tempos, that would have to be a bug or incompatibility with the DAW you are using.

Edit: Just tried it with Waveform 11 and Waveform 12 on Windows 10 and can confirm that the tempo does sync as stated above.


My reply to their answer:
Ah, now, it is clear.
The tempo is correct but not the starting point of the groove.
Or in other words:
There is no functionality for "automatically start groove at beginning of loop" which is how I have seen it implemented in other paid plugins.


Their answer to my reply to their answer:
Exactly right. And I agree that it would be a very useful feature to have. However, we will probably not put it in MTPDK 2 anymore. This will come with MTPDK 3 for sure.

[Watchful]

Thanks for updating us. In other news, there's an MTPDK3 in our future!

[Kott]

Thanks for updating us. In other news, there's an MTPDK3 in our future!

wow, where can we read about MTPDK3?