Get Good Midi Groove (GGD Drums) issue

[mgmessner]

So I’ve contacted GGD and they haven’t got back to me so I thought I’d good this route. I purchased a midi pack from them and all the grooves show up in SD3 as 2000 Bars length so obviously this creates tons of blank space which is tedious to delete and resave as a new groove. Anyone have a fix or at least having this issue too?

Superior Drummer 3 version: 3.1.7
Operating system: Windows 10

Topic

[John]

Hi,

I downloaded their MIDI Taster Pack and the grooves show as correct length of Bars. It’s most likely something in the specific pack. If it isn’t you will have to ask their permission to send us files to look at, if there is something that could be done in the Toontrack end.

BR,
John

John Rammelt - Toontrack
Technical Advisor

[Perrygoround]

I have the same problem. Has the issue been found?

Superior Drummer 3 version: 3.2.3
Operating system: Windows 10

[Mark King]

Not sure why you would expect these to work in SD3 or why toontrack would do anything about it when there are plenty of issues related to SD3 that need addressing. It’s not really toontracks problem to make midi packs from other companies work.

SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors

• This post was modified 4 years, 6 months ago by Mark King.

[Perrygoround]

Thanks for your very valuable help sorting out something some people have found when trying to use SD3.

At least the technical advisor from Toontrack though it was worth his time to find out what was going on when the OP started the thread.

[Halen]

Not sure why you would expect these to work in SD3

Probably because the program has an explicit feature to import third party midi grooves/midi loops?

2

Thanked by: Brooks H and Perrygoround

[Brooks H]

I have this issue with drum midi from other developers as well; Loop Loft, Addictive Drums 2, BFD, Logic… SD3 must have an issue interpreting something in the files.

I’ve only seen up to 600+ bars. 2,000 must be a record.

I’ve taken the time to fix some that I really want to use. But I think some of the grooves are changed a bit when dragging them to the sequencer. SD3 maps everything to their default once dragged, so putting them back in a folder with another mapping assignment seems to cause slight differences.

These 2 things are some of the few gripes I have; not counting bars of 3rd party midi correctly, and MIDI in & out maps being independent. Toontrack, please address these things. I get that the midi in/out independence is intentional, but give us an option to link them.

SD3 v3.3.6, EZbass v1.1.7, EZkeys v1.3.4
Studio One v5.5.2, Cubase v12.0.60
3.6GHz Intel i9 iMac, 64GB RAM, OS 12.6.1

1

Thanked by: Perrygoround

[tahoebrian5]

Same problem here

[Dominik Wolff]

There is a solution to the excess bars problem, but it’s not free and it takes some time.

I bought the Fluid Fusion pack from GGD and encountered the same problem: Every single file would cause SD3 to show 2482 (!) bars so it was simply unusable in the song track.

GGD support told me, those packs were designed for the GGD environment exclusively (which is bulls***t in my opinion) but recommended to convert them via https://www.midiremap.com/ which turned out to be quite helpful.

I created a ZIP file with all  225 files and ran a batch convert using the provided presets for GGD and SD3. They ask for some money, but not very much (1,18 € for a customer from Germany). I re-imported those converted files into my user library and the bar issue was fixed. The whole process took me about half an hour.

Nevertheless, from now on I will be very careful choosing the source of my MIDI files, obviously GGD does not give a f*** on compatibility.

Superior Drummer 3 version: 3.2.4
Operating system: macOS Big Sur (11)

1

Thanked by: kevin jesensky

[kevin jesensky]

this was a great idea.

a few tips for anyone else as i messed it up a few times

-make sure you extract all files and then make one zipped folder to convert. I mistakenly downloaded 6 ggd groove packs and put all the zipped folders into 1 zipped folder and the process did not work. I then extracted all 6 folders into 1 folder,then zipped that one and it worked.

– after you convert, open up the folders, sort by date modified then delete the originals leaving only the converted ones ( they will have -midi-remap-com on the end of the file names) if you don’t do this and just link the new folder as is sd3 will show both the fixed one and the ~5000 bar ones side by side.

– the program was $1.06 for me to run a zipped batch.

[Mohan Klein]

Hello there!

I am the developer of MidiRemap. I just took a deep look into this: The GGD groove files use MIDI “Format Type 1” whereas the Toontrack grooves use “Format Type 0”.
Both are absolutely fine for MIDI drums and none of them is right or wrong. I see that type 0 is more preferable for MIDI drums but type 1 is not wrong and therefore I am happy to support @Toontrack investing and maybe fixing this on their side as the GGD files are fine just different than Toontrack’s? Happy to help with this further just write to us at MidiRemap.com!

Attached the file structure which causes the “million bars” problem inside the Toontrack groove players.

Love from Germany
Mohan

Superior Drummer 3 version: 3.3.5
Operating system: macOS Ventura (13)

• This post was modified 1 year, 4 months ago by Mohan Klein.

[Mohan Klein]

[Mohan Klein]

UPDATE: It seems my first explanation was wrong: The GGD Grooves contain a long End of Track MIDI Event in the first MIDI Meta Track (MIDI Format 1 allows multiple tracks) which seems to confuse the Toontrack Groove Players to extend the end/bar length. When dragging the file directly to any DAW they seem to ignore this information and determine the correct MIDI event end after the last real note or similar information. Maybe something to consider adjusting @Toontrack.

Love from Germany
Mohan

[Mohan Klein]

Ah right most important: We added an updated solution for this specific problem at MidiRemap so this should now (again) fix this issue when converting GGD Grooves to Toontrack via MidiRemap!

Cheers!

1

Thanked by: John

[Author]

Replies