Who is Now Using V11.683 for Paid Projects?

TheRhino wrote on 5/17/2012, 7:34 AM

PLEASE do not turn this into a rant/rave discussion about Vegas or compare it to other NLEs (like past forum posts...) I just want to know how many of you are happy with the 683 update & now find it stable-enough to use for paid projects.

As for me, I have used V11.683 for several short paid projects without any glitches. However, I have started-out all 2+ hour projects in Vegas 9.0e. Once I nail the cuts, color correction, etc. I load the project into V11 for 3rd party FX & final render. So far, so good. Right now my biggest dislike is the new arrangement of the color wheels but I am adapting... I also do not use GPU accel. because our video cards are not CUDA....

Back to post

Comments

Editguy43 wrote on 5/18/2012, 1:02 AM

I have used it pretty heavy for the last couple of months for projects, the only weird problem I have had is on a couple of renders to AVI there would be no audio in the render I checked the timeline and it worked fine and also checked the render settings still no problem. When I re-rendered the audio would be fine. Anyone else had that problem.
Other than that I am enjoying V11 ( really nice cause my MS natural mouse wheel zoom is now fixed) yipppeee...

Most of my projects are still in SD from clients, and AVCHD from my camera.

Paul B

Former user wrote on 5/18/2012, 1:45 AM

My day job is VP11, and my freelance gigs are VP11. So yes, I'm using the latest version of VP11 as paid gigs (if ALL your bills count).

Jr. Pascual wrote on 5/18/2012, 2:34 AM

Same here. VP11's latest build on paid gigs. Ingesting AVCHD multicam, output to mpeg2, SD & Blu-ray & mp4.

JohnnyRoy wrote on 5/18/2012, 9:42 AM

> "As for me, I have used V11.683 for several short paid projects without any glitches."

Ditto here... been making money with Vegas Pro 11.0 just like all the versions before that. In fact the last 6 Boris TV episodes I've produced have all been on Vegas Pro 11.0 with whatever the latest build was at the time and the Boris BCC8 beta and it's been stable for me.

I also did a live one hour Boris Webinar with Vegas Pro 11.0, BCC8, & Boris RED where I was doing some pretty advanced compositing and FX and it was very stable. I had no problems in the dry run and it crashed once during the live webinar (but I was using beta plug-ins so there is no telling who was at fault)

You can watch the Boris Webinar at the link below and see Vegas Pro 11.0 recorded "live" in action:

Professional Titles and VFX in Sony Vegas Pro 11

~jr

Laurence wrote on 5/18/2012, 10:30 AM

JR, are you using any NewBluFX Video Essentials filters? I am suspicious that they might have something to do with some of our problems. Though this latest build does seem quite stable.

JohnnyRoy wrote on 5/18/2012, 12:17 PM

> "JR, are you using any NewBluFX Video Essentials filters?"

I do have them installed but I haven't used them lately. I know I haven't used any in my Vegas Pro 11.0 projects yet.

~jr

rmack350 wrote on 5/18/2012, 12:42 PM

I just want to point out that what you're generating here is a list of people who can use the latest build for paid gigs. It's a positive list with a bright outlook, to be sure, and demonstrates that it's possible to reliably use the latest build of VP11 for mission critical work.

Still, those who can't rely on it still can't rely on it.

I'm in the middle here. I can rely on it on one machine but not another. Happily, the installation I can rely on is the one I use at work.

The list is a little like a phone survey asking people if they have a phone.

Rob

mudsmith wrote on 5/18/2012, 1:37 PM

So, if you can use it on machine and not another, can you report to us the difference between machines?.......Useful info, I think, and well beyond a phone survey for phone owners.

TheRhino wrote on 5/18/2012, 2:17 PM

I'm glad I started this thread because we are getting some useful information. Some of us use Vegas 8+ hours per day on multiple machines so we have a means to separate Vegas-only problems from those related to drivers, hardware, etc.

For instance, my main editing rig triple boots between (3) SSD drives. The drive with Office 2010, Adobe CS5.5, etc. and all the latest drivers & Windows updates installed now runs V11.683 glitch-free. This drive is rather messy and reaching its capacity, so I was thinking of cleaning it up some but it is working great & therefore I do not want to lose a good thing...

On another much cleaner boot drive on the same system I just have Windows 7 64 SP1, Vegas 8.0c, 9.0e, 10.0e and V11.683 - no other software or 3rd party FX. V9.0e and V10.e peform the same on both installs. However, V11.683 takes longer to load, the preview is slower, and the renders take longer. It also sometimes crashes when I close the program. I haven't had time to check, but it has to be a Windows update or driver issue since the hardware is identical. When I have more time I am going to chart the differences, but for now I just don't have time to sort it out...

Therefore my conclusion is that Vegas 11.683 is definitely more touchy about the Windows updates and/or driver updates. This could be the reason some are enjoying excellent stability while others find it almost unusable. IMO it could be something as small as a .NET update, etc. that came-out after Windows 64 SP1.

DavidMcKnight wrote on 5/18/2012, 3:19 PM

Using it every day, at least 2 - 6 hours a day on two PCs. I also use the NewBlue Video Essentials plugs pretty regularly FWIW.

rmack350 wrote on 5/18/2012, 4:52 PM

Mudsmith, click on my name and you should find a list of my posts. I've described the diffs in the two machines a few times. No need to do it here since it'd stray from the original question.

TheRhino...I suspect that the OFX filter dialog/Compatibility mode issue is related to a .NET update but wouldn't know how to prove it. It's SCS' job to fix it, not mine.

The problem with not knowing the source of a problem is that you also don't know how to avoid it, short of unplugging the network cable and never doing another update. But it's good to know that the most recent build of Vegas can be reliable enough to do paying work on.

Rob

MUTTLEY wrote on 5/18/2012, 5:45 PM

Do I need to add my name to the list? Pretty sure everyone here knows I am from countless other threads! =)

I've proudly used Vegas, and only Vegas, for 10+ years now with video production being my sole vocation. Music videos, commercials, feature length films, infomercials, TV pilots, training DVD's. Haven't had a project yet that Vegas couldn't handle.

- Ray
Underground Planet

drrohle wrote on 5/22/2012, 1:32 PM

Been editing a weekly 30 min. TV prog. for 6 years now in Vegas. Jumped from Vs. 6 to 10(64Bit) last year and was terribly disappointed in it's stability. Upgraded to Vs. 11 with NewBlueFX and was REALLY disappointed! Lot's of crashes, poor stability, and an audio track that would render to NO sound unless I restarted Vegas first. etc....

Now the good news...With the release of build of 682/683 & NB's latest attempt (who knows what version), the only crash I have experienced in the last 3 weeks has been when closing Vegas at the end of the session (and that was just once). This new rel. is much more stable and I don't have to restart it before rendering the audio anymore.

Whew! I was this || close to jumping into another editing system. Sony cut if awfully close this time but I may stay with Vegas now.

Editguy43 wrote on 5/22/2012, 3:18 PM

As I said the other day I have been doing OK until yesterday, I was in the middle of and edit, some light CC work and Boom crash and I had just saved about 30 seconds before.
I restarted and all was well, I think that has been about the 4th or 5th I have had since using 11 so overall I am still happy..

Seth wrote on 5/22/2012, 4:21 PM

Just used it today on, get this, an ultrabook with only 4GB RAM! and it ran beautifully with no effects or fancy editing operations. Final render to MainConcept was 5:1 realtime, with no GPU.

Granted, I did not resize, did not adjust frame rate, did not time re-map in any way, and only applied a simple LUT and audio tweaks.

EDIT: yes, it was a paying job, but a one-off, location SDE, ergo the use of an unconventional 'workstation'.

