jliljebl
Render Issues
I'm opening a sticky issue for render rendering related issues. There seems to be many non-reproducing issues and keeping them in single thread will maybe help provide a better over all picture.
Users can still open new issues for rendering but I will merge them here if unless some immediate fix is found.
very slow rendering #918
50-minute movie renders 12-14h!
lossless h264 25 FPS 1080p intel i5 3330 8GB ram
Pathological memory allocation during rendering #914
I have a flowblade timeline I composed that was attempting to render a 21 minute output from 3.7GB of source material. Consistently across two machines, the rendering will get close to finishing with reasonable (<10GB) resource usage, and then attempt to allocate more than 32GB towards the end of rendering, causing an OOM crash.
4K rendering seems slow #887
Edit a vidjeo in 4k, render this less than 5 minutes footage and then :
After a night (11h) it still did not complete.
Flowblade 1.16 consistently fails to render #576
This is probably not relevant anymore.
Memory use issues #327
Windsaw commented on Sep 25, 2018 I installed melt (same version as shown for MLT) and followed your instructions. Rendering from command line works. Memory usage is constant and from glancing over it the finished video seems to be as intended. I am going to use this as a workaround for now.
Rendering a sequence in a media file consumes a lot of computer resources. #554
VKontakte message from the user - "It consumes a lot of resources .... Openshot and Kdenlive - much less ... 8Gb-RAM + 9.7-swap ... Davinchi on Windows loaded the processor so much, but DVNCH has 12Gb RAM system requirements. .
I was able to load the project from issue #914 and render it but there was no issues, problem does not reproduce here. I will continually every now and then keep trying to get stuff reproduced here from now on, hopefully we get results.
Memory leak when rendering with 60FPS #926 was merged here, see that for details.
Compression artifacts in video that contains screen recordings #797 merged, see that for details.
H.264 sequence rendering was fixed and H.264 support for single track transitions was dropped which will fix most issues with those.
Alright, I have found a reproduction for quite few of the problems, e.g. a Flowblade render failed but melt render from XML export succeeded.
The sequence giving the reproduction had a single 3+ hours 59.97/FPS clip edited very quickly which is not a pattern a material/editing I have not used previously.
Now that we have something in cross-hairs we will surely get improvement for 2.10.
Slow/fast motion doesn't seems to work: stop on "starting .." Debian, flowblade 2.8.2
Hey @jliljebl I reported #1008 . It seems that the memory leak occurs when I'm scrubbing through the video timeline, not just when I'm rendering. I can scrub through the same place in the timeline and watch the memory consumption grow in htop. If it would help I could probably create a sample project that reproduces this behavior with royalty free videos - please let me know!
Hey all,
Very new to Flowblade here. I encountered an issue someone else mentioned already, when rendering it get's stuck at 5% (but timers keep counting). Tried changing render profile and encoding format to no avail.
BUT I enabled Render using args (without editing the args) and problem was fixed.
Hope this helps...
User DisasterRunnner writes:
I recently started using flowblade for a recent editing project, and I needed to speed up a series of clips and when I used the in build thing for it, the task appeared in the jobs tab but even after leaving it for 30 minutes it never went past 0% any one else having this issue or is it just me? I am using the basic settings, I just upped the threat count to 2 in the settings, I am using PopOS with an Intel i7-4700U processor, would be thankful of any help.