Is Important Update to 17 a scam?

martin-g1565 wrote on 5/14/2021, 2:04 PM

So Matrix can get me to have to endlessly subscribe to it's versions?

I'm skeptical. I paid for 17 but after that stopped paying. I have learned to live w crashes to 17, which I use strictly for audioplays. Why the sudden concern from Matrix about Version 17's issues w Windows 10?

Comments

adis-a3097 wrote on 5/14/2021, 2:19 PM

Neo, that you?

martin-g1565 wrote on 5/14/2021, 2:34 PM

No, Martin, sorry.

jetdv wrote on 5/14/2021, 3:13 PM

First of all, it's Magix. Secondly, a recent Windows update was causing issues with current versions of Vegas loading some files correct. Magix graciously made the fixes needed to version 17 as well as version 18. It is not a "ploy" to get you to upgrade. It's a fix needed to resolve an issue caused by a Windows update.

Vegas Pro 18 is also available as a one time purchase as well.

martin-g1565 wrote on 5/14/2021, 3:59 PM

Fair enough. Apologies for my name dyslexia.

martin-g1565 wrote on 5/14/2021, 4:00 PM

Don't require 18 as I only use Vegas Pro for audio these days. But thank you, Magix!

Richard-Senften wrote on 5/14/2021, 5:45 PM

That's very friendly of Magix to offer a patch to fix compatibility for it software but it wont install and Magix doesn't seem to offer a standalone download. I'm getting pretty P###ed about being told to fix something but only given a broken tool to do it. They should at least give the option to opt-out or a direct download of the patch. I'm downloaded this crap 6 times and it crashes every time.

martin-g1565 wrote on 5/14/2021, 6:06 PM

Hmmm...Perhaps that's what they want--so the only option available to you is to upgrade. Otherwise, why support an old product? (Before any others attack--this is just commonsense.)

Mine's not crashing but I'm doing simply audio edits right now--no video. I assume that you're probably loading an existing video timeline, yes?

VEGASDerek wrote on 5/14/2021, 6:19 PM

I obviously cannot change your opinion if you truly think we are scamming you. I can tell you that it takes a lot of time and effort for us to resurrect a old version of code to do an update like this. We very much dislike doing it because it takes a lot of engineering and test resources away from fixing bugs in the currently shipping version as well as working on features for upcoming version. Believe it or not, we made only a single, very targeted change for VP17 to fix the issue caused by a recent Windows 10 update...a change that would only affect file decoding of some specific file formats. Doing anything more could jeopardize the stability of the software. Believe it or not, we are trying our best to avoid doing anything to upset our customers.

martin-g1565 wrote on 5/14/2021, 6:24 PM

Fair enough. But I'm 56 and this is not my first rodeo. And in this day and age, you can't fault us for being skeptical. But I'll take you at your word that you are wanting to keep purchasers of 17 happy. That would be a wise policy IMO.

john_dennis wrote on 5/14/2021, 8:21 PM

I'm seven decades old and my first rodeo was Cattlemen's Days in Gunnison, Colorado over the July 4th weekend in 1965. I remember it well! Even though I've since decided that I don't give a damn about rodeo, I got paid for being there.

By the way, I've installed the recent Vegas Pro update for 17 and 18 without incident.

martin-g1565 wrote on 5/14/2021, 8:24 PM

Wow, the same year I was born! ;-) Glad you've had no incidents with update. The Magix rep seems credible and I trust my audio stability w 17 holds.

Musicvid wrote on 5/14/2021, 9:57 PM

Fair enough. But I'm 56 and this is not my first rodeo.

Hey Martin, I'm 71 and this is not my last rodeo. VegasDerek is a straight shooter, and deserving of our respect. He and the team bent over backwards just for you, and this is the first time I've seen a retroactive version update. I've worked with the product for twenty years, through three brand owners, and I've never heard anything like what you are suggesting. If you would really like assistance, we are here to help.

martin-g1565 wrote on 5/14/2021, 10:31 PM

