yes, you are right, 4k is available in Vegas 13. But many new video features added to Vegas14, joint work in 1 project with 4k and not-4k video. Thank you for link!

New promotion, Jan 18th-31st😀

https://diyvideoeditor.com/the-friday-roundup-vegas-pro-discounts-laws-of-light-and-editing-101/

Promotion is not valid for UPGRADES though , only for buying new full version ( new clients )

The current NetNotify when I open SVP13 (/older/SMSP13/SFAS10). Valid till Jan.26, $249/299/399 (Edit/Pro/Suite)-

New promotion, Jan 18th-31st😀

 

https://diyvideoeditor.com/the-friday-roundup-vegas-pro-discounts-laws-of-light-and-editing-101/

Thank you!

Wonder why nobody has mentioned this path:

https://support2.magix.com/customer/vegas/upgrade

for $249/299/399

Wonder why nobody has mentioned this path:

https://support2.magix.com/customer/vegas/upgrade

Do not wonder any more. The following was the 1st comment in this thread.

TheHappyFriar wrote on 01/20/2017

you get it directly from magix: https://support2.magix.com/customer/vegas/upgrade

 " many new video features added to Vegas14, joint work in 1 project with 4k and not-4k video."

I would like to know what those are....still on 13 here...no issues

am I the only one concerned about upgrading to Vegas Pro 14? I have the vegas pro 13 suite and worried about the update situation with version pro 14. I am a hobbyist and always felt teh Sony upgrades were fine and I dont even mind the upgrade of $350 dollars to the 14 suite but I am unsure about the update situation between versions, as I understand it after 1 year you get no more updates unless you pay for them until the next version comes along. maybe someone can clarify as that tehthering to forking out more money is stopping me upgrading to pro 14. I am even more concerned that if I go for v 14 and have some event where I need to reinstall windows that then it would regress to the least stable version. I am very wary now to fork out money.

The gist of peter-b's comment is indeed to be read here and the question remains if any or all of what that page says is valid for the VEGAS line of products. Unlike the "old" Magix products, VEGAS is not even mentioned there.

Thanks for the link @vkmast it doesnt help at all as, as you say no mention of vegas product at all. I cant even see how much the update service actually costs either. I am obviously keen to maintain updates but I really would have thought that for an expensive product like these that updates were included. its like the worst of a joint subscription and upfront purchase cost all in one.

am I the only one concerned about upgrading to Vegas Pro 14?

I still have 10 and haven't upgraded past that. I haven't had a need to. I've thought about it though. The biggest difference between now & when I got 10 is my HDV camera recorder/playback isn't working properly so I got a mp4/whatever SD card camera now. Besides that there hasn't been anything I wanted to do that Vegas 10 + Blender doesn't do.

...the question remains if any or all of what that page says is valid for the VEGAS line of products.

Currently what that page says does not apply to VP 14 nor to the upcoming VMS 14. Both titles will continue to follow the same plan for updates that the software has for years and that VP 14 has already followed through several free updates since the initial release. In short, you will not have to pay for any update to VP 14 or VMS 14. An exception could be if we decided to charge for a ".5" update (VMS 14.5, for instance), but at this point I think that's not very likely to happen for VP. Maybe a bit more likely for VMS 14, but I can't predict that at this point. Whether we adopt the methods discussed in that page for a future version beyond 14 is also not known at this point.

Thank you for explaining the current policy.

I would not be too sure many will want to upgrade now that TitlerEX has been excluded from VMS14..

I would not be too sure many will want to upgrade now that TitlerEX has been excluded from VMS14..

It's included in the Suite version. [EDIT: This is incorrect. See here.]