![]() ![]() A 3rd party producer uses my place quite a bit, and bring his huge Waves Mercury bundle with him.he's on V9. I have Waves SSL bundle, previously running V8. Hi - posted this on general, and osx forums.probably should have gone here. I will try the same with the Mac Pro, and then open the files on the other computer, respectively. If I save a project with one instance of East West Spaces on my Macbook, I can close it and open it again, and hurray, the settings are still there.Įdit: I've loaded 6 instances of Spaces in a project on my Macbook, and the settings appear correctly after re-opening Reaper. They both have OS x 1.6.8, but anyway, maybe Reaper didn't like that. Maybe the thing with Spaces was due to me opening a project that was originally set up on a Mac Pro on my Macbook, and then going back to the studio's Mac Pro. Reaper opens the first IR available in Altiverb instead of the one that was actually set through the user.Īnd Nebula 3 quit working after I had used it in Reaper, and doesn't work anymore now in Logic, too. I spent a day setting reverbs, and the next day none of them appeared. Reaper opens empty instances when opening a project again. OneKnob Phatter, Brighter, Driver, Louder, Wetter, Filter I've tried the v9 AUs in Ableton Live, and they load fine, so the problem seems to be in Reaper. If I take WaveShell-AU 9.0.component out of the library path and leave WaveShell-AU 7.0.component, the v7 AUs work, including those that didn't work in v9 (v7 is the last working one I have. But they don't lag in Reaper64 like previous versions. The VST versions work fine, but will only run in 32bit, regardless of which Reaper version. This happens on both 32 and 64 bit versions of Reaper. Now, I've installed Waves 9 and some of the AUs are crashing when I load them or previous projects that used them, others are fine. After switching to Reaper 32bit, everything was fine. ![]() I was using Reaper64, and the Waves AUs were only 32 bit, so it would only find them when I did a manual scan. I eventually worked out that original problem I had. The Waves as VST's load without my having to scan, but they're incredibly laggy. It works in the end, but a bit of a pain. but I have to do this every time I start Reaper, and before opening a session that uses them. My Waves AU's also stopped working, but if I do a Scan for New Plugins, it finds them. ![]()
0 Comments
Leave a Reply. |