Vegas pro 11 not good I want refund.

Lingo wrote on 10/18/2011, 6:38 AM
Hi

I have just purchased the upgrade from Vegas pro 9.
Unfortunately the graphics card I have on my Dell pc (Radeon X1300) is not comptible with the Blue FX plug in titler. No suitable updated drivers available as this card is not compatible fully with Windows 7 (which I updated to from XP)
Vegas 9 works OK.
Also when I tried a trial render of an existing project the notice that there is insufiicient memory to render came up.
I have 2 gigg of RAM.
And plenty of hard drive space.
So I would like to get my money back any ideas how to do this.
The Vegas 11 was downloaded from Sony Creative.

Thanks for any help.

Comments

Former user wrote on 10/18/2011, 8:17 AM
YOu need to contact SCS customer service at one of the links above.

Dave T2
Kimberly wrote on 10/18/2011, 8:26 AM
Regardless which version you use, do consider adding more RAM if your computer will take it. RAM is pretty cheap, easy to add, and every little bit helps!

Good luck.
ritsmer wrote on 10/18/2011, 9:00 AM
Lingo: even without knowing what media you edit and to what output format - in my experience 2 GB RAM is way below what you need. Also using good old XP in a 32 bit version (as to your system specs?) is not what Vegas 11 needs with all the features built-in today.
I guess that you might even have applied the sodalled 2 GB "hack" on your Vegas 9 long time ago. I dunno if this might help Vegas 11..

I run a 64 bit Vegas 11 on a Windows 7 ultimate machine - and it just works and works several hours every day.
I had some difficulties yesterday using my old rendering templates from Vegas 10 - but have just made the few ones, that I need, from scratch - and now that works too.
musicvid10 wrote on 10/18/2011, 9:23 AM
First four of the system requirements:
Vegas Pro 11 system requirements

* Microsoft® Windows Vista® 32-bit or 64-bit SP2, or Windows 7 32-bit or 64-bit
* 2 GHz processor (multicore or multiprocessor CPU recommended for HD or stereoscopic 3D)
* 500 MB hard-disk space for program installation
* 2 GB RAM (4 GB recommended)

OP is running a single core 2.4 GHz processor, 2GB RAM, ancient video and audio on a machine that was no doubt built in 2004. I've got one of those. Vegas 8 runs on mine, too. That system isn't fit for Windows 7, yet he expects Vegas 11 to run smoothly. Hmmm.
Randy Brown wrote on 10/18/2011, 9:29 AM
So I would like to get my money back any ideas how to do this.
I just gotta ask; why wouldn't you try the fully functional trial before buying?
Former user wrote on 10/18/2011, 9:34 AM
Not to dispute anybody's information, but I am runing Windows 7 on a 2.8 Pentium 4 single processor, dual threaded. 2gig of memory (just upped it from 1 gig). It doesn't run like XP did, but it works and I can edit with Vegas 10 on it. I just loaded 11 on it and I will see how it does. I can't use the NewBlue effx, but that is not a show stopper for me.

I have a second computer that is a core 2 duo so it is obviously more suited.

Just FYI.

Dave T2
musicvid10 wrote on 10/18/2011, 12:54 PM
Dave, apparently yours and the OP's CPU speeds are just fast enough to clear the minimum specs for Windows 7. When I gave my machine specs (which are close) to Microsoft, they said basically don't bother but if you do you're on your own. Not wishing to run in a marginal area, I decided not to upgrade the OS.
Former user wrote on 10/18/2011, 1:23 PM
Other than video, the computer runs very well. I turned off some of the graphic features of win 7 since I don't need them anyway (the aero stuff), but I have been running Win 7 on 1 gig memory for a few months and an AGP video card that did not support aero at all. Worked fine. I just upgraded my motherboard trying to extend the life of my cpu and added a PCI-E video card. Still works fine.

I have edited video on here and SD DV files play and edit fine. Any effx are not real time, but I can deal with that because of the type of stuff I edit at home. Not as demanding as my real job where we, unfortunately, use Final Cut.

I would prefer to upgrade to an i7 and the latest, but just can't spend the money. Maybe someday!! I always stay about one or two generations behind in tech and accept the limitations of the practice.

