![]() 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 SVGs may contain excessive numbers of anchor points or problematic data like masking or clipping paths, which can contribute to freezes or crashes. The SVGs that work best in videoscribe can usually be less than 100KB and contain only stroked paths and/or filled paths. 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: In this example the original image is so sharp and high contrast that it actually looks grainy in the scribe. ![]() Here is a link to a scribe using an oversized JPG image and a smaller, better optimized version of the same jpg image. GIMP (free at ) and photoshop and other programs offer methods for saving images with smaller file sizes without noticeable reduction in image quality. (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. 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. Properly prepared JPG and PNG images can usually be in the 1-250 KB range. If you don't know anything about optimizing images, a search on youtube or google may help bring you up to speed. If you have Version 2 export/import instructions: import-and-export using Version 2ģ) IMPORTANT!!! Videoscribe works best if you optimize ALL of your images for good quality and small file sizes. Then import it back into videoscribe which will force the program to check for errors. If you have version 1, close the scribe, right-click the thumbnail image in the locally saved scribes directory and choose "export to file". If a scribe or element actually becomes corrupt, and you cannot open or render a scribe, you may be able to identify and remove the damaged element(s) by exporting and then importing the scribe. If you have one or more problematic elements in your scribe, they can cause a crash or prevent the scribe from rendering or saving properly. Other problems mentioned below may result in one or more damaged or faulty element while working or saving. Rebooting may also free up some memory and allow problematic scribes to render successfully.Ģ) Possible workaround for a scribe that won't open: ![]() I only listed this tip first because it may be the easiest thing to try. ![]() 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. If you use Version2, just save the file with a new name (If you have Version1 use the "save as a NEW copy and close" option) and then restart videoscribe, and open the new scribe. Most freezes, slowdowns and crashes probably result from excessive memory use 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:ĮDIT: At the time this was last edited, version 1.3.26 and version 2.0 through 2.0.3 are the supported versions of videoscribeġ) Save a new copy of your scribe with a new name, and restart videoscribe. QUESTION: How can I fix or PREVENT crashing, freezing, slowdowns, problems opening saving or rendering scribes, or exporting or uploading video in VideoScribe? (Also: how can I avoid memory related problems like problems with the timeline?)ĪNSWERS AND TIPS: (The numbering of the tips may have changed slightly in recent edits.) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |