VEGAS Pro 16 Update 2 (build 307) - General Discussion

NickHope wrote on 10/27/2018, 1:30 AM

Although not yet officially announced*, VEGAS Pro 16 Update 2 (build 307) is available.

If you already have an earlier build of VEGAS Pro 16 installed, there is no need to uninstall it. Build 307 will overwrite your installation and retain your settings. Your computer will need to be online for activation after the update.

Download link. Another download link. At this moment, the download managers (...dlm.exe) are still fetching build 261.

*Update Oct 29th: now officially announced.

New Features

You can now set any preset of the Titles and Text media generator as the default for the Insert Subtitles from Files and Insert Subtitles from Regions functions
You can now create subtitles by importing SRT files with the Insert Subtitles from files feature
Video scopes can now be set to display the NITS scale for HDR work, including for 8-bit projects
VEGAS now warns you if no track has been armed for recording when you start recording and enables you to specify which existing track or tracks you want to record to, or to create a new track and record to that
Replacing media in the Main Storyboard timeline now updates the project timeline
The user now has the ability to "pin" another video event to a motion tracked event
Custom frame rates can now be set when encoding using AMD and VCE render templates in the MAGIX AVC/HEVC formats
The Main Timeline storyboard no longer automatically reacts to changes on the timeline. A Refresh Storyboard button has been added to the Project Media window when viewing a storyboard which enables you to manually match the storyboard to the timeline
A Red background for the Main Timeline storyboard alerts the user when the storyboard is out of sync with the project timeline and must be manually updated
A dialog box warns the user that the Main Timeline storyboard cannot be altered until it is updated to be in sync with the main timeline
A Red warning bar at the edge of storyboard thumbnails indicates when the timeline event is longer than the media it holds
You can now set in/out points in the storyboard for audio-only files
You can now set in/out points in the storyboard for still-image files
The Storyboard now properly recognizes L and J cuts and orders itself appropriately
Added support for time stretched/compressed events hover scrub in and out point trimming, and storyboard refresh
A new OFX plug-in enables you to add video stabilization to 360° video

Bugfixes

The Neat Video (and other temporal effects) now works properly when placed before Pan/Crop in an event FX chain
MTS files now render properly at 25p or lower framerates
The Internet HD 720p 29.97 fps (AMD VCE) template now yields the proper framerate
Reordering items in the storyboard no longer causes media in and out points to be reset
Audio recorded using Quicktime on a Macbook Air no longer get corrupted by so4compoundplug
The stabilization tool's Zoom parameter now properly persists through project save, close, and reload
The Render As dialog box no longer gets hidden off screen in a dual monitor set up which would cause the appearance of VEGAS freezing
Media in and out points are now properly honored when adding an unassociated storyboard bin to the timeline
The Insert Subtitles from File operation now properly recognizes commas in the subtitle text
The Add at Project Frame Rate operation now works properly when the media frame rate does not match the project frame rate
The audio meter context menu properly appears as expected again
The Scene Rotation plug-in has been optimized and should no longer cause occasional crashes at start up
The AutoSave function no longer triggers the creation of an unwanted duplicate storyboard which could occur in some cases
Crash has been resolved when using video stabilization and motion tracking with an AMD Phenom II card
Double-clicking Color Correction custom tab parameters now properly sets the parameters to their defaults
Overwriting files when rendering with AMD VCE templates now properly reports file size
Deleting storyboard placeholders no longer cause crashes as they did in certain instances
Replacing a generated placeholder with a clip no long crashes the application as was the case in certain scenarios
Moving generated media in the storyboard now follows expected behavior
External preview now works properly through Decklink cards in 32-bit projects
Fixed potential inconsistencies caused by replacing a generated placeholder with a video clip
Moving a generated media thumbnail to the end of the storyboard no longer causes an unwanted duplicate thumbnail
Sync Cursor to Media Timeline again works properly when user clicks on a keyframe in the FX automation section
Unwanted extra generated media thumbnails are no longer created in the storyboard when changing the order of thumbnails
Importing bins from one project into another no longer causes a crash
Importing media from one project into another now works properly
The BattleCompVintage VST and other plug-ins now work properly
32-bit projects created in older versions of VEGAS now open properly as 32-bit in VEGAS Pro 16
Dragging a media generator to the Main Timeline Storyboard no longer causes a crash
The render destination folder is now used for temporary file creation during the render process to avoid inadvertently filling up the user's C: drive
Certain specific MOV files no longer cause a crash when stabilization is applied
Switching through presets no longer disables stabilization in any case
Event Pan/Crop animation now works properly on events that hold still images
Color samplers in the Parameters and Custom tabs of the Color Corrector OFX plug-in are now correct and consistent
Stabilization of video clips that contain zooms now works properly
The Auto Zoom option now works more exactly to eliminate black borders
Right Alt+z and Shift+Right Alt+z now properly give users of the Polish localized version ż and Ż
Color Curve channel behavior has been improved so that changing the channel on one changes only that one and no others, and new curves are always added with the default settings instead of the settings from the previous curve worked with
All files now retain Markers & Regions in Trimmer
Timeline performance problems caused by automatically updating the Main Timeline storyboard during a timeline edit have been resolved

Back to post

Comments

bitman wrote on 10/28/2018, 10:28 AM

Yes this is an 'old' bug. You will also notice, that the FX windows/interface can still not be used wirh 150% nor 175% scaling in High DPI mode.

Confirmed, I was not aware of that. 125% it will remain then. At least I will have more real-estate, but my old eyes start to suffer 😵

richardbushell wrote on 10/28/2018, 10:42 AM

Nope, 307 still crashes upon startup for me. I've uninstalled all plugins installed from previous Vegas versions, and I have simply have not been able to use Vegas 16 since purchasing it, it has never started up yet. Despite reporting the startup bug several times officially, there has been no resolution to this issue. I am nearing the point where I need to demand a refund, as I simply cannot use the product.

Peter_P wrote on 10/28/2018, 10:55 AM

At least I will have more real-estate, but my old eyes start to suffer 😵

@bitman

I really can not work with 125%. The text becomes too smal for my older eyes. But 149% seems to work concering the FX interface as well but I had stability problem with that scaling. Does that occur with 125% on your system as well ?

NickHope wrote on 10/28/2018, 11:07 AM

Nope, 307 still crashes upon startup for me. I've uninstalled all plugins installed from previous Vegas versions, and I have simply have not been able to use Vegas 16 since purchasing it, it has never started up yet. Despite reporting the startup bug several times officially, there has been no resolution to this issue. I am nearing the point where I need to demand a refund, as I simply cannot use the product.

@richardbushell Have you been thoroughly through this troubleshooting post?

NickHope wrote on 10/28/2018, 11:08 AM

@bitman @Peter_P What is your display resolution?

bitman wrote on 10/28/2018, 11:27 AM

@bitman @Peter_P What is your display resolution?

3840x1600 (ultra wide, updated in signature)

Peter_P wrote on 10/28/2018, 11:37 AM

@bitman @Peter_P What is your display resolution?@

@Nick Hope

Mine is UHD : 3840 x 2160.
Even I could very hardly read the text, I switched to 125% scaling and in this mode I did not get the mentioned freezes, but with some minor editing of XAVC-S footage (So4 TRUE) in the TL Vp16 B307 just terminated with an error to be send.

bitman wrote on 10/28/2018, 11:40 AM

At least I will have more real-estate, but my old eyes start to suffer 😵

@bitman

I really can not work with 125%. The text becomes too smal for my older eyes. But 149% seems to work concering the FX interface as well but I had stability problem with that scaling. Does that occur with 125% on your system as well ?

I have not used anything other than 125%, I am a bit cautious about using a non-default scaling (like a custom scaling le.g.149%) as Microsoft warns that such custom scaling is not recommended (as opposed to default scaling 100/125/150 etc...) it is even hidden in the advanced properties which is further sign of "better not mess with it".

NickHope wrote on 10/28/2018, 11:45 AM

Let's go and use this post to continue the high DPI scaling discussion. I've removed "248" from the post name: https://www.vegascreativesoftware.info/us/forum/vp16-high-dpi-scaling-issues--112578/

bitman wrote on 10/28/2018, 11:47 AM

@bitman @Peter_P What is your display resolution?@

@Nick Hope

Mine is UHD : 3840 x 2160.
Even I could very hardly read the text, I switched to 125% scaling and in this mode I did not get the mentioned freezes, but with some minor editing of XAVC-S footage (So4 TRUE) in the TL Vp16 B307 just terminated with an error to be send.

I understand now that you need more scaling than 125% to read text with your 4K monitor. This is one of the reasons I did not purchase a 4K monitor, but an ultra wide curved, which requires less scaling and has great horizontal space for timeline editing (and is a great gaming monitor for immersion as well).

Peter_P wrote on 10/28/2018, 11:48 AM

I have not used anything other than 125%, I am a bit cautious about using a non-default scaling (like a custom scaling le.g.149%) as Microsoft warns that such custom scaling is not recommended (as opposed to default scaling 100/125/150 etc...) it is even hidden in the advanced properties which is further sign of "better not mess with it".

I only tried the 149%, because it was recommended in the High DPI thread. Normal/System-text is also not as clear as with the regular scaliling. For my system MS is recommending 150%, but this results in too small text for me and does not help Vegas to display the FX interfaces properly. So I stay with 175% and hope that some days I can use Vegas with clear text, icon and pictures in High DPI mode.

Peter_P wrote on 10/28/2018, 11:59 AM

I understand now that you need more scaling than 125% to read text with your 4K monitor. This is one of the reasons I did not purchase a 4K monitor, but an ultra wide curved, which requires less scaling and has great horizontal space for timeline editing (and is a great gaming monitor for immersion as well).

I’m not interested in gaming but want to have a 1:1 mapping of my UHD footage on the display on full preview.

/OT

Coriaman wrote on 10/28/2018, 8:56 PM

being used interchangeably between Japanese and English.

When used in English, Japanese is mixed up.

NickHope wrote on 10/28/2018, 9:50 PM

being used interchangeably between Japanese and English.

