some fx plugins not working

AJF wrote on 2/16/2021, 4:38 PM

I just purchased Acid Pro 10 and I like it very much, however many of the fx plug-ins that came with it will not work. Some work, but many others do not. When I try to acces them and apply them to a track, I get the message:

"The plug-in could not run. One or more of the components required to run this program may be missing. If a harware key (dongle) is required to operaate this plug in, ensure that it is properly installed. The COM object failed to initialze."

I honestly have no idea what any of that means. Why include the fx if they do not work? Does anyone know how to fix this? Thank you!

Comments

Former user wrote on 2/16/2021, 6:00 PM

AJF, Yes, AP is a very likeable and a unique DAW however, I have written about this in many posts that the Magix plugins are still very buggy. I am not sure if Magix is still working on that issue but if you start to experience crashes, uninstall any additional packages you may have downloaded along with Acid Pro.

I would recommend going back to your Magix account, re-download the packages and give it one more try re-installing. The only other possibility would be, depending on which version you bought, some plugins may be "suite" exclusive. I own a pro version so there are plugins/synths that will be in Demo version.

AJF wrote on 2/17/2021, 2:26 AM

Great, thank you. Yes that is unfortunate. I bought ACID PRO 10 (not suite), so that could be it. I will try reinstalling it again. Would I lose my current projects if I did that?

Frank_Fader wrote on 2/17/2021, 4:32 AM

Please contact our support. We had some reports like that, and our support could find a solution for them.

AJF wrote on 2/17/2021, 5:57 AM

Okay I will, thanks!

Peter-Elfman wrote on 2/18/2021, 10:35 AM

I just purchased Acid Pro 10 and I like it very much, however many of the fx plug-ins that came with it will not work. Some work, but many others do not. When I try to acces them and apply them to a track, I get the message:

"The plug-in could not run. One or more of the components required to run this program may be missing. If a harware key (dongle) is required to operaate this plug in, ensure that it is properly installed. The COM object failed to initialze."

I honestly have no idea what any of that means. Why include the fx if they do not work? Does anyone know how to fix this? Thank you!

