SCS wants help to "improve Vegas Pro 11"!

Comments

TeetimeNC wrote on 4/15/2012, 8:15 AM
>Also Adobe use CUDA and seem to have their own code. SCS use OpenCL.

CS6 supports OpenCL, but of course we don't know yet if CS6 will be stable.

/jerry
VanLazarus wrote on 6/25/2012, 6:35 AM
Unfortunately, it appears that all efforts to report bugs and assist in identifying methods to recreate them does not have any effect on the speed with which they are fixed. In fact, SCS has been unable to fix even ONE bug I have reported in the last 4 months.

My concerns for the degrading stability of Vegas Pro seem to have fallen on deaf ears, and if SCS is concerned, I have yet to see any results of their concern. I greatly fear that Vegas Pro 12 will be released with as many bugs as Vegas 11 currently has, probably more.

I sincerely hope I'm wrong, but it is not looking good.
farss wrote on 6/25/2012, 7:23 AM
"Unfortunately, it appears that all efforts to report bugs and assist in identifying methods to recreate them does not have any effect on the speed with which they are fixed. In fact, SCS has been unable to fix even ONE bug I have reported in the last 4 months."

Thanks for the update although I held out a glimmer of hope that the news would be better. I'd at least of hoped they could have identified the cause of one of your problems even if they were not able to fix it quickly.


Bob.
craftech wrote on 6/25/2012, 9:27 AM
A nice "start" would be for one of the SCS reps to post a comment right here in this thread instead of all of us having to draw conclusions or make assumptions both positive and / or negative.

John
Christian de Godzinsky wrote on 6/25/2012, 11:22 AM
Ditto...

And what about the sudden SCS' public interest to find new beta testers among us (complainers/whiners) - a thing totally unheard and unseen before..?

My whining will probably diminish if they accept my application, but that is not probably the solution to fix the real (software) problems - to quiet us down? Reading your info about the ability (or disability) to fix even a single error you reported during these 4 moths, is somewhat scary... How would my input differ from yours... ?

I would really be prudent to get some first hand info from SCS, some kind of constructive update what is happening? We need that definitively, we who have problems and need to reinforce our believes in this somewhat crippled product. What is going on? When do we get the next patch and what will be fixed?

It would be very shortsighted of SCS to publish V12 without fixing the serious problems in VP11 first. History tends to repeat itself, but not anymore for me. Going from VP9 to VP10 was already a horror that is hard to forget...

Again - I understand that many of you have a completely smooth ride - but for the rest of us - that fact does not make our lives easier trying to work(around) with a product we once loved so much...

Cheers,

Christian

WIN10 Pro 64-bit | Version 1903 | OS build 18362.535 | Studio 16.1.2 | Vegas Pro 17 b387
CPU i9-7940C 14-core @4.4GHz | 64GB DDR4@XMP3600 | ASUS X299M1
GPU 2 x GTX1080Ti (2x11G GBDDR) | 442.19 nVidia driver | Intensity Pro 4K (BlackMagic)
4x Spyder calibrated monitors (1x4K, 1xUHD, 2xHD)
SSD 500GB system | 2x1TB HD | Internal 4x1TB HD's @RAID10 | Raid1 HDD array via 1Gb ethernet
Steinberg UR2 USB audio Interface (24bit/192kHz)
ShuttlePro2 controller

519tbarr wrote on 6/25/2012, 2:26 PM
Why can't sony creative software do something like this for Acid Pro?
Great for Vegas but the loyal Acid Pro users sure feel left out.
Andy_L wrote on 6/25/2012, 5:50 PM
Any time I hear the words Acid Pro I shudder. The fate of AP says a lot about Sony as a software developer.
Pete Ferg wrote on 6/25/2012, 7:38 PM
Remember Speed Razor? How long is Vegas viable?
Radio Guy wrote on 6/25/2012, 8:04 PM
Remember Speed Razor? Oh my God. Has it been that long. There was even a 64 bit back version in the 90s running on my old Dec Alphas. When 500Mhz was considered a real power house processor.