Comments

rs170a wrote on 1/18/2014, 12:06 PM
Those that do know can't say. Everyone else is guessing.
Having said that, my prediction is NAB in Las Vegas, April 5 – 10, 2014

Mike
wwjd wrote on 1/18/2014, 7:16 PM
12 has been failing and worthless to me (and many others here) since the day I wasted $130 on it. If they release 13 to "Fix the bugs" in 12, we should get it for free.

When cars fail in a massive scope, they have recalls costly to the company..... when software fails, I guess we just go "Oh well".

PRETTY DOUBTFUL I'LL THROW ANY MORE MONEY WAY ON 13.

(caps to help stress how I feel)
John_Cline wrote on 1/19/2014, 7:16 AM
Conversely, there are thousands of Vegas Pro 12 users (like me) who are not having any problems at all...
ritsmer wrote on 1/19/2014, 8:06 AM
... right, John - and here is one more ...
Rv6tc wrote on 1/19/2014, 11:27 AM
Your success does not nullify his issues.

I had huge problems with VP10. It's frustrating to hear person after person chime in saying that their's works fine, which lends the impression that "It must be YOU" (Which one Vegas Forum member actually said to me). As a result, when VP11 worked very well for me I refused to get 12, which sounds like the way he feels.

I speak from experience, it's very frustrating when you can't get it to work and seemingly everyone else can.
Christian de Godzinsky wrote on 1/19/2014, 11:55 AM
Probably those that have no or little problems has the GPU rendering completely turned off. Alternatively, those that have no or little problems are running on old GPU's like GTX560-570-580.

I have a new computer with a GTX660Ti GPU and I get numerous crashes if I try to render videos including jpeg stills. Just to mention ONE problem. Vegas GPU page does not say that this hadware is not compatible.

Fine - I can (and I am forced to) run CPU only, but it seems that VP12 is so much slower than VP10 when rendering CPU only. It's like SCS put all eggs in the GPU basket (that is still seriously broken) and that CPU rendering is not more that much optimized...

So I'm running very slow renders and cannot use some advertized features. Well, not at least without getting from somewhere a second hand used GPU. I would not call this progress... In principle I refuse. SCS needs to fix this.

So it is MY fault that Vegas does not perform without problems? Or is it Vegas'? All my other (NLE) programs run completely fine on the same hardware.

SCS MUST get this sorted out in VP13! And it should be free for us that still have trouble with VP12 after numerous (are they 7?) bug fix releases...

Sorry to be so negative. Coming from Vegas 6 ... The reliability of this wonderful software took the biggest hit after SCS started to play with GPU's...

Agree, I'm glad for all of you that can run full speed. But your smooth run does not help us others...

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

OldSmoke wrote on 1/19/2014, 12:17 PM
As I already mentioned in another thread:

"I rather use "old" hardware and drivers then wait for a new version of VP that may or may not support newer HW. Also keep in mind that the "new" hardware is old in 6-10month and then what? You could have saved yourself plenty of hours by going the proven route.
I am working everyday on my system and I have 0, Zero, nada issues with GPU acceleration; that is worth to me more then the bride of using the so called latest hardware.
The last project was 3 cam multicam project with fx and transitions, text overlay, 6 audio tracks and it plays back at Good/Full 60fps in my preview window and simultaneously on my external preview monitor. It's amazing what "old" hardware can do."

I come from MediaStudio Pro and if you wanted it to perform well, you had to get hardware en/decoder cards that where very expensive. I then switched to VP7 and I am so glad VP11 came along as suddenly preview and render times where cut in half with my GTX460. I quickly changed to a GTX570, the 580 was out of my price range, because that was what SCS had done all it's testing with at that time. VP12 is just an extension of that and now you can get a GTX580 off eBay for $150... nothing is easier then that.
They only thing I grant you is that SCS doesn't update their website and make it clear that newer cards don't work as well; aside from the R9 series.
As for bug fixes; have you ever counted the amount of updates you get on your Windows version? I believe its more then 7 but I don't hear anyone complaining.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

JJKizak wrote on 1/19/2014, 12:22 PM
At least Vegas doesn't do what the Adobe Reader update from 9 to 11 did to XP, it blew out my Windows XP options file that contained every option in Windows and 3rd party apps. and the favorites and address book and the internet connection. You ain't never heard such words as a result.
Vegas 12 works well in my old Vista 64 machine with GPU on with the old GTX 8800 card with the newest Nvidia driver and very few 3rd party apps.
JJK
BruceUSA wrote on 1/19/2014, 1:32 PM
Oldsmoke, Well said.... my 3930K @5.0Ghz and 6970 card are old hardware as well. But it is rocking hard for many years to comes, I can't see any old hardware issue with mine.

Intel i7 12700k @5.2Ghz all P Cores, 5.3@ 6 Core, Turbo boost 3 Cores @5.4Ghz. 4.1Ghz All E Cores.                                          

MSI Z690 MPG Edge DDR5 Wifi                                                     

TEAMGROUP T-Force Delta RGB 32GB DDR5 -6200                     

Samsung 980 Pro x4 Nvme .M2 1tb Pcie Gen 4                                     

ASRock RX 6900XT Phantom 16GB                                                        

PSU Eva Supernova G2 1300w                                                     

Black Ice GTX 480mm radiator top mount push/pull                    

MCP35X dual pump w/ dual pump housing.                                

Corsair RGB water block. RGB Fan thru out                           

Phanteks Enthoo full tower

Windows 11 Pro

Jedman wrote on 1/19/2014, 3:33 PM
Heres a thought..
It seems the frustrating thing for most people is the "Not knowing" when ordering hardware which card, processor, mobo, ram, is going to work.
I say the whole combo because it must be more than just the GPU that has a bearing on it. I have a 3930k, GTX580 and I cant use GPU successfully, if its on my previews are worse/slower and I have more strange hangs/crashes.
Yet other people with same combo of processor/GPU are happy and using GPU with success.
I would applaud Sony if they just came out and said,
"You need this (insert specific Mobo, Processor, GPU, Ram and other hardware that makes a difference)".
Or, offer a prebuilt "Sony Pro PC" made to their specs.
I know this wont keep all the people with existing hardware happy, fair enough.
But with a new version Sony should just stop trying to keep all the people happy, all of the time.
I for one (and I can imagine a fair few others) would build/buy a new system today If I was guaranteed, It would just work! (with maximum pun intended :)
wwjd wrote on 1/19/2014, 4:46 PM
I bought a brand new i7 with lots of great parts to run 12 and it still has issues. 11 is practically flawless to me so I have that to rely on. Just YESTERDAY, thought I'd try 12 for a tiny project.... some titles, followed by a 8 minute video that was already complete.... 12 crashed randomly in the middle. Fine. Started up again, got it setup, went to render final MOV, and it took ONE SECOND and completed successfully. REALLY?? No file was created. Rebooted, tried again, same thing, installed lastest QUICKTIME incase that had anything to do with, nope. Gave up on 12... again. Ima PC tech by day and my system runs very clean.
My new computer runs everything I own flawlessly INCLUDING Vega Pro 11. hmmmmmm

If they don't FIX 12, and sell 13, they are just money gobbling.
OldSmoke wrote on 1/19/2014, 6:15 PM
wwjd would you mind sharing those great parts are? I can't understand that you got VP11 running but not 12. Do you only have issues with Quicktime renders or others too?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

videoITguy wrote on 1/19/2014, 7:16 PM
As it has been stated many times in this forum by many members, you cannot fine tweak a system to run VPro11 versions and install with success a version of VPro12 that will run concurrently at the same level. You can have both on the same system only if you are willing to jump the hoops of system switching such as partitions or alternate boots.
No such interaction between 12 and 10 or earlier versions has been documented...it is a problematic perfection for 12 versus 11.
OldSmoke wrote on 1/19/2014, 7:56 PM
I am sorry but that isn't true at all. I have VP11 64bit and VP12 64bit on the same machine without any issue. You may however run into problems with 3rd part plug-ins as some may not work with 11 but 12 and vice versa.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

