Hi All,
I realize it is dependent on the particular card but I was wondering if anyone could tell me what kind of speed increase they are getting with hardware acceleration vs CPU only for proxy generation? Thanks!
It only uses the CPU (I assume you are talking about proxies and not selective prerender?)
This is the problem I see with proxys, specially in old computers. If I am not mistaken, vegas generate a mpeg2 via CPU, so the proxy takes more time than GPU render, and in an old computer or a laptop this could be huge. An later, when you play the proxy in the timeline, this format doesn't look to use the GPU to play, so it consumes more CPU that a format accelerated via hardware. It works but this implementation could make even better.
The proxy idea is cool, just an option to select some formats in the proxy would be nice, specially if we could render and playback using GPU, to discharge our CPUs.
Happy Otter Kwik Proxy FTW. 😉
Hi @RogerS,
Thanks for your post. I thought there was some discussion about the new versions of Vegas having hardware accelerated proxy creation. If this isn't the case, I don't have to go out and purchase an expensive GPU right now. Thanks again!
There were early builds of 18 that had AVC proxies but it was a step backwards for those who had weaker system as XDCAM files play back well without GPU decoding and are easy on CPUs.
I'd guess something like the selectable settings for prerenders will be applied to proxy files but no word from developers on that
To create your own proxies/ intermediates, I recommend Vegasaur for Vegas.
When I used proxies, I was glad that Vegas turned back to XDCAM for proxy creation. They are quickly generated and good quality, something I cannot say from GPU rendered proxies.
Also when you have an good GPU you normally have no need for proxies.
Nvenc Render of proxies would be much faster than the current CPU only render. It would be nice if they added this feature natively to vegas.
Proxy creation times using Happy Otter Scripts Kwik Proxy are usually much faster since proxies are created externally, especially for HEVC media. Here are some representative comparisons using V17.
Here's a demo. https://tools4vegas.com/kwikproxy-demo/
Nvenc Render of proxies would be much faster than the current CPU only render. It would be nice if they added this feature natively to vegas.
That's not true, XDCAM proxy files are generated very quickly, NVENC render is only quickly when you have a good GPU. Normally you make proxies for 4k footage only, when your GPU doesn't support 4k, NVENC proxy generation doesn't work either. In VP18 this NVENC proxy feature was added but withdrawn luckily shortly after.
Nvenc Render of proxies would be much faster than the current CPU only render. It would be nice if they added this feature natively to vegas.
That's not true, XDCAM proxy files are generated very quickly, NVENC render is only quickly when you have a good GPU.
That's incorrect, a transcode has very little to do with the power of a GPU, The GPU encoders are the same power as long as the same generation, the encoder in gtx1650super has the same speed as 2080ti, and even 3080ti
Normally you make proxies for 4k footage only, when your GPU doesn't support 4k, NVENC proxy generation doesn't work either. In VP18 this NVENC proxy feature was added but withdrawn luckily shortly after.
It was a bug, GPU creation of proxies work fine in other editors and are very fast, should always be user select though, a 1080P AVC proxy may work well on 1 person's computer but on less powerful it will need XDCAM proxy
From own experience I wasn't able to create NVENC proxies from 4k footage with my previous weak GPU. XDCAM proxies no problem.
Nvenc Render of proxies would be much faster than the current CPU only render. It would be nice if they added this feature natively to vegas.
That's not true, XDCAM proxy files are generated very quickly, NVENC render is only quickly when you have a good GPU.
That's incorrect, a transcode has very little to do with the power of a GPU, The GPU encoders are the same power as long as the same generation, the encoder in gtx1650super has the same speed as 2080ti, and even 3080ti
Normally you make proxies for 4k footage only, when your GPU doesn't support 4k, NVENC proxy generation doesn't work either. In VP18 this NVENC proxy feature was added but withdrawn luckily shortly after.
It was a bug, GPU creation of proxies work fine in other editors and are very fast, should always be user select though, a 1080P AVC proxy may work well on 1 person's computer but on less powerful it will need XDCAM proxy
Todd, you're not wrong but also missing the point, and this has nothing to do with bugs. If you are using GPUs older than the recommended minimums in Vegas with ancient drivers, you get no GPU decoding or encoding. We're not talking 10XX series, we're talking weak systems with say 8 year old CPUs and GPUs. These are systems that need XDCAM proxies to even work with 4K AVC.
The solution would be something like Vegas just implemented with the prerender (shift M) feature where you can select the type of file to be created. You could choose NVENC AVC proxies, ProRes, Magic YUV, etc. depending on your needs, for example.
@3POINT I do understand the NVENC proxy creater on early VP18 was slow, but that doesn't mean it wasn't a good idea or is inherently slow, it was buggy, if a HARDWARE encoding options returns it won't have the same bugs and work properly
I ran a test on another editor with 4K60 HEVC footage(3:30 duration) creating a 1080p60 proxy
Quicktime (h.264 NVENC) generated in 0:52 with very little CPU
DNxHD generated in 1:23 with 80% - 100% CPU
Not seeing much of a speed difference but I have a 12core CPU, someone with 4 or 6 core will see a big advantage
Todd, you're not wrong but also missing the point, and this has nothing to do with bugs. If you are using GPUs older than the recommended minimums in Vegas with ancient drivers, you get no GPU decoding or encoding. We're not talking 10XX series, we're talking weak systems with say 8 year old CPUs and GPUs. These are systems that need XDCAM proxies to even work with 4K AVC.
The solution would be something like Vegas just implemented with the prerender (shift M) feature where you can select the type of file to be created. You could choose NVENC AVC proxies, ProRes, Magix YUV, etc. depending on your needs, for example.
Good point about the old GPU's and the solution needing to be user selected proxy creation option
Can you write to me what I am doing wrong....
I want to create proxy files for vegas pro 19 using the following code:
nvencc64 -i "c:\!!!_YouTube_upload\_media_file_extractor_ffmpeg_input\05_zakonczenie_Sony_FX3_004.MP4" --codec h264 --vbr 17 --cqp 23 --preset default --colorrange full --fps 23.976 --avsync forcecfr --audio-codec aac --audio-bitrate 128 --output-res 1280x720 -o "c:\!!!_YouTube_upload\_media_file_extractor_ffmpeg_input\05_zakonczenie_Sony_FX3_004_proxied_VBR.MP4"
I change the output file to: 05_zakonczenie_Sony_FX3_004.MP4.sfvp0, but unfortunately I noticed that Vegas is not using this proxy file.
Can you help me what I am doing wrong?
I change Preview - to Auto/Quarter/Half - none of this options works.
I have input video:
General
Complete name : C:\!!!_YouTube_upload\_media_file_extractor_ffmpeg_input\05_zakonczenie_Sony_FX3_004.MP4
Format : XAVC
Codec ID : XAVC (XAVC/mp42/iso2/nras)
File size : 288 MiB
Duration : 11 s 520 ms
Overall bit rate : 210 Mb/s
Encoded date : UTC 2022-06-25 17:28:59
Tagged date : UTC 2022-06-25 17:28:59Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Format Range@L5.1@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 11 s 520 ms
Bit rate : 200 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 50.000 FPS
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.483
Stream size : 275 MiB (95%)
Encoded date : UTC 2022-06-25 17:28:59
Tagged date : UTC 2022-06-25 17:28:59
Color range : Full
Metas : 3
Codec configuration box : hvcCAudio
ID : 2
Format : PCM
Format settings : Big / Signed
Codec ID : twos
Duration : 11 s 520 ms
Bit rate mode : Constant
Bit rate : 1 536 kb/s
Channel(s) : 2 channels
Sampling rate : 48.0 kHz
Bit depth : 16 bits
Stream size : 2.11 MiB (1%)
Encoded date : UTC 2022-06-25 17:28:59
Tagged date : UTC 2022-06-25 17:28:59
Vegas creates proxy file with such media info data (but it takes a long time to create such proxy file):
General
Complete name : C:\!!!_YouTube_upload\_media_file_extractor_ffmpeg_input\05_zakonczenie_Sony_FX3_004.MP4_VEGAS.sfvp0
Format : MPEG-4
Commercial name : XDCAM EX 35
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42)
File size : 48.9 MiB
Duration : 23 s 941 ms
Overall bit rate mode : Variable
Overall bit rate : 17.1 Mb/s
Encoded date : UTC 2022-06-26 02:54:07
Tagged date : UTC 2022-06-26 02:54:07
FileExtension_Invalid : braw mov mp4 m4v m4a m4b m4p m4r 3ga 3gpa 3gpp 3gp 3gpp2 3g2 k3g jpm jpx mqv ismv isma ismt f4a f4b f4vVideo
ID : 1
Format : MPEG Video
Commercial name : XDCAM EX 35
Format version : Version 2
Format profile : Main@High
Format settings : CustomMatrix / BVOP
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : M=3, N=12
Codec ID : mp4v-61
Duration : 23 s 941 ms
Bit rate mode : Variable
Bit rate : 17.1 Mb/s
Maximum bit rate : 35.0 Mb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.776
Time code of first frame : 00:00:00:00
Time code source : Group of pictures header
GOP, Open/Closed : Open
GOP, Open/Closed of first frame : Closed
Stream size : 48.9 MiB (100%)
Language : English
Encoded date : UTC 2022-06-26 02:54:07
Tagged date : UTC 2022-06-26 02:54:07
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Please help me!!!!
Thank you in advance for your help?
Do I need to mux this quarter/half/Full conversions into the one video sfvp0 file to make Vegas see this combined proxy file? If yes, how can I combine this quarter/half/Full sources into single sfvp0 video file?
Is it a source of failure that Vegas doesn't see this proxy file?