I had a troublesome ,scribe that would not render. While I'd seen references that said rendering issues are often connected to memory issues, I had no clue as to how to determine if this was my problem.
I know the answer was in a variety of places. But, I didn't find it until support told me how to check memory by opening up Task Manager and finding the VideoScribe application ("VideoScribeDe...").
As can be seen in the sample image, my .scribe pushed the memory usage to about 1.3GB. Apparently, at least for now, a preferred size is under 1.1GB.
Knowing this allows us to work on our zoom levels (Keep near 100% per view) and imported image sizes to reduce the memory requirements for better results.
The next version of VideoScribe (version 2.0.2) will be more memory efficient which will help too.