Oh well, was a long shot. I used to get some similar message from cineform software to do with trying to read/render files greater than HD (this is several years ago now though.)

Obviously this is not normal behavior, so something about your install is broken. I presume you've tried the usual preferences reset and software reinstall. Other than that it's down Magix tech support to get you up and running.

It's Vegas. The opening message appears when I try to open a veg, nothing on the time line. The save when I tried to save a veg with a single png (but could have been generated media). I've never seen a message about a codec. I typically use mts, mp4, png, jpg and wav files.

Do you have Vegasaur installed for VP14 or any other 3rd party plugin that may require licensing. Some of these check for their license status on startup of Vegas some when you use them in the project.

I think that this is the right line of inquiry. You never know what is going on in the background with various bits of software installed. And it would explain all the "symptoms."

I think that this is the right line of inquiry. You never know what is going on in the background with various bits of software installed. And it would explain all the "symptoms."

How does another plugin explain all the symptoms? Why the reluctance to put the blame on Vegas? I do have Vegasaur and various izotope plugins and Hitfilm but I don't think it is them. It happens with an empty timeline and if I reregister Vegas the issue goes away.

Obviously this is not normal behavior, so something about your install is broken. I presume you've tried the usual preferences reset and software reinstall. Other than that it's down Magix tech support to get you up and running.

The behaviour may not be normal but it has been consistent and yes I've tried the usual remedies. Magic Tech support have not helped. I know I'm not the only person who has this issue. Gary stated that the phone home is supposed to fail gracefully but it doesn't., at least not with v14. And Version 14 was not supposed to phone home at all:

MAGIX_Eric D wrote on 6/17/2016, 12:39 AM
In 2015 the MAGIX activation requirements changed, and while initial activation does require internet access, users are no longer obligated to be online once per month for license validation. The requirement to be online once per month is still communicated on the MAGIX web site as people are still using versions of the software which did use that system.

MAGIX_Eric D wrote on 6/17/2016, 4:36 AM
The only time internet access is required is for the initial activation. The only time you would be required to access the internet again is if you reinstall the program.

Why are you so reluctant to opening your mind to all the possible explanations?

Anyway, if you've made up your mind, and covered all the bases then you are done. Nobody can help you.

Why are you so reluctant to opening your mind to all the possible explanations?

I'm not - I'm interested in a solution. If you have a suggestion I can try I'm perfectly willing to give it a go. So far the available evidence suggests that Vegas alone is at fault. Any ideas on how to garner more evidence either way?

Why are you so reluctant to opening your mind to all the possible explanations?

I'm not - I'm interested in a solution. If you have a suggestion I can try I'm perfectly willing to give it a go. So far the available evidence suggests that Vegas alone is at fault. Any ideas on how to garner more evidence either way?

Fine. I have VP14 on my editing machine and I will disconnect it from the internet to test this out. I have a few plugins, NeatVideo and Vegasaur installed too. I don't use VP14 for various reasons not to be discussed here but I will start for testing purpose once a day, without internet. I would however need to know which codecs inside VP14 need a first time verification to make this a simpler process.

I would however need to know which codecs inside VP14 need a first time verification to make this a simpler process.

As far as we know:

• Intel HEVC/MAGIX ProRes
• Magix AVC/AAC MP4
• MainConcept MPEG-2
• MP3 Audio
• AAC Audio
• Dolby Digital AC-3 Studio

Fine. I have VP14 on my editing machine and I will disconnect it from the internet to test this out.

In addition you may want to install a firewall, that by default blocks all programs. This way, you get informed when any program tries to connect the internet.

Fine. I have VP14 on my editing machine and I will disconnect it from the internet to test this out.

In addition you may want to install a firewall, that by default blocks all programs. This way, you get informed when any program tries to connect the internet.

All we are trying to test is if VP14 works without internet or not after the software and all codecs are verified. I have no intention to take this beyond that, I have other things today and since my workstation is usually always connected, I don’t have an issue at all.

But, you can always do your own testing, especially if you are one of those affected.

But, you can always do your own testing, especially if you are one of those affected.

I did set up my system that way already ;)

 

I'm not - I'm interested in a solution. If you have a suggestion I can try I'm perfectly willing to give it a go. So far the available evidence suggests that Vegas alone is at fault. Any ideas on how to garner more evidence either way?

Great! My suggestion is to pare back to bare bones and then add back one by one. So for now, how about uninstalling all your 3rd party plugins. Then see if the message occurs.

Remind me: how often does this happen? Can you reproduce the error reliably?

But, you can always do your own testing, especially if you are one of those affected.

I did set up my system that way already ;)

And what are your findings so far?

OldSmoke wrote on 10/23/2017, 8:40 AM
Fine. I have VP14 on my editing machine and I will disconnect it from the internet to test this out. I have a few plugins, NeatVideo and Vegasaur installed too. I don't use VP14 for various reasons not to be discussed here but I will start for testing purpose once a day, without internet. I would however need to know which codecs inside VP14 need a first time verification to make this a simpler process.

Thanks Oldsmoke. I appreciate the help.

Kinvermark wrote on 10/23/2017, 9:39 AM

Great! My suggestion is to pare back to bare bones and then add back one by one. So for now, how about uninstalling all your 3rd party plugins. Then see if the message occurs.

Remind me: how often does this happen? Can you reproduce the error reliably?
 

I can do this next time I get the error messages. I probably won't see them for another month though it might be as short as two weeks according to Gary's email on the 18th.

But, you can always do your own testing, especially if you are one of those affected.

I did set up my system that way already ;)

And what are your findings so far?

It takes time.

As I wrote above, I already had Vp14 to crash on project save and then worked fine after beeing startet with an internet connection. But I did not take notes on the time Vp14 was connected before. All I can say up to now, it was more than 14 days.

you have replicated what others have said . That being no connection an unknown duration period but longer than 14 days it seems to envoke an 'anti piracy' measure where it just crashes & if a pirate version would stay continuously crashed as it wouldn't be able to contact the vegas servers as it would reveal it'self to be pirated.

But Non pirates just have to connect their internet again & suddnely no more crashes on project save. It's very suspicious that the Vegas staff member says it's not deliberate when that's the perfect way to deal with a pirate version because it makes the hacker seem like an incompetent fool who's hacked software is unstable it's a way of hiding that it's an anti piracy measure.,but also ruins the experience of computers not on the internet (for whatever reason) or stringent firewall policy..

I've written a song for you MAGIX, it goes something like this:

Honesty is such a lonely word
Everyone is so untrue
Honesty is hardly ever heard
And mostly what I need from you

@Former user

You may think that is subtle or funny, but it is actually just offensive. Whatever your private thoughts, you have no right to publicly accuse Magix staff of dishonesty. You are not doing yourself or this forum any favors.

I think that at the moment we don't have real proof of what is going on. So far, none of the affected users have provided hard evidence but if there is hard evidence, dishonesty is just one if the many words that would apply.

Well yes that is true, I"m believing the allegedly aggrieved, crashing software stories supposedly associated with saving projects after a period of time not connected to the vegas servers. What sway'd me is this confirmation story of constantly crashing until connecting to internet, then it's assumed no crashing when saving project fault until 14+ days of no internet again. If true it surely can't be coincidence, or even another technical fault that gives the user the impression it's a vegas fault. It's too specific.

Thinking critically these users are either liars with a very strange agenda or they are experiencing this vegas software fault related to not having internet.If they have shown no proof then it's about time they did. Screen capture is easy enough, save a project without any active plugins or filters.

There is no "critical thinking" being applied here. It is all guesswork based on very scant information. That doesn't make ANYONE (including Magix) a "liar" or have a "strange agenda" it only means they (and you) are jumping to conclusions that may or may not be accurate in part or in whole. And "proof" in the form of one users' experience cannot always be extrapolated to the entire user base.

Sigh...Maybe I wasn't clear...We do not, ever, under any circumstances intentionally crash the application. Never. Never have. Never will. Maybe we can move beyond that nonsense and try to find a solution to a very real problem some of you are having.

@Kit-As-Was, we do not have any support ticket open for you on this issue, so I've asked our support manager to open one. You will shortly (if you haven't already) receive email notification with some preliminary suggestions. Please work through that system and hopefully we can find out what's going on and get you fixed up.

Did I mention that we never intentionally crash VEGAS under any circumstances? Ever.

@Kit-As-Was, we do not have any support ticket open for you on this issue, so I've asked our support manager to open one. You will shortly (if you haven't already) receive email notification with some preliminary suggestions. Please work through that system and hopefully we can find out what's going on and get you fixed up.

Did I mention that we never intentionally crash VEGAS under any circumstances? Ever.

Dear Gary, thanks for getting another support ticket opened. I just received the email and hopefully a solution can be found. You mentioned not intentionally crashing Vegas. Actually, I found your mentioning of that on the 18th a little surprising. I don't think anyone suggested that before you did. I'd be grateful if you would answer my outstanding questions:

1. Is Nick's list of Codecs that require registering complete and does it also apply to Vegas 14?
2. When Vegas phones home what data does it collect and send?
3. Are usage statistics being sent?
4. Does Vegas 15 require reactivation after an update before it will work? (this is the case with Vegas 14)
5. If Vegas is supposed to fail silently if it can't phone home how can this behaviour really counter piracy?
6. If Vegas really doesn't require periodic connection to the internet why is that written into the Eula?

Thanks, I hope your answers will be sufficient for me to continue upgrading. I've been using Vegas since Version 6.