Yes. That's pretty much the same input video. Except your files are Intra. That case is good. The problem I have is when you're using the mp42/avcl mainly.

So... I was wondering, if some of you has the similar experience to me. I am now completing several projects with 4K60fps presets, few video & audio tracks, no effects in the fx. Just pure footage.

With proxy files encoded the editing seems to be better - unfortunately the VEGAS keeps crashing all the time during editing. So basically proxy is useless for me, same as the VEGAS 15 for 4K editing.

What I am editing (on my rig mentioned in the first post) is pretty much basic video files which are encoded by Panasonic GH5:

Width                       : 3 840 pixels
Height                      : 2 160 pixels
Display aspect ratio        : 16:9
Frame rate mode             : Constant
Frame rate                  : 59.940 (60000/1001) FPS

So your use GH5 files, UHD 60p what is 8bit 420 recorded by the GH5?

If yes - I have also seen some freezes with UHD 50p 8bit 420 files from the GH5, where the GPU utilization goes up to 100% and stays there during Playback. Even if you stop the Playback it takes some time for the 100% GPU utilization to come down again - or Vegas crashes.

Seems to be still in work by the development team. Hopefully they can fix it.

So... I was wondering, if some of you has the similar experience to me. I am now completing several projects with 4K60fps presets, few video & audio tracks, no effects in the fx. Just pure footage.

With proxy files encoded the editing seems to be better - unfortunately the VEGAS keeps crashing all the time during editing. So basically proxy is useless for me, same as the VEGAS 15 for 4K editing.

What I am editing (on my rig mentioned in the first post) is pretty much basic video files which are encoded by Panasonic GH5:

Width                       : 3 840 pixels
Height                      : 2 160 pixels
Display aspect ratio        : 16:9
Frame rate mode             : Constant
Frame rate                  : 59.940 (60000/1001) FPS

So your use GH5 files, UHD 60p what is 8bit 420 recorded by the GH5?

If yes - I have also seen some freezes with UHD 50p 8bit 420 files from the GH5, where the GPU utilization goes up to 100% and stays there during Playback. Even if you stop the Playback it takes some time for the 100% GPU utilization to come down again - or Vegas crashes.

Seems to be still in work by the development team. Hopefully they can fix it.

They are working on it for half of the year... it's too long to just fix the issues. They probably CAN'T fix it...

Yes, Vegas Pro 15 is horrible right now. Where is Update 3?

They are working on it for half of the year... it's too long to just fix the issues. They probably CAN'T fix it...

No I do not agree here. But I canot say more at the moment.

They are working on it for half of the year... it's too long to just fix the issues. They probably CAN'T fix it...

No I do not agree here. But I canot say more at the moment.

I am really sorry If I am being rude right now here, but why not? Why not?

I am really sorry If I am being rude right now here, but why not? Why not?

Do you also have an answer to my question or a comment on the video playing and rendering the files?

I have not. I am sorry, your footage looks like i would imagine it should work, but it just isnt working for me right now - in fact, it's not working even on other PC's we have in the studio. What is your configuration of the rig you are using, please?

They are working on it for half of the year... it's too long to just fix the issues. They probably CAN'T fix it...

No I do not agree here. But I canot say more at the moment.

I am really sorry If I am being rude right now here, but why not? Why not?

He's probably a secret beta tester, indicating they've fixed some things. The new version is supposed to have a February release.

There are no "secrets" if somebody is a beta tester, neither in my opinion nor in the NDA that ever beta tester has to sign. It is up to every tester to say that in the public or not.

But you are not allowed to publish any informations about upcoming builds, as that is forebidden in the NDA. So I do not indicate anything. But since the Software is a human made product, why should it be impossible to improve the product again by humans? That is what I say.

There are no "secrets" if somebody is a beta tester, neither in my opinion nor in the NDA that ever beta tester has to sign. It is up to every tester to say that in the public or not.

But you are not allowed to publish any informations about upcoming builds, as that is forebidden in the NDA. So I do not indicate anything. But since the Software is a human made product, why should it be impossible to improve the product again by humans? That is what I say.

 

Thank you! I completely agree with you! But from my side it looks that Magix is just so silent. No words about when and what they are doing. I was seeing the information about new Vegas 16 and Vegas 365, but after update 2, which unfortunately didn't solve any problem during editing and rendering, i just can't keep motivation like that. The Vegas 14 is not working with NVENC and Vegas 15 has problems now too. I just want to know, if they address this issue.

I am also concerned how it is possible, that Cornico here can preview and render 4K video without any problem. We have different PC's in our studio and neither one of these can preview used 4K footage. Using proxies we were able to get preview, but what's the point of them when Vegas keeps crashing during playback preview or even render.
 

