Registered Member
|
Hello,
I am currently having problems while rendering videos with kdeenlive. I create a new topic because, it is very strange. I'm working with two different workstations. As you will see, they differ only by their respective hardware. 1/First WS
2/Second WS
On both of them, here are the versions of the differents packages required:
The video clips used are all from my Sony HDR-AS-100 and are all like this:
They are all playable with any video player. I can run avprobe without error on any of them. The kdenlive project file is the same on both WS My problem : on the first workstation, I can render (MPEG-A/AAC, 1 pass) a short 5 min video without any problem (multitracks, speed/sound effects, and usage of two audio tracks) On the second workstation, the rendering always hangs at the same moment (around 26%). So i decide to run the corresponding rendering script directly from a shell (I also add the -debug flag to melt) ...and the rendering still crashes. Just before the script beeing in stuck I notice many repeating errors like:
or
Then I tried to run it under gdb, to see what's really happens....nothing more than the melt -debug shows I also tried to get/compile mlt from it's git repo...nothing has changed Any idea ? Thank you so much
Last edited by mrdocin on Wed Jun 11, 2014 9:00 pm, edited 2 times in total.
|
Administrator
|
Can you please try running the render command under a new user to ensure it is not configuration files causing this behaviour (by changing how it reads the source files). Also, please verify that the source files being used are the same - one machine may have a corrupted/damaged file.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Hello bcooksley,
--> no changes
--> I just compare the md5sum of each file on each WS : no diff I also ran avprobe on each file/each side : no diff too |
Registered Member
|
hi guys,
i'm still in stuck I've notice today, that on both servers, the output of ldd /usr/bin/kdenlive is not the same. ldd dos not indicate that there is missing libraries, but on the server where rendering is successfull, kdenlive use 11 more librairies:
is it normal ? |
Registered Member
|
After different tests, my pb seems to be libx264 specific
It occurs only when i choose the MP4 predefined profile H.264/AAC content of this profile :
used command line :
When choosing MPEG-4/MP3 Profile, the rendering completes successfuly Then, the command line is:
|
Registered Member
|
examining generated core files witch gdb gave me:
backtrace:
|
Administrator
|
Hmm. As threads are probably involved could you try generating a backtrace for all threads?
See https://wiki.debian.org/HowToGetABacktrace for more information on this.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Hi bcooksley,
I pass the "thread apply all bt full" command to gdb and got many lines of debug. Where can I put them, to make them viewable here ? |
Administrator
|
You can use the pastebin at paste.kde.org.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
ok. here it is : http://paste.kde.org/pnf0hrzxp/iv74gn |
Administrator
|
Hmm, unfortunately that is truncated before it reaches the necessary point in the trace. However it did reveal:
Can you please ensure Kdenlive, MLT, Jack, libx264 and ffmpeg/avconv are all installed from the same repository (or from repositories that are compatible with each other)? Based on the above, it seems unlikely that is the case - something is built against a different version of Jack and ffmpeg/avconv at least.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
hello,
Indeed, there was a mismatch for libx264. now it' is still crashing, but for other reasons (I suppose) Here is details of my latest core file http://paste.kde.org/pp3pgknvq/7n9cxz |
Administrator
|
Yep, that is a different crash - this time within MLT. You'll need to report a bug in their bug tracker concerning that i'm afraid.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft