Replies created

 

Viewing 9 replies - 1 through 9 (of 9 total)
  • GregRockN
    Participant

    After installing SUPERIOR DRUMMER 3, it says that it can’t find the percussion sounds. When I go into the groove, the percussion groove is blank with nothing in it. I installed it as instructed.

    Please, help me! What’s the solution?

    Reply To: After installing SUPERIOR DRUMMER 3, the percussion groove is blank in it. version: 3.3.7
    Operating system: macOS Big Sur (11)

    I had the same problem a few weeks ago.  Please see this Forum thread for the solution:

    https://www.toontrack.com/forums/topic/midi-data-missing/


    Reply To: After installing SUPERIOR DRUMMER 3, the percussion groove is blank in it. version: 3.3.7
    Operating system: Windows 10
    • This post was modified 8 months, 3 weeks ago by GregRockN.
    GregRockN
    Participant

    I just finished programming a Neil Peart performance in SD3.  I had to do some switching back and forth between triplets and straight display in the grid while doing the programming.  While it’s not too difficult to switch the grid display back and forth, I do think that it would be a nice new feature of SD3 to be able to define the grid-type for subsections of the song… something similar to how we can change the meter of several measures in a subsection of a song today.


    Reply To: Grid Display – Partial Section for Triplets version: 3.3.7
    Operating system: Windows 10
    • This post was modified 9 months, 4 weeks ago by GregRockN.
    GregRockN
    Participant

    Greg sums it up

    The bottom line is that the SD3 library Percussion Grooves do, in fact, have MIDI in them but you need to have a drum kit defined with an instrument that associates itself with “Note 1” (Power Hand “One Shot Pad”), or “Note 2” (Power Hand “Shaker Pad”), or “Note 3” (Power Hand “Tambourine Pad”).  It appears that SD3’s Percussion grooves are associated only with “Future Hit Instruments” such as shakers and tambourines.

    As you can see in the very first screen shot, the Power hand is one of the “pads”, which means you need to have an instrument loaded there for the MIDI to produce sound.
    For “normal” instruments, substitution would kick into place but not the special Percussion pads.

    BR,
    John

    John, can you please tell us what Future Hit Instrument is associated with the SD3 Percussion grooves with a Power Hand of  “One Hit Pad”?

    In the Drums tab when I pull down the menu for “Add an Instrument” and select Future Hit Instrument I only see two options:  1.) Shaker, and 2.) Tambourine.  Those two instruments are associated with SD3 Percussion grooves with the Power Hand of “Shaker Pad” and “Tambourine Pad”.  I do not see a Future Hit Instrument called “One Shot”.  Therefore I do not know what instrument(s) is associated with the SD3 Percussion grooves with the Power Hand of “One Shot Pad”.

    Thanks in advance for your help.

    -Greg


    Reply To: Midi data missing version: 3.3.7
    Operating system: Windows 10
    • This post was modified 9 months, 4 weeks ago by GregRockN.
    GregRockN
    Participant

    Same problem here.  If I search Grooves for Percussion, the SD3 library shows lots of grooves but none of them appear to have any MIDI… at first glance.  I have attached a screenshot of the Groove search on “Percussion”.  Note that grooves in the top half of the list are from the SD3 base library and the bottom half are from the EZX Latin Percussion library.  None of the SD3 grooves show any MIDI, while all of the Latin Percussion grooves show MIDI (see attached screenshot).  If I audition any of the SD3 library grooves there is no sound produced.  If I audition any of the Latin Percussion grooves they all make sound as expected.

    However, despite the fact that an SD3 Percussion groove produces no audible sound and appears to contain no MIDI data (based on the visual display in the Groove search window), there does in fact appear to be some MIDI in the SD3 Percussion grooves.  As an example, I dragged the SD3 Percussion groove “8th Acc 1 2 3, Straight 3/4, Shaker Pad” groove to the song track and viewed it in the Grid Editor (see attached screenshot).  In the Grid Editor I can see (but not hear) 7 MIDI notes that are all assigned to the Instrument called “Note 2”.  That “Note 2” Instrument is not assigned to an instrument in the default SD3 kit nor the default Latin Percussion kit and therefore produces no sound when the song track is played (nor when auditioning the groove in the Grooves List). BUT… if I go to the Drums tab so that I can view my kit, and then I add an Instrument to the kit (button in the upper-left corner of the Drums window) as Future Hit Instrument/Shaker, then the MIDI in that SD3 Percussion library groove makes sound.  Going back to the Grid Editor we find that SD3 has automatically re-named the “Note 2” instrument to “Shaker 1” (see attached screenshot).  Having added the “Future Hit Instrument/Shaker” to the kit allows the MIDI to be heard both when playing the song track or auditioning any of the SD3 Percussion grooves in the Grooves window where the Power Hand is the “Shaker Pad”.  Note that SD3 Percussion library grooves where the Power Hand is NOT “Shaker Pad” continue to be silent and show no MIDI.  Therefore the “Shaker Pad” grooves need to have a Future Hit Instrument/Shaker in the kit in order for them to work.

    I then went back to the Drums tab and added a Future Hit Instrument/Tambourine.  After doing this the MIDI for all of the Power Hand “Tambourine Pad” became visible in the Grooves window and became audible when auditioning those grooves.  The SD3 Percussion grooves with the Power Hand of “One Shot Pad” have MIDI that is associated with an Instrument called “Note 1”.  I was never able to determine how to add an instrument to the drum kit that would associate itself with “Note 1”.  I’m sure there is a way, but I just couldn’t find it and it is not by adding an “Import Audio File…” instrument to the kit.

    The bottom line is that the SD3 library Percussion Grooves do, in fact, have MIDI in them but you need to have a drum kit defined with an instrument that associates itself with “Note 1” (Power Hand “One Shot Pad”), or “Note 2” (Power Hand “Shaker Pad”), or “Note 3” (Power Hand “Tambourine Pad”).  It appears that SD3’s Percussion grooves are associated only with “Future Hit Instruments” such as shakers and tambourines.

    Hope this helps.


    Reply To: Midi data missing version: 3.3.7
    Operating system: Windows 10
    • This post was modified 9 months, 4 weeks ago by GregRockN.
    GregRockN
    Participant

    Almost all of the acoustic drums in the Toontracks libraries that I own have names where the first part of the name string is the dimensions of the drum.  Therefore, in the instrument search screen the first column of available drums is the “Name” column.  If you click on “Name” at the top of the column it will order the column in ascending or descending order… and since the first part of the name string is the instrument dimensions you will end up with an ordered list of instruments by size that you can quickly scroll through to find the size you are looking for.

    In addition to the sorted list by Name/Size you can also type something like “10x” in the search field on the instrument search window and it will only show instruments with the string ’10x’ in the name… i.e. all the drums with a 10″ diameter.  Or if you are looking for a 10″ deep drum, you would search on the string ‘x10″‘.

    Hope this helps.


    Reply To: Search by drum size version: 3.3.7
    Operating system: Windows 10
    GregRockN
    Participant

    I recently ran into the same problem of not being able to search the forum.  The first thing to understand is that the search bar for the forum is the same as the search bar for the entire Toontrack website… they are one and the same.  There is not a separate search bar for the forum.  The next problem I needed to solve was the search bar was not letting me search for anything and was giving an error.  This problem was solved by enabling ALL of the cookies on the Toontrack site.  I tried enabling just a subset of the cookie types but I did not have success with the search function until I enabled ALL cookies.  Once I did that I was able to search the forum with no problem.  Hope this works for you.

    NOTE:  in order to enable the Toontrack cookies, click on the cookie icon with the three circular arrows around it in the lower left corner of the web page.  That will bring up the cookies panel that will allow you to enable them.


    Reply To: Weird Velocity Curve Behavior version: 3.3.7
    Operating system: Windows 10
    • This post was modified 10 months ago by GregRockN.

    1

    Thanked by: SteadyEddie
    GregRockN
    Participant

    Thanks Jord.  You have confirmed the conclusion that I reached that I need to trim off the silence at the start of the audio clips in order to avoid the time offset in the Tracker-generated MIDI.  I received the audio files from somebody else that had generated them in a different DAW and different session, and imported I them into Tracker as-is/as-received.  I can quickly import them into Pro Tools to trim off the silence and then export them before importing them into Tracker.  Alternatively (and even easier) I simply dragged the “All Tracks Combined” track from Tracker into the SD3 timeline, selected all notes, turned off the snap-to-grid, and then slid all the notes left by 200 msec to get them properly aligned with the measures so that they play properly on the beat in my DAW session.

    I had mistakenly thought that by using the “Find Tempo” feature of Tracker and getting the drum hits to line up with the measure markers in Tracker that Tracker would then export the MIDI properly aligned to the measures as seen in Tracker.  However that exported MIDI (or simply dragging the “All Tracks Combined” track to the SD3 song timeline”) is not properly measure-aligned due to that silence at the beginning of the original audio drum tracks.  This still confuses me a bit, and it would be nice if Tracker would export things the way they are visually seen in the Tracker timeline (i.e. if the drum hit is perfectly aligned on beat 1 of measure 2 after using “Find Tempo”, for example, then when exported from Tracker that drum hit would occur on beat 1 of measure 2 rather than beat 1 + (amount of silence at the beginning of the audio file) measure 2.

    It would therefore be a nice feature for SD3 to add the ability to tell Tracker to ignore some user-defined amount of silence or some amount of time that the user does NOT want Tracker to analyze at the start of the audio files.  This, I think, would be fairly simple to program for the SD3 developers and would be a major convenience for the end-user in cases like mine where I received audio files with undesired silence at the start of the waveforms.  I know how to work around the issue, but it would be a lot nicer if I could deal with it with a simple “Ignore XXX msec of time at the start of the audio” feature in Tracker.

    Thanks again for the reply.

    GregRockN
    Participant

    +1

    GregRockN
    Participant

    You are absolutely right.  The problem is that Cymbal 5 in the Grid Editor does not have a kit piece assigned to it, and dragging notes across that lane causes the crash.  Thank you for your help to figure that out.

    Something in my SD3 session appears to be corrupted.  If I exit the Grid Editor and go to the Drums tab, cymbal 5 DOES appear to have a kit piece assigned to it.  Yet, if I manually trigger cymbal 5 with a mouse click it does play a sound but the visual on-screen in the GUI is that cymbal 4 is being struck (the audible sound is the crash kit piece assigned to cymbal 5, but the visual on screen is that cymbal 4 is vibrating from the hit).  I looked at the MIDI mapping for cymbal 5 and cymbal 4 and they do not share the same notes.  So somehow some internal “SD3 wires” have gotten crossed up/messed up on cymbal 5 in my session.  I’m not sure what I would have done to get into that bad state.

    This morning I have re-loaded the Dry Yamaha Rock kit, and added my X-Drum.  Cymbal 5 now works as it is supposed to in the Drums tab (both visually and audibly), and also has an assigned kit piece in the Grid Editor.  And now I can successfully drag notes across all lanes in the Grid Editor (including cymbal 5) without crashing Pro Tools.

    I think there would still be value for the tech folks at Toontrack to take a look at my SD3P session file and produce a fix that would not crash Pro Tools if notes in the Grid Editor get dragged across a lane with no kit piece assigned.  That bug caused some frustrating losses of work and time for me.


    Reply To: SD3 Crashes Pro Tools When Dragging Notes to/from an X-Drum in the Grid Editor version: 3.1.7
    Operating system: Windows 10
Viewing 9 replies - 1 through 9 (of 9 total)

No products in the cart.

×