Vegas: never again

Sebaz wrote on 3/16/2013, 3:00 PM
I still remember when I enjoyed editing in Vegas between 2007 and 2010. It was innovative and original software, way better than FCP or anything else. But with each subsequent release it became more unstable, to the point where now it has turned into a sad joke.

I had bought all the upgrades until version 10, when it was so unstable that it became aggravating. Of course plenty of users here would tell me that my computer was the reason, but well, when every other software works perfectly fine and Vegas is the only one crashing, it's obvious where the problem lies. So I never bought version 11. I switched to Edius, which would crash once a month at the most. But one day in December I got an email from Sony saying that Vegas 12 was $99 for one day, so I decided to buy it, especially since version 10 would not install anymore, possibly because now I had 3 TB drives with a GUID partition.

But even $99 is too expensive for something that doesn't work. I normally edit in Premiere CS6, which can go days without a single crash, and previous to that I was editing in Edius 6, which goes months without a crash. But I got some Vegas nostalgia so I decided to edit a short home video in Vegas 12. It's just two black solids, one at the beginning and one at the end, and 6 clips in between, AVCHD from a Panasonic HMC40 at 1080i. The only two filters I applied to each clip are curves and saturation.

I wanted to post it on Facebook, so I went to the render as dialog, choose the Internet 1080p template and changed just three things, upper field to match the footage, then I switched from VBR to CBR at 20 Mbps, and finally set Encode Mode to CUDA since I have a GTX570. Other than that, I set rendering quality to Best. What followed is proof that this has to be the most unstable software in the history of computing.

First of all, their implementation of CUDA is a joke, since it takes forever to encode, even for this one minute and fifty second sequence. It actually doesn't make a difference between CPU or CUDA, both say they're going to take like 9 minutes to encode. But, it doesn't even finish encoding, either in CUDA or CPU. Sometimes it goes up to a certain point and gets stuck forever until I kill the process because the cancel button doesn't cancel anything except the joy of editing video in Vegas. Other times, it just tells me that an error occurred while creating the file, and the reason for the error could not be determined. Then when it actually encodes all the way through, it does two passes even though I set it to CBR, which has only one pass in this encoding module, and still it took like ten minutes for a 1:50 sequence. The only way I got it to encode all the way on the first try was using the Sony AVC encoder to an m2ts file, and that also took like 6 minutes. This is on a i7 3930k, six cores at 4 Ghz and 32 GB of RAM.

It's obvious to me that SCS just doesn't care about this software anymore. When a simple timeline of 2 solids and 6 clips with 2 filters each takes ten minutes to render or can't render at all, when in Premiere CS6 something like this encodes in almost real time (or faster than real time when I use the Matrox MXO2), it's obvious that this is not even a Pro NLE anymore, it's not even a consumer NLE, it's just a bad joke. So I'm going to email Sony asking for a refund, and if they don't give it to me I'm going to try to sell it for $99, at least to recover the money I wasted the last time. And I will never buy anything from Sony Creative Software, ever again.

Comments

videoITguy wrote on 3/16/2013, 3:27 PM
So it appears that misery must love company, otherwise you would not try to sell for $99 fullprice (come-on, what about used discount?) so that some other poor soul will have to bear unfortunate consequences - shame on you!

If I were you and wanted to work with SCS NLE versions 10 thru 12, I would ditch your camera source and go to high data rate Sony or Canon systems.
Sebaz wrote on 3/16/2013, 3:43 PM
Hey, there are fan boys everywhere. I'm sure that somebody else would be happy to get Vegas for $99 instead of the $600 SCS charges for it.

As for the other suggestion, I do have a Canon XF100, the footage from which also crashes in Vegas, and doesn't crash either Edius or Premiere CS6. Besides, why would I have to change my gear just to accommodate very poorly written software? The camera works perfectly fine, doesn't crash any other NLE. It's not the camera, it's the flaky software.
rmack350 wrote on 3/16/2013, 3:53 PM
why would I have to change my gear...?

You shouldn't. Use the software that works, rather than banging your head against software that has never worked for you. It's madness to keep trying something when you know it doesn't work.

Frankly, it's been this way for you for so long that I don't understand why you're still trying.

Rob
john_dennis wrote on 3/16/2013, 4:12 PM
I'm curious enough about the range of outcomes with Vegas that I would offer to render your project for you if you zip the project and all the assets and put them on dropbox. Then, at least you'll have the output you wanted after you sell your copy of Vegas.

Other than that, I have no comment.
Sebaz wrote on 3/16/2013, 4:36 PM
"Frankly, it's been this way for you for so long that I don't understand why you're still trying."

