[opensuse-factory] ffmpeg multithreads support
HI, while rendering with kdenlive, 1 core at 100% and 3 doing nothing. It' not clear to me if is a problem withn kdenlive, mlt or ffmpeg. I'm not the only one with this problem.. I've found some old post about ffmpeg that needs to be compiled with the option "--enable-pthreads". It seem that both version (suse and packman) are compiled without this option. So, is still valid ? If so, why is missing ? What else could be the problem ? Thanks, Daniele -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 15/11/2017 20:44, Daniele ha scritto:
HI, while rendering with kdenlive, 1 core at 100% and 3 doing nothing. It' not clear to me if is a problem withn kdenlive, mlt or ffmpeg. I'm not the only one with this problem.. I've found some old post about ffmpeg that needs to be compiled with the option "--enable-pthreads".
It seem that both version (suse and packman) are compiled without this option. So, is still valid ? If so, why is missing ? What else could be the problem ?
Thanks, Daniele
Uch.. ffmpeg is working fine: ffmpeg -i a.mp4 -c:v libx264 -crf 23 -c:a libvorbis b.mp4 4 core at 100%. Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2017-11-15 at 21:44 +0100, Daniele wrote:
Il 15/11/2017 20:44, Daniele ha scritto:
HI, while rendering with kdenlive, 1 core at 100% and 3 doing nothing. It' not clear to me if is a problem withn kdenlive, mlt or ffmpeg. I'm not the only one with this problem.. I've found some old post about ffmpeg that needs to be compiled with the option "--enable-pthreads".
It seem that both version (suse and packman) are compiled without this option. So, is still valid ? If so, why is missing ? What else could be the problem ?
Thanks, Daniele
Uch.. ffmpeg is working fine: ffmpeg -i a.mp4 -c:v libx264 -crf 23 -c:a libvorbis b.mp4 4 core at 100%.
I found few years ago that it depends on the codec. Some would process perfectly with several cores, and some wouldn't, would take actually longer. So I wrote a script to launch one conversion script per core to process several movies, if the workload allowed. I used "-threads 2", or not. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloN2NUACgkQtTMYHG2NR9UynACfaFCSXCdSFdu5s9zpJsZoe4RH /0gAn2lj/RTxnfnMIY5vXef/mzFcT3bT =CmhY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 16/11/2017 19:28, Carlos E. R. ha scritto:
I found few years ago that it depends on the codec. Some would process perfectly with several cores, and some wouldn't, would take actually longer. So I wrote a script to launch one conversion script per core to process several movies, if the workload allowed.
I used "-threads 2", or not.
Yes I know.. h264 is ok. Anyway: https://forum.kde.org/viewtopic.php?f=272&t=128817&p=384054#p384033 So I'm trying Openshot, and after a quick test, 4 core with cpu at 80%-90%. A lot better ! Thanks, Daniele. P.S: I think that we can close this thread here.. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 15 november 2017 20:44:05 CET schreef Daniele:
HI, while rendering with kdenlive, 1 core at 100% and 3 doing nothing. It' not clear to me if is a problem withn kdenlive, mlt or ffmpeg. I'm not the only one with this problem.. I've found some old post about ffmpeg that needs to be compiled with the option "--enable-pthreads".
It seem that both version (suse and packman) are compiled without this option. So, is still valid ? If so, why is missing ? What else could be the problem ?
Thanks, Daniele
I use rendering with kdenlive weekly. A few weeks ago I also noticed the use of only one core, however the last few weeks kdenlive is using again 4 cores. Did you configure in Environment Proxy clips "Concurrent threads" -- fr.gr. Freek de Kruijf member openSUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 15/11/2017 21:47, Freek de Kruijf ha scritto:
I use rendering with kdenlive weekly. A few weeks ago I also noticed the use of only one core, however the last few weeks kdenlive is using again 4 cores.
Did you configure in Environment Proxy clips "Concurrent threads"
Yes but I don't think that is useful for final render. "Processing threads" should be the right option (becomes real_time). I saved the rendering script then I did a lot of test with threads and real_time options, no luck. Thanks, Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2017-11-15 20:44, Daniele wrote:
HI, while rendering with kdenlive, 1 core at 100% and 3 doing nothing. It' not clear to me if is a problem withn kdenlive, mlt or ffmpeg. I'm not the only one with this problem.. I've found some old post about ffmpeg that needs to be compiled with the option "--enable-pthreads".
Please don't find old posts - find current ones. ffmpeg has it enabled by default, so nothing needs to be done in openSUSE:
osc bl [ 211s] postprocessing support yes [ 211s] network support yes [ 211s] threading support pthreads [ 211s] safe bitstream reader yes -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 11/15/2017, 08:44 PM, Daniele wrote:
HI, while rendering with kdenlive, 1 core at 100% and 3 doing nothing. It' not clear to me if is a problem withn kdenlive, mlt or ffmpeg. I'm not the only one with this problem.. I've found some old post about ffmpeg that needs to be compiled with the option "--enable-pthreads".
It seem that both version (suse and packman) are compiled without this option. So, is still valid ? If so, why is missing ? What else could be the problem ?
Do you have project->render->more options->threads set to something higher than 1? -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 16/11/2017 08:38, Jiri Slaby ha scritto:
On 11/15/2017, 08:44 PM, Daniele wrote:
HI, while rendering with kdenlive, 1 core at 100% and 3 doing nothing. It' not clear to me if is a problem withn kdenlive, mlt or ffmpeg. I'm not the only one with this problem.. I've found some old post about ffmpeg that needs to be compiled with the option "--enable-pthreads".
It seem that both version (suse and packman) are compiled without this option. So, is still valid ? If so, why is missing ? What else could be the problem ?
Do you have project->render->more options->threads set to something higher than 1?
Yes, does nothing :( It also happens with shotcut, so the problem is in mlt or.. who knows.. Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
Il 18/11/2017 09:09, Dave Plater ha scritto:
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
Done: #1068792 But I don't know how to assign it to you.. Let me know if you need more info. Thanks, Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Daniele, I'm trying to Render in kdenlive and whenever I do I get a corrupt video output. Every thing I try from h264 to h265 results in the same corrupted render. The video plays, but the output is all artifacts in the video. Have you seen this at all. I'm trying to see what could be the problem. Thanks, Cameron On 11/18/2017 04:09 AM, Daniele wrote:
Il 18/11/2017 09:09, Dave Plater ha scritto:
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
Done: #1068792 But I don't know how to assign it to you.. Let me know if you need more info. Thanks, Daniele.
-- Cameron Seader Technology Strategist SUSE cs@suse.com (P)+1 208.572.0095 (M)+1 208.420.2167 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 28/11/2017 21:23, Cameron Seader ha scritto:
Hi Daniele, I'm trying to Render in kdenlive and whenever I do I get a corrupt video output. Every thing I try from h264 to h265 results in the same corrupted render. The video plays, but the output is all artifacts in the video. Have you seen this at all. I'm trying to see what could be the problem.
Thanks, Cameron
Hi, sorry I can't help you, For me kdenlive is ok under this point of view. Try here: https://forum.kde.org/viewforum.php?f=272 or opensuse forum.. Good luck ! Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Nevermind i figured it out. My project settings did not match the FPS of the clip I added in my project. I simply modified the project settings to match and it worked. Never had that problem before. :-) On 11/28/2017 01:35 PM, Daniele wrote:
Il 28/11/2017 21:23, Cameron Seader ha scritto:
Hi Daniele, I'm trying to Render in kdenlive and whenever I do I get a corrupt video output. Every thing I try from h264 to h265 results in the same corrupted render. The video plays, but the output is all artifacts in the video. Have you seen this at all. I'm trying to see what could be the problem.
Thanks, Cameron
Hi, sorry I can't help you, For me kdenlive is ok under this point of view.
Try here: https://forum.kde.org/viewforum.php?f=272 or opensuse forum.. Good luck !
Daniele.
-- Cameron Seader Technology Strategist SUSE cs@suse.com (P)+1 208.572.0095 (M)+1 208.420.2167 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Kdenlive in openSUSE Factory causes corrupt video clips when applying effects. See my screen capture of it occurring. https://youtu.be/9eGJHpz0lnQ Anyone seen it yet? I wonder if I'm missing a package or something else would be causing this? On 11/28/2017 01:39 PM, Cameron Seader wrote:
Nevermind i figured it out. My project settings did not match the FPS of the clip I added in my project. I simply modified the project settings to match and it worked. Never had that problem before. :-)
On 11/28/2017 01:35 PM, Daniele wrote:
Il 28/11/2017 21:23, Cameron Seader ha scritto:
Hi Daniele, I'm trying to Render in kdenlive and whenever I do I get a corrupt video output. Every thing I try from h264 to h265 results in the same corrupted render. The video plays, but the output is all artifacts in the video. Have you seen this at all. I'm trying to see what could be the problem.
Thanks, Cameron
Hi, sorry I can't help you, For me kdenlive is ok under this point of view.
Try here: https://forum.kde.org/viewforum.php?f=272 or opensuse forum.. Good luck !
Daniele.
-- Cameron Seader Technology Strategist SUSE cs@suse.com (P)+1 208.572.0095 (M)+1 208.420.2167 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2017-11-29 19:42, Cameron Seader wrote:
Kdenlive in openSUSE Factory causes corrupt video clips when applying effects. See my screen capture of it occurring.
Anyone seen it yet?
That kind of artifact happens when you fail to start decoding at the previous keyframe/I-frame and instead start right away with a delta/P-frame. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Il 29/11/2017 20:04, Jan Engelhardt ha scritto: ..
That kind of artifact happens when you fail to start decoding at the previous keyframe/I-frame and instead start right away with a delta/P-frame.
Jan (and others), can you look at #1068792 ? We need fresh ideas.. Basically the problems is that melt uses only one core when the package frei0r-plugins is installed. https://forums.opensuse.org/showthread.php/522727-Problem-when-rendering-vid... Thanks, Daniele. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Cameron Seader -
Carlos E. R. -
Daniele -
Dave Plater -
Freek de Kruijf -
Jan Engelhardt -
Jiri Slaby