@Stan-Bateman Suggest you start a new thread for your problem.
Yes, users who are experiencing problems... Please make a thread about it... if you could then post a link to that thread in this post, it'll help us keep track of the issues with this particular build... but having your own thread guarantees that we can help you get your issue sorted without 10 other people posting about separate things and burying your request for help.
Trying to update Vegas Pro 20, get message C:\Users\wdepr\AppData\Local\Temp\mgxheaqx3oq\product\ not found. Scanned complete c drive cannout find.
Try using these links to download the installers. Download and install both of these, in this order.
VEGAS Pro 20 Build 326: https://rdir.magix.net/?page=KM8YQU96NTT1
Deep Learning Models 20.4: https://rdir.magix.net/?page=LHEFN95YY0ZY
If this fails, please make a new thread so we can further help you.
Under Update 2 mine crashes if I attempt to open MTS files from my Panasonic camcorder, including MTS files which worked previously. Other files (such as MP4 and AVI previously rendered in Vegas) are fine.
I've uninstalled and gone back to Build 214 and the same files open no problem.
Problem Description Application Name: VEGAS Pro Application Version: Version 20.0 (Build 326) Problem: Unmanaged Exception (0xccccfffe) Fault Module: C:\WINDOWS\System32\KERNELBASE.dll Fault Address: 0x00007FF8360ECD29 Fault Offset: 0x000000000002CD29 Fault Process Details Process Path: C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe Process Version: Version 20.0 (Build 326) Process Description: VEGAS Pro Process Image Date: 2023-01-16 (Mon Jan 16) 17:03:24
Happy to do testing if required. It's an old rig but still does the job for me:-
Windows 10 Pro 21H2
CPU: Intel Xeon X5670 2.93GHz hexa-core
RAM: 48GB
MB: Asus P6X58D-E
HDD: 480GB SSD, 2TB HDD, 8TB NAS
Video: AMD Radeon HD 6870 (4 x 1920x1080 screens)
Video: AMD Radeon HD 6570 (1 x 1920x1200 screen)
If you could upload a sample of that media to google drive or dropbox, we can try to test it on other systems to try to determine the cause and possible workarounds.
@TVJohn ok.... At least we know that the issue is specifically with Magix AVC.
By the way, have you dabbled with Voukoder ?...... It is what i use for all my renders. Yeah, this thing spits out the best outputs.
If you could upload a sample of that media to google drive or dropbox, we can try to test it on other systems to try to determine the cause and possible workarounds.
Try this. It's not a file I've tested on Update 2 but it's from the same recording session as the one which crashed (which is a 3GB file). This one's only 55MB.
https://drive.google.com/drive/folders/17pWONZf7Z5K7i9aCM8QlnXRsTUb4I1VC?usp=sharing
It's importing ok on my end... my gut is telling me it's those GPUs, definitely older than recommended spec... perhaps a driver update might help? Worth a shot.
If you could upload a sample of that media to google drive or dropbox, we can try to test it on other systems to try to determine the cause and possible workarounds.
Try this. It's not a file I've tested on Update 2 but it's from the same recording session as the one which crashed (which is a 3GB file). This one's only 55MB.
https://drive.google.com/drive/folders/17pWONZf7Z5K7i9aCM8QlnXRsTUb4I1VC?usp=sharing
Tested your file on my system and I have no problems loading the file.
Here is the media info
General ID : 1 (0x1) Complete name : C:\Users\...\Downloads\00008.MTS Format : BDAV Format/Info : Blu-ray Video File size : 54.2 MiB Duration : 25 s 412 ms Overall bit rate mode : Variable Overall bit rate : 17.9 Mb/s Maximum Overall bit rate : 18.0 Mb/s Recorded date : 2023-01-24 22:16:42+00:00 Writing application : Panasonic Video ID : 4113 (0x1011) Menu ID : 1 (0x1) Format : AVC Format/Info : Advanced Video Codec Format profile : High@L4 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 2 frames Format settings, GOP : M=3, N=12 Codec ID : 27 Duration : 25 s 360 ms Bit rate mode : Variable Bit rate : 16.8 Mb/s Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16:9 Frame rate : 25.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Interlaced Scan type, store method : Separated fields Scan order : Top Field First Bits/(Pixel*Frame) : 0.324 Stream size : 51.1 MiB (94%) Audio ID : 4352 (0x1100) Menu ID : 1 (0x1) Format : AC-3 Format/Info : Audio Coding 3 Commercial name : Dolby Digital Codec ID : 129 Duration : 25 s 440 ms Bit rate mode : Constant Bit rate : 256 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 31.250 FPS (1536 SPF) Compression mode : Lossy Delay relative to video : -80 ms Stream size : 795 KiB (1%) Service kind : Complete Main Text ID : 4608 (0x1200) Menu ID : 1 (0x1) Format : PGS Codec ID : 144 Duration : 24 s 896 ms Delay relative to video : -80 ms
I noticed that some important corrections were made that were not mentioned in the official note. I want to thank you for these corrections:
1. The option Trim Events to include all frames now works correctly with velocity envelopes and other time adjustment options. https://www.vegascreativesoftware.info/us/forum/vegas-pro-19-build-636-improvements-suggestions--135876/
2.Rendering in ProRes 4444 format with alpha channel no longer produces a giant file. Now the rendered file size is normal. https://www.vegascreativesoftware.info/us/forum/native-prores-4444-with-alpha-channel-in-vegas-very-big-file--136827/#ca870591
There is just a small bug in the render window that doesn't show the rendered file size correctly but that doesn't affect the final result at all.
3.The Deep Lerning Models installation bug that occurred on some machines and prevented the use of AI resources no longer occurs. https://www.vegascreativesoftware.info/us/forum/vegas-deep-learning-models-bug-fix--136228/
So far this version is pretty stable. I'm enjoying the improvements, especially the improvements that have been made to the Preview quality. Thank you! Keep up the good work.
1. The option Trim Events to include all frames now works correctly with velocity envelopes and other time adjustment options. https://www.vegascreativesoftware.info/us/forum/vegas-pro-19-build-636-improvements-suggestions--135876/
@Vegas_Pro_Brasil Que massa! Nem sabia disso. Show de bola!
2.Rendering in ProRes 4444 format with alpha channel no longer produces a giant file. Now the rendered file size is normal. https://www.vegascreativesoftware.info/us/forum/native-prores-4444-with-alpha-channel-in-vegas-very-big-file--136827/#ca870591
There is just a small bug in the render window that doesn't show the rendered file size correctly but that doesn't affect the final result at all.
Wooow! Very good! Made me want to re-render all my animations in alpha. :(
Some old issues remain. @VEGASDerek
- The filter pack bug that it is not possible to rename a saved preset.
- Ctrl + Z does not work when using Curves from Lane/Curves.
- Ctrl + Z in Bézier Masking doesn't work either.
- GIFs leave the complementary vegas lagged.
- Being able to drag a VFX to several tracks at the same time.
- Scroll down the vfx keyframe animation timeline with the mouse wheel. And not just for the scrolling sidebar.
Random black frames - preview and encode https://www.dropbox.com/s/8zj5njudr50v8uh/4K60p%20iphone13.mov?dl=0
Black frames are completely random. May appear many times, may appear only once when the bicyclist with safety vest enters scene, may not appear at all
Crash - This test file has likely been crashing vegas for over a decade, nothing has changed. I converted the AC3 audio to pcm but it was crashing the same with AC3 except with deafening white noise.
Random black frames - preview and encode https://www.dropbox.com/s/8zj5njudr50v8uh/4K60p%20iphone13.mov?dl=0
Black frames are completely random. May appear many times, may appear only once when the bicyclist with safety vest enters scene, may not appear at all
Crash - This test file has likely been crashing vegas for over a decade, nothing has changed. I converted the AC3 audio to pcm but it was crashing the same with AC3 except with deafening white noise.
When I see iPhone, it rings the VFR red flag. Can you send a MediaInfo of your iPhone files. iPhone creates Variable Frame Rate files (VFR) which is incompatible with a NLE editor. I have the same problem when using files from my iPhone, I need to convert them using Handbrake to Constant Frame Rate (CFR) before using it.
Hello everyone,
The VEGAS Team is excited to announce the release of our second update for VEGAS Pro 20, build 326. Please use this thread to post general comments on this update. For details on build 326, please read this post in the News forum.
Thank you,
The VEGAS Creative Software Team
I've found the Smart Mask (beta) in the Media Generator section but if I drag it to an event on the timeline I just get a message saying "Model not found". Is there a tutorial about what this plugin is all about somewhere? I really have no idea what it's suppose to do. Even though I've used vegas for more than a decade, I think sometimes the Vegas developers knowing everything about the program so very well forget that there are those of us out here that need some instructions with new features.
Thanks
Glad you're enjoying the welcome screen here. Sure, it gave the developers an awful lot of time and work, but the slow motion optical flow needs to be fixed more. Bitten wavy edges appear. This makes this function unusable.Isn't it better to implement AI slowmotion from Nvidia? Even Topaz Video AI has better slow motion
Furthermore, there has been a problem with wav and other audio files for several years. The more people voiced the problems. I play sounds in them that are not supposed to be played.
I don't want to spoil everyone's enjoyment of the new things, but there are much more important ones that are still not fixed. It's time for the guys from the team to comment on these problems as well.
The welcome screen will not make your work easier.
When I see iPhone, it rings the VFR red flag. Can you send a MediaInfo of your iPhone files. iPhone creates Variable Frame Rate files (VFR) which is incompatible with a NLE editor. I have the same problem when using files from my iPhone, I need to convert them using Handbrake to Constant Frame Rate (CFR) before using it.
@Illusion It shows as VFR like all phone videos, but the auto frame rate thing would not be happening here. A good example of where it's seen is at a night concert recording in 60fps, zoomed in on well lit stage with lighting effects 60fps, change to crowd shot 30fps. It's used to get that extra f-stop of exposure where there's not enough light.
It is a good observation on your part though, relating the high visibility vest bumping up frame rate from 30fps to 60 and down to 30fps after he passes . On such a well lit sunny day I don't think that would be happening, and most likely locked at 60fps
@Former user, you can also use Shutter Encoder to conform your footage to 60fps fixed.
VEGAS Pro 20 Build 326
Just installed new update and I am experiencing very slow rendering.. 1 noticeable change is my GPU load which use do be minimal is now doing most all the work (now over over 85%)..Not sure what caused this...
No other changes from the day before I installed update
I9-13900k, 128 mg ram
RTX 3080ti
Trying to give some help:
What are your used settings for Options/Preferences/Video and Options/Preferences /File I/O?
Give also a screenshot of the Help/Check for Driver Updates
My NVIDEO studio drivers are the latest..
Re: Pref / video... I tried Dynamic ram to both 65% and 75% no change..I just tried setting it to 0..rendering time improved but still not very good.
Re: Pref /IO.. the only change I made was turning OFF Legacy HEVC ( which I don't need )
thank you for any input
It looks that your good intel GPU is not showing up.
If that one is not visible at your Device Manager/Display Adapters, you have to allow it to show up in the BIOS.
After that restart your Windows and reset Vegas exactly following this: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/
Hello everyone,
The VEGAS Team is excited to announce the release of our second update for VEGAS Pro 20, build 326. Please use this thread to post general comments on this update. For details on build 326, please read this post in the News forum.
Thank you,
The VEGAS Creative Software Team
Maybe it is better in such announcements to add:; " but when you encounter problems that need a solution start also your own post with your detailed information about your problem" or something like that