I do like Win 7 over XP now that I have gotten used to it, and I was a BIG fan of XP.

Dave T2
TheRhino wrote on 10/18/2011, 2:27 PM
Is the OP kidding with us?

The 6 year-old entry level system the OP is running only has a X1300 video card and I think it was built-into the motherboard on that version of Opliplex. We installed those systems in a school about 6 years ago and they cost around $400 each, so definitely an entry-level system for even back then. With 2GB of memory, they were JUST capable of running XP nicely but fall well-short of Windows 7 specs... Yes, you can install Windows 7, but it just barely runs. My lawnmower engine will also move my car, but tops out at 5mph...

In comparison, I just helped my Uncle buy a new entry level system for $350. It came with a dual core 2.6ghz processor, 6GB or RAM, 1TB HD, HD video card with dual output (one is HDMI), DVD burner, etc. For $275, after a trade-in program, I also purchased a dual core laptop recently and upgraded it to 8gb for $50 extra. Both run Windows 7 nicely and both would work nicely with any recent version of Vegas.

IMO the OP should have opted to buy faster hardware vs. software updates... Faster HW will do more wonders than faster SW unless you really, really need a feature lacking on earlier versions...

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...

ChipGallo wrote on 10/18/2011, 2:50 PM
Something is hinky. (Now I see from his web site, he is a video pro. What a comedian!) He lists these system specs:

System #1
Windows Version: XP
RAM: 512mb - 1gb
Processor: AMD Athlon 3700+ 2.4GHZ
Video Card: NVidia Geforce 6800 GT
Sound Card: SB Audigy Audio (A400O)
[r]Evolution wrote on 10/18/2011, 3:17 PM
People wanted refunds after purchasing FCPx because of what FCPx lacked.
It's weird to see someone asking for a refund of Vegas Pro 11 stating that it offers too much.

Keep the software (Vegas 11 Pro), as you probably got it at an incredible savings versus buying it later, and save up to upgrade your Hardware.

At any rate, I think the best bet has already been stated: contact Customer Service and state your case.
Jeff9329 wrote on 10/19/2011, 9:29 AM
I was able to get a refund. Just give them a call.
peterB wrote on 10/19/2011, 9:57 AM
I think subsequent updates will resolve all the problems. I'm using dual quad xeons, 32 gig RAM and nVidia QuadroFX 4800 so haven't experienced any problems with any version of Vegas. 150$ is just over an hour's editing charge so I don't know why anyone would freak out about such a trival amount of money.
FrigidNDEditing wrote on 10/19/2011, 11:50 AM
lol, what on earth??? why do you people buy before you try?

This is kind of absurd, it's a software that you can't really un-own a license of, and you had a 30 day trial offer of, and you bought it outright, and then want a refund, but you'll end up having a license key to both Vegas 11 and the NB Pro Titler...

That seems kind of shady almost. I think they shouldn't have given you a refund because you knew full well there was a trial before you bought, but that's just my personal opinion.

Dave
Jeff9329 wrote on 10/19/2011, 9:29 PM
See if I send you any more work!

Just kidding, I will.

Im sure that SCS can tell when or if the license # is used. Probably can remotely disable too. Plus, I have no way to use the product, and like someone else said, $139 is not a lot of money to fight over.

I was actually looking forward to moving on past V8. But, it still works fine.
Tom G wrote on 10/20/2011, 9:32 AM
Deleted
Tomthumb



FrigidNDEditing wrote on 10/20/2011, 9:38 AM
often times I will buy on the sale price and then wait to use till I find it to be stable enough, but from 8, you're really missing a few good things there. I'm by no means looking to fight or trying to insult people, it just kinda left me a little surprised, but I could actually understand ordering outright, if you're planning to upgrade from 8. Though personally I think that you're probably better off just holding on to it at the good price and using it when it's stabilized in a point or two. When they change that much to the software's core stuff, it's bound to have more problems than normal.

