[jdmille2]

Thanks for that.  I think that, with all the other users that have chimed in here, the bottom line is that, regardless of the original name, we all want the ability to change that name to be more meaningful to our particular situation.

Can we look forward to having user-editable clip names in a new release soon?

It’s been over two years since I posted this thread originally, and other users continue to +1 this as a feature they want, too.

Reply To: SD3 Blocks: How to rename/change title displayed in SD3 Track? version: 3.2.8
Operating system: macOS Monterey (12)

[jdmille2]

thanks, Billy86, I +1’d it there last night

Reply To: SD3 Blocks: How to rename/change title displayed in SD3 Track? version: 3.2.8
Operating system: macOS Mojave (10.14)

[jdmille2]

Now that I’ve (re)invested this time (I did something similar back with SD2 and then moving to SD3) I think that it *will* be faster next time – which for me means the next kit I make, out of the 8 SDX + SD3 content I have.

Here’s what one has to juggle:

1. Start with an SD3 kit, either a preset, or one you make.  Because of the odd way that SD3 maps additional Instruments (i.e., it reuses already-assigned notes, rather than picking empty ones!!!!) I HIGHLY RECOMMEND adding those additional instruments FIRST, if at all possible.  Of course, later, if you decide you want, say, a cowbell, tambourine, claps, sticks, whatever, because SD3 reuses assigned notes (even tho there are plenty unassigned notes available – grrrr) you may have to revisit the mapping then.  And it’s not like SD3 *tells* you that it’s remapped a note; you have to find it yourself.  Next time, I will try to start with a stock kit and then manually map the new instruments to something that doesn’t collide.  And that’s a PITA because you have to go find the ones that got stomped on and put them back to what they were before.
2. Create or modify a Cubase Drum Map (if you use Cubase, that is).  For me it’s critical to sort the instruments in some logical order, e.g., kick, snare, hat, cymbals, toms, extra, so when I’m editing in Cubase it’s easier to see what’s going on.  I’ve done these maps a few different ways – the one attached maps the entire SDX; I’ll whittle it down later to make it more compact.  I end up with a map with just the instruments I’m using.
3. Create a new preset on the DTX (copying a similar one, if you have one already) and map the instruments and articulations you want in the SD3 kit.  There’s a lot of variation in the SDXs re instruments and articulations, especially.  Rock Warehouse, for example, just has cymbal crashes, whereas Legacy of Rock has a few more articulations.

I would have attached files here, but xlsx files aren’t allowed.  So I put them on Dropbox: https://www.dropbox.com/sh/0y7exa0i7n59f61/AACxzjcKKpLgUqZsGaZigdNOa?dl=0  I used the MIDI map from the SDX kit and weeded out the “aliases” – I don’t need 5 ways to hit the same snare hit; it just clutters things.  Even still, there are a few things that appear in two places or more.  I initially picked one, but sometimes that one turned out to be one that SD3 remapped when adding other instruments.  (Have I said how frustrating that is?  There are 127 notes available, so no need to take a note that’s already mapped.)

Since the SD3 kit definitive, it’s easiest to start there, ala step #1.  I had to create this spreadsheet by hand, and this is why some sort of map export from SD3 would be very very welcome.  From there, I could easily write a Python script to generate the Cubase Drum Map (which is an XML file), as well as having the information I need to create the DTX preset, too.  And please, show *both* MIDI note and note number, as they each get used in different places. (Cubase Drum Maps and DTX both want MIDI note, e.g., C#3)

cheers,

— jdm

Reply To: Q. Save a text file of the complete MIDI map for the current kit? version: 3.2.4
Operating system: macOS Catalina (10.15)

1

Thanked by: Bobby Campbell

[jdmille2]

One thing I forgot to add to the list:

4. Make it possible to edit a Groove (e.g., Grid Editor and Edit Play Style) directly from the GROOVES tab.  Now, just to make a change to a User MIDI block, I have to drag it down to the Track, open it in either editor, and then drag it back to the User MIDI, delete the old one, and rename the new one to the original name.

cheers,

— jdm

Reply To: User MIDI User Library: how to change location and/or add other MIDI lib dirs? version: 3.1.7
Operating system: macOS Catalina (10.15)

1

Thanked by: leon kleikers

[jdmille2]

Thanks, all.  I use Mac, now Windows – actually, a Hackintosh, built on Core i7-4670 “Skylake” @ 4.8 Ghz.

And I guess I was not clear: I get very low latency using USB on the FireFace UFX: 1.396 ms using Cubase buffer size of 64 samples.  (Or more conservatively, <3ms at 192 samples)   This is why I was so surprised to have heinous latency with SD3 out of the box.  HOWEVER, that is “fixed” essentially by turning off Cubase ASIO-Guard, either globally or just for SD3 in the VST Plugin Manager.

This seems odd to me, as no other VST soft synth that I have (including heavy-weights like Ivory) requires this for low-latency real-time playing.  Perhaps SD3 isn’t properly reporting latency to Cubase via the VST3 interface?  Or, as I suspected in my original post, SD3 is doing some extra processing that, while desirable during mix down, add too much latency for real-time playing, and thus could/should be turned off until then.

If disabling ASIO Guard for the SD3 plugin is really is the right thing to do, I guess that’s fine.  I suggest that become part of the SD3 installation instructions and manual, so that others don’t have to waste precious studio time figuring that out for themselves.  And if there is some better way, e.g., disable “extra” processing in SD3 until needed, I’d like to know that, too.

— jdm

ps – if desired, I could quantify the SD3 latency with ASIO Guard enabled, esp. compared to other soft synths, e.g., Ivory.

1

Thanked by: pbony

[jdmille2]

Hey Scott – thanks for the quick reply.  I use all RME gear, with the main being an RME Fireface UFX.  I can set the buffer size down to 64 (I’d usually use 128 or 192) and still, without disabling ASIO Guard, either globally (bad idea) or in the VST Plugin Manager for SD3 specifically, the latency for SD3 is at least a dozen ms – unusable.  But like I said, disabling ASIO-Guard in VST Plugin Manager *does* make it playable, so that’s good to know.  If that truly is the right way to address the issue, hallelujah, let’s get that documented for everyone else, so they don’t have to bang their heads against the wall, too.  But methinks that indicates some mismatch between what Cubase is expecting and what SD3 is expecting, such that you guys might wanna take a look at that handshake to maximize the total performance.

I’m happy to try different things, etc., to help characterize this further.  FWIW, my day job is as a computer scientist, so I’m not afraid to dig in, as it were….

— jdm

[jdmille2]

Me too – tho I’m looking for SD2 manual. IMHO this should be highly visible – and available to anyone, even pre-sales. AND, with the new Product Manager, getting the manual (and then opening it from wherever it installs) should be there, too – and easy to find, please!!

[jdmille2]

yes please!!!

[Author]

Replies