Vegas Pro 13 - Bug Fixes

Selina wrote on 10/6/2016, 4:05 AM

I see from other posts that many bug fixes have been addressed in Vegas Pro 14, namely:

  1. Fixed a bug that caused a disabled Beziér mask to become enabled when the mask is moved
  2. Fixed a bug that caused some Video Capture Help links to be non functional
  3. Fixed a bug that caused the Sharpen FX to exhibit different results when set to 0.000 depending upon whether the GPU was engaged or not
  4. Fixed a but that caused the arrow keys and J/K/L shortcuts to lose the ability to move the play head after undoing a framerate change in Project Properties
  5. Fixed a bug that prevented users from choosing their language during the installation process
  6. Fixed a bug that prevented video files from some cell phone devices from being recognized
  7. Fixed a bug in the scripting API that could cause an OverflowException in scripting extensions
  8. Fixed a bug that could cause VEGAS Pro to hang if the Escape key is pressed to dismiss the Render As dialog box
  9. Improved support for HiDPI displays. WIndows 8.1 or Windows 10 is recommended when using a HiDPI display.
  10. Fixed a bug that could cause Vegas to crash when clicking in the header of the Vegas Explorer in Details view.
  11. Fixed a bug that could cause Vegas to crash when renaming an in-use file in the Vegas Explorer.
  12. Fixed a bug that could cause Vegas to crash during startup when running with multiple GPUs.
  13. Fixed a bug that could cause Vegas to crash during startup when running with many network adapters.
  14. Fixed a bug that could cause Vegas to become unresponsive when loading projects that contained unavailable plug-ins.
  15. Fixed a bug that could cause rendered files to be truncated when rendering from FLAC source audio.
  16. Fixed a bug that could cause inconsistent audio and video stream lengths when working with some MP4 clips.
  17. Fixed an issue that could cause one frame to appear black when using Side by side (full) stereoscopic 3D mode with GPU acceleration enabled.
  18. Fixed an issue that could cause incorrect output when using Track Motion to offset horizontally only with GPU acceleration enabled.
  19. Fixed an issue that could cause incorrect output when using Track Motion when the 2D Glow check box was selected with GPU acceleration enabled.
  20. Fixed an issue that could cause incorrect display when using FX Bypass mode in a split-screen configuration with GPU acceleration enabled.
  21. Fixed an error that incorrectly listed the Studio RGB range in the Broadcast Colors plug-in as 16-135. The correct range -- 16-235 -- is now displayed.
  22. Fixed drawing and scaling issues that could occur when running Vegas Pro with a HiDPI display on Windows 8/8.1 or Windows 10.
  23. Fixed drawing issues that could occur when scaling the keyframe timeline for OpenFX plug-ins.
  24. Improved performance when using 64-bit VST plug-ins.
  25. Fixed a bug that could result in inconsistent behavior after pasting video event attributes.
  26. Fixed a bug that could prevent Vegas Pro from correctly reading the Field Order value in some MOV files.
  27. Fixed a bug that prevented the Titles & Text plug-in from working correctly.
  28. Fixed a bug that could cause the application to become unresponsive in projects that contain a large number of bins in the Project Media window.
  29. Fixed a bug that prevented smart bins from preserving their Condition setting.
  30. Pressing A in the Trimmer now adds the current selection to the timeline as an event. If there is no selection in the Trimmer, the entire clip is used.

When will these fixes be released to existing Vegas Pro 13 users?

Last changed by Selina on 10/6/2016, 4:06 AM, changed a total of 1 times.

Operating System
    Windows 10 Pro 64-bit
CPU
    Intel Core i7 2600K @ 3.40GHz    32 °C
    Sandy Bridge 32nm Technology
RAM
    32.0GB Dual-Channel DDR3 @ 784MHz (10-10-10-27)
Motherboard
    MSI P67A-G45 (MS-7673) (SOCKET 0)    37 °C
Graphics
    D2342P (1920x1080@60Hz)
    D2342P (1920x1080@60Hz)
    1023MB NVIDIA GeForce GTX 560 Ti (MSI)    36 °C
Storage
    465GB SAMSUNG HD502HJ (SATA )    26 °C
    0B SAMSUNG HD204UI (RAID )
    1863GB Western Digital WDC WD20EURS-73TLHY0 (SATA )    28 °C
    953GB Intel Raid 0 Volume (RAID )
    298GB Western Digital WD 3200BEV External USB Device (USB (SATA) )    32 °C
Optical Drives
    HL-DT-ST BD-RE BH10LS30
Audio
    Realtek High Definition Audio
  Plantronics Blackwire 3220 Series
  TASCAM US-122L

Comments

ushere wrote on 10/6/2016, 4:14 AM

when pigs fly ;-)

i think it highly unlikely that any bug fixes in 14 will be released for 13. wouldn't make sense (unfortunately)

Selina wrote on 10/6/2016, 4:33 AM

http://www.adweek.com/files/imagecache/node-blog/blogs/maxwell_1.jpg

