Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro new build of Pro 12 is out

  • new build of Pro 12 is out

    Posted by Mike Kujbida on January 30, 2013 at 12:25 am

    We’re up to build 486 and there’s a long list of bug fixes.
    https://www.sonycreativesoftware.com/download/updates/vegaspro

    Notable fixes/changes in version 12.0 (Build 486)

    Added support for exporting nested Vegas Pro projects as compound clips when exporting to Final Cut Pro X format.
    Added support for importing compound clips as nested Vegas Pro projects when importing from Final Cut Pro X format.

    When importing a Final Cut Pro X project, a Vegas project is created for the main project using the same base name as the .fcpxml file, and separate nested Vegas projects are created for each compound clip and for each clip that contains an audio and a video stream.
    Added Anchor point setting to the Titles & Text plug-in. Text now scales relative to the anchor point, which does not move.
    Added support for reading and rendering up to 16 channels of audio in HD MXF files.
    Added support for reading Sony XAVC files. You can use the Device Explorer window to browse and import clips from XAVC disc images.
    Added support for timecode in P2 MXF files. If you’re using a project that was created in version 12.0 (build 394) or earlier, please update P2 clip timecode as follows:
    If you imported the clip from a disc image, right-click the clip in the Project Media window, choose Replace, and then select the clip from the disc image.
    If you imported the clip using the Vegas Device Explorer, delete the .mxf file from the C:UsersDocumentsImported Media folder and reimport the clip using the Device Explorer.
    The Documents library and custom libraries from Windows Explorer are now available in the Vegas Pro Explorer.
    File Open dialogs have been updated to allow you to browse and open files from mobile devices.
    Fixed a bug that prevented the Sony Stabilize plug-in from working when 32-bit floating point (video levels) or 32-bit floating point (full range) was selected in the Pixel format drop-down list in the Project Properties dialog.
    Improved performance when using audio preview through SDI video preview devices.
    Fixed a bug that prevented the Sony Stabilize plug-in from being applied during playback.
    Fixed a bug that could cause Vegas Pro to crash when loading some projects.
    Fixed a bug that could reset event effect automation envelopes when splitting events.
    Fixed a bug that prevented some fonts from previewing correctly when using the Titles & Text plug-in.
    Fixed a bug that could start a different version of Vegas Pro when right-clicking a nested project and choosing Edit in Vegas from the shortcut menu when multiple versions of Vegas Pro are installed.
    Fixed a bug that could cause the incorrect images to be displayed for selected Mute and Solo buttons in the Assignable FX dialog.
    Fixed a bug that prevented the Plug-In Chooser from closing when Esc is pressed.
    Fixed a bug that could cause all HDCAM SR templates to be marked as favorites in the Render As dialog when selecting a single template as a favorite.
    Fixed an issue that could cause the “None of the files dropped on Vegas Pro could be opened” error message to be displayed incorrectly in the Vegas Explorer.
    Fixed a bug that could cause a crash when using the FBmn Software White Balance plug-in.
    Fixed a bug that could cause Stereoscopic 3D Camera settings to be displayed in the Track Motion window when working with 2D projects.
    Fixed a bug that prevented the Use audio-capable preview device during external video preview setting from being saved when exiting Vegas (Preferences > Audio Device).
    Fixed a bug that could cause Vegas Pro to hang when rendering MVC video for a Blu-ray Disc.
    Fixed a bug that could cause Vegas Pro to hang when dragging a .mov file from the Vegas Explorer to the timeline if QuickTime was not installed.
    Fixed a bug that could — in some circumstances — prevent the application from starting after registering.
    Fixed a bug that could cause image sequences to have black frames in Video Preview and rendered output after zooming in with the Event Pan/Crop plug-in and time compressing.
    Fixed a bug that could cause P2 MXF video to be opened without its associated audio streams.
    Fixed a bug that could prevent the application from being uninstalled properly.
    Fixed a bug that could prevent the application from entering expanded edit mode when pressing 5 on the numeric keypad.
    Fixed a bug that could cause the first frame of an MVC file to appear briefly at the end when previewing the file from the Explorer window.
    Fixed a bug that could cause XDCAM clips to have an incorrect timecode.
    Fixed a bug that could cause the Video Preview window to flash when starting playback.
    Fixed a bug that could cause doubled audio to be recorded after changing a track’s input monitoring mode.
    Fixed a bug that prevented regions being dragged from the Explorer window to the timeline.
    Fixed a bug that could cause the application to freeze when changing the capture device in the Capture Preferences dialog.
    Fixed a bug where the timeline did not show only the current edit track (at the default track height) when entering expanded edit mode for some screen resolutions and for user-modified track heights.
    Fixed a bug that could cause the current edit track height to decrease after exiting and then re-entering expanded edit mode.
    Fixed a bug that could cause application extension windows to be hidden after loading an extension.

    John Rofrano replied 13 years, 4 months ago 6 Members · 15 Replies
  • 15 Replies
  • Steve Rhoden

    January 30, 2013 at 12:59 am

    Good…..

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    https://www.facebook.com/FilmexCreativeMedia
    1-876-832-4956

  • Steve Rhoden

    January 30, 2013 at 1:09 am

    Timecode in P2 MXF files
    Yes, that timecode in P2 files was a high request.

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    https://www.facebook.com/FilmexCreativeMedia
    1-876-832-4956

  • David Shirey

    January 30, 2013 at 7:33 am

    Here’s hoping it fixes the freezing while rendering that a lot of us have experienced. Wouldn’t you know it’d be released the day I finally broke down and installed 11 on my new computer after not wanting to risk another project on 12. I’ll continue editing in 11 then dump it into 12 when it’s done and see if it renders okay. Worries me that the notes don’t mention that specifically though.

  • John Rofrano

    January 30, 2013 at 1:40 pm

    [Mike Kujbida] “Fixed a bug that could cause application extension windows to be hidden after loading an extension.”

    SWEET! No more customer complains that my plug-ins don’t show up. lol 😉

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Jay Allen

    January 30, 2013 at 1:56 pm

    I loaded the new build and I still freeze on main concept renders. Maybe they will fix this by ver 13, 14, 15…
    Preview is still bad, still buggy, and I’m sure glad sony spent time fixing export to Final cut – I guess that codecs that don’t render, bad preview etc will have to go on the back burner.

  • Steve Rhoden

    January 30, 2013 at 2:23 pm

    Preview is still bad, still buggy
    What specifically do you mean Jay?

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    https://www.facebook.com/FilmexCreativeMedia
    1-876-832-4956

  • Jay Allen

    January 30, 2013 at 3:31 pm

    I mean v11 had a better preview rate and rendered faster.
    I have a rock solid preview in cs6 with same matterial.

  • David Shirey

    January 30, 2013 at 6:28 pm

    Yeah, all the troubles I’ve had with 12 actually got me thinking maybe I should finally just just ship for Premiere. Then I realized I was perfectly happy with 11, and the only reason I bothered getting 12 was I happened to be building a new rig around the time it came out, and figured I’d just start fresh with a single install. I’m now back to being happy with 11 and I guess the money I spent on 12 and time wasted with failed renders was cheaper than buying and learning CS6, so I still come out ahead. I just really dislike the way Premiere works and will stick with Vegas unless they manage to fall behind technologically.

  • Jay Allen

    January 30, 2013 at 7:46 pm

    Your post worries me a little because I am about to build a new computer with fresh 12 install. I usually get a new computer when the last one has 3 versions of vegas. (4,5,6) (7,8,9) (10, 11,12)

  • Norman Austin

    January 30, 2013 at 8:36 pm

    I just upgraded from the previous version of 12… then I tried to customize an AVI HD 1080 template and there is no adjustment for bitrate.
    So I rendered my 5 minute video and it came out at 35 Gig. This is crazy!!!
    Anyone have any ideas how I can reduce the size of my video in this format yet still retain 1920×1080 frame size?

    Why would there be reduced customization options in this new version?

    Norman

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy