Hello,
I've struggled with this problem for hour now (2014 Macbook Pro Retina 15"), while trying to debug based on what I know from experience, combined with the crash reports.
The ONLY thing that worked for me, was opening the Macbook lid before starting iMovie. It still works after closing it again though.
- The webcam/Facetime video source is not available in "clamshell" mode. iMovie's initial dialogue & first responder is the command "Import media". It could be an inconsistency bug that occurs if no camera/live video source can be found even though the iMovie startup hardware check reports otherwise, proceeds to kickstart the Quartz filters and import mechanisms etc, and..yeah, you get the idea.
- From what I can recall, I had the Macbook lid open (i.e. not in clamshell mode) the last time I used iMovie, literally ages ago. Even though I'm pretty sure I deleted every preference file, it is not unlikely that this specific configuration is "forced" on the subsequent iMovie launch.
- On top of that, if you add the fact the Photos database was upgraded while installing High Sierra (and with that, also the structure of your files inside the photo library, which ultimately is critical with regards to the import/export procedures in iMovie (and other apps, of course).
Even though it appeared to work flawlessly after I opened/closed the MB lid - just to be on the safe side, I quit iMovie, and relaunched it while holding down ⌥ , and (when prompted), I chose to create a completely new iMovie project library.
- When was the last time the app/software worked without any problems?
- Is there any minor/major differences in hardware or system configuration, compared to before?
- The first, perhaps obvious thing to try, is to wipe the preference file(s). However, if it doesn't help, try to "reverse" it (by making sure the preference files are exactly the same as the last time it actually worked).
Come to think of it, that's pretty much the spirit of any emulator software out there. You actually "trick" the software into working, circumstances where it shouldn't (and in most cases, on completely different hardware - but that's another story).