VEGAS Pro 16 Update 4 (build 361) - General Discussion

Comments

arthur7 wrote on 3/23/2019, 6:07 PM

My setup i7 6700HQ, 16GB RAM, 4K display, 1TB SSD as C:, iGPU HD530 + GPU 970GTXm with 6GB VRAM.. i edit through a 2.5" 2TB USB 3.0 WD (not SSD). In Vegas 13 in 8bit project 1080p 25fps and Preview (full) in preview window i have NO dropped frames even with 3 video streams one below the other in the timeline (no multicam mode activated) in Vegas 15 and 16 with the same settings with Preview (half) it cannot keep up the realtime framerate unless i solo one of the 3 videos which play same time and wait 5 seconds to load the buffer and stop lagging and dropping frames!!!!!! I use only iGPU HD530 since the nVidia GPU i noticed hanging and crashing Vegas after 20-30 minutes of editing. Files from Canon 80Ds are 85Mbps which is quite high, still in Magix (V15, V16) preview engine works CRAPPY!!!!! :((((

Also even if i make proxies of my GH5 4K files in V15/16 plays normally only in Preview(half) which is unusable for the purpose of previewing since it is too pixely!

Newest info about my problem is when i edit a big project like a wedding which is 3-5 hours long i experience these performance problems. Because i tried to edit a small multi camera project in V16 build 307 and had same performance described as V13. Maybe it has to do with each clips thumbnails when there are hundreds of clips.

Eagle Six wrote on 3/23/2019, 7:20 PM

@arthur7 when you say hundreds of clips, how many hundreds would that be. Also, are you using a lot of sub-clips? The latest VP16 build is 361, is there a reason you are not using that build?

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

arthur7 wrote on 3/24/2019, 8:27 AM

How can i count the clips being used in timeline? I dont update to newer version since i am sure it has no other bugs reported from members.

Eagle Six wrote on 3/24/2019, 9:49 AM

@arthur7 here are some of the fixes, with what looks like at least 2 may directly benefit you......

Bug fixes

Crash that can happen when OpenColorIO library is not installed properly is now prevented

Incorrect values in metadata for HDR renders has been corrected

Improved handling of hardware dependent video plugins when GPU does not initialize properly

Likelihood of crash when resizing thumbnails in Project Media window has been reduced

Improved performance of thumbnail drawing within the project media window

Problem with some valid video plugins not appearing in the plugin chooser has been resolved

Crash when launching on a 2 GPU system when with one GPU disabled has been fixed

Smoothing parameter is now available in the basic mode of the Video Stabilization plugin

Crash when updating a grouped track that is not visible has been fixed

Crash when reading certain MP4 files is now prevented

Disabled some JDR project properties for non-HDR projects

Disabled HDR preview preference for 8 bit projects

Crash that may occur if the timeline ruler and speed controls are not visible as been resolved

Crash they may occur when beginning a render of building peaks or other similar tasks has been resolved

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

Christian de Godzinsky wrote on 3/25/2019, 10:37 AM

I have the exact same problem. After editing - the first “render as” crashes Vegas 15 (all versions of it, including the last 461 update). Every time, regardless what’s on the timeline. If there is no fix to this available to VP15... then count me out. Been with Vegas since version 6. That was the only rock stable version of this excellent program. After that it’s been downhill all the way ... VP15 has many other problems too, its not only this one that will make me soon abandon the ship.... A pro software should deliver and be rock stable. Vegas is neither. I would gladly pay for 16 but there is NO guarantee that these problems are fixed. Just reading this forum proves this.

 

fr0sty wrote on 3/25/2019, 10:53 AM

I have the exact same problem. After editing - the first “render as” crashes Vegas 15 (all versions of it, including the last 461 update). Every time, regardless what’s on the timeline. If there is no fix to this available to VP15... then count me out. Been with Vegas since version 6. That was the only rock stable version of this excellent program. After that it’s been downhill all the way ... VP15 has many other problems too, its not only this one that will make me soon abandon the ship.... A pro software should deliver and be rock stable. Vegas is neither. I would gladly pay for 16 but there is NO guarantee that these problems are fixed. Just reading this forum proves this.

 

You do realize there is a demo for 16, right? You do realize there was a demo for 15 as well, BEFORE you bought it, that you could have tried out?

