Comments

flacnvinyl wrote on 8/7/2012, 4:07 PM
They are a little late to the game. The entire thing means nothing to someone like myself using a Galaxy 670 card. It should be fully supported and running smoothly. System is a rock.

If they release 12 before updating 11 to something solid, I will immediately leave Vegas. I am the middle of wrapping up a series of projects and am HEAVILY considering doing the CS6 migration.

THIS, is why Red Giant and other plugin developers don't take Sony seriously.
ushere wrote on 8/7/2012, 6:51 PM
not really helpful in as much as these problems should have been sorted out BEFORE release.

if there's no fix forthcoming in 11 for the wacom problem then, to use grazie's term, 'taxi!'
VidMus wrote on 8/8/2012, 11:20 PM
ushere said, "not really helpful in as much as these problems should have been sorted out BEFORE release."

That is absolute non-sense and not realistically possible!

When SCS released version 11 there were bugs and issues they could not have possibly foreseen, considering the major re-write of the code that Vegas uses and the fact that there are so many various system configurations out there that the programmers and beta testers most likely never heard of and/or never used with an NLE. The Wacom tablet or whatever it is called? How many NLE users have that on their system(s)? And there are many, many more!

There were unforeseen issues with the video card drivers. There were unforeseen issues with the New Blue Titler that SCS is not responsible for in any way shape or form. It is simply not their product and SCS is not responsible for any other company’s product. Even so, they have made an excellent effort to go beyond what they are required to do in helping with other company’s products.

To those who choose to leave Vegas for another NLE I sincerely wish the best to you.

diverG wrote on 8/9/2012, 7:25 AM
When SCS released version 11 there were bugs and issues they could not have possibly foreseen.

So how come 'Print HDV to Tape' took 4 months to correct. It was downright carelessness/incompetence in the first place. Just too much haste to release VP11.

I now have little faith in SCS sorting out VP11. VP 12 is now the priority.. Like others on this board I received and email inviting me to become a beta tester for 12.
I see no point in joining as the upgrade $$ have been spent on cross grade to Edius6 with Edius 6.5 included.
Maybe I'm pushing my luck now but not a single crash on E6 (since early May) and the newer E6.5 also running smoothly.

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & 122(194), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

farss wrote on 8/9/2012, 8:08 AM
"When SCS released version 11 there were bugs and issues they could not have possibly foreseen"

Really, wow, I've read some pretty scathing posts regarding their lack of competance but your post takes the cake.
It is the responsibility of any engineered product's vendor to forsee problems and gee whiz, variations in hardware, operating systems and drivers are a very well understood part of compatibility testing.

As for Wacom tablets, please, a very large percentage of people working in the visual arts use them. I can assure you many of the beta testers would have them. That you think them uncommon does reveal how little you know about this industry.
That SCS have managed to break something that used to work shows a distinct lack of "regression testing", seeing as how you're such an expert on software and how it's tested I trust you know what that means.

"There were unforeseen issues with the New Blue Titler that SCS is not responsible for in any way shape or form. It is simply not their product and SCS is not responsible for any other company’s product."

Rubbish. SCS supplied NB's code, if it doesn't work right with SCS's code it is SCS's problem. Adobe uses a lot of 3rd party code and if fails I sure blame Adobe. If you buy a new car it comes with tyres made by a 3rd party vendor. If those tyres fail and you get injured as a result the first person you sue is the car manufacturer. They were the ones who determined those tyres were suitable for their vehicle. Maybe the car manufacturer will in turn sue the tyre manufacturer but that's of zero interest to the purchaser of the vehicle.


Bob.
Andy_L wrote on 8/9/2012, 9:46 AM
there were bugs and issues they could not have possibly foreseen, considering the major re-write of the code that Vegas uses

Who says there was a major re-write? V10 added 3-d support and V11 added GPU rendering support. I see both as additions to a outdated code base, and predictably both added a lot more strain to existing problems (including poor development habits).

Really the problem is that there hasn't been a major re-write. Legacy bugs are the story of the Vegas upgrade cycle now. Things I saw in V9 persist through the subsequent upgrades. You can believe SCS developers are so incompetent that they can't fix the simplest of bugs, or (more likely) that their hands are tied until the powers that be decide to do a ground-up overhaul. Or kill the product.

That the upcoming release is presumably going to be called V12 suggests to me that it's going to carry on all these unfortunate traditions. Though I sure hope I'm wrong!
JJKizak wrote on 8/9/2012, 3:03 PM
That's very interesting, Vegas Pro code base outdated. Any particulars here?
JJK
Andy_L wrote on 8/9/2012, 5:35 PM
I should be clear that's my speculation. Obviously I'm not a Vegas developer and I don't have experience coding large commercial products. Others have suggested they've talked to third party developers who find working with Vegas uniquely challenging, and suggestions that Vegas itself is built using an outdated environment, but I have no direct knowledge of either, so again, I'm speculating.
TheRhino wrote on 8/9/2012, 6:26 PM
I'm hoping that switching to a 64 bit-only code will clean things up. IMO there are issues with attempting to keep the code compatible with a 32-bit OS. Adobe & Apple both went to 64-bit only code with Apple basically re-writing FCP from the ground-up. IMO they introduced FCP X as a "lite" version based on this new code and will offer future additions with more powerful features. Although their decision to drop FCP 7 compatibility made everyone furious the positives outweigh the negatives. They now have a code that is not bound to legacy issues... Only the Apple team (or SCS, etc.) know what legacy code is creating havoc...

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