[Beat6er]

Thanks Jesse for the heads up. You’re the third forum contributor that told me that work around doesn’t work. So, yeah, that is a downer. I hadn’t tried it yet so I don’t have any time invested in that work around. But just so I didn’t lose my 79 bucks (somehow I got a $20 discount) i’m going to be heading to Reaper. I think it’s gonna be good to have 2 DAWs anyway. I think it’s gonna be fun learning how compatible they are working with each other. Acids got its strengths, but I heard a whole lot of good things about Reaper. Being that it is recognized as one of the best DAWs in the industry, and for 60 bucks, plus getting lifetime updates, it’s a no brained. I can’t leave this post Jesse, without thanking you. I think it was great to be able to learn from guys that have already blazed the trail that I’m trying to follow. You guys keep me from straying off into the weeds. Not only is seasoned advice a great timesaver, it also protects my operating system from dangling leftover files, when I realize I installed something I shouldn’t have and the uninstall goes sideways. This is a great forum and thanks for your help.

Beat6er

Reply To: EZD3 Audio engine Inactive in ACID Pro 10 Suite version: 3.0.2
Operating system: Windows 10

[Beat6er]

Thank you Brad,

You were spot on in telling me a wrapper was not the way to go.  I certainly appreciate your advise. I haven’t attempted this yet, I left my computer for some time today and enjoyed some Father’s Day activities. A fellow forum participant with the handle  Rednroll was thinking along the same lines as your instruction. The problem is indeed within Acid, and your answer made me realize that a wrapper would just terribly complicate things for me. The last thing I needed was to go racing off the road and into a ditch somewhere just trying to fix something which I know little about.  This is what Rednroll suggested and he said it worked. I can’t wait to try it.

Here is Rednrol’s post:

I ran into this same problem with EZDrummer 2 as well as Superior Drummer 3 when working with Acid Pro. I’m guessing since I don’t own EZD3…..but it’s likely the same problem.

What you may notice is that all ToonTrack Plugins are currently VST3 plugins. What I noticed is that all my other VST3 instrument plugins install with a “.VST3” file extension for the plugin, where ToonTrack’s plugs install with a “.DLL” file extension instead. By default, they get installed to your PC’s “C:\Program Files\Common Files\ VST3\” plugins folder.

For some reason Acid Pro seems to have a problem with the the different file extension and being located in the default VST3 plugin folder but Reaper doesn’t as mentioned.

So how to get it to work?

1. Navigate to your VST3 plugin folder : “C:\Program Files\Common Files\ VST3\”

2. Find the EZDrummer3 plugin file

3. Copy or move that file to your VST2 64bit install plugins folder, typically located at C:\Program Files\VSTPlugins\ or C:\Program Files\Steinberg\VSTPlugins\ (ie which ever folder you have Acid setup to scan for 64bit VST2 plugins).

4. Restart Acid. Acid will go through a re-scan of your plugins and EZDrummer will now load and function correctly.

I don’t visit here often since I’ve moved onto other DAW programs but may fire up Acid via re-wire from time to time if working with loops. This should likely be stickied to the top of the forum, if Magix isn’t going to get around to fixing the issue. I responded to a few other posts in the past with the same issue of ToonTrack plugins not working in Acid after I had the same problem and eventually figured out how to solve it.

 

Brad, Thanks again. I am grateful for the advice and instruction I receive from you and other contributors on forums just like this one.

I’m in your debt.

Beat6er

Reply To: EZD3 Audio engine Inactive in ACID Pro 10 Suite version: 3.0.2
Operating system: Windows 10

1

Thanked by: Brad

[Beat6er]

Please forgive me for my first post on this. I totally butchered my grammar and my sentence logic. Here is my second attempt at what I think. I have the very same problem. Perhaps we can share each other’s insights to help one another. I have found that easy drummer 3 works just fine when used as a standalone application. As a standalone application, you can access the midi  in and out panel located in the right bottom corner. I can assignor my audio engine is my midi audio interface, and all is well. When I try to use easy drummer three as a instrument within acid pro 10, on a midi track, just like we did with easy drummer 2, we can’t access that little panel where the Midi in and out selectors are because that panel instantly gets covered up by the audio engine inactive message. I have been interacting with Toon tracks about this. The reply I received told me that EZD3 is a VST3 and not a midi program. We all know that Easy drummer 2 was a midi program, and therefore we naturally opened it up on a midi track. Toomtrack told me that it’s a VST3 and not a Midi application. That totally confused me. The reason being, I cannot figure out how to activate a VST3 instrument application all by itself on a track. Worse yet, I’m now thinking on an audio track. I’m thinking, “How do you do that”?  It has always been my understanding for quite a few years that a VST or a vst3 is an effect, like reverb, compression or delay and vst effects are used to enhance or modify an audio signal. Now we both know that Acid Pro 10  has a vst3 because  it comes with a vst3 plugin resident as a track fx. I now think that the VST3 (Sidechainer) is ok working inside Acid because a side chain isn’t a musical instrument However,  I’ve been doing a lot of digging around and i have learned that contrary to what I previously believed, there are such things as VST3 instruments that are musical  just like vstis. But I still don’t understand it completely. Some VST3 instruments if the DAW doesn’t provide direct access to the audio engine,  will only work if they are inside a “Wrapper”. From what I have gathered so far, a wrapper is a vst itself, which is equipped with single or even multiple pairs of midi ins and outputs. It’s purpose of the wrapper, is to handle the audio engine connections and a VST3 instrument resides inside the wrapper and the  vst3 instrument is what makes the music. I’m beginning to think that the reason EZdrummer 3 throws up that “Audio exngine inactive” sign that covers up the midi selectors, that we can “see “ when EXD3 is started as a standalone, may be because when EZD3 is started as a stand-alone, it looks to the computer to access the audio connections. But when EXD3 is started inside a some, but not all DAWs, EXD3 looks to the DAW for its access to the audio interface. So, I think it’s like this. When EXD3 starts as a stand-alone, it does fine. But when EXD3 is loaded inside of some DAWs, it looks to the the DAW to provide its connections,  and some DAWs just aren’t  “wired” to provide those connections. So we can see the picture of EXD3 if we try to run it as midi, but it ain’t midi, so there is no sound. And if we try to run it as a vst, it won’t even appear in Acids fx list. All of this is just my theory. Let’s keep digging sharing and we’ll soon crack this nut. I’m just beginning to learn that “ and I’m still not confident in my terminology” but  some DAWs  don’t “render back the audio” I think I read that somewhere. But don’t hold me to that. So, perhaps a wrapper may be the solution to Acids inability to provide audio engine access to EXD3.  I did know that wrappers can act as a host itself for even any ordinary vst like overdrive, reverb, delay, whatever, entire chains of vst’s to work as stand-alone effects . Where you don’t even need a DAW to use them. What great news for a guitarist. Imagine going to a gig and all the gear you need is your guitar, an audio interface (mine is a Behringer Uphoria UMC204HD , no bigger than a change purse, and a laptop and the house takes it from there. So, it stands to reason if a wrapper can make any vst operate as a stand-alone, it could also make and vst, vst3, operate inside a DAW. I’m likening the wrapper to a “conduit” that connects the “instrumental” type vst3’s audio engine’s audio needs, to the DAW’s audio access. Let’s keep digging and sharing.

Reply To: EZD3 Audio engine Inactive in ACID Pro 10 Suite version: 3.0.2
Operating system: Windows 10

[Author]

Replies