32

[Scott Eshleman]

I’ve seen Toontrack address this question in other threads.

As I understand it, but haven’t tried it for myself,
If you record the MIDI that you created/edited/hosted in Logic into the SD3 SongTrack,
the SD3 algorithm will ‘transform’ that MIDI,

I do not know whether it can do this with a Logic Drummer track alone
or if the Logic Drummer track must be converted to a general MIDI track within Logic first
Logic has a function to do this. Please try it both ways and compare the results.

[Scott Eshleman]

I’ve seen Toontrack address this question in other threads.

As I understand it, but haven’t tried it for myself,
If you record the MIDI that you created/edited/hosted in Logic into the SD3 SongTrack,
the SD3 algorithm will ‘transform’ that MIDI,

I do not know whether it can do this with a Logic Drummer track alone
or if the Logic Drummer track must be converted to a general MIDI track within Logic first
Logic has a function to do this. Please try it both ways and compare the results.

[Scott Eshleman]

@Sonny Luciano said:
Both, pieces I added in my DAW and added hits here and there.

As Henrik has said, “it doesn’t matter where you have the MIDI…“
if EZD2 is the instrument that is playing the MDI editted & hosted in your DAW
then the multi-output routing configured in the EZD2 mixer will apply.

Obviously, the kit pieces & MIDI not played by an instance of EZD2 will not be routed through the EZD2 mixer,
but you could bus the multiple EZD2 outputs and those ‘extra’ kit pieces played
by another instrument to a shared AUX to mix them blended.

[Scott Eshleman]

Please clarify,

@Ibex said:
… because those parts are not in EZD2.

By ‘parts’, do you mean additional kit pieces not played by EZD2,
or do you mean MIDI ‘hits’ that you’ve added?

[Scott Eshleman]

@Olle said:
If you press REC in SD3 and play it in your host so that it gets recorded,
much like you would have done in SD2, then it should work.

The E-drum MIDI transform works on incoming MIDI. The MIDI track
in SD3, sort of, sits inside of it. If you import your MIDI directly into
the track in SD3 it doesn’t get applied.  

SD3 is so cool.
Just saying.

Thanks.

[Scott Eshleman]

@Chad Austin said:
I found all of my SL-“insert-SDX-name-here” folders here:
(path) Macintosh HD->Library->Application Support->Superior Drummer
So, would I simply copy-and-paste the entire (for example) SL-Allaire folder? 

Yes. Correct.
Copy the entire SL-“insert-SDX-name-here” folder
and re-point/remap each SDX entry to the new location in the SD2 and SD3 library location settings.

[Scott Eshleman]

@Mark King said:
Search through the posts but I think SD3 is only 64bit and only comes as a vsti and not the old rtas plugin so is probably not compatible with older versions of pro tools. Do a search as this is explained in the forums and I’m not a PT but sure I read this from an earlier poster.  

bottom of the SD3 Product Description page: (i added the underlining)

SYSTEM REQUIREMENTS

64-bit Windows 7 or newer, 4 GB RAM (8 GB RAM or more recommended). Mac OS X 10.6 or higher, 64-bit Intel-based Mac with 4 GB RAM (8 GB RAM or more recommended).
64-bit host (with support for VST, AU or AAX). Standalone is included.
SOFTWARE: Approx. 320 MB download + installation space.
SOUND LIBRARY: Basic install: Approx. 41 GB download and an additional 41 GB for the installation process. Complete install: Approx. 236 GB download and an additional 55 GB for the installation process.
SSD install (optional): Approx. 236 GB pre-installed.

[Scott Eshleman]

@stitch_3 said:
I have HP computer with Windows 10 and Intel core i5-6400 2,70 ghz. processor. I download demo of ez drummer 2 and had error trying to unzip. is my computer powerful enough?  

In a word…
Probably.

The real question is probably whether or not you have enough disk space to unzip the download.
What error are you getting?
Maybe the download was corrupted or incomplete.
Perhaps you could delete the 1st download and try again.

[Scott Eshleman]

I’m not in the studio right now or I’d post a current screenshot.
Perhaps this Toontrack FAQ will help:

https://www.toontrack.com/faq/how-do-i-open-ezdrummer-in-logic/

“The text and pictures in this FAQ explains how to open EZdrummer in Logic 9,
but it works the exact same way with Superior Drummer 2,
Beatstation or any other virtual sampler from Toontrack.

First open a new session and create a Software Instrument track.
Please go to the channel strip on your bottom left, where among others your I/O, Inserts and Sends show.
The track will probably open with a one of Logic’s own instruments..

Click and hold beneath the I/O button (on EVP88 in this case) to bring up a number of submenus.

Now please click to AU Instruments – Toontrack – EZdrummer – Stereo.
EZdrummer will now be inserted in your Logic session.
If you are to drag any MIDI files from the MIDI browser inside EZdrummer (or from Finder)
please note that you need to drag it to the same track as EZdrummer is inserted on.“

1

Thanked by: BernieJohn

[Scott Eshleman]

does the SD3 standalone version open properly?

Please respond & continue in your other post, where I’ve responded as well.

3 threads for the same issue is very confusing.

[Scott Eshleman]

@MF5152 said:
Yes it did but now I have found that SD3 does not work with pro tools yet?  

To what version of Pro Tools are you referring?
We have SD3 licensed & running on 2 different versions of Pro Tools (12.7.1, 12.8.1)
on 3 different Mac computers (all running Sierra).
(I do not believe that Pro Tools is High-Sierra certified yet.)

[Scott Eshleman]

That’s odd. Those tabs are all visible by default when you open SD3.
Can you please upload a screenshot of what you are seeing when you open SD3?

Also, is this your experience with both the plugin and the standalone?

If as a plugin, in what host/DAW are you running it?

[Scott Eshleman]

There is a demo available for EZKeys. Give it a try.
I can try it myself later and give you an answer,
but I’ve only ever dealt with changing chord & chord inversions within EZKeys.

[Scott Eshleman]

After years of computing-related experience; I offer:

Technology Suggestion #1: Never, ever do a major operating system upgrade (Windows or Mac) without first checking compatibility
of your critical hardware, peripherals, software programs & plugins.

Technology Suggestion #2: After an initial roll-out of an OS upgrade, if you cannot document, diagnose and/or resolve any issues that may arise, it is often best to wait & allow others to bear that responsibility. Even the most diligent testing is unlikely to expose every issue that a much larger user base will uncover once an upgrade is released to the public.

Technology Suggestion #3: When cleared to proceed with aforementioned upgrades,
it is still best to do so with caution and a watchful observance of any ‘unexpected consequences’.

[Author]

Replies