Sony VEGAS Pro

Version 13 of Sony VEGAS Pro; released: 11 April 2014

This is the last release shipped by Sony before the "Creative Software" line got sold to MAGIX.

Official status: superseded

Application Details:

Version: 13
License: Retail
URL: http://www.sonycreativesoftwar...
Votes: 0
Latest Rating: Silver
Latest Wine Version Tested: 4.0

Maintainers: About Maintainership

Test Results

Selected Test Results

What works


Video effects

Panning, Cropping, and Stretching frames

Importing MP4 video

Importing images

Importing WAV and FLAC audio

Third-Party OFX Video Plugins

Audio effects

Media generators (except using other fonts on Titles & Text)

Rendering as MP4 and AVI video

Saving & Loading

Project properties

Program Settings

Saving a PNG or JPEG snapshot of the video project

What does not

MP3 files can import but is unusable due to them sounding corrupted in Vegas.

Importing or Rendering WMV files.

Using fonts other than Verdana on Titles & Text Media Generator.

The Installer runs and completes, but does not actually extract files.


Winetricks used: corefonts d3dx10 d3dx11_42 d3dx11_43 d3dx9 directmusic directplay dotnet40 dsound msxml3 msxml6 quartz quicktime76 vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015

Windows Version: Windows 7 (Installing these winetricks verbs switches Windows version to XP which is not recommended for using Vegas Pro 13)

Override msxml3 set to Native then Builtin

Installed Vegas Pro 13 on a system running Windows then copied these folders to the Wine prefix:

C:\Program Files\Sony\Vegas Pro 13.0

C:\Program Files (x86)\Sony\Shared Plug-Ins

Prefix needs to be configured to use Virtual Desktop in order to make the "Render As" window usable. (It's completely black otherwise.)

What was not tested


Third-Party VST Audio Effect Plug-Ins

Rendering as anything other than MP4, WMV, and AVI

Importing as anything other than MP4 and WMV.

CD Ripper

DVD/Blu-Ray Burning


Some others I haven't thought of

Hardware tested


  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

64-bit Wine is required.

Surprisingly, very usable! Turns out it's much more reliable than Vegas Pro 8.

May be a deal breaker if you prefer working with WMV and MP3 files.

Vegas Pro 13 running on Wine is prone to freezing. Save often!

Important to note: If you have Magix VEGAS Pro 14 or later installed on your Windows machine before installing Sony Vegas Pro 13, copy the folder C:\Program Files (x86)\VEGAS\Shared Plug-Ins to get audio effects. Vegas Pro 13 installer knows that there are already audio effects installed and will not install them under "C:\Program Files (x86)\Sony\Shared Plug-Ins" if you have Magix Vegas Pro 14 or later already installed beforehand.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
CurrentKDE neonMar 09 20194.0No, but has workaround Yes YesSilverSergey Kononenko 
ShowDeepin Linux 15.8Dec 07 20183.21-stagingNo Not installable YesGarbageScy Productions 
ShowUbuntu 15.10 "Wily" i386 (+ variants like Kubuntu)Mar 20 20161.6.2No Not installable Garbagean anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Visual C++ runtime error
by MiMillie on Saturday March 23rd 2019, 5:44
i got this error when i lunch vegas pro
an application has made an attempt to load the c runtime library incorrectly please contact tge appliation's support team for more information.

i've installed all the workaround
all wine versions
and when i start any wine version i got a rundll32 error (when i restart my pc)
RE: Visual C++ runtime error
by Sergey Kononenko on Friday April 5th 2019, 17:37
The runtime error does show up and it only shows up once. If you get Vegas Pro 13 to launch the first time, you shouldn't see the runtime error the next time you launch Vegas Pro 13.

If Vegas Pro 13 crashes upon startup, it probably means you forgot to set the msxml3 library to Native then Builtin in winecfg. Have you tried that? Make sure that the Windows version is set to Windows 7 or later as well if it was set to Windows XP.