1

[Mario Krušelj]

Yes, I’m tired of deleting the folder all the time, the app should not create it in the first place if there were no downloads whatsoever. Also when “cleaning up”, it should clean up completely, removing the download folder as well. Simples.

[Mario Krušelj]

Nobody?

[Mario Krušelj]

Stopping from development doesn’t mean suddenly ARA support in it stops working though. It’s sad to see Gibson killing yet another DAW, even if I don’t use it (I did use Sonar 7 many moons ago).

However, Reaper will be getting ARA support, it has been hinted by the devs, very soon from what it looks like. (And I’m a Reaper user, ehehe.)

So yes, definitely do try and invest some time in doing this, if at all possible! 🙂

[Mario Krušelj]

Just one of default SD3 presets, but it doesn’t matter which library is loaded.

[Mario Krušelj]

OK in 3.0.2 this seems sorta fixed… Except there aer now TWO “Open 1” hits, and there’s one entry less in Hi-Hat CC Edit pane. Is this really intentional?

It’s weird how movable dots between openness levels don’t match with where the text is… But if that’s intended, alright. 🙂

[Mario Krušelj]

Macro controls sounds like just the thing.

[Mario Krušelj]

Just starting the count from 1 instead of 0 seems best and easiest, really 🙂

[Mario Krušelj]

Sure, but that doesn’t answer the question. Notice this visual mismatch:

I have confirmed that they sound the same when used via hatsTipTrig and getting the CC at the same level. So 0 is really the same hit as 1. They are just numbered starting from the wrong number in the MIDI Mapping Keys and MIDI Mapping pane, whereas the Hi-Hat CC Edit pane has it shown correctly, in human readable form, starting from 1. 🙂

[Mario Krušelj]

They’re likely showing percentage rather than actual velocity value. There’s probably/hopefully an option to change that, but I dunno. It’s a bad design, for sure.

[Mario Krušelj]

You can save a full preset and then choose to only load the mixer part.  

That is too slow, unfortunately (especially when I don’t want to have that extra info saved, but JUST a part of it). Having separate mixer presets (and articulation MIDI mapping presets, as well) would be EXTREMELY welcome. SD2 did it right there.

[Mario Krušelj]

Great. It’s good that you have thought of it, so I am pretty hopeful that we will see it in one of many, many updates to come! 🙂

[Mario Krušelj]

@Henrik, I think what ahrayeph wants is to be able to completely clear the mapping of ALL hits for the currently loaded kit. So, not in MIDI in/E-drums section, but in the “MIDI Mapping Key” area to the very right of SD3 GUI.

I agree that this would be useful. It would also be useful if we could directly delete a mapping there, instead of only being able to drag&drop around swapping the mapping keys. Sometehing like Alt+click on a key to remove mapping from the clicked key? Shift/Ctrl+click on keys for a regular contiguous/non-contiguous multiple selection of keys, then Alt+click on deleting all that are selected? Definitely a workflow enhancer!

Some kitpieces have more than 15 aliases on the keyboard, often (I’m looking at you, ride bow hit!). Removing them one by one by first selecting a kitpiece, then expanding the hit type in MIDI Mapping panel, then right-clicking and removing each one is a long and arduous process. It’s also RSI inducing, which is not nice! 🙂

[Mario Krušelj]

Thanks for the reply (again!), Henrik! 🙂

I can understand if there are technical hurdles to supporting EZX presets in Superior. I thought it wouldn’t be a hard thing to do, since I assumed they’re basically running the same engine in the back-end, with the same (if not extremely similar) preset format. Sucks to not be right sometimes! 🙂

[Mario Krušelj]

OK, thanks!

Scratch those last two strikes 🙂

Also… I am sorry for posting in the wrong subforum!

[Author]

Replies