Is there a way how to sign up for beta version too? I think I can provide valuable data from our rigs.

I noticed that after some time not only Vegas' interface slows down but any new window in Windows opening very slow. Seems Vegas don't close all windows inside it (Pan/crop, event fx etc) but just hide them and after some time Windows goes crazy. When I'll have free time I try to not edit but just open and close different windows at different events to check my theory...

Thank you! I completely agree with you! But from my side it looks that Magix is just so silent. No words about when and what they are doing. I was seeing the information about new Vegas 16 and Vegas 365, but after update 2, which unfortunately didn't solve any problem during editing and rendering, i just can't keep motivation like that. The Vegas 14 is not working with NVENC and Vegas 15 has problems now too. I just want to know, if they address this issue.

It is up to Magix when and how they communicate. And since Gary is very active also in this Forum I do not think that they are silent overall.

Vegas 16? We are still with Vegas 15, and the new licensing model Vegas 365 is based on Vegas 15 too.

Sorry again that I cannot say anything about if they address this issue - NDA.

I am also concerned how it is possible, that Cornico here can preview and render 4K video without any problem. We have different PC's in our studio and neither one of these can preview used 4K footage. Using proxies we were able to get preview, but what's the point of them when Vegas keeps crashing during playback preview or even render.
 

I have seen in the small Video that Cornico has set the preview to auto. Well, then UHD 50p footage runs (he uses public available GH5 test footage as one can see here). On my system I see I have also no issue to run one GH5 50p footage with such settings. The differences may exist in the details: another processor, another GPU, other drivers, other Settings of allocation to the dynamic ram preview and so on.

Is there a way how to sign up for beta version too? I think I can provide valuable data from our rigs.

All what you could do is to contact Magix about that question.

I noticed that after some time not only Vegas' interface slows down but any new window in Windows opening very slow. Seems Vegas don't close all windows inside it (Pan/crop, event fx etc) but just hide them and after some time Windows goes crazy. When I'll have free time I try to not edit but just open and close different windows at different events to check my theory...

Maybe you try also my theory that almost 90% from all the troubles I read on this forum are due to the fact that people use Windows with a user account i.s.o administrator or boss of your hardware.
That's the reason that Windows does not close windows or task because it waits for the permission to close or end. But that permission never comes.

So use the admin Windows account, start all programs as admin en sometimes in comptability mode and delete Windows defender. This is the way I'm the boss of all my hardware and can manage the things how I want them to play, behave and render.😉 😇

Man you're GENIUS!!! I always in admin account but started VEGAS with admin rules and at least seems UNDO/REDO start work like a charm and not holding Vegas for 10 seconds like before. But problem with slow opening windows is still there((((((( And drag-n-drop doesn't work in this case.

@Pashi

Be careful if you launch vegas 15 as administrator, if you do that, for some weird reason your countour shuttlepro V2 (that is if you happen to use/own that sort of handy video controller) does not recognize vegas any more. This is confirmed by other forum members, see my post:

http://www.vegascreativesoftware.info/us/forum/bug-shuttleprov2-fails-to-recognize-if-vp15-launched-as-administrator--110205/

Actually, I am almost sure that launching the Vegas 15 as administrator is not the right solution. I have the Super-Admin rights. There is no need to do that. I tried Vegas 15 and except less windows glitching when opening/closing, is the result the game.

Fiola, I am so glad I found your post. I wonder if you ever found a solution? I have a 2080, 64gb i7 rig and have had the same symptoms you describe in Vegas across versions 14/15/16/17/18 and they have been getting WORSE not better. The NVENC / NVidia support is terrible and I have EXACTLY the same symptoms. I work in 4k with large projects and my love of the Vegas workflow has probably been extremely damaging to my mental health - hundreds of hours lost due to these issues.

As for thread necromancy - Over the 4 years of trying to solve this I have raised tickets / reached out / posted specs etc. all just to face the "well it works OK to me", but I am finally realising the truth; Vegas has more "fix the crashes videos" and google searches than any other video editing programme, and the most sluggish performance. In what world should I have to disable GPU support, disable plugins and readers and fall back on processor tech, or be told - you should buy an ATi card.

So Fiola - three generations of the software later, the same problems exist across "undo's", and particularly 4k footage from GoPros / GH5 without transcoding, I've spent hundreds in hardware upgrades to fix this problem only to realise I have a powerhouse for video editing in all software that I despise the workflow for, and for Vegas - as a musician and videographer and software I have used since Acid - shambling corpse level performance from the workflow I love that as so frustrating as it was inspired.

