[Mike Kujbida]

Try Video4YouTube, free from the good folks at Vegasaur and see if it’s any better.
https://vegasaur.com/download

[Mike Kujbida]

Yes and correct.

From the Vegas Pro 12 Edit page at https://www.sonycreativesoftware.com/buy/vegasproedit

“Vegas Pro 12 Edit features the same award-winning video and audio toolset as the Vegas Pro 12 collection, but removes DVD Architect™ Pro to create a more cost-effective package.”

[Mike Kujbida]

This was very recently posted to the Sony Vegas forum by Chris Dolan from Sony.

765 was pulled after QA verified the MainConcept GPU render issues reported in this thread. Adding support for LPCM audio in the CPU code (as opposed to AAC) accidentally left the GPU code without any audio codec selected so it bailed out. The jump back to frame 0 that some of you saw was Vegas trying to recover in CPU mode, but still without any audio codec selected.
The fix looks simple (auto-select AAC for the GPU modes) so I predict a new update soon but please don’t hold me to that because it’s not my call!

[Mike Kujbida]

Build 765 is no longer available on the Sony site so they must have pulled it due to several complaints on the Sony Vegas forum.

[Mike Kujbida]

Notable fixes/changes in version 12.0 (Build 765)

Added support for MOV files when exporting to Media Composer AAF format.
Added support for writing sidecar XML files when rendering XAVC and XAVC S video.
Added templates for rendering Sony XAVC / XAVC S video.
When rendering XAVC S files, audio is now rendered in LPCM format.
Fixed a bug that could cause a crash when rendering a project that contained an empty metadata command marker.
Fixed a bug that could cause a crash when using Tools > Multicamera > Create Multicamera Track with an empty track selected.
Fixed a bug that could cause a crash when importing 1440×1080 XAVC files.
Fixed a bug that could cause a crash when dragging a preset chain (filter package) from the Plug-In Manager to an event, track, media file, or the video output.
Fixed a bug that could cause a crash on some systems with NVIDIA graphics when reading 4:2:0 480p widescreen media.
Fixed a bug that could cause Vegas to freeze when adding some interlaced MP4 videos to the timeline.
Fixed a bug that could cause rendering to hang when rendering to XDCAM EX MP4 files with the Enable no-recompress long-GOP rendering check box (Preferences > General) selected.
Fixed a bug that could cause .aaf files imported from Media Composer to be read using an incorrect frame rate in Vegas Pro.
Fixed a bug that could cause .mov and .mp4 files imported from Media Composer to be read using incorrect timecode in Vegas Pro.
Fixed a bug that could cause a hang when rendering 4K XAVC S video on some computers.
Fixed a bug that could cause an error to be displayed when importing and MXF file from an Optical Disc Archive unit.
Fixed a bug that could cause Vegas Pro to hang when reading MP4 video from the GoPro Hero 3+.
Fixed a bug that added a green bar when reading 480p widescreen AVC files.
Fixed a bug that prevented Vegas Pro from updating the file size estimate when Render Loop Region Only was selected during Blu-ray Disc burning.
Fixed a bug that prevented Sony F5 cameras from playing XAVC HD 23.98p clips rendered in Vegas.
Fixed a bug that caused the Iris transition to reverse A- and B-roll video when GPU acceleration was turned off.
Fixed a bug that prevented Vegas from correctly reading SD MP4 clips that were shot in portrait mode.
Fixed a bug that prevented Vegas from persisting the View transform setting on the Video tab of the Project Properties dialog.

[Mike Kujbida]

Try option #1 and point it to the new directory. If things go the way they’re supposed to, Vegas will say something like “found xxx file too, do you want to use this location?”. Say yes and it should import all your files without any more prompting.

[Mike Kujbida]

I’m sorry but your computer doesn’t come close to meeting the minimum specs to be able to efficiently edit HD video.
Even Sony says that the bare bones spec is “2 GHz processor (multicore or multiprocessor CPU recommended for HD or stereoscopic 3D)”.
Users on here and elsewhere will tell you that you should be running an i7 processor with at least 8GB. of RAM
The other issue is the free space on your hard drive as that drive is almost full and that’s very bad for anything, especially video editing.
My guess is that’s the only one you have. Ideally you have at least two hard drives with one being for strictly for your software and a second one for all your program assets (video, audio, graphics, etc.).

[Mike Kujbida]

[John Hancock] “I have Vegas pro 12 build 367…”

Pro 12 is now at build 726 and there have been 7 updates to get us there which means LOTS of bug fixes.
Unless you have a really good reason not to, I would strongly encourage you to update to the latest build ASAP.

https://www.sonycreativesoftware.com/download/updates/vegaspro

[Mike Kujbida]

Your bitrate is far too high for a 2.5 hr. video.
I used Mark’s Bitrate Calculator and got the following numbers:

Low: 2,104,000
Avg: 3,512,000
High: 6,152,000

This assumes AC-3 for your audio at the default of 192.

For this long of a program a 2-pass render is, IMO, a necessity.

Use the DVD Architect NTSC video stream template (24P and widescreen are options as well) and customize it.

[Mike Kujbida]

Chris, don’t beat yourself up over an honest mistake. I’ve been using Vegas since version 1.0 and that still catches me at times when I’m not paying attention 🙂