New Update!!!

jpenn wrote on 7/23/2013, 7:25 PM
Notable fixes/changes in version $BuildNumber$
Added smart rendering support for Panasonic P2 files.
The Panasonic P2 format now preserves 10-bit color when rendering.
Added support for rendering 29.97p, 25p, 59.94i, and 50i AVC-Intra 100 Panasonic P2 video.
Added an Optimize GPU display performance check box to the Video Preview tab in the Preferences dialog when Windows Graphics Card is selected in the Device drop-down list. We recommend leaving this check box selected. You can clear the check box if you experience system, external monitor, or video preview performance problems.
Improved the Color Match plug-in to prevent an issue that could cause .veg file sizes to grow significantly for each instance of the Color Match plug-in.
Improved AMD GPU performance when using Catalyst 13.x (format of driver version number changed).
Improved Intel GPU performance when using driver 9.18.10.3070 or newer.
Improved playback performance for AVC-Intra 100 Panasonic P2 video.
New right-click menu in the Titles & Text plug-in allows quick access to Cut, Copy, Paste, Delete, and Select All commands for editing text.
Fixed a bug that could cause a crash when attempting to explore a deleted folder in the Vegas Pro Explorer.
Fixed a bug that could Vegas to crash when using the Device Explorer to view XAVC volumes that contained invalid clips.
Fixed a bug that could cause Vegas to freeze when zooming the timeline when playing some projects with XAVC media.
Fixed a bug that could cause a crash on some systems with NVIDIA graphics when resizing the Video Preview window during playback.
Fixed a bug that could cause a crash when rendering some very large projects to QuickTime format.
Fixed a bug that could cause a crash when double-clicking the Computer icon in the Vegas Explorer window.
Fixed a bug that could cause some large, very complex projects to crash when working with very large MP4 videos on 64-bit systems (or when using the Upload to YouTube command).
Fixed a bug that could cause a crash when pressing Esc to exit expanded edit mode after the edit track had been removed from the timeline.
Prerendered video files are no longer invalidated by Project Properties changes unless settings on the Video tab are edited.
Fixed a bug that caused field order in interlaced P2 files to be read incorrectly.
Fixed a bug that could cause timecode to be written incorrectly when rendering Panasonic P2 files in 50p or 60p format.
Fixed a bug that could prevent files from being removed after canceling a P2 render.
Fixed a bug when rendering MainConcept MPEG-2 files that caused YUV color values from the source file to be changed in the rendered file.
Fixed a bug that could cause the Preferences > General > Import MXF as multichannel setting to be ignored when importing XAVC video.
Fixed a bug that prevented Vegas Pro from importing SStP MXF clips recorded by F5/F55 cameras.
Fixed a bug that could cause audio dropouts when playing projects containing XAVC video.
Fixed a bug that could cause video-proxy creation to fail for XAVC and P2 formats when switching away from Vegas Pro when the Close media files when not the active application General preference was selected.
Fixed a bug that could cause generated media to use incorrect attributes after opening and closing projects with similar generated-media assets.
Fixed a bug that caused the monitor to remain black after turning off Video Preview on External Monitor on systems with a Radeon GPU and Catalyst driver 12.10 or later.
Fixed a bug that prevented thumbnail images in the Project Media window from displaying media rotation.
Fixed a bug that could cause thumbnail images in the Project Media window to display at the incorrect size.
Fixed a bug that could cause some MP4 video files to be read as audio-only files.
Fixed a bug that could prevent Vegas from reading some rendered P2, MXF, and XAVC files.
Fixed a bug that caused rendered MXF files to incorrectly report that they had been created using Vegas Pro 10.0.
Fixed a bug that could cause playback issues with some standard-definition XDCAM MXF files.
Fixed a bug that could cause a USB-connected P2 camera to be displayed multiple times in the Device Explorer.
Fixed a bug that could prevent a USB-connected P2 camera from being displayed in the Device Explorer.
Fixed a bug that prevented OFX track effects from being saved and applied properly with default track properties.
Implemented a workaround for a Final Cut Pro X limitation when handling file names containing spaces. Media file naming has been revised when using File > Export > Final Cut Pro X and clicking Yes when prompted to export the media pool.
Fixed a bug that could cause some projects to fail when exporting to Final Cut Pro X format if media field order was unknown.
Fixed a bug that caused punch-in events to be displayed incorrectly in expanded edit mode.
Fixed a bug that could cause MOV files recorded by iOS devices to be displayed with the incorrect rotation or aspect ratio.

Comments

videoITguy wrote on 7/23/2013, 7:29 PM
Nvidia is in the dust?
"Improved AMD GPU performance when using Catalyst 13.x (format of driver version number changed).
Improved Intel GPU performance when using driver 9.18.10.3070 or newer."
JJKizak wrote on 7/23/2013, 7:30 PM
Looks like they were busy fixing things. Installed 670 ok but I don't use about 99% of all that stuff.
JJK
jpenn wrote on 7/23/2013, 7:45 PM
"Improved Intel GPU performance when using driver 9.18.10.3070 or newer."

