94

[Henrik Ekblom]

This thread: http://duc.avid.com/showthread.php?t=269005 – has a discussion regarding a bug in Pro Tools, that disables some instruments when loading a project. Can this be what you are experiencing?

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

We have added this and it will be included in the next update – which is currently being beta tested!

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

You set a tempo in your DAW (Studio One), and when you enable Follow Host in Superior Drummer 3 it will follow that tempo. E.g., you can’t set a tempo in SD3 and make Studio One follow that tempo.

The original tempo of the MIDI files in Grooves is just the tempo that the MIDI files was recorded in. You can still use a MIDI file recorded in 196 in your 120 BPM project – this is one of the strengths of MIDI! However, sometimes a MIDI file that has been recorded in a tempo that’s too far away from your project, the quantisation of the file may make it sound bad. In that case you can always quantise the MIDI in the grid editor, to make it “tighter”. But if the MIDI you hear sound good, the original tempo doesn’t matter!

Does this clarify things for you?

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

We notify our users via e-mail, and you can check the Toontrack product manager regularly. We have a point on our todo list to incorporate a notification within the software itself, to alert when new updates are available. We have lots to do at the moment with bug fixes etc., we’ll see if, and in that case when, we can add it to an update… Thanks for the feedback!

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

What Library, and what tom is it you have the problem with? What Drums and Mixer Preset is loaded?
Does it occur when you just click on the drum in the interface?

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

Are you using a DAW? Most of them has advanced options, such as duplicating values from one CC to another.
In Logic, for example, you can write a script that does this…

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

Can you reproduce the crash? I wonder if there’s anything particular in what you did that causes this crash.
When I load Superior Drummer 3 in Live 10, add a MIDI block and add and edit some notes (in SD3), and then press cmd + z – it doesn’t crash. Cmd + z removes Superior Drummer 3, which is the expected behaviour – it undo:s the latest thing I did in Live 10, which was to add SD3 as a plugin…

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

* removed duplicate answer *

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

The reason for not using the standard keyboard shortcuts is because they can’t be used when Superior Drummer 3 is run in a DAW. Ctrl + x will, for example, always be hijacked by the operative system, so we had to find other keyboard shortcuts. We wanted to have Superior Drummer 3 consistent in its behaviour, so we didn’t change these shortcuts in the standalone version, versus the plugin version. We tried it and figured out that it would lead to more problems and confusions.

One example of this: one of the worst drawbacks of having ctrl + z (or cmd + z on Mac) to undo in the standalone was that users got used to undo things in Superior, using those keys. When the users later ran the Superior in a DAW, they still used those shortcuts, and what ctrl + z did was to undo the last thing done in the DAW, which was to add Superior as a plugin. All this meant that the Superior plugin was removed, and couldn’t be recalled to its previous state – leading to all the work done in Superior was lost…

We can’t unfortunately make a perfekt system here, where we would use the standard keyboard shortcuts that everyone knows about – that’s a drawback when we make plugins that operates in other hosts than our own.

Sorry for the long post, but I wanted to share some insights in how complex all the decisions we make are! Sometimes we have to go with what’s least potentially damaging for the user. However – getting feedback from you, our users, is crucial, so we can make better products – because we know that they still can get better 🙂

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

Instruments can’t share CC nor MIDI notes. The added hi-hat can listen to a different CC, CC1 one for example. Can your e-kit/DAW send multiple CC:s at once (both 1 and 4)?

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

In EZdrummer 2 you have to keep track of what instrument it was to be able to revert to it.
In Superior Drummer 3, you can load only a selected instrument from a preset, e.g. load the snare that the preset started with.

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

@Dale said:
Hi There!
Just begging for an update add.
PLEASE MAKE THE GRID EDITOR “TAB” AVAILABLE ON THE FRONT PAGE. PLEASE ALSO ALLOW IT TO OPEN EMPTY, instead of having to add a midi block to see it.
Keep up the great work!
Thank you.  

Did you know that you can right click on any empty area and select “Add empty MIDI block”? And then you can double click that block to enter the grid editor.
Since that workflow is pretty quick, it hasn’t been prioritised to be able to enter the Grid Editor quicker. Do you have any particular scenario where the current work flow feels cumbersome for you?

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

Thanks for the feedback! I agree that we can make the tab system more usable by making it rearrangeable, and make use of the entire screen estate instead of only seeing 4 tabs at a time. It hasn’t been done simply because we haven’t had the time! I will take a note of this and try to make a better design of it!
Thanks for the feedback

Henrik Ekblom - User Experience Designer
Toontrack

1

Thanked by: LDG

[Henrik Ekblom]

Some questions to start addressing the issue:
– are all the parts of SD3 updated? (It’s easiest to use Product Manager to check that)
– do you have the same glitches when you use SD3 in standalone?
– have your tried increasing the buffer size to decrease the workload of the CPU?
– does it happen to all, or some, Drums and Mixer Presets?

Henrik Ekblom - User Experience Designer
Toontrack

[Henrik Ekblom]

Thanks for the feedback! It’s not possible to control this from a global setting, but it might be a good idea so I’ll take a note of it.

I can describe how the system currently works:
If channels should be hidden or shown is decided by the preset maker. So if you load a Drums and Mixer Preset, the creator of that has decided what channels to hide. If you hide, or show, some channels and save a User Preset, that state will be saved. The same goes when you save a Project, it will will look the same when you open it the next time.

To make you workflow a bit quicker; have you seen that you can right click a channel and select “Hide” (instead of clicking Edit Visibility and doing it that way)? It does also work on multiple selected channels…

Henrik Ekblom - User Experience Designer
Toontrack

[Author]

Replies