Dave
Gary James wrote on 10/20/2011, 10:23 AM
I just received my boxed version of S.V.P. 11.0. Installation went pretty smooth except for a sub-directory security permissions issue during the installation of Media Manager. This was my first install of MM. It was not an upgrade. A little manual tweaking of the permissions, and the install finished without problems.

My first impression of v11.0 is .... this release was not ready for prime time. This release has major memory allocation problems. My old standby version of Vegas v9.x has none of the problems I'm now seeing in version 11.0. I typically work on very large slideshow projects. My projects have well over 1000 large .jpg and .png images in them. And when I apply random transitions to all of these images using the Timeline Tools Vegas Extension that I wrote, I get intermittent "out of memory" errors and crashes that simply do not happen in Vegas Pro 9.x.

In my first day using Sony Vegas Pro v11.0, I've encountered and sent in over two dozen crash reports. My biggest regret is that in one of my projects, I accidentally told Vegas to overwrite my old .VEG project file. So, for that project I'm stuck using v11.0.

I'm sure that Sony will address these problems soon. But it's too bad that for whatever reason, they decided to release the product early with so many major flaws.
FrigidNDEditing wrote on 10/20/2011, 2:30 PM
Hey Gary, I feel your pain there, I've tested out new versions on projects just to see how it's doing, and accidentally saved over my file. That being said, I think that there were some changes to the scripting stuff in this one too, so it may be what's causing some of your problems if your scripting tool is having problems at all?

You might be able to pull a .veg.bak version if that's possibly still in the V10 iteration of your project ( depends on how long you had it open ). Hoping maybe that will fix it for you but best of luck! Oh, and TLF is right on the saving off versions of your project file :), even though I know it's not intentional, I've saved my own backside several times because of that.
FrigidNDEditing wrote on 10/20/2011, 2:36 PM
TLF,

Disregarding the rest of your comments, your last line is one area in which you are quite mistaken.

There was a huge amount of change in this version from the previous version. While the tools may still be 'the same tools' they all had to be re-coded to work in what is likely a new engine which also had to be coded. The interface and automation of every facet individually and with curves or keyframes has been added to every FX tool in the set, and support for additional tools has been added, so in point of fact, there is quite a dramatic amount of change between this version and previous versions. This would make backwards compatibility even harder than it would have been before not easier.

Not trying to argue with you or anyone else, it just seemed that you may not have been grasping the amount of change that has actually occurred in this version, and that's certainly not all of it either, just the obvious stuff.
Gary James wrote on 10/20/2011, 4:02 PM
FrigidNDEditing

At first I suspected there may be a compatibility issue with my Extension and S.V.P. 11. But after spending several hours analyzing my code in the debugger while v11 is running, I came to the conclusion that the problem lies in Vegas.

My Extension is compatible with 32 / 64 bit versions of Vegas Pro back to 8.0. That means I'm NOT using any new API calls that may have been added to the Interface in v11.0. It is the software developers responsibility (int this case Sony) to maintain compatibility with existing Interfaces, Also the problems are intermittent. This is usually a sign of failures due to memory allocation problems. Available memory gets used up in thousands of small chucks that, if not properly returned to the memory pool when no longer needed, causes memory fragmentation. This is where it becomes impossible for the program to request memory from the pool in large enough chunks to meet it's needs. This causes out of memory errors, even thought there is plenty of memory available, but not in large enough chunk sizes to give to the program.

Also, if I limit adding Transitions to about 400 images at a time, v11.0 seems to be able to handle it. This isn't a sign of incompatibility. And finally, Vegas version 9.x works perfectly.

Feel free to try it out and let me know what you find:

http://www.nfatoys.com/moasoftwarellc/




Gary James wrote on 10/20/2011, 4:21 PM
prepare yourself for the wrath of the posse who will tell you:

1. you should have tested the trial version first.
2. you shouldn't have used it mid-project
3. you should have made a back-up of your projects

TLE.

Yes, it was a lapse of better judgment that sent my fingers to click on the Yes button to overwrite my .VEG project file. But fortunately that particular project is an older one; not one I'm working on.

After installing v11.0, I opened several older projects to make performance comparisons. But that's when I ran into the "out of memory" crashes. So I never had a chance to make those tests.