VideoScribe v3.9 release notes

We’ve just released VideoScribe v3.9 and it’s now ready for you to download from your account page.

If you are upgrading from a version older than v3.8 please make sure you read all the release notes between your current version and v3.9 so you fully understand the changes.

Hindi and Arabic Font Support

We now officially support Hindi in VideoScribe! We currently have 9 fonts that support Hindi text. We’ve also made some updates to Arabic fonts too which means vowels and consonants and written out as they should be. 

  • Check out the supported fonts for these languages here

Image Library Updates

We’ve revamped our image library to make finding the perfect image for your project way easier. 

  • Have a look at the Searching the Image Library article for all of the tips and tricks when it comes to finding images quickly and efficiently. 

Introducing...Text Effects! 

We’ve added in some new effects to make your text stand out even more. We have four new styles that can be easily applied to your text as an alternative to your regular drawing style. These include Rain Drop, Punch, Fade Wave and Typewriter. 

  • To learn more about these styles and how to apply them to your projects, check out the article Text: Animation Styles

General performance and stability fixes

There are always lots of little improvements in every update to make the experience smoother, the most significant of these this time is...

  • Intermittent syncing issues when playing your project from a current element

Hope you like the sound of all these improvements! Here’s how you upgrade to v3.9…

If you’d like to upgrade to the latest release of VideoScribe, simply download and install it here. For detailed instructions on how to do this, please see the links below.

Download and install VideoScribe – PC

Download and install VideoScribe – Mac

--- Addendum for v3.9.1 - released 30th of September 2021 ---

We’ve released this update to fix an issue where some image preview thumbnails were not loading.

This is now fixed in v3.9.1