Since updating to build 643 I cannot load any of the 'media generator - plug-ins'. (titles and text - Solid Colour - Credit Roll etc) Loads onto timeline then then freezes and have to re-start as everything just crashes. Transitions work
......as everything just crashes. ...
Can you show us the crash report?
It just freezes ... no crash report as I then have to re-start the pc.
It just freezes ... no crash report as I then have to re-start the pc.
I'm in the process of being helped by support for constant crashing. As I don't always get the report up after a crash they asked me to give them what was in C:\Users\(UserName)\AppData\Local\VEGAS\ErrorReport
Maybe you've already looked there. I tried all the friendly advice on here but nothing has worked in my case. I even splashed out on a new RX 6800 XT because others seemed happy with it, but that hasn't worked either. I did another clean install of Windows 11 with the new GPU, loaded the drivers and then Vegas 19 only, with no plug-ins, it was the only program on my PC and it still crashed! I hope so much that support can help me.
I just wonder if it would be of benefit to have a separate post for ones (who have crashes often enough that it makes Vegas 19 unusable) to report their crashes just to see if it would highlight common denominators. Would that be of benefit to the program writers? Just a thought.
What is wrong with your servers? It took over an hour to download and only half of the update. It should be 10s with my connection. 😫
It just freezes ... no crash report as I then have to re-start the pc.
I'm in the process of being helped by support for constant crashing. As I don't always get the report up after a crash they asked me to give them what was in C:\Users\(UserName)\AppData\Local\VEGAS\ErrorReport
Maybe you've already looked there. I tried all the friendly advice on here but nothing has worked in my case. I even splashed out on a new RX 6800 XT because others seemed happy with it, but that hasn't worked either. I did another clean install of Windows 11 with the new GPU, loaded the drivers and then Vegas 19 only, with no plug-ins, it was the only program on my PC and it still crashed! I hope so much that support can help me.
I just wonder if it would be of benefit to have a separate post for ones (who have crashes often enough that it makes Vegas 19 unusable) to report their crashes just to see if it would highlight common denominators. Would that be of benefit to the program writers? Just a thought.
Please do start a thread with a clear title. To the extent we can figure out the factors or hardware common to frequent crashes it will be much easier to address. Replicable problems affecting more than one user with some underlying commonality are more solveable. Also include specifics of media in use as it really matters.
I use Voukoder for everything, when I"m encoding I"ll very often remember I should have altered something before encoding. When I attempt to cancel the encode Vegas crashes. Although it sounds like waving a red flag at Vegas taunting it to crash I've never seen this before
I attempted to replicate crash, but so far no more crashes
Has anyone noticed their timeline disappearing for any reason before build 643? Maximum CPU use was 34%
Putting down a series of splits
Also have a look at this line. the dotted background shows through which it shouldn't be doing
Looks like an issue with thumbnail generation. I have had some thumbs take time to load, leaving a blank event in its place (which makes the track look empty there, it can be confusing), but I have not yet seen that.
I used Howard's file https://drive.google.com/file/d/1a0r86Ux1yFcGY4-ub8NnEr0V7MUI-u1F/view
It's over 2GB so if anyone wanted to test. It is a 620Mb/s file, however it's on a Sata SSD, which should be fast enough. This is a speed test for the drive
But if the drive wasn't fast enough, it still seems strange the timeline is behaving like that.
It isn't the drive, as the issues I am experiencing happen even if the media is on an NVME SSD... it's a bug in thumbnail generation, at least in my case.
I use Voukoder for everything, when I"m encoding I"ll very often remember I should have altered something before encoding. When I attempt to cancel the encode Vegas crashes. Although it sounds like waving a red flag at Vegas taunting it to crash I've never seen this before
I attempted to replicate crash, but so far no more crashes
I don't use Voukoder but my VEGAS (18/19) crashes every time when I cancel the render process.
No exception.
I rarely cancel my rendering so can live with it.
It isn't the drive, as the issues I am experiencing happen even if the media is on an NVME SSD... it's a bug in thumbnail generation, at least in my case.
Have had thumbnail generating delays in the past myself and generally keep them turned off for timeline clips in video preferences. I don't think these are cached to the file system like Vegas Explorer's thumbs view.
I am back to version 636. I added a slow motion effect to the video, and after a few adjustments, version 643 simply closed itself. So I took it down and am waiting for a newer version.
How do you go about downgrading it after updating? I'm having back to back crashes and getting nothing done now for 3 days.
Any help would be hugely appreciated!
I am back to version 636. I added a slow motion effect to the video, and after a few adjustments, version 643 simply closed itself. So I took it down and am waiting for a newer version.
How do you go about downgrading it after updating? I'm having back to back crashes and getting nothing done now for 3 days.
Any help would be hugely appreciated!
But if a project has been saved in 643 can it be opened in 636? Maybe someone else can answer.
I've been using 643, and it's been very stable as long as I have Legacy AVC Decoder enabled but tonight I decided to load my free Boris Continuum that came with 19 and then I couldn't even open Vegas without it crashing, instant Problem Report every time. I uninstalled Boris and now it's opening and running fine. But means I can't have a couple of FX I liked. SIGH!! 😩
@Vincent-Brice, I've been quite successful so for with 643 and Boris Continuum Complete 2022.5, Sapphire, NBFX TFX7, Ignite Pro 5, Vitascene and Mercalli Suite 5 and other ancillary addons.
I feel your frustration.... and no... you can't open a 643 project in an earlier build for VP19.
I've been using 643, and it's been very stable as long as I have Legacy AVC Decoder enabled but tonight I decided to load my free Boris Continuum that came with 19 and then I couldn't even open Vegas without it crashing, instant Problem Report every time. I uninstalled Boris and now it's opening and running fine. But means I can't have a couple of FX I liked. SIGH!! 😩
It might be worth reaching out to Boris about that.
When adding music from Vegas Hub to project, video preview becomes 'out of sync' (weird flickering that shows random locations of current timeline when playing preview) and editing is not possible (app stays responsive otherwise). Restarting vegas cures the problem. This problem has been there earlier versions too.
I am using 10-bit HEVC media and Vegas won't play it right and is really choppy. It also crashes regularly, and editing is a nightmare. Everything about the program is just slow and choppy with the 10-bit media. I have a $6,000 Dollar computer with a $1,000 graphics card, so the problem is not my computer. The only way I can even begin to edit is by reverting back and enabling legacy AVC and HEVC decoding. This apparently disables my graphics card, but this is what seems to work best. In the preview window, I use "Preview-Auto." Even so, the program crashes regularly (and they are big crashes) so I have to shut down all other programs and restart my computer. I manually save my work about every 10 seconds because of the number of crashes. It just seems like the 10-bit media is just too heavy for Vegas so it strains to work with it and, therefore, crashes regularly.
I hope and pray Vegas devotes some serious effort to deal with this issue as 10-bit HEVC is the future.
@Todd-Fink from what is known, HEVC using GPU decoding is not advised on Vegas Pro, it delivers a low quality encode, so HEVC LEGACY is the necessary setting, and that probably means you need proxies, either created by Vegas or yourself. A problem with Vegas appears to be slow proxy generation(from what people are saying). A problem you may have however is that the Magix decoder (not legacy HEVC) is forced for some 10bit HEVC codecs, you need to make sure that's not happening. If it is I'd probably re-encode to an intermediate AVC or other format for easier playback
Quality is not an issue with either decoder when using AVC, but if you have enough CPU and you have no compatibility problems, continue to use Legacy AVC, I find it works better in general with smooth playback over edit points. If you get a rare AVC that you can't playback smooth, as it's using too much CPU, consider proxy.
As for builds, I see no benefit to 643, and only negatives, less stable, more crashes, doing weird things. and I would expect that given all the changes you see in release notes. I had reasonable serenity with build 532 that became build 550 with a bug fix. I will most likely return to one of those
Vegas is still using your GPU for processing, it's just not using the GPU decoder when you use the legacy settings
The version 19 build 643. the version crashes the system.
I tested it on 3 computers and I have the same problem. I had to revert to version 19.0.636 which works fine.
I edit with videos from several different sources (GOPRO, Panasonic S5 and Panasonic G9).
Crash on opening a project or crash on opening only the program without a project?