Is that a misprint? Did they mean Nvidia?
videoITguy wrote on 7/23/2013, 9:28 PM
"did they mean NVidia"?
don't believe so.....
ushere wrote on 7/23/2013, 9:55 PM
a pity that titler pro 2 can't use intel hd4000 whilst scs are still working on it....
john_dennis wrote on 7/23/2013, 11:55 PM
@ jpenn

[I]"Improved Intel GPU performance when using driver 9.18.10.3070 or newer."[/I]

Those numbers are for the intel HD 4000 graphics on the die of the latest intel processors, i7-3770 etc.

So far, I'm still running 9.17.10.2792............. 'cause it works.
ushere wrote on 7/24/2013, 12:50 AM
@ jd - i'm running latest intel with no problems. don't think intel's quite as bad as either nvidia or amd regarding screwing up working installations with updates, though ymmv ;-(
videoITguy wrote on 7/24/2013, 12:51 AM
See above narrative - what is the implication of "ushere's" query several posts above the just previous one in the scheme of things developing....
PeterWright wrote on 7/24/2013, 4:21 AM
Fairly low key response to the new build - does that mean almost everyone's happy?

- be interesting to hear from someone for whom this build has solved a problem ...

I've had no specific problems with V12 - occasional white screen lock-ups, not traceable to a common cause, but generally ok for me.
ushere wrote on 7/24/2013, 6:49 AM
as per peter - 12 seems respectably well behaved for what i'm mostly working on. have install latest on one pc and am trying to judge (very inaccurately) any noticeable differences.

Added an Optimize GPU display performance check box to the Video Preview tab in the Preferences dialog when Windows Graphics Card is selected in the Device drop-down list. We recommend leaving this check box selected.

what exactly does this do? and is the final sentence an alternative to turning gpu off ;-)
FilmingPhotoGuy wrote on 7/24/2013, 7:58 AM
Awesome! They fixed it where the most left position of the key would display the last frame of the previous event. [I really hated that]
Ros wrote on 7/24/2013, 8:04 AM
Improved the Color Match plug-in to prevent an issue that could cause .veg file sizes to grow significantly........will be using it now that it is fixed.

They also improved the Color Match UI, looks great!
ritsmer wrote on 7/24/2013, 9:57 AM
"what exactly does this do? and is the final sentence an alternative to turning gpu off ;-)"

When Optimize is checked the CPU/GPU usage on my machine is 41%/15%.

When unchecked it is 35%/45%.

So obviously this setting sends more of the number-crunching work to the GPU and less to the CPU.
wwaag wrote on 7/24/2013, 10:53 AM
For those who still render to MPEG-2, the color issue http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=862011 has been fixed.

Cineform files still do not smart-render, although the use of the V10 aviplug.dll still works.

wwaag


AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

NormanPCN wrote on 7/24/2013, 11:11 AM
Fairly low key response to the new build - does that mean almost everyone's happy?

I wish they would have fixed the problem with OpenType fonts with postscript outlines in the Titles and Text plug-in. I reported it a couple of builds ago and SCS said it was a known problem.

The legacy text, protype and NewBlue Titler all work fine.
VidMus wrote on 7/24/2013, 12:33 PM
The next update will probably be Vegas 13.

I hope they do the beta thing again. I would like to be a part of that.
Lovelight wrote on 7/24/2013, 1:38 PM
This all very good. Thank you.

We still need usb 3, 3 TB HD wav support. These files will not play on these drives. It is a vegas problem. Please fix.
JJKizak wrote on 7/24/2013, 2:43 PM
It's a wonderment to me why Vegas files would not play on a 3 t USB drive. What am I missing here?
JJK
Lovelight wrote on 7/24/2013, 4:27 PM
It is only wav files that do not play. A very strange thing, indeed. It has been confirmed by others, but we are few. All other players play wav files off of 3tb, usb 3 drives. I don't know if it is the 3 tb, the usb 3, or a combination of it all, but these are my new drives unable to play wav file in V12.
DavidMcKnight wrote on 7/24/2013, 5:05 PM
Specifically 24-bit WAV files on very large USB 3 drives.

Yes, it's weird but documented and acknowledged.
Dave McCallister wrote on 7/24/2013, 5:14 PM
Just installed Build 670 on a Dell XPS8000 8gig Core i7 860 box for testing. Will put it on the actual editor box here if all seems well (i7 six-core 980X 24GB).

Imported a .wav file of production music from a Seagate 4TB USB3 external drive.
Played fine. Don't know what to say. If a 4TB drive works, why not a 3TB?


DavidMcKnight wrote on 7/24/2013, 5:33 PM
What are the properties of your audio file? Sample rate and bitrate, etc?
Peter Riding wrote on 7/24/2013, 5:41 PM
I've been editing using 3tb USB3 Seagate drives for over a year without any issues with 16/48 WAV files from 3 different Zoom H1 recorders plus sundry royalty free music which is also 16/48. Probably around 50 multicam projects varying from 30 mins to 2 hours each. Always DVD and MP4 out the other end.

Windows 8, always the latest edition of Vegas Pro, i7, 12gb ram blah blah blah.

The one thing I did give up on long ago is GPU acceleration. Nvidia GTX570. Made a difference at first now its just a problem :- (

Pete
OldSmoke wrote on 7/24/2013, 5:43 PM
I think the problem with the 570 is Windows 8 and the driver for it.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)