vegas does not work with nvidia

Kinvermark wrote on 4/30/2019, 5:25 PM

SHIFT-B

valte799 wrote on 4/30/2019, 5:29 PM

SHIFT-B

ops thank you, yeah i knew it

j-v wrote on 4/30/2019, 5:38 PM

That all has nothing to do with rendering, but with previewing.
The GPU settings you mentioned are in Options/Preferences/ Video and help to accelerate the preview for some effects. Nothing more and it has nothing to do with rendering files.
If you have a problem with previewing your edits you can higher the Dyn. Ram Preview to more than o, but this is only intended for previewing very small selections you have to make first. Nothing more or less.
Rendering is set in the rendersettings per codec and you don't have to see what is happening than because when started you're not able to influence that proces anymore.

Kinvermark wrote on 4/30/2019, 5:41 PM

since i always had problems with vegas carshes and laggy previews

Solving that should be the first priority. Check FAQ section for required information to post and troubleshooting guides.

Not sure why your ram preview isn't running. It does sometimes do this depending on how the events/timeline is selected - but I can't reproduce that right now.

FWIW, I no longer use RAM previews as I consider that function a legacy element that is not 100% accurate, and you can waste a lot of editing time re-rendering this temporary preview. Better to do a SHIFT-M rendered preview or even a render-replace if you are finished with that part of the timeline.

Eagle Six wrote on 4/30/2019, 5:44 PM

Isn't it Shift+M?

Kinvermark wrote on 4/30/2019, 6:01 PM

Yes. :) I guess the minus sign is a tad confusing. Though I am not sure how to "un" press a key.

Eagle Six wrote on 4/30/2019, 6:08 PM

Though I am not sure how to "un" press a key.

If someone can figure that out, we could have a whole new slew of keyboard shortcuts, that might be interesting!

Eagle Six wrote on 4/30/2019, 6:49 PM

@valte799 are you by chance working with 4K or UHD source media? Even if you are working with FHD source do you create proxies and if so is your play still lagging?

What amount of RAM are you dedicating to Dynamic RAM Preview max, out of how much RAM is available?

When I select an area to perform Build Dynamic Ram Preview, if the Dynamic RAM Preview max is too low, it will not do anything because it doesn't have enough RAM to work with, could this be your problem?

BTW: I agree with @Kinvermark, I prefer Selectively Prerender Video (Shift+M).

valte799 wrote on 5/1/2019, 9:11 AM

thank you all but i have already tried to play also with "internal" settings but apparently i have not find the right switch that can solve my laggy previews.

That all has nothing to do with rendering, but with previewing.
The GPU settings you mentioned are in Options/Preferences/ Video and help to accelerate the preview for some effects. Nothing more and it has nothing to do with rendering files.
If you have a problem with previewing your edits you can higher the Dyn. Ram Preview to more than o, but this is only intended for previewing very small selections you have to make first. Nothing more or less.
Rendering is set in the rendersettings per codec and you don't have to see what is happening than because when started you're not able to influence that proces anymore.

yeah i think i have not express myself right. i have no problem with the final render other than a general slowness. my problems are during editing. lets assume that i have a clip wich require a simple s_shake effect at a specific time, so i apply the shake on the clip and then i keyframe it to be right at the time i want. then to be able to see the results of that i must select a loop region wich contain my edited clip and press shift+b and then watch it. i know that the more dyn ram you set, the more long you can make your loop region, but my problem is that the overall time to edit a clip and find the right amount of effects for that clip is very long due to the fact that every time i make an adjustement of the effects (s_shake amplitude for example) i have to re-select the loop region and press shift+b to watch again what i'm doing. This take away a lot of time, specially when i work on bcc effects wich required a lot of time to dyn ram even when the preview is set to "preview(auto)". so i was trying to speed up this process by using the graphic card, but when i choose nvidia graphic card in "gpu acceleration of video processing" and press shift+b nothing happens, the dyn ram preview does not even start, but if i press play without a loop region the preview play normally, i mean, it is gonna play with a lot of frames lag but that is due to the fact that i wasn't able to do a dyn ram loop region first.

valte799 wrote on 5/1/2019, 9:19 AM

@valte799 are you by chance working with 4K or UHD source media? Even if you are working with FHD source do you create proxies and if so is your play still lagging?

What amount of RAM are you dedicating to Dynamic RAM Preview max, out of how much RAM is available?

When I select an area to perform Build Dynamic Ram Preview, if the Dynamic RAM Preview max is too low, it will not do anything because it doesn't have enough RAM to work with, could this be your problem?

BTW: I agree with @Kinvermark, I prefer Selectively Prerender Video (Shift+M).