Hey, AJF. You should definitely listen to Aman and Frank above. Additionally, I have learned that there are a TON of free plugins out there that are absolutely great, and should fill whatever need you have. The only Magix plugin you actually need is the efx_Compressor, which is required to do any sort of sidechaining in Acid (at this time, Acid doesn't inherently support that otherwise). The Bedroom Producer's Blog (https://bedroomproducersblog.com/) is a great place to start if you need one.

AJF wrote on 2/18/2021, 4:39 PM

Yes, thank you! I was looking for a place to find new plugins, so thanks for the great link. I have not even begun to figure out how the sidechaining feature in Acid works yet -- though I am very intrigued -- but am loooking forward to using it. Also I emailed the support team and they have sent me an email back asking which plugins are not working, so I hope the problem will soon be reolved. Thanks again!

Former user wrote on 2/18/2021, 7:57 PM

Thanks Peter. I am gonna look at those myself.

Peter-Elfman wrote on 2/18/2021, 8:24 PM

Yes, thank you! I was looking for a place to find new plugins, so thanks for the great link. I have not even begun to figure out how the sidechaining feature in Acid works yet -- though I am very intrigued -- but am loooking forward to using it. Also I emailed the support team and they have sent me an email back asking which plugins are not working, so I hope the problem will soon be reolved. Thanks again!


I'm happy to help. I'm getting into this stuff just in the last few weeks, and it's been quite a challenge to learn about all of the program's capabilities on top of learning the skills to use them. Sidechaining is actually super easy once you know how to do it. It's plugin specific.
Essentially, you can throw a Compressor or Limiter on a track, and instead of having the plugin react directly to that track's signal, it can "listen" to another track in your song and use that as the basis for it's Compression/Limiting. So for example, side chain a long, held note to your 4 on the floor kick drum, and you can get that sustained note to rise and fall with the beat.

Load your plugin into the FX chain, and right-click on it. If that plugin supports sidechaining, you will see "Sidechain Input" in the menu. Click on that and a list of viable tracks will appear. You can only choose one; this will be the source. In the plugin itself, there's should be a SIDECHAIN or SOURCE toggle, that lets you flip between internal/int (the track hosting the plugin) or external/ext (the source it's listening to). Flip that to 'external' and twiddle the knobs to your heart's content.

Again, not all plugins support this feature, so you'll have to experiment.Also, currently I'm trying to figure out how to use a MIDI track as a source, but it looks like I can't.

Let us know how it works out!

AJF wrote on 2/19/2021, 5:17 PM

Very helpful, thank you! Yes that does sound like an awesome feature, and not as complicated as I thought actually. I will definitely check it out. It would be good if you could use it with a midi track. I tend to do more atmospheric music than beats, per se, so I wonder what way I could use it -- with no kick track for exmaple.

Peter-Elfman wrote on 2/19/2021, 6:49 PM

Very helpful, thank you! Yes that does sound like an awesome feature, and not as complicated as I thought actually. I will definitely check it out. It would be good if you could use it with a midi track. I tend to do more atmospheric music than beats, per se, so I wonder what way I could use it -- with no kick track for exmaple.


The only work-around I have found is to render the desired source MIDI track into an audio track (which can be done with one click, thankfully), and use that. I'm loathe to do that, though, because it removes any flexibility with adjusting the MIDI track for use in production.

AJF wrote on 2/20/2021, 10:42 AM

Very Interesting! I managed to use the sidechaining on the midi track of a pad, for example, and link it to a kick track, and yes it is totally amazing, sounds awesome. When I tried to render the track as a wave file, it is only about a minute track, it said it would take 30 mins tho! Is that normal? Is it better to run it all through a bus or something and then render it? Not sure how it all works, still a newbie. I imagine there is a thread on rendering here already somewhere...

Peter-Elfman wrote on 2/21/2021, 3:13 AM

Very Interesting! I managed to use the sidechaining on the midi track of a pad, for example, and link it to a kick track, and yes it is totally amazing, sounds awesome. When I tried to render the track as a wave file, it is only about a minute track, it said it would take 30 mins tho! Is that normal? Is it better to run it all through a bus or something and then render it? Not sure how it all works, still a newbie. I imagine there is a thread on rendering here already somewhere...


30 minutes to render a single minute of music? To what file type are you rendering, and what settings are you using? Also, what is your workstation build? (operating system, rough processor and memory count, etc). That feels like an excessively long time, but if your machine is old enough, it might just be the real deal. I have a recently made powerhouse of a computer, and it takes a complex, 8 minute long song to render in about 4 or 5 minutes; a less powerful machine would definitely take longer.

AJF wrote on 2/24/2021, 5:45 PM

Thank you. Well I figured it out. If I open the program and render right away, it only takes 30 secs to render a complex track with sidechaining. But if I play the track first, then try to render it, it says it will take 30 mins and my fan kicks on highspeed, and the number just keeps going up actually and I have to kill the program with task manager. Really weird, not sure if it is a bug or if it only happens with a project using sidechaining. But if i just close the project and reopen it and render, there is no problem. Also magix support team has not responded about the plugins not working after asking me which ones do not work. I will have to send them another request I guess. None of the EQ ones work (aside from the one old school acid fx plug in) which is annoying, or the wah plug in either. oh -- and my laptop is intel i7 with 16 gb ram, so should be no problem there.

Peter-Elfman wrote on 2/27/2021, 11:29 AM

Thank you. Well I figured it out. If I open the program and render right away, it only takes 30 secs to render a complex track with sidechaining. But if I play the track first, then try to render it, it says it will take 30 mins and my fan kicks on highspeed, and the number just keeps going up actually and I have to kill the program with task manager. Really weird, not sure if it is a bug or if it only happens with a project using sidechaining. But if i just close the project and reopen it and render, there is no problem. Also magix support team has not responded about the plugins not working after asking me which ones do not work. I will have to send them another request I guess. None of the EQ ones work (aside from the one old school acid fx plug in) which is annoying, or the wah plug in either. oh -- and my laptop is intel i7 with 16 gb ram, so should be no problem there.

That sounds like the program us abusing you memory to the point it can't render quickly at all. It sounds like you found your interim solution; when you're ready to render, save the project, close it out, reload it, and render it from scratch. You might want to consider adding memory to your computer as a more permanent solution.