In VP17 build 421, a new item has somehow found its way onto the View > Extensions menu:
Presumably it's a warning to users of pirate versions. It seems harmless but clearly it shouldn't be there. I was brave and clicked the link. It did take me directly to https://www.vegascreativesoftware.com/kr/
I assume it's coming from VEGAS itself but it could be via a plugin etc.. Anyone not seeing this?
DV Nest looks like an online seller of video related stuff. I would guess it is a plugin.
I guess DV Nest is the Korean distributor and/or support provider for VEGAS.
Just confirming that it does appear in my b421 as well.
it says you will not be able to save or render projects after 3 days, to prevent that happening buy a non counterfeit licence from magix. it will be permanently disabled
That doesn't sound good. Is this a bug?
Best keep your fingers crossed for three days!
Probably a relation of this incident https://www.vegascreativesoftware.info/us/forum/vegas-movie-studio-platinum-16-0-is-this-normal--117473/#ca732645
I saw that too and was wondering why it appeared? Will it do anything?
Re the similar previous issue I linked to above, "a reply from MAGIX !
You have discovered a bug in the latest version of Vegas Movie Studio Platinum 16.
PiratedVersionDialog should not be showing, but it does not effect how the program works".
As advised then, I'm not going to touch it to test.
This has been reported to the dev team.
This would be pure evil, but worse case scenario after 3 days and vegas deactivates it deletes or encrypts all your project files.
@vkmast @NickHope It comes with the latest build 421.
I reinstalled the previous builds 284, 353 and 387 and the item is not included in those builds ... \View\Extensions\PiratedVersionDialogKorean\
I downloaded the build 421 for "Post", its in it also. I then correctly installed b421 for VP, not Post, its in it also.
I haven't purchased the "Post" version, but I had initially downloaded it in error and installed the b421 for "Post".
I think the links should be a little bit more explicit on the 421 download page re: Post or Pro.
Given that I'm not using a pirated version of VP, I assume Magix will make available soon an update to b421 that doesn't include this item.
I have the same in my 421.
So is has New version from Magix gor a virus or what is it all about,, Was thinking of doing the upgrade but not clear as to whether it is a problem or a disaster that MAGIX servers has been hacked with a virus?
It is looking like the Magix servers have been compromised............
I have it on my mine too. It appears to be a part of the 421 version.
This is not a virus. It is a bug and will be removed in the next update.
It may be a BUG... but BUGs do not introduce a complete alien link to a Korean WEB site. Someone in Magix decided to add this??? or it was added by someone hacking the the original download build .
Surely someone in Magix did sign off this build,???....
To say it is a bug is probably not the correct answer. It does add a worry that Magix are not in control of any new builds ... I certainly hope that is not the case....
I agree. Was the Korean web site developer sitting in on the final build and added this?
How can that get into final build? Somebody added it in. Question is who?
It was simply an oversight on our part. No conspiracy. Nothing to do with a Korean web site developer. We have a special distributor in South Korea and they have some specific requirements. This was accidentally left exposed when we were testing to make sure the dialog was working properly. Nothing more than that. It was a very embarrassing mistake on our part that some how slipped through our testing process.
Magix is lucky there being a lot of beta testers here , should speed-up improvements 😃
VEGAS Derek.... Not sure if you work for Magix or just a spokes person in a Marketing Department,,
Somewhere in this thread it mentions that if this version is installed it will cease to work after 3 days to save and render,
Would be useful if you can clarify where the info come from and offer some Guarantee that if any registered uses fall into this problem, Magix will be totally responsible for any losses to users ?.
Whilst you have offer a sort of explanation it does show some sort of lack of Quality Control and I have to assume that whoever was responsible is now not working for Magix.. It has damaged your Brand Name....
Whilst you have offer a sort of explanation it does show some sort of lack of Quality Control and I have to assume that whoever was responsible is now not working for Magix.. It has damaged your Brand Name....
Hey @Harry-Worth... just my opinion, but t reads like you're being overly-critical of them for this apparently harmless oversite in their released version.
It was said above (presumably by an employee?) that this is a harmless bug which inadvertently made it into the release that made it into the release. Sure, you could then question "what else made it into the release which was not caught?" and it's a totally valid question. But bugs DO happen; mistakes are made -- in software development and in most areas of life, ya?
If Magix chooses to publicly share the inner workings of their Version Control System, change management and testing paradigms -- that would be a very unusual thing for a software company to do (with a product at this price-point). For critical software selling for 100K+ it might be more common as part of a due-diligence process, or PR effort to maintain confidence in their client base. While I'd be interested in that info too, I surely don't require it to JOYOUSLY and with gratitude use their software.