Vegas: never again

Comments

Lovelight wrote on 3/17/2013, 4:14 PM
Is that list suppose to help?

It looks like a bunch of excuses for software that is failing because the devs heads are elsewhere like making us buy poorly integrated software like Hitfilm & NB Titler.

We need real updates that increase workflow speed & not days fooling around doing the devs job on how to avoid bugs that never get fixed.


mx1497 wrote on 3/17/2013, 7:17 PM
I see in your post history, it goes from December 2012 asking about a Vegas 10 install and then now in March 2013 a post "Vegas: never again"...yet there are no posts asking for solutions.

Did you update to the latest build with many bug fixes? Did you try compatibility mode? Did you try changing the RAM preview to zero?

You state that you want to render a video for Facebook, tried a specific setting in the render dialogue and because your settings didn't work, gave up. Did you try changing the settings a bit? Other file extensions to render to? They will also make a file good enough for Facebook.

Why do you have to use CUDA? Did you render it normally via CPU and just get your rendered file already? In the time you took to put together and post your diatribe it could have been rendered.

Vegas Pro 12 build 486 works. If you give up that fast you won't be happy with any software.
Ryadia wrote on 3/17/2013, 10:59 PM
Wow!
That really is a rough deal you had there. My experiences are quite the opposite. I build my own PCs and get to choose the hardware... Particularly the RAM I use. My latest PC. A simple i3 system with high quality RAM and on-board intel Video gave me a fair amount of problems at first.

Luckily I didn't set out with the attitude that if all the other software worked OK then the one that kept crashing was at fault. By the time I'd traced the problems to one of the (new) hard drives, I ended up with a sweet system that runs Vegas 12 better and faster than any previous version back to 6. Windows 8 Pro is one sweet program... Once you install classic shell !

Sorry to fit the description of someone telling you it's your hardware but it is. I'll tell you why too. If 25,000 people bought and use successfully Vegas Pro in all versions you never bothered to upgrade to then your computer (or you) has to be the problem.

Sometimes a simple thing like shutting down a service and preventing it from starting again " because it never did anything" can cause one program that relies on it to drag your entire system down. Seriously... Every time someone tells me they've crashed their PC, I can't help but wonder; How come I use 5 or 6 graphics programs and Vegas Pro all at the same time and none of my PCs crash?

I'm sure you've heard "never say never"? Never say its not your hardware when nearly everyone else who bought the same software as you runs it just fine. Hardware problems are hard to find if the PC was built from cheap parts or you bought a cheap system already built. Get what you pay for, sounds right.
NickHope wrote on 3/18/2013, 1:11 AM
Is that list suppose to help?

It's was specific list, in response to Chienworks, of issues to look out for when upgrading from VP9 to VP10.
Sebaz wrote on 3/18/2013, 3:09 AM
"I see in your post history, it goes from December 2012 asking about a Vegas 10 install and then now in March 2013 a post "Vegas: never again"...yet there are no posts asking for solutions."

Perhaps my older posts are not visible anymore, there were far more than two, but from 2007 to sometime in 2010 when I stopped using Vegas.

"Did you update to the latest build with many bug fixes? Did you try compatibility mode? Did you try changing the RAM preview to zero?"

Latest build, yes, comp. mode, no, I don't see why I should run a program in compatibility mode, when that program is supposed to be compatible with my OS, Windows 7 Pro. RAM preview to zero, no, because RAM preview is supposed to offer a function, why would I have to set it to zero?

"Did you try changing the settings a bit? Other file extensions to render to? They will also make a file good enough for Facebook."
"Why do you have to use CUDA? Did you render it normally via CPU and just get your rendered file already? In the time you took to put together and post your diatribe it could have been rendered."

If you read my post in detail you'll see that I rendered fine to Sony AVCHD, although it took too long for a less than two minute sequence. Also if you read my post you'll see that I tried rendering with CPU only with the same buggy result (using the Internet profile, not the AVCHD)

"Vegas Pro 12 build 486 works. If you give up that fast you won't be happy with any software."

Glad that it works for you and a few other people, because it doesn't work well for most people. And again, if you read my post, you'll see that I didn't give up that fast, I was a user of Vegas for many years and stopped using it because it went from a great software to a bug infested piece of junk. And believe me, I'm happy with almost every other software in my computer, including Edius and Premiere. Not that they're perfect, but at least they don't crash all the time for no good reason.
John_Cline wrote on 3/18/2013, 7:47 AM
I don't think it is the least bit accurate to say that Vegas "doesn't work well for most people." However, it is safe to say that most people who come here to complain about Vegas have a problem. People don't typically post here to say how great it's working, they're too busy editing away in Vegas. I have six systems that are running with no problems except that we can't smartrender Cineform .AVI files in version 12. Not really a deal breaker.