Also, to get around the render bug, when you first open Vegas, drop some media into a blank project and select render as. The dialog should open up. Close it, then open your project and begin editing. After you are done SAVE IT, then click render as again. I find that usually gets rid of the render as crash.

If you think a "pro software should deliver and be rock stable", you're going to be sorely disappointed by Resolve and Premiere, both of which crash and have stupid limitations. Maybe you can move to final cut, but then it'll be your computer that has the stupid limitations.

fr0sty wrote on 3/25/2019, 11:06 AM

My setup i7 6700HQ, 16GB RAM, 4K display, 1TB SSD as C:, iGPU HD530 + GPU 970GTXm with 6GB VRAM.. i edit through a 2.5" 2TB USB 3.0 WD (not SSD). In Vegas 13 in 8bit project 1080p 25fps and Preview (full) in preview window i have NO dropped frames even with 3 video streams one below the other in the timeline (no multicam mode activated) in Vegas 15 and 16 with the same settings with Preview (half) it cannot keep up the realtime framerate unless i solo one of the 3 videos which play same time and wait 5 seconds to load the buffer and stop lagging and dropping frames!!!!!! I use only iGPU HD530 since the nVidia GPU i noticed hanging and crashing Vegas after 20-30 minutes of editing. Files from Canon 80Ds are 85Mbps which is quite high, still in Magix (V15, V16) preview engine works CRAPPY!!!!! :((((

Also even if i make proxies of my GH5 4K files in V15/16 plays normally only in Preview(half) which is unusable for the purpose of previewing since it is too pixely!

Newest info about my problem is when i edit a big project like a wedding which is 3-5 hours long i experience these performance problems. Because i tried to edit a small multi camera project in V16 build 307 and had same performance described as V13. Maybe it has to do with each clips thumbnails when there are hundreds of clips.

I edit multicam GH5 4K 10 bit files all the time just fine... Just finished a 5 camera 4k shoot with 4 4k gh4 tracks and 1 4k gh5 track. must be your system.

joost-berk wrote on 3/26/2019, 4:46 AM

I have the exact same problem. After editing - the first “render as” crashes Vegas 15 (all versions of it, including the last 461 update). Every time, regardless what’s on the timeline. If there is no fix to this available to VP15... then count me out. Been with Vegas since version 6. That was the only rock stable version of this excellent program. After that it’s been downhill all the way ... VP15 has many other problems too, its not only this one that will make me soon abandon the ship.... A pro software should deliver and be rock stable. Vegas is neither. I would gladly pay for 16 but there is NO guarantee that these problems are fixed. Just reading this forum proves this.

 

I am in communication with Magix - Vegas support about the Render As.. crash. And we're able to make a flow-chart wheter Vegas will crash Yes or No. This makes it easier for the support team to point a finger on this bug. Right now I can create genuine crash-error reports by following steps.

Now, Support is working on this. maybe that is the reason that it takes some time before a new patch is comming. They say it has something to do with .NET

We should be patience for now. I have all faith in a good fix for this issue!

Vegas Pro user since version 1.2

OS: Windows 10 Pro 1809

CPU: Intel Core i7-7820X

RAM: 32GB

GPU: Nvidia GeForce GTX 1080 8GB GDDR

Monitoring: Black Magic Design DeckLink SDI 4K

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

Dexcon wrote on 3/26/2019, 5:35 AM

They say it has something to do with .NET

That's interesting. After the Windows 10 update in Sept (I think it was) last year, both ProDad's RSpeedr and Mercalli 4 SAL had a significant display problem on opening the Import Media window. An error dialogue box attributed the problem to Netframework 3.5. Whatever the .NET problem was, MS didn't resolve it in the next W10 update, and then ProDad released updates for ReSpeedr and Mercalli 4 SAL which resolved the display problem.

I wonder if the .NET 3.5 issue has also affected Vegas Pro in some way.

Fiola wrote on 3/26/2019, 2:35 PM

My setup i7 6700HQ, 16GB RAM, 4K display, 1TB SSD as C:, iGPU HD530 + GPU 970GTXm with 6GB VRAM.. i edit through a 2.5" 2TB USB 3.0 WD (not SSD). In Vegas 13 in 8bit project 1080p 25fps and Preview (full) in preview window i have NO dropped frames even with 3 video streams one below the other in the timeline (no multicam mode activated) in Vegas 15 and 16 with the same settings with Preview (half) it cannot keep up the realtime framerate unless i solo one of the 3 videos which play same time and wait 5 seconds to load the buffer and stop lagging and dropping frames!!!!!! I use only iGPU HD530 since the nVidia GPU i noticed hanging and crashing Vegas after 20-30 minutes of editing. Files from Canon 80Ds are 85Mbps which is quite high, still in Magix (V15, V16) preview engine works CRAPPY!!!!! :((((

Also even if i make proxies of my GH5 4K files in V15/16 plays normally only in Preview(half) which is unusable for the purpose of previewing since it is too pixely!

Newest info about my problem is when i edit a big project like a wedding which is 3-5 hours long i experience these performance problems. Because i tried to edit a small multi camera project in V16 build 307 and had same performance described as V13. Maybe it has to do with each clips thumbnails when there are hundreds of clips.

I edit multicam GH5 4K 10 bit files all the time just fine... Just finished a 5 camera 4k shoot with 4 4k gh4 tracks and 1 4k gh5 track. must be your system.

Can you please share with us detailed hardware specs of your system? Because I am sorry to say. On our 5 different computers in our studios (hi-end PC's) is VEGAS 16 unable to edit multicam GH5 4K 10 bit files "just fine"... it's more like power-point presentation, but it doens't work. So actually using Power Point is better because VEGAS crashes after some time in playback for no reason. We discuss it here for 2 years straight, and I am still surprised that there are people which are defending bad state of the software.

It's not a stable software, if it crashes after 10 minutes in project without any plugins, just because you edit videos. That's why it's video editing software and not video crashing software. It's weird that it works for you "just fine" and for so many people and PC's don't. So please, share with us your hardware pick - so I can setup same PC here in our studio too and finally have good VEGAS PC...

Right now: I have great playback performance without major crashing on Resolve and Premiere. Yes, there are times that even these crashes, but it's minor, minimal chance they will.

I am going here every week. Every week I am working on one project (releasing one episode of our show each week), and everytime the VEGAS crashes, I am going to see here if someone finally explained or shared news ... but for some months quiet now.

What I see MAGIX needs to do, is to sit down and INVEST in finally fixing the code. And stop making any upgrades/new plugins/new features. They need to firstly have stable editing. That means playback + cut. After that they will be back on track.

It's hard to say this on loud. It's also kind of arrogant from me - I get it. But I am not satisfied consumer right now. And I want to be one! I am working through many lost hours which I could spent with my family instead of launching VEGAS every few minutes over again and again when I hit spacebar to see preview and all I get is crash.

Try to understand this perspective.

Kinvermark wrote on 3/26/2019, 3:54 PM

@Fiola

Your post is an example of why I really dislike the "General Discussion" threads: people post their own peculiar problem and make believe it applies to everyone.

That's why you are

still surprised that there are people which are defending bad state of the software.

Believe it! There are MANY, MANY OF US who work with Vegas Pro 16 and have nothing more than minor issues - The same as applies to every other piece of software.

j-v wrote on 3/26/2019, 4:23 PM

I agree on my 2 machines no problems at all exept as I overule the limits of the program for HEVC 4K files without taken precaution measure as proxy files or very heavy load of those non proxy files.

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

fr0sty wrote on 3/27/2019, 2:24 AM

My setup i7 6700HQ, 16GB RAM, 4K display, 1TB SSD as C:, iGPU HD530 + GPU 970GTXm with 6GB VRAM.. i edit through a 2.5" 2TB USB 3.0 WD (not SSD). In Vegas 13 in 8bit project 1080p 25fps and Preview (full) in preview window i have NO dropped frames even with 3 video streams one below the other in the timeline (no multicam mode activated) in Vegas 15 and 16 with the same settings with Preview (half) it cannot keep up the realtime framerate unless i solo one of the 3 videos which play same time and wait 5 seconds to load the buffer and stop lagging and dropping frames!!!!!! I use only iGPU HD530 since the nVidia GPU i noticed hanging and crashing Vegas after 20-30 minutes of editing. Files from Canon 80Ds are 85Mbps which is quite high, still in Magix (V15, V16) preview engine works CRAPPY!!!!! :((((

Also even if i make proxies of my GH5 4K files in V15/16 plays normally only in Preview(half) which is unusable for the purpose of previewing since it is too pixely!

Newest info about my problem is when i edit a big project like a wedding which is 3-5 hours long i experience these performance problems. Because i tried to edit a small multi camera project in V16 build 307 and had same performance described as V13. Maybe it has to do with each clips thumbnails when there are hundreds of clips.

I edit multicam GH5 4K 10 bit files all the time just fine... Just finished a 5 camera 4k shoot with 4 4k gh4 tracks and 1 4k gh5 track. must be your system.

Can you please share with us detailed hardware specs of your system? Because I am sorry to say. On our 5 different computers in our studios (hi-end PC's) is VEGAS 16 unable to edit multicam GH5 4K 10 bit files "just fine"... it's more like power-point presentation, but it doens't work. So actually using Power Point is better because VEGAS crashes after some time in playback for no reason. We discuss it here for 2 years straight, and I am still surprised that there are people which are defending bad state of the software.

Ryzen 7 1800x

64GB DDR4

GTX 970 GPU

Windows 10

It's not a stable software, if it crashes after 10 minutes in project without any plugins, just because you edit videos. That's why it's video editing software and not video crashing software. It's weird that it works for you "just fine" and for so many people and PC's don't. So please, share with us your hardware pick - so I can setup same PC here in our studio too and finally have good VEGAS PC...

Right now: I have great playback performance without major crashing on Resolve and Premiere. Yes, there are times that even these crashes, but it's minor, minimal chance they will.

Here I am unable to wrap up an after effects project because Media encoder won't encode...

I am going here every week. Every week I am working on one project (releasing one episode of our show each week), and everytime the VEGAS crashes, I am going to see here if someone finally explained or shared news ... but for some months quiet now.

It can take a while to sort issues sometimes, especially when they only affect a small number of people and the issue is therefore hard to reproduce.

What I see MAGIX needs to do, is to sit down and INVEST in finally fixing the code. And stop making any upgrades/new plugins/new features. They need to firstly have stable editing. That means playback + cut. After that they will be back on track.

They've been investing in fixing the code for years. Go look at the bug fixes since they bought Vegas... you could fill a book with them. It would be nice to see the pace pick up, maybe see them grow the team a bit, but to try to act like they're ignoring underlying problems just because they haven't tackled your specific issue yet is ridiculous.

It's hard to say this on loud. It's also kind of arrogant from me - I get it. But I am not satisfied consumer right now. And I want to be one! I am working through many lost hours which I could spent with my family instead of launching VEGAS every few minutes over again and again when I hit spacebar to see preview and all I get is crash.

Try to understand this perspective.

I've been there... I've even lost gigs because I was late getting work out due to Vegas crashing on me, but in time I decided to work with the developers rather than whine and cry expecting them to snap their fingers and make the bug disappear. I began figuring out how to reproduce the bugs, and started making detailed video bug reports and sending it to them, and now we communicate regularly when I have an issue, and they usually get it sorted pretty quickly when I don't manage to figure it out on my own.

 

And just to prove it... Here's a 5 camera edit (proxies are used, as one camera was a gopro and its video decodes horribly) running at native frame rate in Vegas 16 update 4 on the system described above. I use full resolution preview quality settings. I can smoothly edit up to 3 cameras without proxies, and my system isn't exactly fast compared to modern top shelf CPUs.

 

Marco. wrote on 3/27/2019, 4:04 AM

"proxies are used"

For all of the 4k clips?

fr0sty wrote on 3/27/2019, 4:30 PM

Yes, on this particular project I proxied everything, but I brought the point up because the user above was claiming that not even the proxy system produced usable results for them. I was showing this not to be the case on my system, even in a very complex project. I've also had similar results on projects with 3 or fewer cameras without a proxy at all, and my system isn't anything to write home about.

Fiola wrote on 3/28/2019, 10:26 AM

Yes, on this particular project I proxied everything, but I brought the point up because the user above was claiming that not even the proxy system produced usable results for them. I was showing this not to be the case on my system, even in a very complex project. I've also had similar results on projects with 3 or fewer cameras without a proxy at all, and my system isn't anything to write home about.


This is not fair comparison towards to me. I tried to work with developers too. But they never actually continue to communicate on this. I even tried to get into insider beta program. I am using VEGAS for a very long time. I'm also fan and believer in Magix as reliable company. VEGAS is important tool in our pipeline - I would be really an idiot to be against it.

But, what I am doing is not a whining. Maybe my few last posts looks like that. I am providing feedback, that things Magix is working on are not getting better for us in studio at all. It's important feedback as well. I am buyer too. Minority or not. And fact is, that for our studio, there is minimum support.

With proxies, we can edit footage smoothly too. Apart from that case, when we hit crash of software every 10 minutes - it doesn't depend if we are using proxies or not. I am basically unable to edit anything or see preview windows. Playback is constatly lagging between cuts.

My rigg is:

  • i9 7900X (10 core/20 threads)
  • 64 GB DDR4
  • RTX 2080 Ti
  • 2TB NVMe SSD Samsung Pro
  • WINDOWS 10

And you know what? Just like you have shown you have no problem, I did that for Magix too - shown them I have a problem - no response on my try ever by their team so far.

Here is the video I posted about our issues directly to Magix:

I did also comparison of Premiere on the same machine. I also offered to logs, deep insight into our machine. Nothing comes from that so far. There is also recorded in that video our famous "10 minutes" crash for no reason, when I clicked on timeline and hit spacebar for playback.

Sorry, but I am not alone in this. It should be addressed.

So again: it working for you, good for you. Perfect. Amazing. You're using proxies - when I am using proxies, Vegas is still crashing. I have smoother playback - but it doesn't solve my problem with stability.

One thing on top of that though, based on what information you provided (thank you!) I will invest my time & resources into this and try to build AMD rig similar to yours to see if processor is the case. We are using mainly INTEL processors in our studio. That's probably only big different thing between your PC and mine's.

Nevertheless, my posts are not about whining and shaming. It's more about caring actually and being frustrated that there is total silence about it.

 

 

Kinvermark wrote on 3/28/2019, 9:38 PM

The specs of your machine look very good, but from what I see in your video you are still overloading your system. It caches and runs smoothly until the next edit cut then stutters. If Vegas gets too overloaded it can crash. Not always, but the risk goes up. This shouldn't be the case with proxies, so that I don't understand that (what kind/size of proxies are you using?)

It may be that Magix cannot tell you anything specific right now as they are working on performance improvements that are difficult to implement (speculation on my part). So that means you are going to have to make some tests, and maybe compromise (just a little) with your workflow and expectations.

Some things to try:

1) get rid of the MOV files; try cineform AVI proxies or stick with the gh5 mp4 files

2) Use NTSC 29.97 not double NTSC.