videoITguy wrote on 1/19/2014, 8:15 PM
As always it depends on what you are doing, and how you are doing it. Forget the employment of GPU for example.
NormanPCN wrote on 1/19/2014, 8:29 PM
you cannot fine tweak a system to run VPro11 versions and install with success a version of VPro12 that will run concurrently at the same level.


I'll disagree with that. Everything functional. OFX plug-ins show in both.
I have noticed Vegas with separate registry folder and separate AppData folders. Vegas does not install outside its own installation folder.

Limited experience however.
BruceUSA wrote on 1/19/2014, 8:40 PM
Sony Vegas benchmark is pretty complex right? Heavily FX and multi tracks on the timeline. I have no problem what so ever on VP11 and VP12 see pic in link, if you care.

VP12

https://www.dropbox.com/s/6zfs91fpvz4ype6/xdcam%20benchmark%20rendering.jpg




VP11

https://dl-web.dropbox.com/get/VP11%20benchmark%20MC%20AVC.jpg?_subject_uid=258671110&w=AABu0PZvjT17Qt9sc6QV2Sl4qBtPexROrqzoAnX8uWPbwg



Intel i7 12700k @5.2Ghz all P Cores, 5.3@ 6 Core, Turbo boost 3 Cores @5.4Ghz. 4.1Ghz All E Cores.                                          

MSI Z690 MPG Edge DDR5 Wifi                                                     

TEAMGROUP T-Force Delta RGB 32GB DDR5 -6200                     

Samsung 980 Pro x4 Nvme .M2 1tb Pcie Gen 4                                     

ASRock RX 6900XT Phantom 16GB                                                        

PSU Eva Supernova G2 1300w                                                     

Black Ice GTX 480mm radiator top mount push/pull                    

MCP35X dual pump w/ dual pump housing.                                

Corsair RGB water block. RGB Fan thru out                           

Phanteks Enthoo full tower

Windows 11 Pro

wwjd wrote on 1/20/2014, 6:18 PM
my specs. not TOL, but it's what I could afford:

i7-3770K Processor (4x 3.50GHz/8MB L3 Cache)
Motherboard ASRock Fatal1ty Z77 Professional -- 2x Gb LAN, 2x PCI-E 3.0 x16, 6x USB 3.0
32 GB [8 GB x4] DDR3-1600 Memory Module
NVIDIA GeForce GTX Titan - 6GB
1 TB WD VelociRaptor HARD DRIVE -- 64M Cache, 10000 RPM, 6.0Gb/s
2 TB HARD DRIVE -- 64M Cache, 7200rpm, 6.0Gb/s
[12X Blu-Ray] Pioneer BLU-RAY Re-Writer, DVD±R/±RW Burner Combo Drive
3D Premium Surround Sound Onboard

IIRC I ran 12 alone a while, it kept failing in ways I KNOW 11 wasn't so I added 11 (32bit)
VidMus wrote on 1/20/2014, 6:40 PM
@BruceUSA,

The VP11 link gives a 403 error.
Marc S wrote on 1/20/2014, 7:06 PM
I just tried the trial version and there is a nice new feature that shows the selected timeline clip length at the bottom of the timeline which updates live when while making length adjustments to the selected clip. Been waiting for that one for a long time.
TheHappyFriar wrote on 1/20/2014, 8:05 PM
I think it's an internet fact that everyone who complains a company should fix their old versions before releasing a new one will always buy the new one and make the same complaints.

The forum software should track those stats. :)
Steve Mann wrote on 1/20/2014, 9:51 PM
I am not seeing whatever you are referring to. Vegas has always shown the size of the region. Since there are no clips on the timeline, (everything on the timeline is an event) I am guessing you are describing the trimmer, but I am seeing nothing new there either.
Marc S wrote on 1/21/2014, 1:15 AM
It's not a region selection I'm referring to. All you have to do now is click select the clip and the length will show at the bottom right. If you drag the edge of the clip the time will update. It was Movie Studio Platinum 13 I tried out at a friends. I'm assuming this new feature will show up in Vegas 13 as well.