Anyway, Sebaz, you've made your point, now move along to Premiere or Edius.
Rory Cooper wrote on 3/18/2013, 8:41 AM
The only issue I did find with windows 7 and Vegas was the type faces was causing Vegas to lock-up especially with projects using Pro type titler so I deleted all the type faces in 7 and copied them from my xp and pasted in 7 and then I could work as usual. So something went t bad with windows 7 no idea what. I suspect a lot of issues are with windows and not Vegas
farss wrote on 3/18/2013, 8:42 AM
riredale said:
"I've made this suggestion before and I'll make it one more time now.

Totally agree with you.
Company I used to work for did exactly that. Several times our suppliers did the same thing when we struck problems with their products.

As some are hinting at we cannot know for certain how many happy V12 users there are compared to those having issues. The problem I see is Vegas's already small market share is in decline, in part because the competition is improving. SCS simply cannot afford to lose customers because of the negative sentiment the number of people who are having issues is creating. It's not just the recent customers, many of the old hands have left for greener pastures.
SCS have also attempted to diversify and that hasn't gone well either, SF for Mac is a disaster, even the reviewers can't get it to work reliably.

What also troubles me is SCS with V12 started out with what seemed like a new approach by going to an almost public beta. That seemed very poorly managed.

Modern software development of applications that push the envelop such as NLEs is not simple. It takes more work not just in the coding but also in the testing. If that entails higher costs that have to be passed onto the users then so be it. If SCS believe the market will not bear the cost then the choice is simple, offer less that works rather than more that doesn't. The most attractive feature that Vegas used to offer was that "it just worked".

Bob.
Chienworks wrote on 3/18/2013, 9:01 AM
Nick, thanks for the comments. I'll look into them.
NormanPCN wrote on 3/18/2013, 11:00 AM
"SWAT team"

Yes, something like this. The only issue I have had is with GPU enabled in video prefs on slideshow project(s). Vegas locks up, no responding, at random points during preview playback. The random point and not responding with a wait chain which is not empty seems to point to a thread race condition lockout.

Race conditions are uber tough to debug. Hard to reproduce on a different machine. If you cannot reproduce i house, then how do you debug?

For me, I have uploaded sample projects to Sony in the hopes that can help but still they might likely need a machine quite similar to mine.

One, Movie Studio 12, item they said they could not duplicate.
The Vegas 12 one, is still sitting at support.
OldSmoke wrote on 3/18/2013, 12:12 PM
Sebaz:

I am a bit late to this thread but I am one of the rather many users that have almost no issues with VP since version 7. I say almost as there are bugs in the software but I have not had any random crashes and I am currently working with VP12 394 professionaly. I also use GPU acceleration since its itroduction in VP11. As mentioned in this thread already, it would be wrong to assume that VP doesnt work for many or even the majority of users as only those that have issues are posting here which I would rather say is a minority.

Have you recently updated your hardware? I am asking as your published system specification doesnt reflect the GTX570 nore the i7-3930K you mentioned in your original post. BTW I have those PC components in my system since I upgraded to VP11.

I am really interested to see if I can replicate your problem but and it would be great to have your project and related media to do so since its only a couple of clips that would need to be uploadede to Dropbox. As offered by anoher user, I am willing to render your project and even spend some time to replicate your problem on my machine if that is possible at all. So, if you are interested then please upload your files to Dropbox or so.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Skuzzy wrote on 3/18/2013, 1:59 PM
As someone who has worked some 25 years in software development, I can say it is easy to complain about a problem and demand a fix, but software issues can only be resolved if they can be duplicated.

That said, I do not see much which would be an aid to a programmer in determining what could be the problem. It is frustrating for programmers to see users having problems they cannot duplicate in the lab.

I have had my shares of issues with Vegas. However, I know software this complex is not going to be one hundred percent bug free. I am a happy camper if I can work around an issue until it is fixed.

I had serious problems with the 32bit version of V11. Memory leaks on any render, regardless of the settings or the codec used. Switched to the 64bit version and that solved most issues.

Got the black frame problem, then turned off GPU acceleration, and that solved that problem. Then just for giggles I turned off thumbnail generation in the timeline and the media viewer. Never really needed them anyway.

