Multiple problems with Sony Vegas Pro 11

Vegas Filmmaker wrote on 10/18/2011, 3:49 PM
Hi everyone, I joined the forum to see if there's any fixes to some of these issues. Vegas Pro 11 has caused me a bunch of problems. I've been using Vegas 8-10 largely without problems, though with Vegas 10 I've been experiencing more bugs and may even consider rolling back to Vegas 9. For now I'll continue using Vegas Pro 10.

Here are my system specs:

i7 950 3.04 Ghz CPU
12 GB DDR3 RAM
GeForce GTS 450 (until yesterday a Radeon 6870, which Sony says should work with the GPU acceleration, but Vegas didn't utilize it, and I couldn't even manually make it do so. The option wasn't available, even after installing the latest drivers)

Here are my problems.

1. Multicamera editing is choppy. It's really slow, maybe around 10 frames per second. I'm editing avi video that's 1440x1080. This was never a problem on Vegas 9 or 10. I had 8 video tracks of the same high definition footage in Vegas 10 with barely a stutter. Same footage and projects. It's almost unworkable, because on video with lots of motion and camera movement, it's hard to tell exactly what I'm cutting. Same thing when I add NewBlue's 3D titles, even with one video track in addition to the titles. Vegas slows to a stutter.

2. Every single one of my avi files, of which I have thousands, are being set to an aspect ratio of 1 when the resolution is 1440x1080. That requires an aspect ratio of 1.33. In Vegas Pro 9 and 10 my footage is fine-I just tried opening the same projects in Vegas 10 that I tried in 11, and the aspect ratio was 1.33 as it should be. To edit on Vegas 11, I have to right click every single piece of video media and adjust the aspect ratio to 1.33. Choosing "Adjust source media to to better match project or render settings" did nothing to help.

3. The video stabilizer doesn't work. Vegas gives an error message at 99% of any subclip I try to stabilize. And, while not a bug, Sony took away the feature to easily stabilize individual events on the timeline. Now I have to create a subclip of any video I want to stabilize, and even at that, Vegas basically crashes before I can stabilize anything.

4. As I mentioned, Vegas Pro 11 doesn't recognize or list my Radeon 6870 as a card it can utilize for GPU acceleration.

Until there are fixes for these, I'm going back to Vegas Pro 10, or even 9. I only like Pro 10's stabilize feature. But even 10 crashes for me fairly often.

Comments

TheRhino wrote on 10/18/2011, 7:29 PM
Although I haven't messed-around with Vegas 11 yet, I can say that Vegas 10 was acting-up after we installed a couple of other programs like Adobe CS5.5 which installs their own flavor of codecs. After that install, I had a problem with the aspect ratio of my Vegas footage going out-of-wack and some other issues that really freaked me out. Past VEG files that were flawless started showing glitches or even locked-up...

After saving a current image of the drive, I went back to an earlier hard drive image where Vegas 10 worked fine. I tested it, and all worked fine. Therefore I unstalled Vegas, installed CS5.5 & other programs, and then re-installed Vegas - LAST. All seem to work correctly now.

As a video editor, I use Vegas EVERY day and this is how I earn my living... However, I do not install the latest version until revision "b" or "c" is released with most of the kinks worked-out. THEN, and this is important, I reinstall my OS from the ground-up. I keep the last version of Vegas just for security, and then install the new version. I THEN install any codecs or other scripts, etc. that work with Vegas. This year I will likely re-install CS5.5 & other less-used programs before Vegas 10 & 11, but the rest holds true...

Along the way I always make multiple images of my HD. For instance, when I reinstall this year, I can start-out with an image of Windows 7 64 that does not have any programs installed yet...

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

Vegas Filmmaker wrote on 10/19/2011, 4:59 PM
Good information. I wanted to upgrade quickly since I had an offer to upgrade free, but I've already switched back to Vegas 10. Way too many bugs and issues like changing the aspect ratio on my footage (what on earth could that be about?). I'll keep it ready for when Sony fixes these issues.
DavidMcKnight wrote on 10/19/2011, 5:52 PM
Be sure to log that as a bug in their support system (tab at top of this page) and not just here on the user forum. Hopefully there won't be too many of those but they usually do a good job of fixing them in rev A

...or B....