On 17/11/2017 19:14, Daniele wrote:
Il 17/11/2017 09:29, Dave Plater ha scritto:
On 16/11/2017 19:27, Daniele wrote:
Yes, does nothing :( It also happens with shotcut, so the problem is in mlt or.. who knows.. Daniele. If you can specify a test case, and file a bug against shotcut and/or mlt I will take it up with the developer. File a bug and assign it to davejplater@gmail.com. ffmpeg is excellent in it's use of threads so the problem can't be there. Dave P
I'm quite sure that is a bug/limit of mlt. It seem a well known issue. I'll fill a bug but I don't know how to attach a video for testing (to big).
Thanks, Daniele. I had a look around MLT Framework on github this morning and found a closed bug against melt, relating to the cpu usage of libavformat, which looked similar to your problem. You can post the output of "ffprobe video" and I can try to duplicate it. Also ffmpeg has the option: "-t duration (input/output) When used as an input option (before "-i"), limit the duration of data read from the input file." duration has the same format as the duration section in the output of ffprobe. Make it long enough for a glance at cpu usage if you can. The output of ffprobe is important. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org