Hi Dave and thanks for your on going responses.
I seem to have resolved most of my Premiere Pro cc2018 issues.
This current “Crash Prone” cc2018 project was exported via Project Manager from another computer, which required me to upgrade from cc2017. From the beginning of my involvement, this project had issues, which I attributed to cc2018 and inherent new rollout bugs. Yesterday, I scrubbed my system, reinstalled Windows 10 Pro, and reinstalled only the minimal necessary cc2018 programs, as well as needed third party plugins. This did not solve the issue. In my panic, I exported a XML copy of the project, then downloaded Vegas Pro15 and imported the cc2018 project, which didn’t work, then the XML project which did not work. I then co-installed cc2017 and imported the XML which only made the issues worst.
In a brief moment of inspiration (even a broken clock is right twice a day), I opened the cc2018 project and also created a new project and copy/pasted objects from one timeline to another. In the new project I had no issues at all.
Bottom line, when receiving a project first thing is to create a new project and copy-paste one timeline to another…
Your suggestion on Resolve was considered, but I always have too much work to take time to learn a new NLE. Additionally, the “Node Based” learning curve would be very steep.
Have a great day and I’m sure I’ll continue to see your “If it ain’t broke don’t fix it” sage advice in the Creative Cow forums.
Joseph