18

In the prerender case I've matched source which is 4K 29.97 fps - render resolution is the same

In the project case it's 1920x1080 29.97 fps, render resolution is the same, but the source files for clips are 4K

Dell Precision 5530, WIndows 10 Pro, 64bit

image is my processor

32GB of ram, solid state drive with 137 GB free

Nvidia Quadro P2000 and Intel UHD Graphics 630

Use a "nested " veg instead of the prerender the same file with the fx in a project that has the same dimensions as your final output.

So are you suggesting- take a source file (let's say 4K), put it in a project with dimensions 1920x1080, add my Denoise, save, and then nest that into my main project which is also 1920x1080?

Nesting pretty much crashes vegas every time I've tried to use it. This was actually the primary reason I upgraded to Vegas Pro from MSP this weekend and the feature doesn't work for me, and now I can't render. I have a note into Magix support but nothing back.

If you take the time after selecting that veg during the time a swap0 file ( kind of proxy) is being build and than add it, with me no problems to use a lot of nested vegs.
With me there is also a problem with the Denois FX because executing freezes my VPro 18 time after time on laptop, but for me no problem because I never use it. With old files of my DV cam I use Neat Video and with my now used camera's I never have to use a denoiser.

Just tried it, 15sec 4k clip, rendered with sony avc to 1920x1080, 18sec with just levels filter, 4mins with denoise set at 0.7 (CPU only).

@andyrpsmith for me just wrapping up about 18s of video with denoise on, it took 1 hour 23 minutes to render. Although mine were 4K and I used Magix Intermediate. That 18s created a 1GB file

What was your source file format? What various settings do you have that might affect rendering (e.g. hardware acceleration, RAM)?

I"ll add - the end result was still quite grainy - I could maybe dial it in better if preview wasn't sooooo slow... I tried Neat trial and was very difficult to use and end results didn't look great either.

My source file is 4K XAVCS 15 sec (from Sony AX700 camcorder). Render Sony AVC internet 1920x1080 mp4 template - bit rate 16,000000 24fps, i5 CPU @4GHz, 32GB ram. The Sony AVC uses CPU only. Give it a try.

Would this be a reasonable high quality format to use for pre rendering and then inserting into another project and rendering again? Or will it degrade quality rendering multiple times. If I don't have to prerender, that would be great, but my project has loads of trouble rendering without effects, and worried once I do color correction and denoise, it won't render at all. Other recommendations have been that the VFR from my source files may be causing the render challenges.

Vfr does cause issues with Vegas, quite a few posts about it. The Sony avc produces an excellent image, the best in my view.

so, I tried the sony acv... and it's got this little glitch in it - take a look... this was done with 0 RAM preview.. (the 4 quadrants were just testing different color correction and the last one with the Neat trial, but needless to say this one work with this weird glitching). SOoo tired of troubleshooting... wished I could just port my project back to MSP :(

Very strange, never had that. is this still with VFR or have you transcoded it to CFR

still with VFR. I'm trying to find out best way to convert to CFR... I've been trying MAGIX intermediate but end file is laggy and slow mo like. I'm looking at FFMPEG scripts from J-N. I do have handbrake but also having speed issues there and unsure about best settings. Any guidance appreciated.

separate note for @j-v - is this a good practice/troubleshooting approach to render complex projects? Nest the project into a new file and render from there? I read that somewhere but because of crashes, never got it to work.

Each render has its loss in quality and more than one takes a lot of time.
By using a nested Vegs there is only one render and thus better handling of a big project and better quality.

I converted my file to CFR and can't render at all with DeNoise. Tried multiple formats, with and without acceleration

@sakendrick,

Denoise is completely useless on my machine even for standard definition files, except for the sharpening part. Since I already have Neat Video and the NewBlueFx plugin, there's no point in using Denoise. Something's not right with the Vegas Denoise, what the h--- is it trying to do?

It is working for me but is very resource intensive and i mean very.

@Robert Johnston - well I guess glad to know I'm not the only one. I have tried Neat and may go that way but was hoping not to sink more money into this. Basically trying to fix some high action videos shot on cell phone (Galaxy S20, rear camera, 4K), that unfortunately kind of look poor quality. Not sure why.

How much is Neat? Glad you have a reasonable solution.

$75 for a "consumer" version, which I think is limited to 1920x1080 output and single gpu. $130 for a pro version for multi gpu and higher res. I went with consumer for now. So far on tests No issue rendering, but haven't done a full project yet. Seems to do a good job removing noise and not destroying the integrity of the image. UI isn't the most intuitive but so far I've just be using the defaults, and pushing back a little sharpness.

Seems like Magix needs to do work on this feature.

@sakendrick - And in the meantime we’d need to get our Videos clean. I’ve plumped for NEAT Video and moved on. NV has just so many cool new features that it’s obvious that here there’s a Company, NV, that focuses solely wants/wishes to do better for its User Base and THAT right there is precious. Making a decision to pursue this route, is my preferred way. Along with other 3rd Party plugs - MOCHA Pro, Particle Illusion, TWIXTOR, Magic Bullet Looks - I’ve let/allowed VegasPro to do its thing and know it’s just stable and effective.