Disclaimer: The following tips include solutions from previous threads combined with my personal recommendations which allow me to work without any problems in videoscribe. Here is a link to the official INSTANT ANSWER related to this topic : crashing-and-freezing-videoscribe-free-pro-and-edu
QUESTION: How can I fix or PREVENT crashing, freezing, slowdowns, problems opening, saving, or rendering scribes, or problems exporting or uploading video in VideoScribe? (Also: how can I avoid memory related problems like problems with the timeline?)
ANSWERS AND TIPS: (updated version focusing on videoscribe version 2) Most freezes, slowdowns and crashes probably result from excessive memory usage and can be avoided by using properly optimized images and moderate camera zoom settings, but here is a more detailed list of tips, suggestions, guidelines and workarounds:
1) Save a new copy of your scribe with a new name, and restart videoscribe.Save a copy of the scribe (your work file) with a new name and then restart videoscribe, and open the new scribe. This process MAY provide a TEMPORARY workaround and allow you to render a scribe or continue editing your work even if there are still other problems (listed below) that should probably be addressed. I only listed this tip first because it may be the easiest thing to try. Rebooting may also free up some memory and allow problematic scribes to render successfully.
NOTE: Videoscribe V1/V2 has a memory cap of about 1.7GB even if your computer has more memory than that: Link to thread mentioning memory limit
Link: how to import-and-export using Version 2
If the scribe is saved online instead of locally, you can download the scribe from your Sparkol.com account page https://my.sparkol.com/online-scribes and then import it into videoscribe. (NOTE: This process does not "FIX" everything wrong with a scribe, but it sometimes removes damaged elements, so that you can continue working on it.
3) IMPORTANT!!! Videoscribe works best if you optimize ALL of your images for good quality and small file sizes. If you don't know anything about optimizing images, a search on youtube or google may help bring you up to speed.
Properly prepared JPG and PNG images can usually be in the 1-250 KB range. If you are using images that are more than 1 MB then they are probably larger than necessary and may be causing out-of-memory problems. (the file sizes I provided are only a rough guideline.) For JPG and PNG images: the dimensions of the image probably do not need to be larger than the dimensions of the finished video. GIMP (free at gimp.org) and photoshop and other programs offer methods for saving images with smaller file sizes without noticeable reduction in image quality.
Here is a link to a scribe using an oversized JPG image and a smaller, better optimized version of the same jpg image. In this example the original image is so sharp and high contrast that it actually looks grainy in the scribe. Adding a little bit of blur and reducing the image size and the file size results in a better looking image that traces better, looks cleaner, and is less likely to contribute to memory problems:
The SVGs that work best in videoscribe can usually be less than 100KB and contain only stroked paths and/or filled paths. Larger SVGs may contain excessive numbers of anchor points or problematic data like masking or clipping paths, which can contribute to freezes or crashes. Delete hidden layers from your SVGs. (hidden layers increase file size. larger file sizes require more memory to process.) Also there are are some youtube tutorials that mention leaving embedded JPGs or PNGs or other images in your SVG files, but you should probably optimize such images first if you are going to embed them. Larger files may cause excessive memory use resulting in slowdowns, freezes or crashes.
Recommended SVG save settings for illustrator:
NOTE: select "embed" instead of "link" if you are embedding an image in your SVG (optimize the image before adding it to your SVG!)
Related link: How can I make SVGs that draw well in videoscribe
NOTE: SVGs made with illustrator creative cloud may appear solid black (or exhibit other odd symptoms in videoscribe as a result of some newer formatting that videoscribe does not recognize. Here is a solution in: a related thread
4) Avoid very large very fast camera movements or extreme zoom in/zoom out between elements. If you are experiencing a freeze and you have at least one huge camera movement, try reducing the camera's travel distance by moving the elements closer together and/or scaling the elements to similar sizes, or slightly increasing the transition time for that camera move. If your images are very spread out then the final zoom-out-at-end may be so extreme that it causes a problem. Grouping elements closer together into a roundish blob may be better than spreading them out in a long line.
5) Things will probably run more smoothly if you keep your camera zoom approximately in the 15%-500% range for EVERY element. After you add any element, immediately click "set camera" then scale or move the element as desired. You can set the camera again if needed. Do this for every element you add in order to avoid accidental zooming which may become worse with each element. (when you zoom in and out, you should see a little blue tab in the lower left corner of the canvas showing your current zoom level.) You MAY be able to zoom in to 1000% or more before seeing problems, but I wouldn't recommend it. (percentages mentioned here are only estimated). LINK to camera setting tips
6) Some previous threads have suggested that very large blocks of text may cause problems. If you have paragraphs of text, then breaking the text element into 2 or 3 smaller elements may help.
7) ASK SUPPORT for specific feedback: If you are not able to resolve the problem and you have already checked the INSTANT ANSWERS page for known bugs or solutions to common problems, you can save the scribe online, and Raise a Ticket to contact customer support providing the name of your saved scribe. Describe the symptom you are experiencing and ask customer support to take a look at it.
8) in all versions, if you have insufficient hard drive space, your video may fail to save. I believe even videos being saved directly to youtube, must first save a copy on your hard drive.
9) Some users have reported problems rendering WMV files, or uploading directly to facebook, youtube or powerpoint, but not other file formats. Try rendering to MOV or FLV instead (requires a pro membership)
10) If you have imported many fonts, try deleting the ones you aren't using. More imported fonts take up more memory. Some fonts may use more memory than others.There may be cases where fonts with unsupported special characters cause problems.
11) If your video rendering repeatedly freezes at the same part, and you've already tried restarting videoscribe and optimizing your images and making your camera settings moderate, I'd suggest deleting that image and maybe the image after it, and then importing them back in.
12) I believe that higher image import quality settings require more processsing power and memory. The maximum setting is 4000. I'd suggest 1000 or less.
13) Sometimes a corrupt image may cause the timeline to appear blank.
To solve this:
1. Select all the items on the canvas - CTRL+A
2. Copy all the items - CTRL+C
3. Close the scribe and open a new, blank scribe
4. Paste all the items into the new scribe - CTRL+V
All the items should re-appear along with all the items in the timeline. You may find that there is a particular image that appears blank in the timeline or is really small on the canvas. You should delete this item.
-Mike (videoscribe user)
Fabulous, Mike! Thanks for pulling this all together!
(thanks for the nice feedback, Dave!)
15) Sometimes deleting the audio (voiceover or music) will allow you to to render the video or save the video even if you were unable to render or save before. Possibly because it frees up a bit of memory on scribes that are pushing the limit, or possibly because of problems with videoscribe locating the sound file. You may be able to immediately re-add the audio file before rendering successfully. Otherwise, you could use a video editing program to add the audio back in after rendering.
16) in some cases SVGs may contain data that can cause certain videscribe functions to stop working. This can include strange visual issues in the timeline, failure of keyboard commands like arrow keys, cut and paste, or other issues. related link: http://help.videoscribe.co/support/discussions/topics/1000067878
saving with the recommended settings should prevent the problems, or running problematic SVGs through SVG Cleaner.
(this message has been deleted and resubmitted with some editing)
-Mike (videoscribe user)
17) Elements seem to be missing or appearing in the wrong locations: Ongoing bug in versions 2.3.2 2.3.3 and 2.3.4 (possibly other 2.x.x versions as well)
Symptom: If you use a "move-in" (or possibly "morph") as your animation type, with a zero second animation time, elements may not appear in the correct location in rendered video. I don't know if the symptom has been explicitly explained anywhere, but my guess is that the elements get stuck at the origin position of the move-in (the starting point from which they are supposed to move in). This means that they are off-camera when it is time for them to appear and they may end up in the path of the camera as it continues to move around the canvas later in the scribe.
(Additional symptom: In some versions, if you have an element with a zero animation time, the timing of subsequent elements may also be affected unexpectedly in the rendered video.)
Solution: If any elements have an animation time of zero seconds change the element's animation type from "move-in" to "draw"
and/or increase your animation time to some amount of time greater than
-Mike (videoscribe user)
Just a note to support Mikes number 3 which is probably one of the most common causes of crashes - There are a number of free tools you can use to optimise your images which are outlined in a post on our blog entitled 9 Free tools to pimp VideoScribe.
Very nice, Mike, thanks for the work you put into this!
Just to clarify.
2.3.6 fixes a bug where you have an element set to Move-in that has a zero second animate time. It can appear in the wrong place or not appear at all on the rendered video. 2.3.6 can be installed using the following links.
2.3.6 still contains a bug where a text element with a 0 second Animate time is followed by another element that has 0 second Animate time. Any pause and transition time are ignored for the first element on the rendered video. A workaround for now is to add 0.1 seconds to the Animate time and remove the hand, of either element.
I find the software really unstable. I have lost hours upon hours of work due to the software not letting me save, it often crashes when playing back a scene, the images freeze but the audio keeps on going. It's all very frustrating. I am using a Macbook Pro 2004 so I would be surprise if it were my computer causing the issue!
The recover feature does not work either, it recovers the piece of work but recovers it in a way that you cannot use it anyway as the frames are missing from the animation! Is it something I'm doing?
Saving issues are sometimes the result of an error in the soundtrack and it is preventing the save. If you have problems saving the scribe, try removing the soundtrack. Then add another soundtrack from the soundtrack library - choose a short one e.g. Adrenaline Junkie, which is the first one in the list. Click on the tick in the add soundtrack window and then you should be able to save using the tick icon. I have attached a video here that shows you.
Now you should be able to save the scribe.
Disabling the auto-save sorted all my bugs/frozen screen.
Unfortunately I cannot render the video.
The staff at VideoScribe explained (to check on my task manager): "If the memoryusage is getting above 1.2GB then this is where problems can start to happen (VideoScribe cannot use the full amount of a computer's RAM). If you are already near this limit and you try to add more elements then this will tip it over the edge of the memory limit."