VEGAS Pro 15 release date


TheDingo wrote on 7/16/2017, 9:36 PM

>>>By the way, I think there may be many other reasons to upgrade to VP15 ...

Of course, but I see that several Vegas Pro competitors have already upgraded their software to be able to work with GH5 10-bit files.

GH5 10-bit files have been available since January 2017 ( months before the camera actually shipped at the end of March ), but it really looks like MAGIX sat on their hands when it came to adding compatibility for this new 10-bit format. The GH5 is a huge deal for professional video work, and part of that is it's new 10-bit 4:2:2 internal recording ability.

I also know that there are going to be some new professional cameras coming out a few months AFTER Vegas Pro 15 ships, and these cameras are going to introduce new file formats, but now I'm wondering if I will be forced to wait for Vegas Pro 16 if I work with these new cameras.


BruceUSA wrote on 7/17/2017, 10:04 AM

I really hope I am not forced to upgrade to Vegas Pro 15 just to be able to natively edit GH5 10-bit video files. I've been using Vegas since the days when Sonic Foundry owned it 15 years ago, but I am a little p*ssed that MAGIX has been dragging their feet about enabling GH5 10-bit compatibility.

So far I've been getting by with transcoding my GH5 files to another CODEC, but what happens when other cameras like the Canon C200 or the Panasonic EVA1 come out after Vegas Pro 15 is released ?

Am I going to have to wait until Vegas Pro 16 is released to open files shot with these cameras so MAGIX will have guaranteed Vegas Pro upgrade sales ?

1000% agree. Magix is dragging their feet and did not seems to care much about. The requested for supports for GH5 for along time now and still have not giving us GH5 10 bit update. Perhaps they knew exactly of what is in they plan. VP15 supports GH5 10 bit which means will forced VP14 users to upgrade which will be fine with me. In the means time I just have no choice but to transcode my GH5 footages.

Intel i7 12700k @5.2Ghz all P Cores, 5.3@ 6 Core, Turbo boost 3 Cores @5.4Ghz. 4.1Ghz All E Cores.                                          

MSI Z690 MPG Edge DDR5 Wifi                                                     

TEAMGROUP T-Force Delta RGB 32GB DDR5 -6200                     

Samsung 980 Pro x4 Nvme .M2 1tb Pcie Gen 4                                     

ASRock RX 6900XT Phantom 16GB                                                        

PSU Eva Supernova G2 1300w                                                     

Black Ice GTX 480mm radiator top mount push/pull                    

MCP35X dual pump w/ dual pump housing.                                

Corsair RGB water block. RGB Fan thru out                           

Phanteks Enthoo full tower

Windows 11 Pro

jurgen wrote on 7/17/2017, 1:24 PM

I rather have the magix team working on vp15 than to put more effort and time in vp14. Maybe it's not that simple to integrate those files with that old architecture of vegas. The magix team isn't a 100 man force and in the past we had to upgrade several times to get file support for some formats. You don't expect to be able to render xavc in vegas 9 or so either. Every software needs to be upgraded from time to time, that also keeps the funds coming for improvement. Nobody can work for free these days. I have always bought new versions of vegas the moment they were released, using it on a 36core 72 threads xeon pc with quadro graphics. I have had really very few problems and I use a lot of third party plugins and over 300 clips in about every project all the time. I never use GPU and I have great editing en rendering speeds, even when vegas is only able to use a few of those cores available.. I'm very curious about 15 and the moment it will be released, I'll give it a try.

TheDingo wrote on 7/17/2017, 2:24 PM

>>>I rather have the magix team working on vp15 than to put more effort and time in vp14.

I agree when it comes to new features in VP15, which I am happy to pay for if they help me be more productive.

