Proxy optimization ?

AndyMo wrote on 4/19/2021, 3:16 PM

What resolution are the proxy files created at ? Is there any way to optimize them ?

My system can preview/playback fairly smooth when working with 1080p content. I am now trying to do the same with 5k content and my system is struggling with even basic cursor positioning. I though by having the proxies generated MEP would use those during the NLE editing so that playback of larger resolution files would be smoother/possible. That way you edit with a lightweight proxy that gets replaced during export. Are the proxy files different resolution based on the resolution of the original ?

I would be totally okay with a low-res preview that enabled me to playback and edit before exporting. I do have the lightning bolt options selected BTW.

I've tried having my movie resolution be low during editing as well (with the idea of setting back to normal prior to export) with no effect.

Any ideas ? Thank you

Comments

CubeAce wrote on 4/19/2021, 3:23 PM

@AndyMo

Hi Andy.

Ray.

 

Windows 10 Enterprise. Version 22H2 OS build 19045.5737

Direct X 12.1 latest hardware updates for Western Digital hard drives.

Asus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Driver No 6.0.8960.1 Bios version 1401

Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics .Driver version Graphics Driver 31.0.101.2135 for 7th-10th Gen Intel® with 64GB of 3200MHz Corsair DDR4 ram.

1000 watt EVGA modular power supply.

1 x 250GB Evo 970 NVMe: drive for C: drive backup 1 x 1TB Sabrent NVMe drive for Operating System / Programs only. 1X WD BLACK 1TB internal SATA 7,200rpm hard drives.1 for internal projects, 1 for Library clips/sounds/music/stills./backup of working projects. 1x500GB SSD current project only drive, 2x WD RED 2TB drives for latest footage storage. Total 31TB of 10 external WD drives for backup.

ASUS NVIDIA GeForce RTX 3060 12GB. nVidia Studio driver version 572.60 - 3584xCUDA cores Direct X 12.1. Memory interface 192bit Memory bandwidth 360.05GB/s 12GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x8 Gen3. Two Samsung 27" LED SA350 monitors with 5000000:1 contrast ratios at 60Hz.

Running MMS 2024 Suite v 23.0.1.182 (UDP3) and VPX 14 - v20.0.3.180 (UDP3)

M Audio Axiom AIR Mini MIDI keyboard Ver 5.10.0.3507

VXP 14, MMS 2024 Suite, Vegas Studio 16, Vegas Pro 18, Vegas Pro 21,Cubase 4. CS6, NX Studio, Mixcraft 9 Recording Studio. Mixcraft Pro 10 Studio. CS6 and DXO Photolab 8, OBS Studio.

Audio System 5 x matched bi-wired 150 watt Tannoy Reveal speakers plus one Tannoy 15" 250 watt sub with 5.1 class A amplifier. Tuned to room with Tannoy audio application.

Ram Acoustic Studio speakers amplified by NAD amplifier.

Rogers LS7 speakers run from Cambridge Audio P50 amplifier

Schrodinger's Backup. "The condition of any backup is unknown until a restore is attempted."

AndyMo wrote on 4/19/2021, 3:25 PM

Thanks Ray - I have that set to Best Performance for playback (MXV) thanks.

johnebaker wrote on 4/20/2021, 4:38 AM

@AndyMo

Hi

IIRC the proxy files approximate to 720p resolution or slightly less.

. . . . my system is struggling with even basic cursor positioning . . . .  I do have the lightning bolt options selected . . .

What is you computer specification - see this topic for details required and please quote the processor and graphics card (if any) name and version in full.

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 4/20/2021, 5:13 AM

@AndyMo

Hi

Have you tried setting the Program Settings to Defaults?

Peter

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

AndyMo wrote on 4/20/2021, 6:11 AM

@AndyMo

Hi

Have you tried setting the Program Settings to Defaults?

Peter

Thank you Peter - this worked extremely well. To be honest I didn't think this was going to work since I was thinking it would just clear some preferences etc. but the difference is like night and day! I can smooth playback and everything, just like when i use proxies on my other HD projects.

(and thank you John for your response as well)

Scenestealer wrote on 4/20/2021, 6:37 AM

@AndyMo

Good to hear Andy.

I suspect that the "Program Setting > Playback Tab > Arranger > Display > Update in background" was unchecked. @CubeAce alerted us to this a while back.

FWIW - in VPX you have a huge amount of choices for the creation of proxies - codecs including Intra frame, and resolutions from 240 up to 4K, etc.

Peter

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

AndyMo wrote on 4/20/2021, 8:58 AM

I just did a quick check and unchecked Update in Background. I can still high-speed scrub and everything is still fine (however I didn't stress test it - don't want to break it now that it is fixed :-) )