3) See what happens without the gameplay footage (OBS settings?)

4) Are you running in 32 bit mode? DON'T

5) GH5 10 bit?

Start with the lowest spec footage/project that works and then move up until you hit the ceiling and then report back.

FYI, if I make 1080p cineform proxies exported from Resolve, I can get totally fluid playback on my ancient system (see signature). Once the edit is done, I switch out the files to full resolution UHD cineform intermediates and render NO PROBLEM.

It can be done :)

 

 

 

 

 

Kinvermark wrote on 3/28/2019, 9:44 PM

Also, are your systems overclocked?

Lukasz wrote on 3/31/2019, 12:14 PM

 

Fiola, I have identical problems like you. Continuous vegas failures. Everything you showed in the film touches me just like you. I have already sent my files for analysis, I hope that they will solve the problem.

Kinvermark wrote on 3/31/2019, 12:28 PM

@Lukasz

Great that you have filed a support request. But if you want help from other forum members you should start a new thread and post all your relevant details as outlined in the FAQ section.

The likelihood that your problem and Fiola's are "identical" is very small. Proper technical support by vague commentary in a general thread is impossible; perhaps that is why Fiola has been unable to solve his problems after several months. You will notice none of my questions to him have been answered.

Lukasz wrote on 3/31/2019, 12:34 PM

I've already written about it and I have no strength to write it out again. I am waiting for information directly from Magix. These problems are the old problems from previous vegas editions that have not been repaired today.

kinetik wrote on 4/1/2019, 4:01 AM
Playback is constatly lagging between cuts.

 

 

My problem as well for so long on various pc's ..even with 1080/25p mov files from dslr with no effects added(the situation is getting tragic if im trying to edit 4k files even crapy bitrate like 45Mbps). I've sent tickets and tickets and discussed it here on forum but no solution from devs..and finally for those who reply to us who have issues: if you cant provide any help stop telling us that the program is fine and there is something wrong with our rigs etc because everything runs buttery smooth in Premiere and Resolve...if it works ok for you then its fine. Consider that many users have already abandoned Vegas because of these critical issues. We pay for this as well and we want it to be perfectly functional.. do you think we have spare time to spend on this forum?? Magix has to fix these major issues asap.

Intel i7-6800K @4.0GHz
64GB DDR4 @3.00GHz
Nvidia GTX 1070
Samsung SSD 850 pro 2TB
Win7 64bit

joost-berk wrote on 4/1/2019, 7:11 AM

You'll get better results by dropping all .MOV files. In most camera's where you can record MOV with, there is always a .MP4 option as wel. In my opinion this is always the beter choice. Other thing with the lag on some files on what is seen on GH4/5 files is that it is been coded in Long-GOP. I experience something like that when filming on FS7 in XAVC-L. It is more difficult to start decoding a portion of the clip that has been editted. Because the system needs to calculate towards the I-frame. When I use XAVC-I (intra) I don't have any issues at all. So always try to use Intra-codecs or use the proxies within Vegas Pro, because this is the best solution for lagging frames in playback

