4K from GH4 to Sony Vegas Pro 12

Dan Sherman wrote on 6/24/2016, 7:07 PM
Got footage to the timeline, but no smooth playback even at preview quarter.
Jerky and impossible to edit.
Need to down rez to 1080? Convert? Use proxy.
Used Cine D style.
Anybody solved this one?

Not a screaming machine but thought it could handle 4K.

System #3
Computer Brand/Model:
Operating System: Windows 7 64-bit
Processor: Intel R Core (TM) i7 2600K @ 3.40 GHz
Video Card: nVidia 560 GTX 2Gb Video Card
Sound Card: M-Audio Delta 44
Video Capture: Vegas
CD Burner: LG Blu Ray Writer
DVD Burner: LG Blu Ray Writer
Camera: HPX 170 Panasonic
Add. Comments: Other Stuff, Asus P8H67 Motherboard 60Gb Soliod State Drive - For Windows Antec Sonata Case w.
Modify / Delete


musicvid10 wrote on 6/24/2016, 7:57 PM
I think an XAVC proxy render would go pretty fast on your system.

Wolfgang S. wrote on 6/25/2016, 2:31 AM
My old system had very similar specs, and to edit native UHD 25p footage was possible but on the limit. i used mp4 as record format. I overclocked the 2600k to something about 4.2GHz. And I optimised dynamic ram preview and used the GPU acceleration for the preview. I never used proxys. And XAVC would have a tougher playback behaviour then the GH4 mp4 files I think.
Dan Sherman wrote on 6/25/2016, 3:03 PM
Sorry, pardon my ignorance.
How do I do a XAVC proxy render?
Is it a conversion?
Something that can be done inside Vegas or is third party software required?
Beginning to regret not shooting this project in 1080
Dan Sherman wrote on 6/25/2016, 7:06 PM
Solution could be to batch render to 1080.
Anyone have a workflow for that?
Technical moron here, as you can tell.
wwaag wrote on 6/25/2016, 7:56 PM
Solution could be to batch render to 1080.

You really don't want to do that at the beginning if your final delivery will be 1080 unless you intend to use that as a proxy. The workflow for using a proxy is really quite simple. First, render all of your footage to a lower resolution set of files, referred to as your proxies. If your system is really "weak", you could render to something like HD EX 1280 x 720, making sure you change the frame rate to 30P, assuming you are in NTSC land. Then replace the original files, with the proxy files you just rendered. You should also change your project settings to reflect the proxies. At that point, your preview should be pretty good and you can then do your editing. Once finished with your editing, you simply replace the proxy files with the original 4K footage files, change your project settings back to the original and then do a final render to a delivery format of your choosing. To do batch replacement of original files with proxies and vice-versa, there are freeware scripts that can be used or scripting extensions like Vegasaur. On the other hand, if you only have a few files, you can do it manually just as easy.


AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia 1050ti graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Wolfgang S. wrote on 6/26/2016, 3:31 AM
Sure, but to ignore the fact that other people are able to edit with the same processor the footage native is also funny.
Dan Sherman wrote on 6/27/2016, 8:16 AM
Decided on the proxy route.