@Richvideo -

I would be curious to see what numbers you get with the quality mode set to high (temporal and spatial) and radius set to 3 or 4

Wow! Used NV at your suggested settings, plus TWIXTOR I got 25fps on a 60fps. Not too shabby, methinks. Used the NVENC Speed demon template.

That is great

It is much faster than I get with the 2080 Super GPU

@3POINT Well that's completely opposite to the posts you were just making about rendering speed and claims that Vegas doesn't do hardware decoding (it does.)

Personally I'd much rather have a high quality CPU render for the final file as GPU encoding quality just isn't there yet and that's not a NLE issue.

Than you probably didn't read all my posts here is this thread. I always said that I care about quality and not about speed. When I just would care about speed I would use only my other NLE who does it 3 times faster as Vegas.

 

Sorry, I'm not that interested how to speed up rendering times or in rendering speed tests at all. First because rendering is just a very small part of the whole video editing process and spending a few minutes more or less on that hours taken process, I don't care.

@3POINT Ah righto. So I’m now understanding your depth of dislike about this thread. You have very high standards, nothing wrong with that. And definitely no need to apologise with your “sorry”, I’m now understanding even further your comment about me knowing about rendering. We are fortunate to have your expertise on this Forum. I’m always willing to learn from you.

Grazie, it's not dislike. It just that my priority is not the speed of render but it's quality.

Ah, yah see I want SPEEDY Renders for viewing - I'm all about the Narative. HOS can give a neat way of doing this. Oh quality at the end. My cameras arent your spec, so I kinda live with the best I can achieve.

I see, your cameras are FHD. For FHD you probably will not see a difference between a speedy GPU render or slower CPU render. My cameras are UHD and a down scale FHD renders gives a big difference in quality between a fast GPU render and a slower CPU render. The last gives a FHD quality that I hardly can distinguish from the original UHD on my UHDTV.

@3POINT - Initial timing testing shows the CPU knocks 20 seconds of the GPU Nvenc:

XDCAM EX HQ 1920x1080-60i, 35 Mbps Render(s) CPU 18 Seconds

Internet HD 1080p 59.94 fps (NVENC) GPU 38 Seconds

You've given me a Focussed appreciation of these variables. This PC is a speed Demon and I'll be using the abilities within S/W that can utilise it - so far meaning Neat Video and Rotoscoping MOCHAPRO.

Again, @3POINT, thanks for your valued input. Now, where can I purchase a UHD Cammie ☺️ ?

For Previewing GPU is solid throughout. However without GPU acceleration the FPS does flicker a bit and not flowy. So, GPU acceleration for Previewing - and yes, all set to BEST.

I'm just a journey and grand kids videographer and love for that purpose my DJI Osmo Pocket in 4k50 recordmodus. The downscaling to FHD looks awesome and far better than FHD direct recordings with my FHD cameras, see signature.

The new DJI Osmo Pocket 2 is a nice affordable camera to start your UHD adventure. You save also a lot of time and quality in post because no need for Mercalli or Vegas stabilizing anymore.

+1 @3POINT  ... I have a GoPro Hero 8 Black (which is much better than the 5) and record in 4K but finalise in HD (BD). There's little need for stabilisation, and even the minimum wide angle option removes the need to carry the wide angle add-on lens for the Sony AX100 which, depending on the sun's orientation, can add unwanted reflections between it and the native lens. The absolute worst camera for recording IMO is a smart phone - Samsung in my case. The sensor chip is just too small. The best choice for me is 2.7, but the lack of a 25 fps option makes it even worse. Stabilisation via Mercalli 4 SAL or Mocha Pro stab is mostly disappointing. Different parts of the frame 'wobble' at a different rate than other parts. In Mocha Pro, I can select a specific and large-ish area of the image to stabilise - which works - but the rest of the image becomes a bit jelly-like. As convenient as it may be, a smartphone's camera is for me a last resort.

I also have a Gopro 7 black but recorded always in 2k7 due to it lower wide angle and less distortion. The Gopro is nice for heavy action and bad weather. For my purpose the Osmo Pocket is ideal. No need anymore for stabilizing or horizontal leveling. The only disadvantage is the small display.

So, where do I put my Follow Focus and Matt box? And my Mic inputs?

Do you mean at the Osmo Pocket? The Osmo has an active tracking subject mode and focus follows that subject if set to AFC.

An external microphone can be connected by an optional USB-C adapter. Osmo Pocket 2 has also an optional wireless microphone.

Do not expect XLR inputs. The Osmo is just a little larger than a XLR plug.

Throw as Focus Puller 😆. No XLRs? Deal breaker.

Have you ever seen an affordable camera (with 4k and gimbal) for less than 500 euro with XLR inputs?

Good point. I didn’t think of that.

Let's talk about speed again. Did you render the Red Car test project (redcar16.veg)? What timings did you get with your MONSTA with GTX3080?

I got 17 sec with NV (bitrate11,1 Mbps, size 88Mb), 15 sec with QSV (bitrate11,1 Mbps, size 88Mb) and 22 sec with Voukoder (3,1 Mbps, size 25Mb).

I posted this on the other thread:

Full Project.

XDCAM EX HQ 1920x1080-60i, 35 Mbps Render = 18 seconds

I got 17 sec with NV (bitrate11,1 Mbps, size 88Mb), 15 sec with QSV (bitrate11,1 Mbps, size 88Mb) and 22 sec with Voukoder (3,1 Mbps, size 25Mb).

@3POINT - I gotta be doing something wrong? Can you breakdown your Templates above?

Cheers - G

Ah, I was following the Press Release Template using XDCAM. I think I've now translated correctly your fast timings for NV (NVENC yes) CBR 11,1 and got an almost similar 16 seconds - is that about right?

Here's my settings:

@3POINT - et al and just for Fun I did the MagicYUVA 4444 and got 10 seconds HUGE file!

I posted this on the other thread:

Full Project.

XDCAM EX HQ 1920x1080-60i, 35 Mbps Render = 18 seconds

😱 Why, the Red Car project is 1080p30. XDCAM rendering doesn't take advantage of your GPU. Magix AVC NVENC does:

My PC has also the QSV option, which is even slightly faster than the NVENC option. I compared those renders with Voukoder (crf 23) CPU only render (my favorite) is the slowest but gives higher or equal quality at lower bitrates and smaller filesizes.

Why, the Red Car project is 1080p30. XDCAM rendering doesn't take advantage of your GPU.

@3POINT - I followed the Press Release Template - ugh . . I asked you to breakdown your NVENC so I could understand. I think I now got it correct, almost the same as yours. See above?