pumpkinking
Participant
Topics Started: 5
Replies Created: 84
Has Thanked: 12
Been Thanked: 32
pumpkinkingI know this is not exactly your question, but hopefully a usable datapoint. I am using SD3 with a mac mini with the M1 chip and my audio device is the headphone jack – the reported latencies are: “Output latency: 4.2 ms” and “Buffer latency: 5.8 ms”. These latencies are good for me. When I tried to use bluetooth it was awful.
Are you using the headphone jack on your laptop?
Thanks, Joe
pumpkinkingHi Dan. I just did a test where I dumped a MIDI from SD3 and imported it into Logic, making sure that the midi is on an SD3 track with the exact same kit/mixer/midi config as I recorded the midi file. It seemed to work for me.
So in general it seems to work, so I’m guessing that something is not setup correctly in your case. Maybe try saving the kit/mixer/midi configs in the standalone SD3 where you recorded the midi and then load those same presets in the SD3 plugin for the track in Logic.
-Joe
pumpkinking500GB might be a bit small depending on how many libraries you think you might collect. Personally I use a SanDisk 1TB Extreme, and with the core library and two SDXs (full install for all) it is already half consumed.
pumpkinkingI believe you should be seeing many midi note triggers in the midi monitor as you move the hihat from open to closed and back with the pedal (no hits). If you are not seeing that, there might be some issue with the mapping or midi preset, or the connection/config with the module.
I would start with the basics like: does the module itself do what you expect with the hihat, then what is the module’s hihat midi setting, then what is your SD3 midi preset, then are you getting correct midi values in SD3 for other triggers, then are you getting any midi notes for hihat pedal movement. Basically start from the module and validate that you’re getting what you expect, then work your way to SD3 taking it one step at a time.
1
Thanked by: Ian PrincepumpkinkingHave you confirmed that the midi values generated for a closed hit on the hi-hat (watching the midi monitor box) is matching the closed edge (or whatever hi-hat articulation you want) midi note that SD3 is expecting (in the midi mapping box)?
pumpkinkingI am currently using two drum modules connected individually through USB and SD3 sees both and allows me to select both.
pumpkinkingOK, I might have figured something out here. In the mixer, I open the Route Instrument Microphones window, and select the mic routing for the kick drum. Under the bleed mics, I change the mixer channel for the snare bottom mic to the X-Snare bottom. This change has the desired effect in that kick hits bleed onto the X-Drum snare bottom. Unfortunately, I cannot find a way to have two different snare bottom bleed mics.
pumpkinkingI’ve played with this before as well, and it seems a fundamental limitation in all of the User Mics in the mixer. The bleed options pull-down for every single one has enable/disable all instrument bleed greyed out.
The Route Instrument Microphones window shows bleed mics associated with mixer channels for X Instruments, but it seems they cannot be enabled.
pumpkinkingI have installed SD3 on my main SSD and the core libraries on an external SSD. Works fine. I actually manually moved the core libraries to the external SSD after installing them and just changed the path in the product manager.
No products in the cart.
