No products in the cart.
Bear-Faced Cow
Participant
Topics Started: 30
Replies Created: 2943
Has Thanked: 257
Been Thanked: 1044
All of the instrument aux channels in Logic will stereo from SD3. However, Logic is flexible enough in that you can set up mono aux channels with the input being the left or the right stereo instrument channel. In SD3, you would hard pan your instruments going to these outputs.
jord
1
Thanked by: OFSThere a some EZXs with drum machine samples on them, if you feel the need to go that route. However, I couldn’t see myself spending that kind of money on drum machine samples.
jord
There are already lots of drum machine samples out there that you can import into SD3.
jord
Yeah, I found that to be a pain point as well. Considering that I have the identical MIDI libraries on my other computer, I’m going to try copying the entire folder. If that works, I might just try a symlink to the cloud directory so that I only have to worry about one groove directory.
jord
1
Thanked by: Mac McCormickI had a similar situation on my Mac. You should be able to install the app and then point it to your library. Then run the PM to update any missing items such as grooves.
jord
Check your MIDI input. If you’re not getting a velocity level of 127 on your harder hits, you might want to adjust your pad sensitivity first. Once you have that, then adjust the map.
jord
I believe we can agree on the fact that if you are not getting 127 out of your hardest hit, then yes your controller needs to be adjusted ignorer for you to be able to achieve maximum velocity without having to go all caveman over it. Again that would apply to all controllers (e-drums, pad, etc). However, based on
If I really whack them hard I can get the maximum midi level of 127 (as shown by the Analyser in SD3), but even then that does not sound as loud or as good as clicking on a drums image with a mouse.
if you are achieving higher velocities and it doesn’t sound right, then one needs to adjust the velocity map in SD3. Everything between your softest and hardest hits are not linear.
jord
1
Thanked by: Asa PalmerYou’re right in that everyone hits differently. However, saying that the preset doesn’t take this into account is incorrect. The only reason one doesn’t take it into account is because they don’t use the preset’s input velocity mapping to adjust their sensitivity:
Quite often people are simply loading the preset as is with the input velocity mapping set to linear.
For those of us who use our MIDI controllers, and e-drums are nothing more than a glorified MIDI controller, for more than SD3 (SD3 is only one rhythm producing software that I use), it doesn’t make sense to adjust the hardware, especially if your hardware is performing as desired in other software. It is far more sensible to adjust the software to your playing so that you don’t have to keep readjusting when going between software, which can introduce its own errors.
jord
You libraries should be safe. As long as you repointed SD3 to them and SD3 isn’t barfing or complaining, the Product Manager shouldn’t see it as needing a reinstall (mine didn’t). Just install the updates that the PM downloads and you should be all good to go. Like I said, this is all I had to do.
jord
I just recently went through a similar situation on my Mac..
If you run the product manager, it should indicate that some updates are required. Those should include the MIDI libraries, or at least include them. Download and install the updates and your MIDI libraries should reappear.
jord
The MIDI/e-drum presets do, actually…
I would recommend this over adjusting the hardware sensitivity for many reasons. One of them being that you can have different user variations to suit the type of kits and save them along with your kit presets. There are others…
jord
The velocity map transforms your incoming MIDI. It is probably sending out a lower value and needs to be adjusted to suit your playing style.
jord
You probably want to check the velocity mappings in the MIDI/e-drum settings for that preset and customize them to your playing (and save it as a user preset).
jord
You can already see what my CPU usage is showing. I have posted it twice. And considering that right now, I am running a minimal system as I have been troubleshooting other issues (because that is part of what I do in daily life), SD3 is not one of them.
My system is slower than yours, despite it being a trash can with a Xeon processor. I’m also using mechanical hard drives which are slower. However, I have more than enough to spread out disk traffic in thunderbolt enclosures, which is important when working with audio.
So you are in no position to tell me that it is the software when all of the software that you are running is in my current project in Logic. Attempting the “strength in numbers” approach is futile. That just tells me that there are others running beer budget systems with champagne expectations. Perhaps start by getting two more thunderbolt drives and spread out your audio and sample libraries. Also see what else is running behind the scenes on your Macs as they may be stealing unnecessary resources.
Telling me it’s the software falls on deaf ears.
jord
No products in the cart.