I know this will get jumped on by the forum residents - but after paying full price for V17 / 452, and trying V18 demo I can say it's still the same. Did you ever find a solution @Fiola? Happy to do the "paste your specs / works on my machine / why are you not using proxies / intermediates / 640p footage / contact Magix" but we all know there is something rotten at the core of how Vegas works with high end NVidia cards with complex projects and high end hardware - and no, studio drivers don't fix it either. If I work at 1080p and keep my compositions to less than 12 minutes it's fine. But that's unacceptable.

Sorry for the post exposition - but I'm a month behind my current video due to constant crashes / hangs.

Hi! I actually resolved the issue where I have almost no crashes lately. We still have issues. But VEGAS 18 is by far the best with stability.

This works for VEGAS 17 too - when you are in the VEGAS, just hold SHIFT and click on Options. Still holding shift - go into Preferences, you will see the "internal" tab. In VEGAS 18 is the same, but you don't need to go into preferences, you will see just the INTERNAL item in options context menu.

There you will find: "Enable OpenCL/GL Interop" and set its value to "FALSE". Then - in VEGAS 17 - you need to set to FALSE also the Hardware Decoder for So4 Compound Reader AVC/ ... Reset the vegas. And you are in very stable enviro even for 4K60 editing.

In VEGAS 18 the last step is little different. You will go into Preferences and then in File I/O you will select Enable legacy AVC decoding. Boom done. No more crashes.

From our internal tracking, when we opened VEGAS in Visual Studio Debugger, we have found the crash always leads to Unmanaged exception regarding NVIDIA/OpenCL thing. So that's why probably this option helps. Especially the OpenCL/GL Interop disabling makes everything so fast and snappy that I am curious, why is it even enabled.

Hope you will have less problems as us using this fix. :)

Hi Fiola - there is hope then! Thank you so much for coming back to say you managed to sort it!

Glad you got it sorted thus far. I could not get 17 to be stable with these settings previously, so I'm trying again with V18 pro from now. I have a question just before - "the last step" part - in V18, the wording is different for the So4 Compound reader - this is what I've got where (Name, Value, V18 Default) in the internal settings at the moment!

Blacklist Mode for So4 Compound Reader - 2 - 2

Hardware Decoder for So4 Compound Reader - 1 - 1

Use So4 Audio Reader for Intermediate/HEVC - TRUE - TRUE

I found the Legacy decoding option in File I/O multiplied loading times perhaps by 4-5 times, but worth it if I can make it rock solid. How stable do you find V18 now btw? Will apply and report back. Oh and I also found the NVidia Game Overlay needs to be disabled as it seems to cause issues with V18 too.

You will not change anything to SO4 in Internal for VEGAS 18. Just leave it to 2/1 as you showed.

Use only Legacy decoding.

Before these tweaks, the VEGAS was crashing all the time. Like at least each 2 minutes of editing. With this. I have very rare crash... like almost no crashes whatsoever.

Yeah, this is the crash frequency I have, unfortunately - with AVC legacy on it knocks off NVidia hardware decoder and the project takes an hour to load. Any new smaller projects (sub 20 min duration, perhaps sub 100 clips) are absolutely fine, but my workflow is usually long timelapses etc which I find the live split / ripple editing in Vegas a killer feature for! I guess I'll try these settings on a new composition if I can hobble to the end of this episode! Thanks so much for weighing in, you've given me hope there are others persevering. Kind of horrifying that I can "dumbly load AFX" and do an 8k render scrubbing the timeline at 30fps, and I'm walking on eggshells here, wondering if my next delete / undo will kill it.

Disabling hardware acceleration for the decoding should not be the solution in 2020. But I guess Vegas is such an underdog, I continue to love it. Even if it is like a dysfunctional relationship to work with the backend / settings.

 

There you will find: "Enable OpenCL/GL Interop" and set its value to "FALSE". Then - in VEGAS 17 - you need to set to FALSE also the Hardware Decoder for So4 Compound Reader AVC/ ... Reset the vegas. And you are in very stable enviro even for 4K60 editing.

@Fiola what are the negatives if any with turning both of those off?

Do some codecs/formats require So4 and turning it off reduces compatibility?

Is not using So4 slower with timeline performance in certain instances as this user suggest?

"When So4 is in effect, I can scrub the timeline as fast as I can with a media player."

Well update based on Fiola's post above. If use legacy AVC I go from 60fps preview to 5fps preview, and loading goes from 15 seconds to nearly an hour. Editing is however stable though - with approx only 1 crash an hour - compared to a crash every 5 minutes.

I notice that GPU mem usage is zero with legacy AVC on, and is 6 of 8gb with it off. The workaround can SURELY not be to NOT use an originally £500+ GPU?

@Fiola are you using a deprecated "use legacy GPU support" or similar option in V18 to boost the preview FPS? I know high end i7 will not compete with an i9, but I wonder if you *are* somehow still utilising your GPU?