I just released an update that adds MIDI output. To use it, just enable MIDI out on either of the two built-in Drumagog instances.

Rim

Just checked the update: thanks for providing it so fast!

As far as I see, that's midi output only for kick and snare. The rest of the drums has no midi out?

Second, what would be most useful to me, is not routing to a midi out as trigger, but saving the audio stems as midi files for midi editing. My main purpose for ReBeat would be transcribing drum parts and grooves to midi, fur further use in my DAW.

Yes, it didn't make a lot of sense to have drumagog on stems like toms or cymbals as those contain multiple instruments like high toms, low toms, although I might make that configurable in case someone wants to use it that way anyway. It just won't know the difference between any of the toms or cymbals.

I can pretty easily add a midi file output to the standalone version if you think that would be useful?

Rim

Two export options would be useful:
- export all drum tracks/stems to one midi drum file (on midi channel 10)
- export separated drums as one whole wav file (besides single stems)

I understand that it can't handle Toms of different pitch, or different hihat status. But at least that would give the user either a raw basic midi for editing, or a well separated drum track wav file (separated from the melodic and harmonic content of the song), to try the midi conversion in tools like Rip-X or Melodyne.

All great ideas. I'll see how I can add these to a future update.

The standalone version of ReBeat already can export all the stems mixed as one WAV file. Just check the box in the settings.

Rim

Tried the latter standalone export option and got the whole song instead of the drums from the song, if I remember right. It should export all stems minus the "othter" stem.

The option "return to zero" is not explained in the manual.

I will check again, but perhaps there's a bug?

P.S. Just checked again: mixdown in settings exports the whole song, which makes no sense, since it was the input source.

I bought it today.

In Cubase Pro 14 I had one track with a complete drum set, separated in SpectraLayers.
I ran this track through ReBeat and then duplicated the track and got 7 identical Cubase tracks altogether.
The idea was to solo each of the internal ’tracks’ inside ReBeat as a workaround for not having 7 outputs from ReBeat.

But the plugin is very unstable; often when clicking the ’S’ (for solo) it made Cubase crash brutally. It also happened when I activated the gate.
I had to save after each moment to be able to go on from that last point.

Doesn’t ReBeat like it when there are multiple instances in the DAW?
This didn’t happen with the tryout version as a single instance, I could gladly click any button whithout any crash at all.

This was not the MIDI capable version.

Mac Studio Max M1 64 GB, Sonoma.

@ jimknopf
The mixdown option in the settings is designed to output an audio file of the entire mix including any volume knobs, mutes, solos, effects that you might have enabled. Some users might want to mix a little bit of the "Other" track into the mix for example. So if you want just the drums, mute the Other stem before exporting. I will make that more clear in the manual.

Return to zero just returns the playhead back to zero every time you press play.

@ Marshall K
I fixed some critical crashing issues in 1.0.9 (the version with MIDI). I suggest you download that version to see if it fixes the issues you were seeing in Cubase. I haven't testing with seven instances, but I don't think this should be a problem unless it's running out of memory when doing the processing. I'll test and let you know what I find.

Rim

A couple of questions:

When you separate the stems out, then re-sum, do you get a perfect copy of the original full drum stem? (like you do when you separate using SpectraLayers for example). This is important when using it for mastering.

If you have a 4 minute drum track, do you need to play it through for 4 minutes in real time in order to analyze? If so, wouldn't another option be to let one drag / drop a WAV onto the plugin, and analyze in faster than real time? (i think DSEQ3 does this)

Yes, ReBeat recreates the original mix if you leave all the stems unmuted including the "other" stem.

The standalone version lets you import audio files instead of having to play them in.

Rim

Yes, I've tried a lot now with 1.0.9 and have not managed to provoke any crash.
Seems the initial problems got sorted out.

I must say this is a marvelous tool to have at hand when doing remastering/remixing. It's very easy to get remarkable results.

I wonder 2 things:

1) Does the Drumagog module in ReBeat introduce any latency (the real Drumagog gives me 80 ms of latency, which is no problem to compensate for when I know it)? I can't notice any latency with ReBeat.

2) Dare one ask for MIDI possibilities for the hi-hat as well? With that great tracking from Drumagog?

When using Drumagog inside ReBeat, there is latency but it is automatically compensated by the DAW.