When used in English, Japanese is mixed up.

@Coriaman Please report that issue by submitting a support request at https://support2.magix.com/customer/en/vegas/form

set wrote on 10/29/2018, 8:02 AM

https://www.vegascreativesoftware.info/us/forum/vegas-pro-16-update-2-build-307--113473/
Official announcement

Martin L wrote on 10/29/2018, 2:33 PM

I installed build 307 this morning and it opened! Although the first attempt Vegas didn't manage to open the project I had started three days before, but on second attempt it worked. Then I was able to work with it the rest of the day with only one crash. What that was about I don't know but the error message from the PC said the GPU driver stopped working and had to be reset. That crashed Vegas. But after that no problems.

Build 307 is quicker and smoother too. I like it and hope it continues to work.

jrb101 wrote on 10/30/2018, 4:43 AM

So far with Vegas 16 (365 ed), since update 261 and also 307 I've been enjoying buttery smooth timeline playback (using so4compound and GPU acceleration on!) and no crashes that weren't the fault of a 3rd-party plugin.

I'm actually really impressed with Vegas Pro now, and after toying with going back and forth between Vegas and Davinci Resolve 15, I think I might settle on using Vegas for the vast majority of my projects. Well done Vegas Pro developers - you're doing a great job pushing forward on the product and trying to squash any bugs that get reported!

Lots of people seem to hate on Vegas for being buggy or crashing a lot, but I've found it to be just as stable as other NLEs when set correctly - just look at the forums for Premiere Pro, or Resolve and see how many issues they have too - the main issue is that it's not always obvious what the "right" settings are for anyone's particular setup (e.g. so4compoundplug seems to cause a lot of issues in however it's decoding AVC for a lot of people)

I don't know if there is a "Suggestions"/"Feature Requests" post that I could add to, but if there is I'd like to add a couple of requests as there are a couple of features in Resolve that I do miss in Vegas (but not enough to push me away from it):

1) Native optical flow retiming/resampling - it's not perfect and can lead to odd artefacts, but it is a really useful method in other NLEs

2) A version of "Morph Cut" (PPro), "Flow" (FCPX) or "Smooth Cut" (DVR) transition, which is reliant on optical flow to create new frames (and face-tracking in the case of PPro's Morph Cut) - it's a reasonably specialised requirement, but I say "errr" and "ummm" lots in my videos and using this kind of transition means I can cut all of these out and have a nice smooth talking-face/vlog video without a million jump cuts!

3) Planar tracking, corner pinning and "track backwards/track forwards" for the tracking module (unless I'm missing the options) - the new tracker is great and I hope it continues to get developed further.

Overall I'm really impressed with how far Vegas has come in the last couple of years and where it seems to be going.

VEGASPascal wrote on 10/30/2018, 7:40 AM

The Video Stabilisation autozoom is still to agressive.

Thanks for your feedback and the hint for the checkbox.

I do not understand the word too "agressive". The "Auto Zoom" checkbox is adjusting the minimum borders for you. If you change the zoom slider manually, than you will see black borders.

It's like any other video stabilizer (Mercalli, Boris, etc.)... The zoom is the result of the length of your smoothing and the camera movement. If you increase the smoothing length, the zoom in effect is also increased.

set wrote on 10/30/2018, 8:35 AM

It's like any other video stabilizer (Mercalli, Boris, etc.)... The zoom is the result of the length of your smoothing and the camera movement. If you increase the smoothing length, the zoom in effect is also increased.

Add my experiences (in case you haven't use subclip technique) : I guess it depends on your source or 'shake-level', but, since they required to be put as MediaFX, so it is applied to whole clip including unused part. I usually do cutting first, define the trim range of the clip used, then create subclip based on the range of the clip used. Make stabilization process based on this subclip can make a differences than applying it to whole clip.

fr0sty wrote on 10/30/2018, 9:45 AM

Yeah, requiring that the effect be applied at the media level is very inefficient. Maybe I don't want to stabilize an hour long clip that will take hours to stabilize, maybe I only need the few minutes of it that is going to end up in my final edit... Not only does it waste time, but as pointed out above, it can make the correction more aggressive than needed.

set wrote on 10/30/2018, 10:02 AM

That's why creating a subclip is a solution for me... especially when you need few minutes of an hour long clip source. Creating subclip will limit only the analyzing process for that selected range only.

Martin L wrote on 10/30/2018, 10:11 AM

So, how how do you create a subclip? What does it mean?

jrb101 wrote on 10/30/2018, 10:16 AM

So, how how do you create a subclip? What does it mean?

Just had to look this up myself in the manual - page 142!

You can create a subclip by either viewing the media clip in the trimmer window and selecting in and out points, then click on the "Create Subclip" button in the trimmer window and give it a name in the subclip dialog box

You cut the video on the timeline, then right-click on the portion you've cut to your needs and select "Create Subclip" from the context menu.

I never knew about this before and it looks like it could be a real time-saver with the stabilizer!

j-v wrote on 10/30/2018, 10:20 AM

So, how how do you create a subclip? What does it mean?

1 2 3 4 … 7

of 7