Laurence wrote on 5/22/2012, 9:19 PM

683 is better than previous versions, but still not stable enough to use on anything but the simplest of projects. After a couple of days in a row of relative stability, today was a really bad day for V11 crash wise. I will try again after the next revision.

All my projects are paid ones by the way.

Randini wrote on 5/31/2012, 2:28 AM

I'm full time on the current version. I love this version the best for the acceptance of all the plug-ins but I'm getting a lot of crashes when I close out. This version also crashes my line6 audio. I have also noticed that my computer fan is coming on more which boggles my mind (must be a plugin).

JJKizak wrote on 5/31/2012, 6:40 AM

I remember when the computer fan coming on and off used to raise hell with the rendering.
JJK

cspvideo wrote on 5/31/2012, 9:01 PM

I am. Short and long.

The only issue I've seen happens when I have to use an event velocity effect (slow-motion) on a video which is also moving horizontally. There are some weird flickering issues in between the extra frames created. I didn't use to see it in version 10.

I've got two different machines. The specs for the newest one are in my profile. Both use Nvidia cards.

I've not had issues with crashing at all.

wandering journalist wrote on 6/4/2012, 9:14 AM

I'm using V11 with a modest Sony VAIO to edit on and so far so good. I recently finished a project for a museum. And, I am now in the middle of an hour-long documentary. I still have Vegas Pro 8.1 on my computer because I find it to be rock solid... you never know... Only real issue I have found with 11 so far is the NuBlue Titler crashes often... unfortunate because I quite like what I can create with it when it works.

Dale.

im.away wrote on 6/4/2012, 10:08 AM

Handed a 77 minute production to a customer on Saturday. Five cam multicam shoot (2 at 1920 x 1080 50i, two at 1440 x 1080 50i and one at 720 50p), with 13 audio tracks, lots of cc, effects. Used Bluff Titler for the titles but everything else was done with V11/683. Not one crash or glitch of any kind. Gotta be happy with that.

Russ

chap wrote on 6/7/2012, 2:55 PM

64 Bit is less stable than 32 bit.

I am now using V11 for paid projects, I run it in the Windows Vista Compatibility mode, as described in other threads.

Logan5 wrote on 6/7/2012, 3:15 PM

ONLY when I need to do closed captions.
I edit only in V9.

I had a few issues with v11 and do not have the time to chase them down.

L5

fausseplanete wrote on 6/9/2012, 6:23 AM

Not currently (though I hold out hope). Instead I use mostly Vegas 9 and, for specific things, Vegas 10.

Vegas is the best tool I know for certain aspects of my trade, such as lecture-editing, which is a one-person job where audio is crucial and slide-times (on the timeline) must be determined (taking advantage of media markers, the marker-promotion script and the Edit Details capability of being copied to spreadsheet).

Tried using V11 64-bit (on W7-64 machines with 8GB RAM) but on a paid project immediately encountered problems, so backed-down to V10 which worked fine until I ported the project from laptop to desktop, whereupon MediaFX were lost - apparently a known issue of V10 fixed in V11. Consequently I use V9 mostly, with sparing use of V10 only for yadif-plugin-based deinterlacing to intermediate (Cineform). I await greater "cheers from the crowd" before venturing back to V11.

Naturally, success/failure experience depends not only on the system setup but what one is trying to do with it, so:

Typically I edit under Windows 7 64-bit on a Mac (8-core desktop or 2-core laptop) via BootCamp with multiple USB drives (more portable than my RAID), using footage from up to four HD cameras (split between the drives) in lower-resolution projects, taking advantage of excess resolution for pan/crop (animated), then rendering-to and using Cineform as an intermediate, prior to target-format encoding either within Vegas or third-party application, depending on the format. Also typically use various grading FX (Levels, ColorCurves, Primary, Secondary) to match dissimilar cameras and for "look" at Media, Event, Track and Master level (though not all at once).