[Bill Church]

You gotta love that… Glad you solved it, Raf.

Bill Church
Briarwood Productions LLC

[Bill Church]

Raf,

Try setting your project properties template to match the native footage you shot in 1080i, then render the project out in Quicktime H.264, since the broadcaster also lists that format as an SD option. You’ll get the job done meeting the broadcaster’s specs, it’ll look great, and Vegas probably won’t even break a sweat.

bc

Bill Church
Briarwood Productions LLC

[Bill Church]

Point well taken, John. My bad. Vegas just seems to be much more stable for me, with fewer crashes, when I set it higher. Probably just my imagination!

Bill Church
Briarwood Productions LLC

[Bill Church]

Sounds like you definitely need more RAM allocated to the application while editing, vice rendering. I’d try setting to at least 6000MB, vice 600MB. Should make a big difference.

Bill Church
Briarwood Productions LLC

[Bill Church]

Turns out the first emailed announcement they issued earlier in the day had included a link to the wrong update (for Vega users), so a few hours later, maybe after seeing my post, they sent out another notification with corrected links for both Windows and Vegas Pro updates. They also included an explanation …”Earlier this morning we sent an email with a link to update Titler Pro. Well, wouldn’t you know we accidentally forgot to include a link to the Titler Pro update for Vegas Pro 11 users in our email this morning. Please find this updated link below. We apologize for the oversight and any confusion we may have caused you.”

The correct Vegas Pro update, which required your original serial number to install, updated Titler Pro just fine. Hopefully, my initially having partially installed the incorrect version didn’t screw things up royally, and really corrupt my NB Titler plug-in. I’ll find out when I test it later today.

Bill Church
Briarwood Productions LLC

[Bill Church]

Those are my exact system specs (set up on an Asus P6-X58E motherboard), as well, Frank. As they say, “your mileage may vary,” so I guess I’m one of the fortunate few to be able to use it. It’s very odd how this software responds, or fails to respond, on different platforms with very similar specs. I agree that NBTP is far from ready for prime time, running in Vegas, but it’s getting closer to doing the job dependably for me with each upgrade. Some have suggested that WE are, and have long been, the unwitting beta testers! And there is probably more than a grain of truth to that assertion. It will be quite interesting to see how the Mac and other NLE users fare in the coming releases.

Bill Church
Briarwood Productions LLC

[Bill Church]

I have to totally agree with Mark. I just completed a pretty complex project that included at least a dozen or more Titler Pro graphics, with many added directly on the tracksheet, and others embedded in nested clips. I also created and imported textures for use in some of the titles. There were definitely many crashes along the way, but not nearly as many as when I initially started trying to use the software that came bundled with SVP11. The subsequent updates to both Titler Pro and SVP11 (64-bit), coupled with installing the latest nVidia GPU beta drivers definitely made a big stability difference for me. During that project, I also learned alot about setting RAM allocations for both previewing and for renders; and when to turn the GPU “off” in SVP11 preferences. I know, you shouldn’t have to do all these little workarounds and tricks, but, they help you get the job done and meet your deadlines. So, if you love the creativity, speed, and workflow efficiencies this bundle provides, stick with it. I’ve used many NLE’s over the years, and, dollar for dollar, feature for feature, none can touch Vegas. Last, running the software bundle on a very powerful system with lots of RAM, fast multi-thread processor, E-sata drives, and all the other bells and whistles never hurts, either.

Happy editing!

Bill Church
Briarwood Productions LLC

[Bill Church]

Shaun,

I just saw your post and had to respond. I, too, built a similar Asus system, and had lots of issues with the SVP11/New Blue bundle, as well. I just struggled through a pretty complex edit (my first using SVP11/NBTP) that also included LOTS of New Blue titles and I initially experienced the same crashes as you. My first project is now completed and delivered. After I completed it, I erroneously) posted comments regarding my editorial experience on the Vegas Basics forum. I meant to put them on the Vegas Forum, but, after a very long day editing, groggy and fatigued, I accidentally put them on the Basics Forum. You can read it at https://forums.creativecow.net/readpost/208/880408.

I share your pain, but I didn’t give up, nor should you, because this software bundle is very powerful. I’ve made money with it, and, although all the crashes made the first project a whole lot more difficult and challenging than it should have been, I will be sticking with it until it’s fixed, and long after that. Hang in there!

Bill Church
Briarwood Productions LLC

[Bill Church]

In my experience, updating both SVP11 and New Blue to the latest builds, along with installing the newest nVidia beta drivers did dramatically improve performance on both my new Asus laptop and main editing platforms. Both run Win7 and I7 processors (four and six-core), and both have a fair amount of RAM (8 and 24GB). And, while still far from perfect, I don’t experience anywhere near as many crashes now. And, I can pretty seamlessly move projects from one platform to another, as needed. Fortunately, the newest software upgrades also certified the notebook’s nVidia GeForce GT555M display adaptor, which previously would not work at all, and guaranteed crashes – with or without the GPU selected in SVP prefs. The nVidia GeForce GTX560 on the PC is probably marginal, but is working fine, so far. The crashes I experience now seem to be directly related to the heavy lifting I place on the system, vis-a-vis, complex SVP 11 projects with tracksheets employing nested comps, composited tracks, and lots of New Blue Titler clips. My point is that I believe both Sony and New Blue are trying to address all the legitimate stability and compaibility issues, but there are so many other hardware variables out there that it is an uphill battle, and simply not a one-size-fits-all scenario. As has been pointed out, while the software is still far from perfected, and may never be, your hardware environment DIRECTLY affects your Vegas experience – the better the hardware, the better the performance. Just my humble opinion. Over the years, I’ve used many other NLE’s – both dedicated hardware (think AVID) and software-based, and I love SVP, even with it’s faults, so I will be sticking with it for the forseeable future.

Bill Church
Briarwood Productions LLC

[Bill Church]

Ditto.

My last response from NB, back on December 5th, regarding my (November 16) ticket was: “Thank you for the update. I have sent the developers this updated information.” My ticket has been in perpetual “on-hold” status since then. Realistically, I don’t ever expect another response from them. Love the product, and, while the most recent NB Titler pro build does seem a bit more stable running in SVP11 build 521, I’m not convinced it’s really ready for prime time yet. I just wish they could make it work consistently, and very soon.

Operating System Windows 7 Pro, 64-bit, I7 980 series six-core 3GHz proc., 24GB RAM, GeForce GTX 560 1GB GDDR5, Host Application Version SVP 11.0 (build 521) 64-bit

Bill Church
Briarwood Productions LLC