Operating System
    Windows 10 Pro 64-bit
CPU
    Intel Core i7 2600K @ 3.40GHz    32 °C
    Sandy Bridge 32nm Technology
RAM
    32.0GB Dual-Channel DDR3 @ 784MHz (10-10-10-27)
Motherboard
    MSI P67A-G45 (MS-7673) (SOCKET 0)    37 °C
Graphics
    D2342P (1920x1080@60Hz)
    D2342P (1920x1080@60Hz)
    1023MB NVIDIA GeForce GTX 560 Ti (MSI)    36 °C
Storage
    465GB SAMSUNG HD502HJ (SATA )    26 °C
    0B SAMSUNG HD204UI (RAID )
    1863GB Western Digital WDC WD20EURS-73TLHY0 (SATA )    28 °C
    953GB Intel Raid 0 Volume (RAID )
    298GB Western Digital WD 3200BEV External USB Device (USB (SATA) )    32 °C
Optical Drives
    HL-DT-ST BD-RE BH10LS30
Audio
    Realtek High Definition Audio
  Plantronics Blackwire 3220 Series
  TASCAM US-122L

ushere wrote on 10/6/2016, 8:13 AM

yeah, i should have said fly first class :-P

i'm thinking that i'll probably wait for 15 to come along rather than take on the problems of 14's idiosyncrasies with plugins and the like... none of 13's bugs has been a deal breaker for me and it's been relatively stable in use - i simply don't have time to waste with 14....

OldJack wrote on 10/6/2016, 10:42 AM

Its difficult to understand how they could take a very good VP13 and down grade it so much to produce VP14.

 

NickHope wrote on 10/6/2016, 12:18 PM

Its difficult to understand how they could take a very good VP13 and down grade it so much to produce VP14.

How exactly do you think they've "down graded" it so much, and why is it difficult to understand? This is how I see it (deliberately leaving out pricing to focus on the actual functionality of the product):

GOOD

  • They've added about 10 new features that can be called "significant", some of which are very important to some users.
  • They've fixed 30 bugs (7 of which had affected me directly in VP13).

BAD

  • They've been forced to break compatibility with existing scripts and some plugins because they had no choice because of the previous owner's name being coded into them. Easy to understand. The scripts are simple to update and many of the affected important plugins have already been updated (sadly not including your Plural Eyes).
  • They've introduced about 5 known new bugs, 2 of which have already been fixed for the next patch, and hopefully the other 3 also will be fixed. It's a new release, hence easy to understand.
  • There's actually not so many significant new features for a new upgrade. Easy to understand in view of the transfer from Sony to MAGIX.
  • Most users don't appear to like the new buttons, including me (although I'm getting used to them fast), but easy to understand in terms of design trends.
  • They've removed the AC-3 Pro encoder. Not so easy to understand but the quote to license it from Dolby might have been astronomical.

MAYBE GOOD, MAYBE BAD

  • The AVC GPU-rendering is now hidden in the internal preferences, where users with incompatible graphics cards (i.e. the vast majority) won't misguidedly try to use it. Easy to understand.
Wolfgang S. wrote on 10/6/2016, 12:56 PM

I would not assume that there are further bug fixes for VP13. That has never been done in the past, sure they will fix bugs but in VP14 only.

And there is also no reason to state again and again that VP14 is a downgrade of VP13. Given the list of new features that is not true. 

Desktop: PC AMD 3960X, 24x3,8 Mhz * GTX 3080 Ti * Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Blackmagic Pocket 6K/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. Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG, Atomos Sumo

Selina wrote on 10/6/2016, 3:15 PM

@Nick Hope

http://www.vegascreativesoftware.com/gb/vegas-pro/product-comparison/#productMenu clearly shows Dolby 5.1 surround and stereo AC-3 encoding as part of all 3 editions ???

Operating System
    Windows 10 Pro 64-bit
CPU
    Intel Core i7 2600K @ 3.40GHz    32 °C
    Sandy Bridge 32nm Technology
RAM
    32.0GB Dual-Channel DDR3 @ 784MHz (10-10-10-27)
Motherboard
    MSI P67A-G45 (MS-7673) (SOCKET 0)    37 °C
Graphics
    D2342P (1920x1080@60Hz)
    D2342P (1920x1080@60Hz)
    1023MB NVIDIA GeForce GTX 560 Ti (MSI)    36 °C
Storage
    465GB SAMSUNG HD502HJ (SATA )    26 °C
    0B SAMSUNG HD204UI (RAID )
    1863GB Western Digital WDC WD20EURS-73TLHY0 (SATA )    28 °C
    953GB Intel Raid 0 Volume (RAID )
    298GB Western Digital WD 3200BEV External USB Device (USB (SATA) )    32 °C
Optical Drives
    HL-DT-ST BD-RE BH10LS30
Audio
    Realtek High Definition Audio
  Plantronics Blackwire 3220 Series
  TASCAM US-122L

Marco. wrote on 10/6/2016, 3:23 PM

And this is true but only via the studio encoder while the pro encoder is dropped now.