If anyone has any suggestions of things to try, workarounds, places to look, a "it's going to be OK," etc. Of course I want IK Multimedia to fix this on their end, but it does appear that there's something about its interaction with Reaper that is a poison pill. Tried a clear cache and rescan- now VST3 version of A5 is no longer listed in plugin list, regular VST version is, although I noticed that the "plugins that failed to scan" contained the regular VST version of A5- at least, it didn't say VST3. Unfortunately, it wasn't doing that when I first loaded it on lots of tracks in lots of projects. 1 track with 1 plugin! So it's not like I'm overloading my machine here- there's something really wrong with the VST3 version of A5. so I deleted the A5 instance and then added the VST3 version of A5 on the track- Reaper crashed to the desktop immediately. Obviously, I'm not excited about the idea of text-editing half of my project files and then finding new amp sims for all of those tracks.ĭid an experiment where I started a new project, inserted a track and inserted A5 in the FX. Sadly, this no longer works and all projects with A5 will crash.
I know a lot of this rests on IK Multimedia, but I'm three days out from filing a ticket with no response, and from what I've seen in forums, it appears that a lot of other DAWs don't have this issue so there's a reaper component as well.Ī month or two ago projects with Amplitube 5 started crashing on load (it would get to a track with A5 on it and then immediately exit to the desktop) I found a workaround by starting the standalone version of A5 first, and then opening the project.
I've seen some posts about similar issues elsewhere in the forum but thought I'd post my own experience here.
0 kommentar(er)