I'm considering adding an additional Drumagog instance on the HH stem and enabling auto HH tracking. This might make it into a future update.

Rim

Does not work here in Reaper.
I record the clip, it says processing, and it stuck at 0%. Pressing cancel will do nothing.
Then it crashes the daw if i let it for a while.

Edit:
Standalone does the processing.
It badly needs a loop button though, and drag and drop should also work.

Loop functionality for the standalone version is a great idea. I'll add it.

Are you using 1.0.9, the latest version? I fixed some crashing issues in that version.

Rim

It says 1.0.8, but i have just downloaded it (Trial) an hour ago.

Crashing is the smaller problem, not processing is the bigger one :D

So far i had some good results!

The crashing and the processing might be related, and these should be fixed in 1.0.9.

Rim

Downloaded again, and installing.

One other note:
When exporting from the standalone, it should add the imported filename to the filenames. "XY_snare.wav" (Or ask for a prefix.)

Just now I have accidentally overwritten all the stems of my previous export.

EDIT:
Downloaded and installed again, and it's still 1.0.8.
Windows, Trial

I sent you a PM asking about which download link you used.

Good idea about appending the input filename. Added to the list for the next update. I appreciate the suggestions.

Rim

Thanks, I had the old download links on the trial page. It's all fixed now and should have the latest version.

Rim

Ok now im on 1.0.9.
In Win10, Reaper, still it gets stuck at 0% when it starts processing. Can't click on cancel, and if i remove the plugin it crashes Reaper.

sent you a PM to diagnose.

I wanted to download the new trial version (Win) but it doesn't work. I'd appreciate it if you could check.

The issue that @ highvoltage had was that his Reaper was installed on a drive other than C: I'm working on fixing that.

@ muratengin , what kind of issue are you having?

Rim

Everything's fine now, false alarm

Will dig into this more tomorrow but I'm impressed so far! Couple questions/comments

Sample Rate handling - I saw the previous post that they got 48k files out after loading in 44.1k, I had the opposite happen with the Stand Alone. Loaded a 48k file and got back 44.1k, is it possible to stay at the native sample rate?

Pro Tools - I tried offline committing the track while in Playback mode to see if it would load into the plugin and got a crash (2024.10 on OSX 13.7)
PT AudioSuite - Preview and Render didn't seem to do anything, will try again tomorrow to see if it was just initial operator error

Request - only export checked/solo-ed stems
Enable loading Mono Files in AAX (my main usage for this would be bleed removal from tracks I get to mix so throwing the individual tracks in would save me a step of converting them to stereo. It did a great job on the snare track I loaded in but took ages to process, wonder if a solo/isolate option for a specific drum might be faster in situations like that.

Thanks!

Agree about only exporting checked stems. And all this with 48k vs 44k is cool , I will go to recheck.

The standalone version automatically sample rate converts the stem WAV files to match the sample rate your audio interface is set to. You can change this sample rate by clicking on the options button at the top of the plugin wrapper window.

Thanks for letting me know about offline commit and audio suite. I'll look into that.

When you insert ReBeat into a plugin slot, if you choose the mono version it will process stems in mono.

In terms of processing time, ReBeat's model was trained on all the drums at once, so it's actually processing them all at the same time. There's no way to save time with just one stem.

Just for some context, running ReBeat on a Mac M-series computer is about 12x faster than running on a PC (even a very fast one) or an Intel Mac. It has to do with the built in GPU which ReBeat takes advantage of.

Rim

How would that work?
Stem separation to 7 different midi tracks, and then what, a separate drumplug on each track?
Doesn't seem very practical to me.
Unless you bus'em..or send everything to the same track..

Studio One (and others I'm sure) can separate midi drum tracks by pitch already.

I added MIDI output to the latest version. It's available on the kick and snare tracks (inside Drumagog). This outputs real time MIDI which you can route to a MIDI track or a virtual instrument in your DAW. It's not really feasible to add MIDI output for every stem in ReBeat because Drumagog can't tell the difference between different drums (for example floor tom and high tom or china crash and splash).

Rim

Great thanks for both those answers! Was going to give it a shot on my M1 laptop this morning to see if that was the case (on a 2019 Mac Pro).

Good to know about the sample rate setting, was looking under the cog in the lower right.

Also seconding matching the imported file name and adding a suffix.