poetnprophet
If I don't resolve these crashes with CbB I'll likely switch to Reaper. Although I have heard Reaper is un-crashable....I was able to crash it on my first try. Maybe it's just me...?
As any other DAW, REAPER by default run all plug-ins inside itself, following general rules for dealing with plug-ins. Plug-in can do anything: crash or corrupt memory, freeze, generate under-runs, etc.
But unlike in other DAWs, in case you have such plug-in and have a reason to continue using it, REAPER has a plenty of compatibility options you can tweak. Also the diagnostic of what is the problem is top.
Jesse G
My main question is, how is Reaper with 3rd party plugins, especially Wave Plugins.
I have a hows of Waves Bundle and plugins and they need to work in Reaper.
I watch some videos on YouTube about folks having to create alternate ways of getting the plugins working right in Reaper. Has this been addressed in any of the updates this year?
REAPER keeps track of known plug-ins in simple text files (the same for settings and projects). Waves is known for fancy compatibility issues since unlike most other suppliers they use a "shell", which basically is responsible for authorization (any company except Cockos, since several years including CW, assumes that any consumer is a thief).
Recognition problems are normally solved by manipulating these files, usually just delete and re-scan, in worse cases by editing.
REAPER continuously improve plug-in compatibility (which always was good, but there are always things which can be done to workaround plug-in bugs). This year is not an exception.