Kepler and Sony Vegas – (angry face)

[Roger Bansemer]

Vegas 11 was full of issues and problems. It was horrible. Hope someone else will post because maybe version 12 will work although your probably fed up by this time. I know the feeling.

[John Rofrano]

[John Kendrick] “I am annoyed and pleased at the same time! I am pleased I know the hardware is fine and VERY annoyed that I can’t use it properly!”

Are you saying that you are annoyed that Vegas Pro 11.0 software that was written before the Kepler cards came out could not predict the future changes in architecture and magically work with newer hardware? Or is Vegas Pro 12.0 not working for you with a Kepler card?

Because if you’re mad about Vegas Pro 11.0 not working with Kepler cards, point your anger at NVIDIA for messing up their own backward compatibility.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Dave Osbun]

I would be angry, too, if I spent over $450 on a graphics card and not be able to take advantage of its power. But John is correct in that it’s really nVidia’s fault. Maybe you should contact Sony Creative Software and ask them if Vegas 12 will take advantage of it. I just upgraded from Vegas Pro 8 to Pro 12 last week, and I called Sony Creative Software to ask them if they had any ‘specials’ for me and not having to pay the $189 upgrade price. They gave me the upgrade for $151!!

Intel i5 3570K Ivy Bridge 3.40GHz quad core
Asus P8Z77V-LK
16gb RAM
ATI Radeon HD7850 2gb
Crucial M4 SSD + Seagate Barricuda 7200rpm
Windows 7 Pro 64

[John Kendrick]

Lack of information explaining that SVP12 doesnt work on Kepler is one thing that I am annoyed about.
I was surprised to see that this issue isn’t more clearly stated. People don’t upgrade often (like me) and when they do, they would hope that their new hardware would work with their software.

I haven’t and I am not complaining that Vegas Pro 11 doesn’t work with Kepler. I use solely 12 now.

If I had know that the 6 series nVidia cards (Kepler) didn’t work on Vegas I would have probably thought a little harder / waited until it was sorted.

Shelling out two or three thousand dollars, you kinda (maybe wrongly) believe that things should all slot together.

Money / hardware a side (as I am drawing other benefits from what I bought), I am frustrated that I spent many days of my life attempting to get something to work that never will (not on the current version of drivers / SVP12).

Do I blame Sony, partly – Do I blame nVidia, again, partly, this should be backward compatible with no issues.

I wanted to make sure that my post is out there so people, who like me what to maximise their bang for buck, can cacth this early and either not blow the money, or two, not spend days trying to figure out what the h3ll was wrong…

Overall I want my SVP12 to work on my new machine – I certainly didn’t expect my old kit to run faster!

[Dave Osbun]

I still don’t understand how you can blame Sony. You are trying to run brand new hardware technology on software that was released a few years ago. When I installed Vegas Pro 8 on my brand new workstation, my render times were barely better than it was on my 7 year old laptop. Again, not Sony’s fault as that version of the software was not coded to take advantage of today’s hardware architecture. How long have Kepler cards been out- just a couple of months? It’s wrong to throw any blame at Sony here.

[John Kendrick]

[quote] Lack of information explaining that SVP12 doesnt work on Kepler is one thing that I am annoyed about.[/[quote]

Just to expand on this – I am frustrated there is little or no clear explanation that Sony Vegas Pro 12 does not work properly / well on nVidia 6xx series cards due to the Kepler changes – be it nVidia or Sony fault – that is my issue.

[quote] You are trying to run brand new hardware technology on software that was released a few years ago [/quote]

Nope this is actually related to Sony Vegas Pro 12 only.

[John Kendrick]

– AH, the penny has dropped –

What you all don’t know is that I specifically bought my new machine to work on / with Vegas Pro 12

[John Rofrano]

[John Kendrick] “Just to expand on this – I am frustrated there is little or no clear explanation that Sony Vegas Pro 12 does not work properly / well on nVidia 6xx series cards due to the Kepler changes – be it nVidia or Sony fault – that is my issue.”

Well I have to agree with you there. The Sony web site clearly says that it works with GTX 4xx Series or “greater” and that’s a very dangerous statement for Sony to make. They should update it to say GTX 4xx or 5xx until they know that 6xx works properly. Now you know why Adobe lists the specific cards that work. CUDA compatibility doesn’t seem to be that great.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Dave Haynie]

[John Rofrano] “Now you know why Adobe lists the specific cards that work. CUDA compatibility doesn’t seem to be that great.”

Yup… CUDA and OpenCL are abstractions. Programs like Vegas write to those abstractions, not to any specific hardware. Adobe started out CUDA-only (they’re doing OpenCL now), tested on a very specific set of cards, perhaps even working around bugs related to their performance, and recommend Premiere just for those few cards. Even that’s dangerous, since a change in the CUDA driver could break that compatibility, if nVidia got sloppy.

Sony’s done testing on some cards, and they recommend the series of GPUs supported primarily based on the features they’re using in OpenCL. And they specifically call out some cards that are tested. But a very large part of the puzzle is in the hands of the drivers.

All OpenCL code is basically written in a high-level language. When you want to use it, that code is compiled quickly for that specific GPU — nothing Vegas or Premiere or anyone else has any idea about, prior to that compile being called for. Then the driver serves to manage data being sent to and results back from the card… which of course is running asynchronously to the main CPU. Problems in the compiler, problems with the efficiency of CPU to GPU communications, etc. that’s all on the driver’s side the problem.

It’s technically possible that Vegas would use some operations that just don’t map well to the Kepler, but I’d be extremely surprised, given how the GPUs are all actually evolving toward GPGPU use… new chips rarely deprecate old features, they add new capabilities. Far more likely that the driver you’re using has big problems.

-Dave

[David Alfredo]

Hi guys, I’m using Vegas Pro 12 build 486 with Windows 7 64 Ultimate SP1 and today performed a test with a friend’s 660 Ti… a template that takes me 10 minutes to render at full 1080p with and old GTX 260 took only 3 minutes with the 660 Ti (Kepler architecture) even if only 25% of the CUDA cores are being used as shown in GPU-Z monitoring tool, the 660 Ti GPU activity is way lower than that of the 260 while rendering… but definitely it’s an improvement and had no issues with it using some other random projects and templates, I’m on the latest Nvidia beta drivers 314.14 and Dynamic preview RAM is set to 150 even if it says 3072 MB available (Gigabyte 660 Ti 3GB model).

I guess it’s a matter of time that both Sony and Nvidia provide the updates/drivers necessary for Vegas Pro 12 to take advantage of these increasingly popular cards, they’re very powerful and would benefit sales of both said cards and Sony Vegas, I’m sure they’re at it.

Well that’s all, cheers !