Replies created

 

Viewing 15 replies - 1 through 15 (of 17 total)
  • travis
    Participant

    We have recorded 8 levels of openness for the hihat and the CC-control let’s you use a pedal to control which one you play and also changes any ringing sound into the openness dictated by the pedal. We offer nothing in between these 8 levels.

    Is this something that is intended to be fixed in SD 3 or even the next version?  It’s essentially the same problem in every drum sampler, and it’s really off-putting for playing e-drums.  Could a crossfade between openness levels and an envelope that follow CC-control be added to fix the abrupt switching between openness levels?

    • This post was modified 11 months, 1 week ago by travis.
    travis
    Participant

    @Shootie I bet a video explaining the various mic streams (direct, bleed, overheads, ambience, surround), channels, busses, outputs, and breaking down how the routing of everything works in SD3 would help to relieve a lot of confusion and be a popular video.  A good diagram would definitely help.

    travis
    Participant

    where would you expect default routings to go? You have to start somewhere.

    If I were creating this, I wouldn’t create a ton of unnecessary channels and busses from the getgo.  It just doesn’t make sense in a software interface.  I would allow for those channels and busses to be created as needed.  How many drummers do you think are playing in surround sound?  Maybe very few e-drums enthusiasts who like it as a novelty.  For the other 99.9% of people playing e-drums, it’s probably just in the way in getting to the things that matter.  Same for near, mid, and far ambiences.  How many people wants to route a kick mic to a hi-hat channel?  Probably almost no one.  How about an ‘Route instrument microphones’ window that routes to busses instead?  That actually is very practical.  And why are instrument bleeds in a property box, not in some kind of unified routing window?  I understand how it all works, but the practicality and usability of it isn’t good.

    travis
    Participant

    You can flip switches to route things, sure.  But all those switching options are actually already pre-created.  Why would I want to route a ‘snare top’ mic to a channel called ‘snare bottom’, for example?  It’s pretty impractical, and it’s a lot of unnecessary clutter if you ask me.

    travis
    Participant

    @Bear-Faced Cow What I meant by that is that all routing options are already pre-created, unlike say in Reaper, where if you want a buss, you create it and route your channels to it in whatever configuration that you like.  SD3 is more like pre-made hardware mixer where everything is already set up, and you switch things on/off among the available options, never really adding anything that wasn’t already there.  From a noob point of view, that can be very confusing because there are a ton of channels and busses already pre-made and routing happens by switches.

    travis
    Participant

    @Shootie Unless I’m missing it, I’m not seeing any ‘Original Mix’ options in SD3.  You must be thinking of Ezdrummer 3.

    travis
    Participant

    I got it figured out.  Channels, bleeds, and busses, oh my.  Along with hidden channels.

    @Shootie I’ll take a look at the original mix preset, too.   Thanks.

    The confusing aspect of SD3’s channels and busses and bleeds is that they are all just there (all of them), not being able to create them and see how things are routed.  Everything is routed behind the scenes, so it’s not obvious at first how everything is being routed.

    • This post was modified 1 year ago by travis.
    travis
    Participant

    I’m just getting going with SD3 and some aspects are pretty disappointing.  I would like to see in SD4:

    • Hi-hats that work well with e-drums.  There are only 8 levels of openness, and the switching from one openness level to the next is blatantly obvious.  I can’t believe that this is still a thing in sampled drums made to be used with e-drums.  It’s nearly as bad as machine-gunning.  It should not still be a thing today.  This is my biggest disappointment so far.
    • Kit pieces recorded in a variety of rooms.  I’m not liking the big cinematic room sound slathered all over every kit piece in the core library.  This is also very disappointing.  And I have zero use for the surround channels.  It’s looking like Ezdrummer has Superior Drummer beat badly in this respect, with a smaller and much more practical core library.  I would honestly rather have the EZD3 core library than the SD3 core library, no contest.
    • Reasonably clean samples.  Before I even saw the thread about noises in samples I was hearing a dirty ringing in a lot of the core library samples that sounds like switching power supply noise.  This isn’t as bad as the last two points, but it’s definitely a letdown.  I just assumed when buying SD3 that this sort of thing wouldn’t be an issue in a professional product, but it’s very much there.
    • An interface that shows kit piece mic channels and levels with kit previews for mic channels like the preview pad. For example, if I want to hear the snare in the overheads only, I just click the preview pad for that and adjust the level in the same place, not switching back and forth between the drums tab to select a kit piece and the mixer tab to solo and then adjust the level.  I’m just getting going with SD3, and I’m already noticing a few usability issues like this.  There is a lot of flexibility, and the interface looks nice, but usability could be much improved.  SD3 isn’t really that complicated, but usability issues really make it feel like it is.
    • More default path selections in settings for storing the various kinds of presets and/or SD3 just respecting the selected path for user presets for all types of user presets, not storing some in the selected path and some elsewhere.
    • Linking to downloaded library directories without having to copy the files from the already downloaded library directories to a different directory.  This one is a headscratcher as to why it is currently like this.  It’s just a big waste of time, and it could potentially prevent someone from being able to install the libraries, on say a 250Gb drive.
    • Kit piece calibration.  Play some softest hits, then some hardest hits, and SD adjusts the velocity curve min and max to those velocities.  Then start playing through the range of velocities from softest to hardest while SD lets you tell it if the last hit sounded too soft or two hard.  A real-time graphic indication on the velocity curve could help here.
    • A unified routing window that covers all mic streams, channels, busses, and outputs.

    1

    Thanked by: SaleMesserschmitt
    travis
    Participant

    I’m just a few hours in with SD3, and I’m noticing a lot of noise in samples of the core library that sounds like switching power supply noise, i.e., a dirty high pitched ringing.

    • This post was modified 1 year ago by travis.
    travis
    Participant

    Thank you, it’s insightful. However it’s not an imedance issue, because the SD3 VST and the rest of my instruments plays loud when I hit playback on my DAW.. It’s when I use my edrum kit that the hits aren’t recognized unless I hit my cymbals really REALLY hard. I have to hit them so hard to be able to hear much, and even then it’s too low. Trying to play along with my song in the DAW is almost impossible because of how little it recognizes my trigger hits

    I’m using a TD-17 too, and I’m just getting going with SD3, so I have a long way to go to get things dialed in.  But I have tinkered with this sort of stuff a lot in the past.  I would start by tweaking the velocity envelope of each kit piece in SD3.  Instead of a linear curve (straight line)  you want something more like a log curve (upward pointing curve).  Adding 3 points to the velocity curve is plenty for that.  And you don’t have to change your TD-17 settings.  But if you do change your TD-17 settings it’s going to affect your SD3 velocity curves responses.

    Also, you might wants to sign up at an e-edrums forum such as vdrums.com, since this one doesn’t seem to me to get great responses on such questions.  Editing the velocity curves for kit pieces should have been the first response to your question.  And who knows why this wasn’t done in SD3 from the getgo as a preset.

    • The post has been modified 3 times, last modified 1 year, 1 month ago by travis.
    travis
    Participant

    Installer is doing more than a mere copy of sound content. You’ll just have to be patient while it is doing its work.

    Watching what the install did, it actually does look to be mostly just copying and moving files from the download directories to the ‘SL-SuperiorDrummer3’ directory on the same drive, which adds up to around 100 minutes worth of copying.

    travis
    Participant

    You then have to install them. The download is not the installation. In the toontrack download manager you have a download button and when downloaded you have the option to install.

    So I’m installing part 1 of the core library from the product manager, which seems to be copying part 1 of the core library to the same drive, and I assume that it will do the same for the other parts of the core library. This seems like a waste of time. Surely there is another way to do this. If there is, it’s not in the manual, and I don’t see instructions provided elsewhere.

    travis
    Participant

    Adding to the above, ‘installing’ (copying) the library parts is taking a long time on an internal SSD.  Back to bed.

    • This post was modified 1 year, 1 month ago by travis.
    travis
    Participant

    Hi Travis,

    I take it your TD-17 hasn’t got the option, like my TD-12 has, to set the HH RESOLUTION=HIGH in Settings?
    Anyways, dragging the Slider in the above picture for ‘Fully Closed’ from 127 to 90, should rectify that part for you. Next, I would experiment with the Velocity Transform curve for fine-tuning the response. Finish by saving your tweaks as your own MIDI In/E-drums Preset.

    It’s been a couple of years now since EZdrummer 2 was discontinued, so I wouldn’t expect any further releases for version 2.

    BR,
    John

    No.  The TD-17 doesn’t have that option.  I had a TD-12 too, and I also noticed that option.  I also owned a TD-11 which didn’t have that option and used 0-90 values for cc4.  Roland has MIDI implementation documents for their modules:

    TD-17:  https://static.roland.com/assets/media/pdf/TD-17_MIDI_Imple_eng04_W.pdf

    TD-12:  https://static.roland.com/assets/media/pdf/TD-12_MI.pdf

    I haven’t looked through the Roland MIDI implementation charts many of their modules, but I suspect that a lot of Roland modules aren’t fully supported for hi-hat in Ezdrummer 2 and 3 because of this issue.  And it might be an issue in Superior Drummer versions too.

    I wrote a couple of Reaper plugins to test and correct this for a TD-11 when I owned one.

    • This post was modified 1 year, 2 months ago by travis.
    travis
    Participant

    @John  Does that slider fix the problem for Roland modules that put out MIDI control change 4 messages with values between 0-90?  The TD-17 does put out 0-90 values.  This is also an issue in Ezdrummer 2 that never got fixed, as far as I know.

    • The post has been modified 2 times, last modified 1 year, 2 months ago by travis.
Viewing 15 replies - 1 through 15 (of 17 total)

No products in the cart.

×