I'm even renaming all the the menu items, menu lists to be the same as Acid so everything feels like I'm still working in Acid. If you don't like, you can customize it to do what you want. Once I'm done doing that, Reaper will be just as easy to use as Acid Pro. #Plogue bidule program change event pro#So while Reaper currently has right click options reserved for itself, I'm turning every Acid Pro right click option into a double click button toolbar that pops up instead. Then you can make those toolbars context aware and pop up when you double click on an item. Every feature in Reaper you can assign to a button and create custom toolbars of those buttons. #Plogue bidule program change event how to#While at the surface and out of the box, I didn't like Reaper's user interface, I've gotten to know how to customize it to my preference and essentially at this point I'm creating a user interface that mimics Acid's while still having the solid performance of Reaper. I wish I could say the same things about Acid Pro but I can't, so I have been slowly but surely migrating to Reaper and getting to know the ins and outs of Reaper along the way. Try doing the same thing in Acid and while it's possible, it will take you 10 steps to do it. Things like if you want to render 10 tracks to a single track, alls I have to do is select those tracks and click on a button and it's done. It also has every feature you could want to allow working in it much easier without having to jump through hoops. It runs fast, efficient, most every plugin shows up and runs well and doesn't cause it to crash. What I do enjoy about Reaper is that it just works. I don't enjoy Reaper so much in regards to it's user interface. Waves uses a wrapper but SSL plugs are individual. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |