Building Proxies in VP18 takes forever

cyro wrote on 8/21/2020, 9:30 PM

In VP18 Build 284 on Win10.0.18362 Build 18362 when I import footage larger than 4K resolution the automatic proxy building kicks off but never produces any results and VP18 just hangs. The work around is to disable >4K proxy building and my machine is still plenty fast but what are the typical reasons why proxy building would just languish forever? Any hints welcome, didn't find any previous answers to this topic in the forum, thanks!

Comments

fr0sty wrote on 8/21/2020, 9:48 PM

The proxy format VEGAS uses does not support GPU encoding, so it has to render using the CPU only, and even then it doesn't render that fast. If you want to have better control, download Happy Otter Scripts (tools4vegas.com) and use its proxy system, this lets you choose which codec you render to, so you can choose something like AVC accelerated by NVENC or VCE, and render the same proxy in higher resolution (VEGAS default proxies are 720p) much faster than the stock proxy system does.

Former user wrote on 8/21/2020, 9:55 PM

VP18 encodes 1080 AVC for proxies via NVENC encoder if you have a compatible Nvidia GPU. Not sure if it does for AMD cards using VCE. If you do not have hardware encoding I"M not sure if it software encodes AVC or goes back to the old codec and does 720P

fr0sty wrote on 8/21/2020, 9:56 PM

720p24 XDCAM EX 35Mbps is the format VEGAS encodes for proxies.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Former user wrote on 8/21/2020, 10:01 PM

These are the details for the proxy VP18 built for me

General
Complete name                            : H:\a\C0006.MP4.sfvp0
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (isom/mp42)
File size                                : 19.2 MiB
Duration                                 : 12 s 960 ms
Overall bit rate                         : 12.4 Mb/s
Encoded date                             : UTC 2020-08-21 23:10:19
Tagged date                              : UTC 2020-08-21 23:10:19

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.2
Format settings                          : CABAC / 1 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 1 frame
Format settings, GOP                     : M=1, N=30
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 12 s 960 ms
Bit rate                                 : 12.4 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 50.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.120
Stream size                              : 19.2 MiB (100%)
Language                                 : English
Encoded date                             : UTC 2020-08-21 23:10:21
Tagged date                              : UTC 2020-08-21 23:10:21
Color range                              : Limited
Codec configuration box                  : avcC

fr0sty wrote on 8/21/2020, 10:20 PM

Looks like they did update it... however, it definitely is not using NVENC or VCE on my system, making proxies takes forever still.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Former user wrote on 8/21/2020, 10:52 PM

It does use NVENC for me, though not very efficiently. I cropped out the cpu by mistake, but it's in the range of 65% - 95% and you can see with the gpu encoding it's spiking between doing nothing and encoding. I think that would be acceptable for a 4k proxy creation, but this is just testing with a 720p file. I do wonder however what happens if a computer doesn't have hardware encode, is it software encoding 1080p AVC as that would take longer then 720p XDCAM EX 

cyro wrote on 8/22/2020, 1:57 AM

Yeah, it looks like on my 12-core box it uses <10% CPU and no GPU and runs for hours to do the proxies. Not worth it, the machine is plenty fast (or better: the NVMe and GPU have so much bandwidth) working with >4K footage is not a problem. I'll just disable this.
Thanks for your replies everybody, very helpful!

cyro wrote on 8/22/2020, 12:27 PM

I let that run over night, some progress but proxies are still not done. I guess this is one of those Vegas things that just don't work unless you use the HOS tools or just disable the proxies (which works pretty well on fast machines), sigh.

AVsupport wrote on 8/23/2020, 7:10 AM

would have been good to have the proxy machine machine updated for VP18. Maybe Magix should buy HOS..

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

michael-harrison wrote on 8/23/2020, 10:32 AM

Yeah, it looks like on my 12-core box it uses <10% CPU and no GPU and runs for hours to do the proxies. Not worth it, the machine is plenty fast (or better: the NVMe and GPU have so much bandwidth) working with >4K footage is not a problem. I'll just disable this.
Thanks for your replies everybody, very helpful!


@cyro If you must have proxies go with HOS or do it manually with handbrake.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia GTX 1660 Studio [most likely latest]
Resolution        1920 x 1080 x 60 hertz
Video Memory 6G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

cliff_622 wrote on 10/2/2020, 12:56 PM

Proxys used to work great when it was MPEG-II (720p XDCAM)

Now that they moved to h.264 in 1080,...they look worse,...they perform worse, and they render soooo much slower than MPEG-II.....it's just a mess now!

Why in the heck did they break it that way? Now we have to buy Happy Otter scrips to fix Vegas proxys?

Guys,...can you PLEASE give us the option in a simple check box to let us do the "old" or "legacy" MPEG-II proxys?