Argumentative uh? mmm...Since when having the expectation of products that we paid for to just work is an unrealistic expectation? I have been using Vegas for 10 years, the fact that I don't post or look for help in forums is because i do not have the time to do it, i look for work arounds most of the time or just go to another machine with older version of vegas to finish what I need to finish but this last version of Vegas Pro 15 is just not stable at all.

And by the way...my post IS NOT meant to direct my frustration to other Vegas users but to Magix...I am very frustrated with their reply's. Thanks for reading my post, I hope you don't take any of this personal but I liked it better when Sony was handling the support.

So, what is it you want us Forum members?

Vegas 15 has only been out for just over a month. It is WAYYYY too early to be expecting that all bugs will have been fixed, and of course they get prioritized and worked on in a systematic fashion, not one driven by individual users demands. It is better for everybody this way.

I am amazed that as a long term professional Vegas user you would have switched versions without thoroughly testing to ensure everything is working to your satisfaction.

It sounds like you are already 100% sure that the problem requires code changes, but if not, please ASK A QUESTION and provide some details so that your fellow users may attempt to help you. :)

I read the OP’s post and had no issue with it. With the known issues, it should not have been released at all. As for the question, here it is: “Is Magix ever going to implement a real customer support team that we can talk to?”

My answer is simple: NO.

@OldSmoke “With the known issues, it should not have been released at all.”

And with which release of Vegas Pro did this happen?

Grazie, you may remember they "took down" at least one build of VPro 12 (#710). There may have been another build as well 😎. And SCS never got to release their v 14...

@OldSmoke “With the known issues, it should not have been released at all.”

And with which release of Vegas Pro did this happen?

As far as I remember there was never a version where you had to manually disable a plugin to make it work at all, the so4compound.dll comes to mind.

That general statement is not correct. Here with my XAVC I and ProRes footage it works, and there was never a need for me to disable this decoder.

That general statement is not correct. Here with my XAVC I and ProRes footage it works, and there was never a need for me to disable this decoder.

Well, it doesn’t work with XAVC-S, a more common codec.

That was not the point. The point was that such a general statement is simply wrong.

As for the question, here it is: “Is Magix ever going to implement a real customer support team that we can talk to?”

No, that is a baseless complaint masquerading as a question.  So, what is the actual TECHNICAL question/problem?

That general statement is not correct. Here with my XAVC I and ProRes footage it works, and there was never a need for me to disable this decoder.

Well, it doesn’t work with XAVC-S, a more common codec.

Hmm interesting, all my footage is XAVC-S and I didn't have to disable anything, I just installed Vegas 15 and it all worked. I wonder what's different on our machines.

Nice to see that this forum actually have users that care and respond to questions. I personally don't use forums in general but other forums like steinberg cubase developers or tech support people participate and provide answers directly in forums, when posted this my intend was for Magix to read it.

I am a little surprised however to see that Vegas users consider a bad release to be the norm. Either way I thank you all for replying and now i know how to make better use of this forum when I have a technical question.

You’re very welcome 😉.

@OldSmoke “With the known issues, it should not have been released at all.”

And with which release of Vegas Pro did this happen?

As far as I remember there was never a version where you had to manually disable a plugin to make it work at all, the so4compound.dll comes to mind.

That general statement is not correct. Here with my XAVC I and ProRes footage it works, and there was never a need for me to disable this decoder.

Well, it doesn’t work with XAVC-S, a more common codec.

XAVC-S seems to be OK with so4compoundplug in VP15 build 216, but these issues still exist with it. Editing my GoPro or DJI footage is a complete non-starter unless I disable so4compoungplug. Personally I think it was bold of Magix to release VP15 with this serious issue that affects a huge proportion of users, and which can only be resolved with knowledge of a hidden preference and how to access it.

@OldSmoke “With the known issues, it should not have been released at all.”

And with which release of Vegas Pro did this happen?

As far as I remember there was never a version where you had to manually disable a plugin to make it work at all, the so4compound.dll comes to mind.

That general statement is not correct. Here with my XAVC I and ProRes footage it works, and there was never a need for me to disable this decoder.

Well, it doesn’t work with XAVC-S, a more common codec.

XAVC-S seems to be OK with so4compoundplug in VP15 build 216, but these issues still exist with it. Editing my GoPro or DJI footage is a complete non-starter unless I disable so4compoungplug. Personally I think it was bold of Magix to release VP15 with this serious issue that affects a huge proportion of users, and which can only be resolved with knowledge of a hidden preference and how to access it.

Unfortunately I cant test the latest build, 177 was the one I tested and the trial period is over, no further testing is possible from this point onwards. At least Nick is of a similar opinion, mine is a bit more direct. For me, the last version with major issues, was SVP11 when GPU acceleration was introduced. It took 3 to 4 updates to get it stable and you certainly needed the proper hardware to take advantage of it. The most common work around at that time was disabling GPU acceleration which is done via the preferences, within the software.

There was also an issue with GoPro footage in SVP12 and using the SVP11 decoder in SVP12 solved it. That is the only "hack" I remember.

Is Magix ever going to implement a real customer support team that we can talk to?

I still see this as a legitimate question that so far nobody else bothered to answer. Let me rephrase the question for those that are overly sensitive: "Is there or will there be a support team, that can answer technical questions? One where we can get more help than the standard reply of submitting a ticket?"

My answer to that is still NO.

I agree that the answer to your question is "no." The typical way higher level (ie better, more time consuming, talk on the phone) support is handled with professional software is by maintenance contract.  I don't see that happening at the current Vegas price point and market segment. NLE software is just too cheap. They won't make any money of they sell you an upgrade for $179 and then spend five hours solving your problems.

I've been using Vegas since V3 (good old Sonic Foundry days when you could talk to a human)! I currently own VP10, 12, and 14. VP10 works well for my current needs (I use Win 7 Pro). When I downloaded VP14 including the updates, when I tried to move the Master Fader, the program freezes. Did any of you experience this? Majix said that I have to be signed in as Administrator to install VP14 and that I have to uninstall the program first. If for some reason I choose not to reinstall VP14 , does uninstalling VP14 leave my other Sony products at risk due to common files need for each program (Acid 7, CD 5.2 arch, DVD Arch 6). Thank you for any guidance.

When I downloaded VP14 including the updates, when I tried to move the Master Fader, the program freezes. Did any of you experience this?

@Sneddy Previous discussion here and here. I included it in the known issues list. We never got to the bottom of which common factor(s) causes this. Perhaps it's a Windows 7 thing.

Majix said that I have to be signed in as Administrator to install VP14 and that I have to uninstall the program first. If for some reason I choose not to reinstall VP14 , does uninstalling VP14 leave my other Sony products at risk due to common files need for each program (Acid 7, CD 5.2 arch, DVD Arch 6). Thank you for any guidance.

It shouldn't do (but I can't promise). You could always reinstall those programs if necessary.