i'm using mp4 1920x1080 videos in 50fps. the total ram of my pc is 16gb and for dyn ram loop region i'm using like 2 or 3 giga, it depens on how long my dyn ram region will be. yeah i create proxies for hd videos.

Kinvermark wrote on 5/1/2019, 9:19 AM

OK, so back to why your RAM preview doesn't work. You are going to have to post all the relevent details about your system, project settings, and media. See FAQ for what info to post.

1) Is it all effects / all media types / all projects?

2) Anyone else with NVIDIA card having this problem? (I am on AMD so can't test).

Kinvermark wrote on 5/1/2019, 9:23 AM

When I select an area to perform Build Dynamic Ram Preview, if the Dynamic RAM Preview max is too low, it will not do anything because it doesn't have enough RAM to work with, could this be your problem?

Doesn't work this way for me - just renders as much of the loop region as it can before it runs out of RAM, then starts playing.

Kinvermark wrote on 5/1/2019, 9:25 AM

@valte799

Can you try something simple: Restart Vegas. Then start a new project. Drag a couple of files to the timeline (don't do anything to them), make a loop region, then hit SHIFT+B. What happens?

j-v wrote on 5/1/2019, 9:26 AM

lets assume that i have a clip wich require a simple s_shake effect at a specific time, so i apply the shake on the clip and then i keyframe it to be right at the time i want.

This looks to me a very difficult way to apply an effect.
I think you better make cuts on the timeline ( which gives you a new "event") and if you want a little more space to manipulate the effect make the cuts a littler bit wider. Than apply only the effect to that new event.
The playback of the whole original clip will not be destroyed, but this makes all much easier also to preview.
This is one of the basic principles for editing( in Vegas at least).

rraud wrote on 5/1/2019, 9:29 AM

BTW, Dynamic RAM preview will be grayed out (or Shift>B will not function) if it is set to zero... or... the preview window is closed,

Eagle Six wrote on 5/1/2019, 9:35 AM

Doesn't work this way for me - just renders as much of the loop region as it can before it runs out of RAM, then starts playing.

@Kinvermark UHD source media/project, if Dynamic RAM Preview max is set at the default 200, and I mark a section to Build Dynamic RAM Preview, Shift+B, it will simply do nothing. If I bump up the RAM, it works as it should.

valte799 wrote on 5/1/2019, 9:41 AM

i can't do that. im making a video where music and clips are in sync. so when there is a bass drum for example, i apply s_shake and make it happen exactly on the drum and then the effects sofftly goes away because i put another keyframe and set "0" amplitude at the end of the clip.Every clip last like 1 or 2 seconds so i have to work in very tight spaces if i want to do that on a different event i can ctrl+c my event and put one above the other and apply the effcts on the one above that then is going to fast fade, but that also is not very functional. i use vegas since 2013 but i think i lack knowledge on the basics rules to work efficiently.

valte799 wrote on 5/1/2019, 9:43 AM

@valte799

Can you try something simple: Restart Vegas. Then start a new project. Drag a couple of files to the timeline (don't do anything to them), make a loop region, then hit SHIFT+B. What happens?

i've just tried that and yeah, dyn ram works in the new project without any effects but still nothing in the real project file with all the effects.

john_dennis wrote on 5/1/2019, 9:47 AM

If you're into math, you might want to divide 200 MB by the uncompressed bit rate for your preview pixel dimensions. I think you'll find it's not very long. Neither is 8GB.

Eagle Six wrote on 5/1/2019, 9:48 AM

@valte799 for a test, bump up your Dynamic RAM setting to 1-2gb at a time and see what results you have.

Kinvermark wrote on 5/1/2019, 9:53 AM

@valte799

I suspect the Boris effect may be incompatible. Anyway, you now have a basis for diagnosis: build up a timeline step by step until it "breaks."

valte799 wrote on 5/1/2019, 9:56 AM

@valte799 for a test, bump up your Dynamic RAM setting to 1-2gb at a time and see what results you have.

i always keep it at least at 1gb, otherwise the loop region would last like 10 seconds max. if you increase that number vegas is just gonna allow you a longer loop region, once you find the enough amount of mb for your video than is ok. anyway i have tried to set it to 4 gb but still nothing.

valte799 wrote on 5/1/2019, 10:21 AM

just found a solution that worked for me ---> run vegas in compatibility mode for windows 8, since is the latest one available, even if i have windows 10. now dyn ram works fine... mysterious things...

Kinvermark wrote on 5/1/2019, 1:33 PM

Great! You found a "hack." But you are no wiser as to the actual cause. If it was me, I would take the extra time to find out precisely which component causes the issue.