@j-v

@NickHope  chose to call b550 "Update 4.1" in the VP Release History  (which is more apt, see my comment here below the OP there) as Release notes also say Update 4.1. Please see also my comment here and the next two (from Gary and myself there).

So Gary calls build 550 the newest and real update 4 and the seller (Magix) tells us build 532 is update 4 and advertises it that way.

@j-v MAGIX Download Center offers only the latest updates of VEGAS Pro versions. Currently I'd get VP 19 build 550.

Btw, does MAGIX currently advertise build 532? Can you give us the link (URL) to it?

(Build 532 seems still downloadable using a link in Nick's Download Post.)

This morning I got the upgrade offer from Magix with this link

https://kpc.webmail.kpnmail.nl/appsuite/#!!&app=io.ox/mail&folder=default0/INBOX

you got a link to webmail?

Following that link of my mailprovider leads me to an Upgrade for Vegas Edit with the text I showed in the O.P.

All i saw on your link is a webmail login page.

I wonder what the date of that email might be.

I wonder what the date of that email might be.

This morning and also now the same I showed the O.P you can find now.
I made this video some minutes ago

Thanks @j-v - another Marketing Dept. oversight :(

I expect the upgraders will get VP 19 b 550 (Update 4.1) anyway though (until a newer build comes out).

550 was replaced and both were "Update 4" so it's just a harmless error with no implications for users I think.

550 replaced 532 and the old 532 related post was included in the changelog here.

@NickHope  chose to call b550 "Update 4.1" in the VP Release History  (which is more apt, see my comment here below the OP there) as Release notes also say Update 4.1. Please see also my comment here and the next two (from Gary and myself there).

@vkmast I called it "Update 4.1" in that post, because I saw that's what you had already called it in your comment on the News forum. I was wondering if that was the right approach but then I noticed that it had been called "Update 4.1" somewhere else (which I now can't find) before you made your comment. So I went along with it.

In my opinion it's asking for trouble when the team releases a new update and gives it the same update number as a previous release, especially when the announcement post for the previous release gets edited to make it appear that the previous release never existed. It just causes confusion, and the marketing page still showing "Build 532" is a fine example. I really wish they had incremented that update number to 5. I suppose they had internal/marketing reasons not to.

I'd prefer it even more if they adopted a more industry standard, semantic versioning type of system. If that were the case, build 532 would be, for example, 19.5.0 and build 550 would be 19.5.1 and everything would be clear. It would also avoid mismatches between update numbers in announcement posts and readme files, as we had throughout VP17.

@NickHope thanks for your comment. As I said above [VP 19 b 550] Release Notes also call it Update 4.1.

@vkmast Oops. I missed that in your previous comment. And I can't install VP19 cuz of my old OS, so can't see the release notes for myself. "Update 4.1" definitely the right thing to call it then.