Hi, everything is running off of SSD's. When I look at the settings, there does not seem to be much to change.

Good point, I will try to edit using another NLE and see if that mitigates the issue. If my computer and hardware is too slow then no settings will help.

Okay, I don't know if I'd start there as that's even more variables but you can do that.

If you have SSDs and 32GB of ram your system probably meets minimum requirements for Vegas?

If you do decide you want to troubleshoot, try to include information about your hardware and answers to the above questions. In general, the biggest variable is the media and some (esp. heavily compressed and variable frame rate) causes Vegas trouble.

Hi, I just fired up another NLE and editing is MUCH better. No stuttering, black outs, grey outs, or crashes. I sent a support ticket Magix/Vegas but it takes a few days for them to get back to me. Maybe for another project I will try Vegas again. Maybe the settings need to be played with, I don't know. I don't want to say anything disparaging against Vegas. I thought I met minimum requirements, maybe I don't. I figure 720 p should be cool, I guess not. Anyway, I found a program that works. So it is only two nights of work lost, I've had worse.

Yes, it is.

But many people understand this DynamicRAM in the wrong direction entirely.

D-RAM is a temporary cache for CPU's recompression of dealing part of an event, say 2-5 seconds.

For instance, you put an FX-plugin onto an event and the GPU doesn't know how to follow, then you press:

Shift+B

This command lets CPU undertake the task (how does the FX looks like on the event). If your cache were big enough, you can see the whole event added with the FX after CPU calculated.

Disadvantage: The reserved RAM is isolated from the system and serves only Vegas pro.

And you must hit Shift+B every time.

your case could be a very poor graphic card or very strenge codec, because 720p resolution is really nothing.

Oh yes, you can make your footage to 1080p. Just set your project to 1920x1080 and that's it.

@Yelandkeil Vegas Pro really struggles on my system, but other NLE's tend to fare better. This is not always the case, I have had some positive experiences with Vegas in the past. I used Vegas Pro (subscription) for a month on a prior project and it flew. This project, not so much. Good point about the FX, if I was applying any, the program/project would fall apart! Others tell me that it is probably a settings issue. If the codec was bad, it would not work at all. The fact that another NLE works suggest some setting needs to be toggled. Magix/Vegas has the report so maybe a technician will be able to look into it. It was really fun editing in Vegas that one month, so I will not say Vegas sucks. But I will say it certainly helps to use more than one NLE!

You've given zero information about your system, media or settings, so at this point it's all speculation.
Who are these other people and where did you find them?

I see in the past you used VP 16- it had trouble with DJI, GoPro, and smartphone files, going as far as "blacklisting" them from the hardware decoder. The codec can be fine but still not work well in NLEs.

Things are much improved since then but we don't know what media or version of Vegas you are using and there are still issues with some combinations.

If you want to do simple things that might help with unexpected issues, I'd reset Vegas (control + shift on startup) and then if you have a GPU use the NVIDIA Studio Driver or AMD Pro driver and not the gaming ones.

I happily edit 4K files with LUTs, noise reduction, etc. on a laptop so it's certainly capable of that.

@RogerS My question was how to enlarge the preview buffer, @Yelandkeil answered that. As for whether my system can or cannot handle the program, I will leave that to the developers I sent the ticket to. Past pleasant experience with Vegas Pro 18 subscription (one month) and the other functional NLE suggests my system does meet minimum requirements. I am testing a recent build of Vegas 18 and see it is not something I can complete a project with. I could go to Vegas 16 (good idea, actually) which I do have, maybe it will perform better. Yes, I do use studio drivers and update my systems, etc.. etc.. That said, I will try Vegas 16, sometimes the older programs have the bugs already worked out and they tend to be more stable.

Seems like your mind is made up, and I respect that, but if you would like peer support with troubleshooting your issue, you may begin the path here.

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

While you're investigating, use Vegas Proxy and your problems may go away. Right click on your media In Project Media, and "Build Video Proxy."

@Former user, if your subscription still doesn't expire and you will try a little bit more,

1, change the frame rate to 59.94 or 60 as your footage is 60fps

2, disable resample (which takes plenty edit resources away)

3, confirm that your footage has Variable Frame Rate (which also occur difficulty by decoding )

4, check whether your graphic card support HEVC/AVC (if not, all the minimus requirements etc. are only bullshit)

5, simple way to check how strong your PC is, just give 3 credit rolls parallel and see if it can run.

@Yelandkeil I might have found the culprit, according to Vegas the manual, it suggests in case of performance issues, to go to 'options' , then 'preferences', then uncheck 'optimize GPU display performance'. The program seems to be much smoother now. I will continue with edits, but this may be the culprit. I was able to edit full-on 1080p for a more complex project and Vegas flew. Something to do with the display/graphics I guess, but I do update all drivers. Thanks, I will look into those other tests you mention.

Am still having trouble with no preview for Vegas 18 and I reached out to Vegas support and I got an email response that is supposed to give me 'yes' or 'no' options, but none exist. Support says they are backlogged, so it will be a while yet. I tried out Vegas 16 and it works MUCH better than 18. It's a shame. I have to go back and re-do the project. For those who want to upgrade Vegas, you may want to think twice.Is there a way I can pull a project out of 18 and drop it into 16 because 18 has a lot of problems and tech support is not that responsive.

I make a Selection and then I use SHIFT+B to use the amount of RAM I’ve set. Are you doing this?

@Grazie Yes, for 18, I just tried and now the program turned white and I get audio playback only. It's kind of cool in a way.

I shut the program down (end task), restarted, then 'select all', then 'copy', then pasted in 16, that might save a few hours.

If you want a potential solution then provide more information about your Rig, your Project Settings, the Media you’re using and any FXs you’re employing.

If you don’t, then we are sucking Air.

If you want a potential solution then provide more information about your Rig, your Project Settings, the Media you’re using and any FXs you’re employing.

If you don’t, then we are sucking Air.

He has been asked this several times, but he loves the question and answer game and always finds someone who gets involved.
The worst thing is that the game starts again in his next thread, because he doesn't write his data in his signature.

Bingo. He only wants to share details with Magix support yet is not satisfied with the responses and comes back here to ask for more help with no additional information. Quite impossible to say anything meaningful without info.

It is a pity about the beautiful time.
Let's get back to doing something meaningful:
jogging,
playing with the children or grandchildren,
cutting video
playing with the wife or girlfriend....
and so on.

Is there a way I can pull a project out of 18 and drop it into 16

Yes. Ctrl-A (copy all) on the timeline in VP18, then Ctrl-C (copy), and then Ctrl-V (paste) into VP16. With one rare historical exception back in Sony days, veg files are not backwards compatible.

The trouble with the copy/paste approach from my experience is that not all the tracks align after pasting. My solution to this has been to add an equal length media generator 'black' event to the head of each video track in VP18, and an equal length audio event (unimportant what that audio track is) to the head of each audio track in VP18, before copying. This way. the relative positioning of all the video and audio is retained throughout the project. The 'track headers' can then be deleted once the copy/paste has been done.

Other considerations:

• any FX used in VP18 at event level also need to be available in the earlier VP version; and
• any FX at track or project level need to be set again in the earlier VP version.