6

[pumpkinking]

Hi monospace.  You might be on to something but I’m not able to see it consistently.  If I just open the core library to the default kit, and then place the offending cymbal in slot 5, I hear what you are referring to clearly.  However, if I take an existing core custom preset that I use frequently and do the same, it is OK.  So far I cannot explain why this is the case, however…

Here is more info: if I solo the Ambient ribbon mic, the cymbal is clearly from the right.  If I solo the OH Dynamic, it is very much from the left.  And if I solo the Ambient near it is close to middle.  So maybe check your mixer, maybe the preset that sounds good to me has the OH Dyn off or lowered.  I’m wondering if just one mic (OH Dyn) was L-R reversed.  I’ll keep playing with it.

Reply To: Stereo Bug in Core Library, Cymbal 5 version: 3.2.4
Operating system: macOS Big Sur (11)

• This post was modified 4 years, 5 months ago by pumpkinking.

[pumpkinking]

I just went through all of the articulations on this cymbal in the 5 position you indicated, and they all appeared to originate more in the right side of the stereo field than the left, although the sustain approached a balanced L/R quickly.  Hard to accurately measure in the SD3 mixer (that I know of anyway) so I cannot prove it.  But I did compare it to the default cymbals in positions Cymbal 1 and 2 and there was a distinct difference in perceived location in the stereo field.

Reply To: Stereo Bug in Core Library, Cymbal 5 version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

You should be able to open the Midi In/E-Drums menu, hit the tom rim you want to map, and change its note mapping to the Ride->Bell shank note (or whatever midi equivalent you want) in the mapping tab on the right side of the menu.

Reply To: Add ride bell sound to my kits tom rim in SD3? version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

You might want to compare the midi monitor values when playing the hi-hat in standalone vs. as a plugin to see if there is a difference in the incoming midi values for a closed edge/tip trigger.

I also had this happen once or twice in standalone and I resolved it by powering my modules off, refreshing the midi devices, powering them back on and refreshing/selecting again.  You have to make sure you reselect the midi preset you want to use.  Just seemed like a glitch to me, I think I had the hihat pedal closed while powering up the module and SD3 and maybe that had some negative interaction.

Reply To: Superior Drummer 3 FL Studio 20 – Hi-hat issue Roland TD-30 version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

The M1 chips appear to have 8 cores, but they are not all the same: there are 4 “big” cores and 4 “little” cores.  The big cores are for compute-intensive workloads and the little cores are for smaller workloads (and are much more power efficient).  How these cores all work together is controlled by the hardware/software architecture, and very likely has different modes depending on the workloads.  I am guessing these modes include configurations that use just the 4 little cores and just the 4 big cores, and possibly all 8 together, although the throughput will be different between big and little cores, so I’m not certain of that.

My guess is that these processors work best when running applications that require 4 or fewer threads, although I have no data to back that up.  That said, I have a mini with an M1 chip and I have SD3 set to 4 cores.

Reply To: Correct number of CPU cores settings for M1 Mac version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

I 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

Reply To: Apple M1 Chip MacBook and SD3 latency version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

Hi 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

Reply To: Midi File Not Playing Back Correctly In Logic Pro X version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

500GB 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.

Reply To: Looking for best Samsung SSD drive for SD3 version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

I 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.

Reply To: Unwanted Open Hi Hats – Roland TD-27 version: 3.2.4
Operating system: macOS Big Sur (11)

1

Thanked by: Ian Prince

[pumpkinking]

Have 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)?

Reply To: Unwanted Open Hi Hats – Roland TD-27 version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

I am currently using two drum modules connected individually through USB and SD3 sees both and allows me to select both.

Reply To: Can I trigger SD3 with multiple Modules? version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

OK, 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.

Reply To: Second snare drum, bleed on bottom mic? version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

I’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.

Reply To: Second snare drum, bleed on bottom mic? version: 3.2.4
Operating system: macOS Big Sur (11)

[pumpkinking]

I 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.

Reply To: Superior Drummer 3 and SDX Effects Library contained on two separate hard drives version: 3.2.4
Operating system: macOS Big Sur (11)

[Author]

Replies