-
Is VP11 the ugly duckling?
Posted by Phil Seymour on October 31, 2011 at 6:27 amVP11 seems to have landed with a splat instead of a bang, or am I just being nervous? I have bought the upgrade, new titler and all, but from this and other forums it appears all is not well, so is anyone else thinking like me to leave it in its box and stay with 10 until 11a or b or 12 comes out?
Michal Bronec replied 14 years, 6 months ago 7 Members · 14 Replies -
14 Replies
-
Nigel O’neill
October 31, 2011 at 6:42 amJust used SVP11 for a 3 camera HDV multicam edit with Vasst Ultimate S. Apart from slightly different looking ‘render as’ templates and a few other cosmetic differences, it still works :=)
It is an evolutionary rather than a revolutionary change for what I do. I wish Sony would bring back Cineform… . I miss v8 🙂
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
John Rofrano
October 31, 2011 at 10:44 amWhat bang were you expecting? The biggest feature is GPU support and so I agree with Nigel that it’s an evolutionary release because you don’t see any change (i.e., the insides were updated but not the outside really). In general, it feels faster for me because I have a lot of 3rd party FX and in Vegas Pro 10 it was taking several seconds for the FX window to display. In Vegas Pro 11 it appears in under a second. Perhaps this is because almost all of the Sony FX are OFX now which allows much greater keyframe control. Overall I’m very happy with it so it’s a big bang with me. It’s all I use now.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Thomas Roell
October 31, 2011 at 11:47 amCineform. As I’m here the noobie, this advise might be worthless, but try this:
(1) Pick a “Video for Windows” template (say HD 720-60p YUV)
(2) Select “Customize Template”
(3) Pick “CineForm Codec” in the “Video format” dropdown”
(4) Click in “Configure” to select your Edcoded format/quality
-
Nigel O’neill
October 31, 2011 at 12:03 pmSorry, I meant being able to capture using the Cineform codec and then edit your footage like butter. None of this Cineform Neo Scene or Vasst Gearshift-ing required to convert your AVCHD footage to an easy to edit AVI container. It was in SVP8 but disappeared when SVP9 hit the shelves and is probably the main reason why previews are so laggy. With SVP11, SVP finally takes advantage of/optimises the use of CUDA/OpenCL technology for previewing and rendering. But if you want high performance during editing, Cineform Neo Scene and Gearshift still rock.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Phil Seymour
October 31, 2011 at 12:11 pmThanks for your encouragement John. I wasn’t expecting a huge difference, but the GPU acceleration was an important reason to upgrade. The difficulties that many other users seem to be having with the NewBlue titler is of concern as I was hoping for something better than the awful Pro titler on offer in the previous versions. I run a fairly lean editing machine with Vegas, Architect and After FX and nothing else, so possibly will not encounter the problems others have experienced. 10d has been good to me, whereas some have had issues. Unfortunately odd behaviour is part of the Windows PC world with so many variables. Maybe I am just paranoid with New Version jitters 🙂
-
Michal Bronec
October 31, 2011 at 3:02 pmI can transcode my HDSLR videos to Cineform (in Vegas) without buying Cineform Neoscene? Wow, I didnt know that! I have to try it.
-
Edward Troxel
October 31, 2011 at 8:51 pm[Phil Seymour] “The difficulties that many other users seem to be having with the NewBlue titler is of concern as I was hoping for something better than the awful Pro titler on offer in the previous versions.”
Wow… a handful (out of the hundreds of people downloading Titler Pro) of people have an issue where their video card won’t support Titler Pro and that’s “many other users”…
There do seem to be a few cards that should be able to handle titler and are not for some reason. NewBlue is working with those people to figure out why. In MANY cases, simply updating the video driver and Titler Pro to the most current versions has resolved the issues. And in a few cases, the card simply isn’t powerful enough.
-
Phil Seymour
October 31, 2011 at 10:30 pmI understand where you are coming from Ed, and I probably have had a knee-jerk reaction. Proof will be in the installation… here goes….
-
Nigel O’neill
November 1, 2011 at 3:51 amYou used to be able to capture in Cineform Neoscene
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
John Rofrano
November 1, 2011 at 12:35 pm[Nigel O'Neill] “You used to be able to capture in Cineform Neoscene”
You still can capture in NeoScene if you are using HDV. You can also batch convert if you are using AVCHD. I don’t see the difference. In fact, it’s faster with AVCHD because it can be faster than real-time.
BTW, NeoScene does not “capture” to CineForm. It captures to HDV and converts to CineForm as it’s capturing so you are still transcoding the video to CineForm (you even have the option of keeping the HDV files as well). This is *exactly* the same as you would do with AVCHD. No difference.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up