Vegas Pro user since version 1.2

OS: Windows 10 Pro 1809

CPU: Intel Core i7-7820X

RAM: 32GB

GPU: Nvidia GeForce GTX 1080 8GB GDDR

Monitoring: Black Magic Design DeckLink SDI 4K

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

Quindor wrote on 4/1/2019, 11:49 AM

I'd just like to chime in on the running discussion here but in my experience with Vegas 15 & 16 @Fiola is 100% right.

I too notice very big differences in Vegas Pro speed and bugs editing in 4K. I too encounter the random freezes where at any random moment in time Vegas just halts and hangs. Very sometimes playback will continue but the interface freezes and you have to wait until the end of the timeline for it to unfreeze, sometimes (These occur less often in Vegas 16, not it mostly just hangs completely). Because of these random freezes I've become a very cautious editor, making at least 10 save files per project and saving after even the slightest change just not to lose minutes of work multiple times during a project. The new auto-save feature is workaround for that, but doesn't allow below 5 minutes so still causes me to lose too much time for every random hang.

I also notice a very big difference between 1080p editing and 4k. I can edit a 4K60 project and test render it in 1080p30, works fine then I try to render that exact project in 4K60 and it renders 15x slower and is much more prone to hangs or crashes. Exact same project, exact same files. I still have to tinker with turning on and off GPU acceleration during rendering (options --> preferences --> video). Most of the time I need to turn it off to have it finish a render. Otherwise renders will just stall and the time remaining keeps climbing up while nothing is happening. And yes, my video card (GTX1080) is fine, I can game at 100% for hours no problem or even use GPU transcoding with ffmpeg for hours, also no problem.

In the video settings the Dynamic RAM preview makes a big difference. For some projects I need to set it to 0 to work but other project won't render whatever I try without setting it to at least 1024MB. I have 32GB of memory and Vegas never uses even close to that much. Most often it occupies around 15GB in memory.

Then there are render bugs in 4K where some images will be fine in preview but appear oddly stretched after rendering for 4 hours. And then you have to do it all over again. Or when a simple cross fade between two clips somehow causes them to glitch out and display at the same time after the fade while this certainly isn't the case in the timeline or preview. I've spent literal days changing around settings and exporting formats to just please export my project correctly! Even changing between builds to just get it to work.

Render and especially overlay performance is also a giant problem, just like @Fiola shows. Even doing a simple text overlay means my preview framerate (I always use proxies for everything because my G7 footage is un-editable in 4K otherwise) drops from 60 to 3FPS if that.... Multiple overlays I work with muting timelines because it's impossible to do otherwise.

Also this again is horribly 4K optimized, rendering in 1080p I see up to 80% to 90% on my Ryzen 1700 with 8 cores and GPU NVENC HEVC encoding, great! Switching to 4K drops this to 50% and if text overlays occur it often drops down to 20% total CPU usage during rendering. This is also why 4K encoding doesn't take 4 times as much time but often multiple times of that. :(

So in my experience, most people here who state that they don't have any giant issues are probably still editing in 1080p, in 4K it's a whole different story sadly enough. I keep updating as soon as a new build comes out, some things improve, but the above listed issues haven't for the past 2 years so I too look elsewhere and am editing in different programs. :(