...But not supporting new video cameras means that I am forced to use a Vegas competitor product to work with the 10-bit footage that I shoot now. ( I've been working with Vegas for 15+ years so far )

Right now I am going to see how Vegas Pro 15 compares with DaVinci Resolve 14, because there is not much difference in price between a VP15 upgrade and buying a brand new copy of Resolve 14.

I also want to see which company is going to support Canon's new C200 RAW-Light formats and the Panasonic's new EVA1 400 Mbps 10-bit formats ( the GH5 will also be getting the new 400 Mbps 10-bit format by end of Summer ) because both of these cameras are coming out later this Fall, and I expect they will be popular with many professional video shooters, including me.

heg wrote on 7/18/2017, 9:33 AM

Great news! Thanks... counting the days

vjsouza wrote on 7/18/2017, 9:42 AM

Hey, I was a Beta Tester of Sony Vegas Pro 13. How can I be a Beta Tester of Magix Vegas Pro 15?

oliverSpain wrote on 7/18/2017, 10:31 AM

Always the same. Now we present new functionalities, while the same inherited problems continue to exist. Cuda does not work well and other issues already mentioned in this forum. This time I will not update quickly. I still remember when it was said that Vegas Pro 14 was the future of the new edition:

TheDingo wrote on 7/18/2017, 10:40 AM

>>>Cuda does not work well

Vegas Pro is built upon the open-source OpenCL framework and works best with graphics cards that fully support OpenCL. CUDA is a closed proprietary framework that nVidia controls. If you want the best Vegas Pro performance use a graphics card with the best OpenCL performance, and right now that is AMD graphic cards.

At least you will be able to download a free VP15 trial to see if you like it before upgrading.


mateuszszar wrote on 7/19/2017, 5:14 AM

Please, add LUT native support... (Vegas plugin with LUT full control).

haritol wrote on 7/19/2017, 4:37 PM

Will it be available for Mac? that will be the REAL news.

wilri001 wrote on 7/19/2017, 5:01 PM

This is always good news....but I can only cross my fingers that the dreaded 'black screen' issues have been resolved. I've been struggling with them since version 11 and hope that version 15 will nip it in the bud. For anyone that has had this issue, or has solved this issue, here is the post I have been trying to get answers to.....thanks to all that take the time to reply.


I know many of you have experienced the black preview screen, which leads to the blank rendered screen. I've tried all the fixes I can find online, including switching off hardware acceleration on my video card and switching 'close media files when not the active application'.....etc. None of these fixes work. In my case, the project seems to be moving along very well, the on a dime, just stop previewing properly. Ironically, some clips will continue to work while most will not. But the condition can worsen and include 70-90% of my clips. No issues with audio when this happens. This started in Sony Vegas Platinum 12 for me. I upgraded to version 13, and then Magix Movie Studio Premium 14. I've experienced this problem in each version. Can anyone offer some shreds of hope as to how this problem can be overcome? I found nothing on the Sony site back in the day and I see nothing about it on the Magix site now.

Any help will be greatly appreciated. Thank you so much!

I had this, and it was just a matter of turning video back on. There is a row at the bottom of the time lines to turn ALL video tracks on or off. Somehow, I accidentally set it off. It drove me crazy until I saw this little line at the bottom.

pierre-k wrote on 7/20/2017, 5:20 AM

Please. Vegas Team has to write what specific GPU and Processors are fully supported in Vegas 15 (acceleration preview and render)

For example
Nvidia GTX450 - 980 - yes
NVDEC / CUDA - yes, NVENC - no
AMD RX 380 - RX 560 - yes
Quicksync for acceleration preview - no (only render)

Buying hardware and hoping for success is nonsense. Team can no longer write GTX450 and higher because it's not true! Thanks.

Last changed by pierre-k on 7/20/2017, 5:27 AM, changed a total of 1 times.

PC Desktop 1

Win 10 21H2

Intel i7 13700k, igpu UHD 770


Nvidia Gtx 970


PC Desktop 2

Win10 21H2

Intel Xeon 3,4Ghz

Dram 16GB

Nvidia GTX 970

VMP wrote on 7/20/2017, 7:40 PM

Here is hoping that Acid Pro 8 release news will follow soon!

jeffrey-g wrote on 7/21/2017, 7:23 AM

Oh great and I just bought VP14 Suite just yesterday!

cadudesun wrote on 7/21/2017, 3:14 PM

Considering "Editing speed efficiencies" improvements, please, add a way to close an undocked window (e.g. event fx, event pan/crop windows) using a single keyboard key. I think ESC key would be perfect.

Currently, to close a window you need to use the mouse and click on the X button. Really time consuming.

Thanks for considering it.

OndrejPopp wrote on 7/21/2017, 3:27 PM

Oh great and I just bought VP14 Suite just yesterday!

Yeah, I might have as well but I found out about this thread just in time... However on Facebook I saw Vegas creative software talk about personal upgrade offers, so maybe they will give you a special deal for VP15. I left a message there mentioning the fact that Sony net notify still offers upgrades to VP14 until the 24th of August, which is of course what it is considering the release date of 28th of August for VP15...

altarvic wrote on 7/21/2017, 3:59 PM

Considering "Editing speed efficiencies" improvements, please, add a way to close an undocked window (e.g. event fx, event pan/crop windows) using a single keyboard key.

Also I would like to switch between several effects using the keyboard:

frankie wrote on 7/22/2017, 1:28 PM

Just installed Radeon Vega Frontier Liquid Cooled editions on two different new builds. Both have same problem with color saturated in blue with GPU acceleration on. Had same effect using either Vegas 13 or 14. Found that others had same issue with no fix. Output render had same problem thus it wasn't just preview. Vega Frontier will only work with GPU off. Hope Vegas 15 solves this problem as well

daniel-rimon wrote on 7/22/2017, 3:11 PM

WOW Cant wait.


Since the first versions, there was a big problem in designing the credits titles, for example for me that I write in Hebrew, I am required to write backward. I ask to arrange a right-to-left writing option as well as advanced formatting options, it should be noted that the format has never changed.

Another thing that is very important to me is a function called "puppet tool" that exists in After Effects.

Last thing, designing titles in 3D, the titles in the software are very outdated, you should update titles, effects and video transitions. Add as much as possible.



Moyeen_Ahmed wrote on 7/23/2017, 1:43 PM

any kind of native support for TRACKING MOTION feature will be highly appreciat. Very excited for the next release..... looking forward..... 😍


GiulyProd wrote on 7/26/2017, 6:29 AM

Vegas isn't a VFX Software and it will never be After Effects. it's worrying if you doing tracking with Vegas...




- Multi Sequences possibilities with Tabs.

- Easy and intuitive folder interface for our rushs.

- Darken interface ...

- in the Crop / Resize windows : NO KEY POINT TO THE FIRST IMAGE BY DEFAUT

- in the Crop / Resize windows : Possibility to zoom out much more than actually

- Possibility to create effect layer (for color grading)

- Simple option (right clic) to relink media offline

- WORKING compatibility with .pproj

Thanks <3

set wrote on 7/26/2017, 6:43 AM

Thanks for suggestions... just my thought about one of your requests:

- Multi Sequences possibilities with Tabs.

Vegas Pro software allows you to run multiple applications at once (except for Steam edition). And you can import any .VEG file straight to other timeline. (Nesting sequence)

Jam_One wrote on 7/26/2017, 10:32 AM

1. It's OK to do Tracking with Vegas with Boris RED in it.
And with all other BorisFX plugins that incorporate Mocha as well as Boris's proprietary tracking.

2. I always create "Effect layers", in my each & every project.
It's very simple "stunt to perform" by adding effects behind the [COMPOSITE] (or dragging/pushing [COMPOSITE] to the left, ahead of all the FX in the chain).


...Keeping fingers crossed Vegas will not turn into a mutant "dinocroc" of sorts... 😉

Last changed by Jam_One on 7/26/2017, 10:38 AM, changed a total of 3 times.

Win 7 Ultimate | Intel i7-4790K @ 4GHz | nVidia GTX 760 4GB * 2

SSD | 32 GB RAM | No Swap file | No Overclock | GPU-in-CPU OFF

t.A.T.u. F.o.R.e.V.e.R.!


RedRob-CandlelightProdctns wrote on 7/27/2017, 1:08 AM

I rather have the magix team working on vp15 than to put more effort and time in vp14.

Bug fixes are bug fixes, and how easily they can be implemented across software versions is really just a question of how version control/branching is managed.

For instance, adding support for a new CODEC I would think is a portable enhancement due to the modular I/O design, which could fairly easily be ported as a fix to older versions of the software as well as go into the new version.

Vegas 20.214

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 32GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio