Grid editor gets stuck

[Kari Smolander]

I am using Superior 3 in Windows 10 with Studio One professional. Grid editor is really great, but recently I have had major problems with it. I am editing midi from edrums and I need to clean and move events, for example from one cymbal to another. There is a lot of work in the edits and grid editor is really suitable for the task. Unfortunately it slows down during the sessions and ultimately gets totally stuck at some point. Especially moving events from a drum to another can take a long time, even minutes and finally S3 halts totally. Then I have to kill the process in Windows.

Is there anything I can do to prevent this? I need to complete the task and now it seems quite difficult.
EDIT: I have plenty of memory and processing power – so that is not the reason. Also, MIDI should not really take memory.

Topic

[Kari Smolander]

It seems that the Superior 3 project gets somehow corrupted or the data structure becomes too complex and inefficient. The performance problem stays even if I save the Superior project and open it in a new song. Importing the S3 song takes several minutes and the song is a quite normal 4 minute pop song with three toms, three cymbals and most hits are in 1/8 positions. The only complex thing is the hi hat CC4 controller, which does not have too many events either. This performance problem makes now using S3 impossible, because all event changes take several minutes. The project has one TH3 plugin, one Fat Channel and one Room Reverb. It is in its initial phase with only three recorded tracks and the drum midi. It takes only about 10% of processor capacity.

[Kari Smolander]

When I load the saved Superior 3 project to a new song, the problem persists. Each event move takes minutes. This means that the corrupted or inefficient data structure is stored in the project file and not optimized when opened to the new song.

[Kari Smolander]

The problem could be related to CC4. Somehow the grid editor cannot optimize them but causes some kind of exponential growth of interrupts. When I open the CC4 view instead of velocity in grid editor, Superior gets stuck.
EDIT: Superior version 3.1.1

[Kari Smolander]

I deleted all CC4 events from the song. I selected all, which took about 5 minutes processing time and then pressed delete. After about 30 minutes they were deleted.
It did not help. An event move in grid editor still takes minutes.

[Kari Smolander]

Yet another observation. When I open the same drum project with Superior standalone, it also takes forever to load.
The original MIDI was 67 KB, the MIDI exported from Superior was 785 KB and the Superior project file size is 11034 KB.
Something in Superior add complexity to the MIDI. I have mostly only removed shadow hits caused by the edrum and moved hits between cymbals. And of course some slight quantization.

[Kari Smolander]

I think I found the reason for the problem – or at least an important symptom. I inspected the midi file that I exported from Superior. The Grid Editor had inserted a huge number of CC4 events in one position, in measure 20:01:000. They were not in the original MIDI from the edrum. I do not know why and how this happens, but this should be corrected. There is a block border in 20:01:000, so this may be related to a bug in block processing.

[Kari Smolander]

I deleted all generated CC4 events and now everything works fine again. My summary is that there is a bug in Superior 3 that appears with controllers in block borders. In certain situations Superior may generate huge numbers of controller events. I may be wrong, because I do not know the internals of Superior 3, but that is my interpretation of the problem and how I solved it.

[Henrik Ekblom]

Can you upload a Superior Drummer 3 saved project file, that has these problems, so the coders can have a look at its behaviour? We haven’t gotten this bug report before, so it would be helpful!

Henrik Ekblom - User Experience Designer
Toontrack

[Patrik Wall]

What version of Superior Drummer 3 are you running?
I know we have had a bug previously where moving MIDI events (specifically CC/AT) would create duplicates in some situations, leading to a massive increase in the number of events, eventually leading to slow downs like the ones you describe here.

Bass player in swedish thrash metal band Defiatory
www.defiatory.se

Coder at Toontrack
www.toontrack.com

[Kari Smolander]

@Henrik said:
Can you upload a Superior Drummer 3 saved project file, that has these problems, so the coders can have a look at its behaviour? We haven’t gotten this bug report before, so it would be helpful!  

sd3p files are not allowed. I changed the extension to jpg. Please download and change back to sd3p. Opening it in Superior will take about 15 minutes or so.
Sorry – Upload file size exceeds maximum allowed size
Here it is: https://www.dropbox.com/s/lhhzk5q64xwtvw3/x13s3-3.sd3p?dl=0

@Patrik said:
What version of Superior Drummer 3 are you running?
I know we have had a bug previously where moving MIDI events (specifically CC/AT) would create duplicates in some situations, leading to a massive increase in the number of events, eventually leading to slow downs like the ones you describe here.  

Superior version 3.1.1. This must be the same bug.

[Mike]

The Grid editor seams to be extrem buggy. When i try to move notes it looks good (the graphic) but not sound comes from the note.
Then when i select on another part in the SD3 timeline and after that i go back to the part i previous had selected the note is gone.
Very frustrating and time consuming.
Fix the bugs pls…

Edit. I have the latest version v3.1.1

[Gary Stone]

I am having this exact issue. I’m on a 2013 Mac Pro running Sierra. This happens in Standalone and Pro Tools 2018.4. Superior Drummer v3.1.1.

[Gary Stone]

@Henrik said:
Can you upload a Superior Drummer 3 saved project file, that has these problems, so the coders can have a look at its behaviour? We haven’t gotten this bug report before, so it would be helpful!  

Where do I send the corrupt file? I need this fixed ASAP, I’m at the end of a huge project and I can’t afford to lose or not be able to use this data. Thank you.

[John]

You can ZIP archive the Project and attach that ZIP to a post here. Please do not forget to click the ‘Start Upload’ button.

BR,
John

John Rammelt - Toontrack
Technical Advisor

[Henrik Ekblom]

* removed duplicate answer *

Henrik Ekblom - User Experience Designer
Toontrack

[Author]

Replies