I am now on my eighth project and have not suffered any issues at all. Count me as a happy camper. I will probably switch to V12 once I see a patch or two for it.
Terje wrote on 3/18/2013, 3:52 PM
>> As someone who has worked some 25 years in software development, I
>> can say it is easy to complain about a problem and demand a fix, but
>> software issues can only be resolved if they can be duplicated

In the software industry my self, and it is one thing to deal with bugs that are not easily reproducible in the lab, it is another thing to have bad management. In SCS for the past few years, the latter is definitely the case.

Many of the bugs reported to SCS over the years are low-hanging fruit that has never been addressed. The issue with importing HDV footage is an example. Others are issues with black frames etc. These are not only reproducible and reproduced, they are also straightforward to add test cases for that can be run automatically.

People with these problems have been frustrated by the "we don't really care" response from SCS (that is the effective response when it goes un-handled for years and years) combined with priority adding of all kinds of nonsense.

When developers are removed from finding and fixing bugs in the core product and are instead tasked with adding (often silly or nonsensical) features, then you know, as a software developer, the company is simply suffering from incompetent management. This goes all the way back to the titler thingy that was once added by SCS. It was added, never changed, never fixed, never dealt with. It was a total waste of resources. 3D. Sorry, if your product isn't operational on regular footage, adding 3D support, something that just about ZERO (please note you 3D user, I said just about) of your customers care about, then you have bad management.

For a while (better lately) you also saw bugs come and go, over and over again. Fixed in one release, hosed in the next, fixed in the third and so on. Again, a sign of bad management since quite clearly the QA manager is utterly incompetent and he has added no automatic testing.

In certain areas, Vegas still does the wrong thing (color space stuff for example) and has been doing the wrong thing for years. Sorry, but in the professional market, that is simply not acceptable. I don't care how many features you add, if the data that comes out the other end of my work process is not correct, your product is useless. For me, as a home user, it isn't all that important. That probably also goes for a huge portion of the pros that do not deal with broadcast. For broadcast though, it is simply not acceptable and voila, you're not even a contender.

These are the things that SCS needs to deal with, and on some levels, they still are not. As long as that is the case and management behaves this way, Vegas is not going to be a contender.

To be clear, as of this moment, I am a happy Vegas camper, but that is because what was wrong for me now has been fixed, and the other stuff, broadcast and hdv doesn't apply to me.
JJKizak wrote on 3/18/2013, 4:08 PM
Windows 7 has it's problems also. With my older online computer video card there is no Win 7 driver so it constantly blue screens about once a month. The Microsoft Word program cannot connect to one of my printers and the latest updates from Microsoft blew out Microsoft live essentials and I had to re-install. It's just as slow as Vista 64 bit and it connects to the other 4 networks when it feels like doing so.So if you have old hardware (like me) it's back to the bank.
JJK
Skuzzy wrote on 3/18/2013, 4:25 PM
Terje, I cannot address the depth of the issues with SCS as I have not been around it that much. I have only been using Vegas since V8.

I do concur that issues with addressing problems, within any software package is almost always related to management, as programmers only work on what they are told to work on.

Never been in a shop that allowed any programmer free range to do what they wanted to do.

I do not profess to have knowledge of how SCS is structured, so all I can do is make general assumptions. Curiously, the black frame issue, for me, has been hit and miss. Sometimes it did it, sometimes it did not. It seems to be related to GPU acceleration, which is a grab bag of worms. I could probably change the video driver and either make it worse, or better. Disabling GPU acceleration made it go away.
That can get into a whole new level of finger pointing. I'll just move along on that one.
====

JJKizak, I have been using Window 7 64 bit and what you are describing is simply a lack of support for older hardware. I have to deal with it as well, for my printer and scanner. I use a Linux file server, so I simply added those pieces to my Linux box and made them available over my network to my Windows systems.

I thought it funny I had to go to Linux because of dropped support from both Microsoft and Hewlett Packard.
Tom Pauncz wrote on 3/18/2013, 4:50 PM
Seems a lot of us die-hard Vegas users, at one time or another, have been or are in s/w development. Myself included.

Not wanting to add to the flame, but the V12 public beta was the worst botched beta program I have ever had the (dis)pleasure to be a part of.

SCS, should they be inclined (PADDY PLEASE COMMENT since you obviously lurk here), could strike a committee of us to get this product back on track and resolve some long outstanding issues. Couldn't be that tough to do.

I'd be happy to be a part of it. Been user since Vegas V3 - every version.

Tom
videoITguy wrote on 3/18/2013, 5:05 PM
Tom, you know you are forbidden by secret agrreement to discuss the nature of the beta program?
That said you have now made the comment "botched" in this context. The problem with the whole beta thing in my opinion is that is very badly managed. I for one would like to get to the bottom of this and see if the SCS organization is being entirely driven by corporate marketing, and/OR the development team is in need of serious retooling.
farss wrote on 3/18/2013, 5:13 PM
Tom Pauncz said:
"Not wanting to add to the flame, but the V12 public beta was the worst botched beta program I have ever had the (dis)pleasure to be a part of."

Indeed. I'm of the opinion that was just one example of the real problem.
As any development / engineering effort grows in size or complexity different control and management systems are required. When it's a team of one not much is required. When it becomes a team of five, it changes. Even change itself is something that has to be managed carefully. Oftenly it's not that anyone is doing the wrong thing or not doing everything they can, the system itself has taken on a new life at a new level that requires a different approach to how it is managed. It can be difficult for the team to even see the real problem, people become frustrated, change is resisted because "it has worked so well, so far". This is why we can see a good business grow and then quickly fall over.

Bob.
Tom Pauncz wrote on 3/18/2013, 5:14 PM
Gotcha videoITguy...

However, I feel more than competent and qualified to comment, having been in s/w development for well over 30yrs and having run beta programs on several occasions - h/w and s/w included. And that's all I am going to say on that subject.

I would dearly love to sit down with SCS and talk, should anyone there care to listen.

Tom
ushere wrote on 3/18/2013, 5:48 PM
unfortunately tom i think the only people you could ever hope to 'reach' at scs is marketing, and they'll probably only listen if it's a new gimmick that can 'value add' to their product ;-(
_Lenny_ wrote on 3/18/2013, 6:09 PM
Sebaz, I see what you mean about slow renders.

I just added 3 short AVCHD clips from my Caon Legria M52 to the timeline. Total running time was just over 1 minute.

I tried to render out to Blu-Ray (Main Concept). The progress bar shot immediately to 3%, and there is stayed. Repeated, but with the Sony settings. The progress bar moved to 2%. Then no further. Similar results rendering to HDV and MPEG2 (DVDA compliant).

I'm currently editing HDV footage... I hope it can render that out for DVDA. If not, I'm wasting a whole lot of time!

It seems that SCS is becoming more like the other divisions of Sony - releasing new products instead of providing (firmware) updates to existing one. That's why I am no longer buying Sony electronics. The alternatives come from companies that care about their customers.

I do love Vegas, and it usually words very well for me, But will I upgrade to the next version...? I'll probably stick with 10 & 12 until forced to move on.
TeetimeNC wrote on 3/19/2013, 8:50 AM
Like many here I have an IT background and for the last few years before retiring I was the Enterprise Application Architect for a Fortune 250 company. I have zero insight into Sony's programming practices but the one thing that seems apparent to me is a lack of proper exception handling in the product. In the industry this is called "sunny day scenario programming" where the the programmer fails to take into account the common things that can (and will) go wrong. One example of this is the frequent "white outs" we experience in recent versions of Vegas, some of which might be the result of attempting to access a drive that is sleeping. This is something the program should anticipate and handle gracefully.

There are expert consultants out there who are skilled in software refactoring. Refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior, to fix the kinds of problems we see in Vegas. These people are very knowledgable in how to architect an application for stability and maintainability. If SCS doesn't have this type of person on staff, it should. At a minimum, they should bring in an outside set of eyes to audit their coding practice.

/jerry
Tom Pauncz wrote on 3/19/2013, 10:50 AM
+1 Jerry...
Tom
_Lenny_ wrote on 3/19/2013, 3:49 PM
Quick test. Rendering four AVCHD clips (24Mbs) with 2s cross fades to DVD Architect compliant MPEG2

VP10 - 1:05 (RAM preview 64MB)
VP12 - 0:48 (RAM Preview 0MB)

Now, as I understand it, rendering to MPEG is not GPU accelerated. But having it ON for Video Processing (using Intel HD4000 on-board graphics) resulted in a failed render; VP slowly crept past 0%, and the calculated time remaining just kept going up and up.

So there is some serious programming issue with Vegas' ability to use the GPU effectively / efficiently. Which of course comes as no surprise to many of you.

It strikes me as bizarre that GPU support works in other programs (NLEs) but Vegas gets it spectacularly wrong.

It needs sorting.