BruceUSA wrote on 1/30/2017, 11:53 AM

I edited .h265 a lot. no crash or freeze what so ever. I can import 2+ hrs .h265 footage into VP14 latest build all went fine. on my system. I got an old system i7 4930K @4.5ghz, 64gb of ram. Don't know why you are having issues.

astar wrote on 1/30/2017, 12:50 PM

What is your project settings?

What is your Preview RAM set at?


Also the rule of thumb is 4-8GB of RAM per CPU Core. 14 cores x 4-8GB = 56-112GB of RAM for a Xeon.

What is the core chipset your machine runs? Depending on the chipset, you might need to have 8 DIMMs installed to fill the 8 interface channels. Which at 16GB would be like 8x2GB DIMMs.

gerdagerd wrote on 1/30/2017, 1:01 PM

Thanks guys, project settings match the files, which is 3840x2160 and 25p progressive. GPU on or off does not matter. Preview ram 200mb.

I, too had no problems on my old xeon 1230v3. This is obviously a more specific issue, but it is an issue with the HEVC decoder, since editing is completely fine when H264 files are used. So the system is just fine.
I doubt any user can help here if they dont experience this problem.. this is more of a bug report I suppose..

Converting the HEVC files for now.

gerdagerd wrote on 1/30/2017, 2:08 PM

running in a VM, i also get the error, but only when virtualization is enabled. in binary mode (slower) i do not get the ram error. This further leads me to the conclusion that the problem lies with a particular property of this processor/architecture in conjunction with the HEVC decoder.

Nick Hope wrote on 2/3/2017, 1:43 AM

Sounds like the same problem reported in this comment. HEVC and ProRes get decoded by the same mxhevcplug.dll decoder.

gerdagerd wrote on 2/6/2017, 5:23 AM

thanks for pointing that out. it does sound like the same problem.