Already FullHD (1080p) can be tricky with a 32-bit build.
4K UHD works on a PC with 8 GB RAM, but 8K UHD may allocate around 12 GB,
so I experienced heavy swapping.
Am 06.04.2017, 07:18 Uhr, schrieb Santhoshini Sekar
:
Hi Yiran Li,
We found such memory issues for 32-bit builds even wit
I'm also working with 8K content at the moment, and my goal was mostly to push
it below
16GiB of memory consumption. When working with that, I found out that there are
some
things you can do to reduce memory consumption:
1.) Reduce B-Frames ('--bframes 0'), lowering efficiency
2.) Reduce chroma
Hi Yiran Li,
We found such memory issues for 32-bit builds even with 4K content. It is
very natural for a 32 bit build to fail for high resolution videos. We have
a bitbucket issue pointing to this (
https://bitbucket.org/multicoreware/x265/issues/310/memory-error-crash-in-32-bit-compiler-for
).
Hi Pradeep,
I'm now using x265.exe to reproduce this issue and yes I was able to
reproduce it.
The thing is, x265.exe only accepts .yuv or y4m which store uncompressed
data so even only 1 second long clip takes more than 1 GB so I can't upload
them.
If you want, you can use MSPaint to create a 8
In general, I would recommend against a 32-bit build due to the fact that
several of our assembly optimizations (10-bit and 12-bit, in particular)
work only for 64-bit which would considerably restrict your encoding speed.
This is especially true for 8K where there is so many bits to deal with!
If
Hi guys,
I'm writing a program which can encode video using X265 API. It's a 32 bit
program.
When the program runs to encode a 8K video, I can see every
time encoder_encode is called, the program eats about 100MB so that after
12 frames are sent to encoder and when encoder_encode is called for