Just one reason: I like most of the Vegas interface. However, I have come to terms with the obvious, that Vegas is like a really good looking car that will die and leave you stranded half the times you go out. So I made my decision to never try it again, especially if I return it or sell it, because then I would have to pay full price, which I wouldn't do in a million years. In fact, I wouldn't even pay $50 for it.
TheHappyFriar wrote on 3/16/2013, 4:36 PM
V10, no issues for me. 8)

I'd buy 12 from ya for cheaper then you paid but I have XP32.

When I first installed V8 on my new machine it was the only thing crashing it. Not even GPU benchmarks or Prim95 would.

Turns out I caused a hardware issue. So, my Vegas crashes were my fault.

EDIT: Let me change what I said:
I'll give you $30 for it. You said that $99 was to much for it, so I'll pay you less. Yeah, I can't use it, but that doesn't mean I won't get 64-bit some time this year.
_Lenny_ wrote on 3/16/2013, 5:12 PM
I joined Vegas as version 6 - rock solid
Version 7 - had issued with HDV
Version 8 - stable
Version 9 - stable
Version 10 - issues on initial release, but were fixed
Version 11 - I tried the trial and was so aghast as its instability
Version 12 - works OK for editing. I haven't tried a major render yet. There is the occasional crash, and expanded editing mode is unreliable.

I've never really got along with Premiere. I can just about use it, but it's clunky and audio editing is non existent

I tried Edius. It crashed on first launch, 2nd launch, 3rd launch, 4th launch, 5th launch... you get the picture. It never progressed further than the splash screen.

Back to Vegas, there are those here who will deny that there are problem with Vegas and who blame hardware every time. Undoubtedly, there are issues with the Vegas code; how do we get them fixed?
Chienworks wrote on 3/16/2013, 5:23 PM
Hmmmm. Wondering if i should try the latest release of 10 now. The initial release crashed on me almost every time i tried to do anything with it. I tried the "a" update and got only slightly farther with it, but still not able to complete any editing tasks. So at that point i hung it up and have stuck with 9 ever since.

Maybe i'll download it and give it a try.
Tom Pauncz wrote on 3/16/2013, 5:24 PM
..how do we get them fixed?

SCS has to step up to the plate. Listen to those who have issues and talk with them. I mean really talk - pick up the phone. Don't take 3-4 weeks to respond to a serious issue ticket.

I can't tell you how many times on reporting a problem to various s/w vendors I got a call the next day and the issue was resolved there and then.

My $0.02's worth,.
Tom
Sebaz wrote on 3/16/2013, 6:59 PM
"I tried Edius. It crashed on first launch, 2nd launch, 3rd launch, 4th launch, 5th launch... you get the picture. It never progressed further than the splash screen."

Well, in that case, I can assure you that the problem was your computer, because I ran it on a computer I had in 2010 without any trouble, then the system I built after that rock steady, and my current system, also not a single crash. And if you go online you will be hard pressed to find lots of people who have crashes with Edius consistently, while in this and other Vegas forums crashes are a very common complaint. Vegas, right now, is a piece of junk software with a pretty exterior. It may have features that other NLEs lack and viceversa, but if it crashes all the time, then why waste time trying to fix what the engineers at Sony don't have the will to fix, or maybe the company is terribly mismanaged and short on manpower.
ushere wrote on 3/16/2013, 7:14 PM
i think buying 12 for $99 a bargain. for $600 a rip-off.

i love vegas, i'm working with 12 and having known problems with thumbnail creation (dealt with elsewhere), but if i'd gone out and spent full rrp on it ($600?) i'be be fuming and demanding my money back!

this is so, so sad. a once innovative, robust, reliable nle brought down to a gimmick filled unstable, poorly supported piece of software, where the much hyped gpu function is but a joke in itself.....
ddm wrote on 3/16/2013, 7:32 PM
>>>there are those here who will deny that there are problem with Vegas and who blame hardware every time.

To be fair, there are many here who are having no problems with vegas 12, myself included. Does that mean we are blaming other people's hardware? I'm mystified by the complaints. I mean, doesn't it seem at least remotely strange that many can have no problems and yet others can't go 2 minutes without crashing? I understand the complaint, how can it be that one person can edit footage in Premiere fine, jump to Vegas and instant crash, must be Vegas, and that sounds like a reasonable assumption. Yet many others can edit all day long for days at a time with no problems? That's NOT how we all know troubleshooting buggy programs works, a problem needs to be able to be replicated in order to be classified as a bug. That is why I suspect something else, another piece of very common software? Something. I've installed Vegas on too many different systems to not have some of the problems encountered here, yet I haven't. I know I am neither that smart or that lucky. Clearly, Vegas 12 is very touchy on many systems, but how can something so touchy be so robust on so many other systems? It defies everything I have come to know about computer software.
Tom Pauncz wrote on 3/16/2013, 7:47 PM
ushere & ddm
+1

Tom
Geoff_Wood wrote on 3/17/2013, 12:32 AM
"Well, in that case, I can assure you that the problem was your computer, "

In that case I can assure you you problems with Vegas are due to yor computer. V10 , V12, and V12 all run fine on my computer. Well, maybe not 11 ....

geoff
Lovelight wrote on 3/17/2013, 12:42 AM
OP, thanks for sharing your experience. I wonder a lot about Vegas & the future.

V12 runs well for me with a few crashes a day but V11 ran better.

The gpu feature in V12 is poorly implemented. Sony has no excuse.

riredale wrote on 3/17/2013, 1:36 AM
I've made this suggestion before and I'll make it one more time now.

Sony needs to create a "Swat" team or even just one staff expert who actually goes to certain select people complaining of issues and sits down with them and spends a day working with them on their system. SOMETHING is causing some people all this grief while others report no issues at all. The Vegas expert actually has to see what the user is doing and how the system is responding. Perhaps even bring the PC back to Madison for further analysis, if necessary.

It may very well turn out to be something like "If you have such-and-such driver and at the same time you have version 13.297 of Quicktime, then a call to so-and-so subroutine will crash the system." But it will take an expert on-site to figure this out, I suspect. And I don't think there is any other option.
NickHope wrote on 3/17/2013, 1:42 AM
Chienworks, If you upgrade from 9 to 10e, I think these are the 3 most important unresolved issues you should look out for. None or all of them might affect you depending on the way you use Vegas.

1. "Replaced clips" bug potentially worse in 10 than 9. Beware copy and paste between projects, especially complex projects. Can monitor with timeline tools script.

2. "Black clips/frames" potentially worse in 10 than 9, especially for 3rd party AVI codecs. Restart Vegas last thing before any important render.

3. Phantom keyframes.
Sebaz wrote on 3/17/2013, 2:16 AM
"SOMETHING is causing some people all this grief while others report no issues at all."

See, to me that's the main proof that Vegas is very poorly coded software, or code that got worse with time, since apparently it used to be a very stable program many years ago. I ran Vegas on three different computers, four if you count CPUs, since the first one had an upgrade from a Duo to a Quad Core. Vegas 32 bit ran reasonably well, it crashed more than any other app, but not all the freaking time. But since SCS released the first 64 bit Vegas, 8.1, it's been nothing but an unstable piece of junk. Each and every 64 bit Vegas I ran on all three of my computers would crash for no good reason, sometimes even for scrubbing the timeline. 8.1, 9, 10 and 12 all crashed on a regular basis. Worst of all, it crashed randomly for no good reason, so it couldn't be tracked. Edius, to bring one example of very well coded software, used to crash for me at first when I did a specific thing, and then I realized that it was due to an iZotope plugin that they bundled with Edius. In the next update, the issue was fixed. That's the only problem I ever had with Edius, on all three machines I ran it in. And if you search for Edius crash online, you will find a handful of people that have bad problems with it, in which case it might be their hardware.

But search for Sony Vegas crash and the list is eternal. I even read professional reviews of Vegas attesting to how unstable it has become. So SCS is not a serious company anymore, either their programmers are just bad, or they're good but grossly understaffed because of poor management (and that I can certainly understand), but for whatever reason, Vegas is a disaster. When half the people run it without problems and the other half don't, then that tells you that SCS is barely doing any testing and quality control to ensure their software runs in as many hardware and software combinations as possible. So if they can't put out a decent product anymore, they should sell it to some other company that will make it into what it used to be many years ago.
JJKizak wrote on 3/17/2013, 8:04 AM
You can only cut so far untill your BMW turns into a Yugo.
JJK
Arthur.S wrote on 3/17/2013, 10:05 AM
I came into Vegas at V6 - because my existing NLE (MSP) had become so unstable as it 'climbed' the version numbers. Vegas has gone down the same route. What I've found though is that the last version of a Vegas release runs OK for me. I dropped V11 like a stone after many problems. Tried the last release a while back (701 64bit) and it's running like a champ! The latest version of V12 also ran OK to start with, but then started crashing randomly. This on both Vista 64bit and Windows 8. Back to 11 and wait a while more.
TheRhino wrote on 3/17/2013, 10:57 AM
I teach technology classes where I introduce students to CS6 & FCP but at the studio I prefer to edit with VVPro because the workflow is faster. I simply make more money per hour of editing using VVPro. In this economy, most of my clients want a firm up-front estimate and they really don't care what tools I use as long as the final product meets/exceeds their expectations.

Let's take an example of a corporate safety/training video...

All of the camera work is in HD now and the source files are copied initially to a fast internal RAID.

