[Cin] Complete system hangs (likely out of memory)

Rob Prowel rprowel at comcast.net
Sun Jan 22 19:05:51 CET 2023

On 1/22/23 11:31, Stefan de Konink via Cin wrote:

> My input comes from a hacked Nikon D3200 giving me FullHD, 64Mbit in 
> h264. With only previewing these files I can already push towards the 
> boundaries of my  internal memory.

Since resource utilization is kind of a thing with me, I'm curiously 
watching this thread.  fullHD?  What does that mean in terms of 
resolution and frame rate, and D3200 native codec format?  What is the 
container format you are pulling from the camera?

Also, what happens if you render to a different format?  mjpeg?

does the memory bloat happen slowly as rendering proceeds?  is it a 
linear increase or does it happen after some amount of rendering frames?

common cinelerra transcoding/rendering uses ffmpeg/libavcodec as a 
backend.  I'd be curious if you see similar issue if you transcode your 
content directly, independently of cinelerra

ffmpeg -i source -vf scale=1280:720 -c:v x264 -r:v 29.97 -c:a aac -o out.mp4

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x36472CAD382840B8.asc
Type: application/pgp-keys
Size: 632 bytes
Desc: OpenPGP public key
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20230122/e8329b44/attachment-0001.skr>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20230122/e8329b44/attachment-0001.sig>

More information about the Cin mailing list