![]() Kind of odd since I was testing them all with the 64bit hosts. I found the majority of problems seemed to be with VST2圆4 and VST3圆4 plugins where the VST2x32 bit version seemed to work more often than not. Magix needs to start doing some serious work on plugin compatibility and making these hosts more robusts. What was most eye opening was that I had 1 plugin (Antares Auto-tune) which didn't show up in Reaper which showed up and worked in the Magix apps but I ended up having a much longer list of plugin troubles in regards to the 3 of the Magix apps. Here is the composite list of troublesome plugins I ran into, it unintentionally turned into plugin compatibility test. I went from pointing fingers at the plugin developers to now focusing more on the Hosts. This made me do a 180deg perspective change on where the problems reside. What I soon discovered was that there were quite a few plugins which either didn't show, crashed, or run buggy in the Magix/Sony apps and when I tried those same plugins in Reaper they worked fine. Originally, I didn't have Reaper in my game plan, especially since this meant I would have to organize my plugins in it's plugin manager for a 4th time and learn another program's workflow. I kept running into frustrations with plugins and crashes while working with Acid Pro, so I started to migrate to Reaper. I originally chalked these problems up to "trouble-some plugins". ![]() Vegas Pro doesn't support VST3 plugins so that was a wash on that front. This was all going pretty good until I got to the point of setting up AP10 where I was finding a lot of plugin problems, not showing up, crashing the app, presets not showing/working, etc. Then when I tried them out I started to notice some versions worked and some didn't so then I started to mark the plugins which didn't seem to work in each app. That was my original intent of the excel document, just a way to keep my categories consistent between each app. Although Vegas, Acid and SF all have plugin managers they don't have a way to share plugin manager organizations between them, so I had to do these organization efforts x3. I started off by creating an excel document listing the name of each plugin, trying each plugin out and then categorizing it within each apps Plugin Manager. My original thinking was that between Vegas Pro 18, Acid Pro 10, and Sound Forge Pro 15, combined they will handle most tasks I do and since I'm most familiar with them, I'll stick with them. Configuring preferences, installing VST plugins, organizing those plugins in the Plugin Manager by categories. For the past few months, I've been setting up my PC.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |