Replies created

 

Viewing 15 replies - 31 through 45 (of 59 total)
  • mickg
    Participant

    My kit consists of a Trapkat, 2 Drumkats & 4 pedals. I have them set to comfortably trigger BFD3 (since I owned it before SD3). Using the same patches on the controllers I notice that SD3 plays a little light. By that I mean, sending the same midi velocity to both VIs, BFD3 plays hotter than SD3 (not just volume, which I could control with master volume) but the overall ‘feel’ of the kit. It sounds as though I’m playing SD3 lighter than BFD3. It’s a little hard to explain but it’s as though I’m playing BFD with big rock sticks and SD3 with skinny jazz sticks. The ‘sweet spot’ seems lower in SD3. I could, and have adjusted the velocity curves individually on SD3 but since my kit consists of 48 pads, that is a lot of adjusting. I have the velocity curves on BFD3 & SD3 set to linear and if I had a global curve adjustment on either program I could deal with the discrepancy between the two programs. Perhaps a “copy and paste” tool for velocity curves might make it easier.


    Reply To: volume too low when using MIDI Controller version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    I had big playback problems with my 2017 MacBook Pro using more than 1 core. I switched to 1 core and never looked back. SD3 has been working great since.


    Reply To: Setting SD3 to use multiple Core's version: 3.1.4
    Operating system: macOS Mojave (10.14)

    1

    Thanked by: Isaiah Marshall
    mickg
    Participant

    Pro Tools gives you the option of bouncing files (as WAVs) in split stereo (two files .L &.R) or interleaved (L/R embedded into one file). SD should incorporate that into their program. (Especially now that we can have surround mixes) WAVs can be multi-track files (more than just L/R embedded in one file, 5.1, 7.1 etc…)


    Reply To: split stereo mics weirdness version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    Also check the mixer in SD3. Check that the output routing is going where you need it to go. Perhaps you may only be monitoring the ambiance channels and not actually hearing the direct mics. Solo some of the outputs to see if things change. If you are sending a midi velocity of 127 and not hearing a full hit, something is wrong. An easy check would be to click on a drum to trigger it, it should be pretty loud.

    I would love a to see a global control over midi input sensitivity. I have some controllers that are set for other applications (BFD, Slate) and each seem to respond differently to incoming midi. Also, this would be a quick fix for people who play at different velocity levels (hard hitters vs soft).


    Reply To: volume too low when using MIDI Controller version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    The DITI by Alternate Mode has 24 trigger ins (supposedly). Not sure how they do it since there are only 12 inputs. I guess they are three pin connectors. Like stereo headphone jacks. It also has a crazy amount of bells and whistles that each input can do, like layers, alternating notes, chords and delays.

    mickg
    Participant

    The “all notes off” command is really used to mute stuck notes played from a keyboard controller. Or any controller for that matter. Occasionally notes will hang and not get a note off command, not a big deal for drum sounds which naturally end, but sounds with long sustains (like string) will hang until you hit the panic (x) button. Not really an issue with drum sounds.


    Reply To: Bug? X key command mute all sound version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    Not sure if it is intended as a mute button or if it just sends a “all note off” command. In which case it sounds like it may be working as advertised. You may be expecting it to working like a master mute on the mixer.


    Reply To: Bug? X key command mute all sound version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    Try saving a preset that makes it really obvious what you settings are. Perhaps zero bleed. This way you could tell if it is really making the change or if it’s just a screen redraw issue.


    Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    Are you saving it a a preset or kit? It may not save that info in kits since I think that info may be considered part of the “mix”. But honestly I’m new to SD3, having given up on BFD since they were acquired by ROLI. They seem to be in limbo. SD3 rocks.


    Reply To: Strange issue with overhead bleed levels reverting back after changing them version: 3.1.4
    Operating system: macOS Mojave (10.14)
    • This post was modified 6 years, 3 months ago by mickg.
    mickg
    Participant

    I’ve seen for the first time yesterday. It happens after I closed my MacBook and it when to sleep. After waking up I got the message. No sound. Restart Mac and problem when away. Only time I’ve seen this.


    Reply To: “Audio Engine Inactive” Message in SD3 version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    Try any United Audio interface with a thunderbolt connection. I’m able to get the latency as low as I can set it.

    I’m running a 2117 MacBook Pro with an OWC envoy ssd. Presets load in a few seconds.

    My kit is a Trapkat and two Drumkats. I have kits with over 30 drums. Still takes seconds to load.


    Reply To: Best USB audio interface version: 3.1.4
    Operating system: macOS Mojave (10.14)

    1

    Thanked by: Mercer
    mickg
    Participant

    Perhaps if I restate my request in a way that suggests this is more of a problem than a feature I’d like to see added I might get a response or acknowledgement of my request. Am I on the right forum for requests or is this strictly for issues with things not working as advertised? Perhaps a sub-forum for wish lists?


    Reply To: A few requests… version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    If I understand your question correctly I think you may be looking for the best way to achieve the ideal sound. I think if you are just laying down a stereo drum track then however you get there is fine. However if you are playing an ekit in a live situation and need to have give your sound engineer more control over levels & fx, then direct your individual drums to different physical outputs to send to an outboard mixer. I’m new to SD3 but I believe you can have separate ambiance channels for each drum (not sure exactly how to do it), then group the ambiance channel with your drum mic and output that to its own set of physical outputs. The only drawback to that is only the number of outputs on your audio interface and the number of outputs addressed by SD3.

    It sounds a bit complicated and probably is but going back to my first statement which is, if it sounds good and you only need to track you drums to a stereo mix, then go with whatever works. Also, remember if you are sequencing and laying down tracks, you can record each drum one at time to isolate each drum so as to not get ambiance bleed from other drums sharing the ambiance channels.

    I hope this helps give you some ideas.

    mick


    Reply To: What is the best way for the best result ??? version: 3.1.4
    Operating system: macOS Mojave (10.14)
    mickg
    Participant

    Someone has to be on the bleeding edge! Just keep that time machine handy. I applaud your enthusiasm.


    Reply To: Cannot instal Superior Drummer 3 on MacOS Catalina Public Beta 1 version: 3.0.0
    Operating system: Mac OS X Tiger (10.4)
    mickg
    Participant

    I’ve had a problem like this when I’ve tried to remove a plug in. I stopped doing that. Probably not the best solution.


    Reply To: crash in POP PUNK version: 3.1.4
    Operating system: macOS Mojave (10.14)

    1

    Thanked by: joey pinter-bilek
Viewing 15 replies - 31 through 45 (of 59 total)

No products in the cart.

×