Known Issues in the Latest Version of VEGAS Pro


NickHope wrote on 10/27/2018, 4:10 AM

Removed from OP (fixed in VEGAS Pro 16 update 2 (build 307)):

Added VEGAS Video Stabilization (same issue as legacy Stabilize FX):

Added "possibly improved" note:

Also updated the official list of known issues at the bottom of the OP, which has a couple of small changes relating to the storyboard feature.

Wolfgang S. wrote on 10/27/2018, 7:21 AM

VP 16 b307: the new nit scale shows the correct nit level for „32bit floating point full range“ only (for example for FS7 s-log3 footage).

For both 8bit but also 32bit floating point video levels the nit levels must be corrected at the moment (apply levels and there the settings „Studio RGB to computer RGB“). Please not for 32bit floating point full range.

Desktop: PC AMD 3960X, 24x3,8 Mhz * GTX 3080 Ti * Blackmagic Extreme 4K 12G * Atomos Sumo * QNAP Max8 10 Gb Lan * Blackmagic Pocket 6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED (ProArt Studiobook 16 OLED (i9 12900H with i-GPU Iris XE, 32 GB Ram. Geforce RTX 3070 TI 8GB) with internal HDR preview on the laptop monitor
HDR monitor: ProArt Monitor PA32 UCG

NickHope wrote on 10/27/2018, 8:13 AM

Added to OP (very old issue):

  • [VP≤13+] In the Mixing Console, the width of only the right-most channel can be adjusted using the "Channel Width" controls in the context menu.
NickHope wrote on 11/2/2018, 7:10 AM

Added to OP:

  • [VP16+] Projects saved in previous versions open with Composite after any Track FX and Pan/Crop before any Event FX, despite the order saved in the previous version.
NickHope wrote on 12/22/2018, 11:15 PM

Added to OP:

Updated official known issues list to VP16 build 352.