Workstation C with $600 USD of upgrades in April, 2021
--$360 11700K @ 5.0ghz
--$200 ASRock W480 Creator (onboard 10G net, TB3, etc.)
Borrowed from my 9900K until prices drop:
--32GB of G.Skill DDR4 3200 ($100 on Black Friday...)
Reused from same Tower Case that housed the Xeon:
--Used VEGA 56 GPU ($200 on eBay before mining craze...)
--Noctua Cooler, 750W PSU, OS SSD, LSI RAID Controller, SATAs, etc.

Performs VERY close to my overclocked 9900K (below), but at stock settings with no tweaking...

Workstation D with $1,350 USD of upgrades in April, 2019
--$500 9900K @ 5.0ghz
--$140 Corsair H150i liquid cooling with 360mm radiator (3 fans)
--$200 open box Asus Z390 WS (PLX chip manages 4/5 PCIe slots)
--$160 32GB of G.Skill DDR4 3000 (added another 32GB later...)
--$350 refurbished, but like-new Radeon Vega 64 LQ (liquid cooled)

Renders Vegas11 "Red Car Test" (AMD VCE) in 13s when clocked at 4.9 ghz
(note: BOTH onboard Intel & Vega64 show utilization during QSV & VCE renders...)

Source Video1 = 4TB RAID0--(2) 2TB M.2 on motherboard in RAID0
Source Video2 = 4TB RAID0--(2) 2TB M.2 (1) via U.2 adapter & (1) on separate PCIe card
Target Video1 = 32TB RAID0--(4) 8TB SATA hot-swap drives on PCIe RAID card with backups elsewhere

10G Network using used $30 Mellanox2 Adapters & Qnap QSW-M408-2C 10G Switch
Copy of Work Files, Source & Output Video, OS Images on QNAP 653b NAS with (6) 14TB WD RED
Blackmagic Decklink PCie card for capturing from tape, etc.
(2) internal BR Burners connected via USB 3.0 to SATA adapters
Old Cooler Master CM Stacker ATX case with (13) 5.25" front drive-bays holds & cools everything.

Workstations A & B are the 2 remaining 6-core 4.0ghz Xeon 5660 or I7 980x on Asus P6T6 motherboards.

$999 Walmart Evoo 17 Laptop with I7-9750H 6-core CPU, RTX 2060, (2) M.2 bays & (1) SSD bay...

_Lenny_ wrote on 3/17/2013, 11:43 AM
I am a happy user of VP12. As I don't earn any income from it, the occasional freeze I can forgive.

I can assure you that the problem was your computer

Every other piece of software runs as it should (run = gets past the splash screen and is usable.) OK, so Reveal Codes in WordPerfect X4 doesn't retain custom colours after a restart, but that's a software issue.

I suspect the issue with Edius was a bug - on the initial launch after install, I declined to register or told it not to phone home. This threw up the error.

Here's one for you:

Magix Movie Edit Pro on an AMD Athlon dual core pro processor steadfastly refused to render to MPED2. It worked on single core processors, and all Intel processors. It required a patch before it would render.

Would that be a software or a hardware issue?

Could there be an issue with the microcode in certain processor revisions, or in the firmware of certain motherboards that is causing instability?
Dach wrote on 3/17/2013, 12:29 PM
Very easy to point fingers and want other people to fix the problem. I for one have no clue how to program and even if I did I would not know how to code for video editing. For this reason I am willing to pay for a program.

I can take the responsibility to trouble shoot my own system, I'm familiar enough with hardware to explore such. Vegas is affordable, especially when a $100 purchase is no different than one trip to the gas station or to the grocery store. (Depending on vehicle and family size of course.)

Simply... if Vegas truly never crashed, would the individual be willing to spend more for the program? ($1K, $2K even). That is what would be needed to increase staff and resources in Madison.

- Chad
TheHappyFriar wrote on 3/17/2013, 3:42 PM
1. "Replaced clips" bug potentially worse in 10 than 9. Beware copy and paste between projects, especially complex projects. Can monitor with timeline tools script.

With 10 I've only had this happen when using an external drive with Vegas. Never anything on my internal drives (IDE or SATA). Besides that, I've had HUGE projects and never seen it happen outside this predictability.

2. "Black clips/frames" potentially worse in 10 than 9, especially for 3rd party AVI codecs. Restart Vegas last thing before any important render.

I've had it happen once but I only ever use HDV, DV or image sequences for video. Again, only once and I haven't been able to see it again. I believe I saw it in a project in an HDV file.

3. Phantom keyframes.

Once I figured out what caused it I never had the issue again. I was able to easily reproduce it and avoid it.

All software has issues. The ones in Vegas 10 I managed to either avoid or work around.