Good to have the link ty! Also, I am taking @VEGASDerek at his word. However, you can understand my skepticism since for eons Vegas Pro 17 has annoyingly prompted me repeatedly for a update I already had installed. I still doubt new Vegas Pro versions are tested by editors in real world conditions (complex timelines, etc). I had to stop at 17 for that reason--18 would take forever for Undos, which was a deal breaker for me. Now I'm just doing audio so 17 is fine. Grateful if Magix was only motivated by brand loyalty. If so, they're going about it the right way. Bravo!

Musicvid wrote on 5/14/2021, 11:38 PM

I still doubt new Vegas Pro versions are tested by editors in real world conditions (complex timelines, etc).

That is not correct. You know, sometimes our expectations create their own realities; I would try giving the program the benefit of the doubt first. Or else download some other professional editors and make some personal comparisons. You may even decide it's time to move on.

However, you can understand my skepticism since for eons Vegas Pro 17 has annoyingly prompted me repeatedly for a update I already had installed. 

That, and something else you said in your first thread has me curious. Where did you "get a version of 17 again"? Was it some download you found on the internet?

 

martin-g1565 wrote on 5/15/2021, 12:55 AM

It’s called my opinion @Musicvid—you might wanna try it sometime. What’s that—you might offend the powers that be? Can’t have that... Oh yeah, and I don’t plan on leaving the software that I paid to upgrade for 13-14 years religiously. I only stopped at 17 because 18 wouldn’t undo without hourglassing forever, an issue well documented on here.

As I said before, if Magix upgraded 17 to inspire brand loyalty, I applaud their decision and shall gladly pay to upgrade Vegas Pro in future if the improvements justify the purchase.

martin-g1565 wrote on 5/15/2021, 1:00 AM

One more thing: I can certainly not be the only 17 user to have been annoyed by the promptings to download a version of 17 I already had installed. That told me somebody at Magix was asleep at the wheel.

walter-i. wrote on 5/15/2021, 4:20 AM

If you're interested, here's another guy who downloaded and installed both the Vegas Pro 17 and Vegas Pro 18 updates without any problems, and is running them smoothly.

So the differences are obviously in the configuration of the PCs and in the drivers.
But unfortunately you haven't said a word about that.
If you want to take the chance, you are invited to start now.
But please stop whining, it hasn't brought us one millimetre further in the whole discussion.

https://www.vegascreativesoftware.info/de/forum/important-information-required-to-help-you--110457/


 

EricLNZ wrote on 5/15/2021, 6:24 AM

One more thing: I can certainly not be the only 17 user to have been annoyed by the promptings to download a version of 17 I already had installed. That told me somebody at Magix was asleep at the wheel.

But @martin-g1565 was the prompt not to download an Updated build for the version you already had? Did you not realise that? Software producers do produce updates to rectify bugs and even provide improvements to existing versions.

diverG wrote on 5/15/2021, 7:33 AM

Hello to you youngsters out there. Managed to update VP17/18 with only a minor problem. VC2015++ needed to be replaced. Up and running. Not to bad at 84.

Happy editing.

Sys 1 Gig Z370-HD3, i7 8086K @ 5.0 Ghz 16gb ram, 250gb SSD, 2x2Tb hd,  GTX 4060 8Gb, BMIP4k video out. (PS 750W); Vegas 18 & 19 plus Edius 8WG DVResolve18 Studio. Win 10 Pro (updated)

 

Sys 2 Gig Z170-HD3, i7 6700K @ 3.8Ghz 16gb ram, 250gb SSD, 2x2Tb, hdd GTX 1060 6Gb, BMIP4k video out. (PS 650W) Vegas 18 plus Edius 8WG DVResolve18 Studio Win 10 Pro

Sys 3 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

Richard-Senften wrote on 5/15/2021, 10:02 AM

@EricLNZ Thanks for the download link. I have to apologize for my first post but I was getting a bit frustrated and I think Magix is responsible for some poor communication. My only notification of the fix was a banner at VP17 boot and it was my impression that it was a patch not a full install. (I should have guessed after the lengthy download process) I did find the download yesterday and when I saw the build ### decided to give it a try.

A good question might be, "Why did clicking the banner notification fail so many time but the download from tech support installed without a hiccup?"

martin-g1565 wrote on 5/15/2021, 10:11 AM

@EricLNZ Thank you for download link, I downloaded that for a rainy day and, no, the prompt was for the exact same Build I had installed—sorry.