VEGAS Pro 16 Update 3 (build 352) - General Discussion

Comments

Lukasz wrote on 1/9/2019, 11:20 AM

Hello, yesterday I changed from vegas 13 to vegas 16 bulid 352 and I have a lot of problems. Quite often, the program hangs and turns off. Full preview of the image on vegas 13 worked correctly after adding the plugin HitFilm Bleach Bypas and on the vegas 16 pro very strongly cropped the image and drops to 10 frames. I changed to the old Radeon MSI R9 280X graphics card and the preview problem disappeared. Both cards are podijnej performance and operated on vegas 13 a vegas 16 Asus 1050Ti works very poorly. What could be the reason?
I have
Ryzen 1700X
16 GB Ram
GTX 1050 Ti OC edition 4GB
ASUS PRIME X370-PRO motherboard

HasanKhurshid29 wrote on 1/9/2019, 2:35 PM

I am having trouble as whe I click on full screen the computer screen turns black and then this error shows up. I am on the previous build I think. Secondly I have disabled Gpu acceleration. The file format I usually work on is AVCHD from sony nxcam NX30u.

CPU: intel core i7 8086k
Motherboard: Asrock z390m/itx
Ram: 8gb DDR4 2666 G Skills Agesis
SSD/HDD: 1tb WD Black
GPU: Nvidia Quadro K4000
PSU: Cooler Master 600W Master Lite
Chassis: Cooler MasterWatt Elite 130
OS: Windows 10 64 Bit
 

fr0sty wrote on 1/9/2019, 7:56 PM

Is that the latest driver available for your GPU?

HasanKhurshid29 wrote on 1/10/2019, 10:23 AM

Is that the latest driver available for your GPU?

Yes

HasanKhurshid29 wrote on 1/10/2019, 10:27 AM

Is that the latest driver available for your GPU?

After latest update, it works better but still sometime same issue happens. Secondly I want to know what happens when I disable gpu acceleration (as when it's enabled it crashes more often)

DesertDave wrote on 1/10/2019, 11:42 AM

 

After upgrading to VP 16, I cannot render. Every time I try it just crashes. I updated to Build 352 but it does the same. I need to get this working right away! It is on a brand new Computer as follows:

Operating System
  Platform: Windows 10.0 (64-bit)
  Version: 10.00.17134
  Language: English
  System locale: English
  User locale: English

Processor
  Class: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
  Identifier: GenuineIntel
  Number of processors: 8
  MMX available: Yes
  SSE available: Yes
  SSE2 available: Yes
  SSE3 available: Yes
  SSSE3 available: Yes
  SSE4.1 available: Yes
  SSE4.2 available: Yes

Display
  Primary: 1920x1080x32

Memory
  Physical memory: 16,278.2 MB
  Paging memory available: 18,710.2 MB

AVsupport wrote on 1/10/2019, 4:57 PM

the old tip that works for me: disable iGPU in your BIOS if you can, and run VP solely on your graphics card.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

chris-h wrote on 1/13/2019, 10:42 AM

I was just about to update (because I read in another post that there were 360 render filters in the latest version) when I found this thread. How is it possible that the latest version is less stable than previous ones?
Is anyone else having issues with the latest update?

PC (Windows 10 64Bit)

ASrock Z390 Pro4 Mainboard
Processor (CPU) Intel (R) Core (TM) i9-9900K CPU @ 3.60GHz 
Memory 64GB RAM (4 x 16GB 3000MHz DDR4)
Graphics Card GTX 1060 6GB Palit StormX Graphics Card
500GB Samsung 970 Evo SSD M.2 NVMe
2nd Hard Disk 3TB Toshiba P300 7200RPM

Cameras
Canon 5D Mk3
GoPro Hero 4 Black
GoPro Hero 7 Black
Samsung Gear 360
Samsung Galaxy S7

Vegas Pro 16 Suite

Kinvermark wrote on 1/13/2019, 5:18 PM

It isn't. There are just a lot of unusual "corner cases" that take a long time to surface. Most of these issues are very specific and won't affect the vast majority of users. Except for the storyboard / thumbnail issues I don't get crashes - so I just avoid that area for now.

Martin L wrote on 1/14/2019, 2:01 AM

My build 352 is the best so far.

klapkowscy.com wrote on 1/21/2019, 4:45 AM

Aktualizacja 352 Trochę słabe, ponieważ nie widzi plików mp3 a jak nic dziwnego, że dodajesz je, aby nie grać i jak grać, aby usłyszeć trzaski i pisk, zamiast muzyki.

Dexcon wrote on 1/21/2019, 5:04 AM

Google translate translated klapkowscy.com's post (from Polish) as follows:

Update 352 A bit weak because it can not see mp3 files, and it's no wonder you add them to not play and how to play to hear crackling and squeal instead of music.

 

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2024.5, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

merlin-beedell wrote on 7/30/2019, 3:27 PM

Import media dont have variant *.mp3 and after import mp3 as all files music is screech

See if this helps...
This article gives and explanation and simple a registry fix that can help any application that tries to render MP3 files. I just tried it and Vegas (16 Pro) now correctly rendered an MP3 from a WAV source. For the last year i have been having issues. It seems that the issue may be rooted to Windows Updates.
http://www.komeil.com/blog/enable-fraunhofer-mp3-l3codecp-acm-windows

The solution says to change 2 registry settings from  l3codeca.acm into l3codecp.acm.
Seems that it has worked for CyberLink customers as well!