On Sunday, January 22, 2023 7:05:51 PM CET, Rob Prowel wrote:
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?
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '_DSC0397.MOV': Metadata: major_brand : qt minor_version : 537331968 compatible_brands: qt niko creation_time : 2023-01-21T16:43:02.000000Z Duration: 00:01:50.52, start: 0.000000, bitrate: 61237 kb/s Stream #0:0[0x1](eng): Video: h264 (High) (avc1 / 0x31637661), yuvj420p(pc, smpte170m/bt709/bt470m, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 59681 kb/s, 25 fps, 25 tbr, 25k tbn (default) Metadata: creation_time : 2023-01-21T16:43:02.000000Z vendor_id : [0][0][0][0] Stream #0:1[0x2](eng): Audio: pcm_s16le (sowt / 0x74776F73), 48000 Hz, stereo, s16, 1536 kb/s (default) Metadata: creation_time : 2023-01-21T16:43:02.000000Z vendor_id : [0][0][0][0]
Also, what happens if you render to a different format? mjpeg?
No experience with mjpeg in this context yet.
does the memory bloat happen slowly as rendering proceeds? is it a linear increase or does it happen after some amount of rendering frames?
It has nothing to do with rendering. This occurs when being in Resources > Media and start a few viewers to review my material and make some clips out of them. -- Stefan