Re: Kdenlive v17.12.3 crashes with Title Clips
On 18.03.2018 17:31, farid abdelnour wrote: > I cannot reproduce using 17.12.3 in archlinux, this is an issue with > your build probably. Have you tried the AppImage version to see if it works? Hmmm, I like building my stuff from source. Haven't used AppImage before and (judging from the comments in the sibling thread) that's a different can of worms (but a can of worms nevertheless). That said, it appears the crash lies within melt. Instead of building current master, I chose the v6.6.0 tag, rebuild mlt/kdenlive and the error's gone for me. Cheers, Johannes
Becoming a Windows maintainer
Hallo Kdenlive team Just saw the link on "Kdenlive Café #27 and #28 – You can’t miss it" Like Jeff, I would like to become a Windows maintainer as well. Where can I find information on becoming a Windows maintainer? My NikName on the Forum is Merlimau. Merlimau (Eugen Mohr)
Re: Kdenlive v17.12.3 crashes with Title Clips
2018-03-18 12:49 GMT-03:00 Johannes Bauer: > Hello list, > > Kdenlive v17.12.3 (also tried latest master, same effect) both crash > reproducibly on my machine (x86_64, Ubuntu Mate Artful) with memory > corruption when clicking "Add title clip". In seldom cases (about 1 in > 10) the Title dialog actually opens. In these cases, kdenlive crashes > when hitting "OK" on the Title dialog. > > In the terminal I see: > > *** Error in `kdenlive': corrupted size vs. prev_size: > 0x558cbee63b80 *** > Aborted (core dumped) > > I'm using mostly git master HEAD versions of packages (vid.stab, libvpx, > x264, swfdec, libepoxy, movit, frei0r, FFmpeg, mlt) with the exception > of lame (3.99.5), libx265 (2.7), liboil (0.3.17) and libeigen (3.2.4). > > When running in gdb, I see the following stacktrace: > > #0 0x704290bb in __GI_raise (sig=sig@entry=6) at > ../sysdeps/unix/sysv/linux/raise.c:51 > #1 0x7042af5d in __GI_abort () at abort.c:90 > #2 0x7047328d in __libc_message (action=action@entry=do_abort, > fmt=fmt@entry=0x7059a528 "*** Error in `%s': %s: 0x%s ***\n") at > ../sysdeps/posix/libc_fatal.c:181 > #3 0x7047a64a in malloc_printerr (action=, > str=0x70596dee "corrupted size vs. prev_size", ptr=, > ar_ptr=) > at malloc.c:5426 > #4 0x7047ea15 in _int_malloc (av=av@entry=0x707ccc20 > , bytes=bytes@entry=400) at malloc.c:4035 > #5 0x70480f3e in __GI___libc_malloc (bytes=400) at malloc.c:3086 > #6 0x771fd982 in mlt_properties_add (name=0x7fffb120 "0", > self=0x59006270) at mlt_properties.c:553 > #7 0x771fd982 in mlt_properties_fetch > (self=self@entry=0x59006270, name=name@entry=0x7fffb120 "0") at > mlt_properties.c:587 > #8 0x771fd9d1 in mlt_properties_set_data > (self=self@entry=0x59006270, name=name@entry=0x7fffb120 "0", > value=value@entry=0x58ff03a0, length=length@entry=0, > destroy=destroy@entry=0x77201de0 , > serialise=serialise@entry=0x0) at mlt_properties.c:1146 > #9 0x77202382 in mlt_events_listen > (self=self@entry=0x58fb6930, service=service@entry=0x58fb6930, > id=id@entry=0x7fffb5f58675 "service-changed", > listener=listener@entry=0x7fffb5f57840 ) at > mlt_events.c:280 > #10 0x7fffb5f5845e in filter_deinterlace_init (profile= out>, type=, id=, arg=0x0) at > filter_deinterlace.c:351 > #11 0x7720f05a in mlt_factory_filter > (profile=profile@entry=0x58ffdf90, > service=service@entry=0x58ffc1e0 "deinterlace", input=0x0) at > mlt_factory.c:370 > #12 0x7fffb6fd0604 in create_filter > (profile=profile@entry=0x58ffdf90, > producer=producer@entry=0x58f75480, effect=, > created=created@entry=0x7fffb27c) at producer_loader.c:170 > #13 0x7fffb6fce092 in attach_normalisers > (profile=profile@entry=0x58ffdf90, > producer=producer@entry=0x58f75480) at producer_loader.c:206 > #14 0x7fffb6fd07c3 in producer_loader_init (profile=0x58ffdf90, > type=, id=, arg=) at > producer_loader.c:231 > #15 0x7720ef3a in mlt_factory_producer (profile=0x58ffdf90, > service=0x5660c0b0 "loader", service@entry=0x0, > resource=resource@entry=0x58fabed8) > at mlt_factory.c:342 > #16 0x76fdfbbf in Mlt::Producer::Producer(Mlt::Profile&, char > const*, char const*) (this=0x58fc1d50, profile=..., id= out>, service=0x0) > at MltProducer.cpp:41 > #17 0x55afd822 in KThumb::getImage(QUrl const&, int, int, int) () > #18 0x55a18956 in TitleWidget::refreshTitleTemplates(QString > const&) () > #19 0x55a1749d in TitleWidget::TitleWidget(QUrl const&, Timecode > const&, QString const&, Render*, QWidget*) () > #20 0x55893cc2 in > ClipCreationDialog::createTitleClip(KdenliveDoc*, QStringList const&, > QString const&, Bin*) () > #21 0x55ab4109 in Bin::slotCreateProjectClip() () > #22 0x55b5ccce in Bin::qt_static_metacall(QObject*, > QMetaObject::Call, int, void**) () > #23 0x711668e5 in QMetaObject::activate(QObject*, int, int, > void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #24 0x731edd82 in QAction::triggered(bool) () at > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #25 0x731f046c in QAction::activate(QAction::ActionEvent) () at > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #26 0x73348e1c in () at > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #27 0x7335018b in () at > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #28 0x73350fd3 in QMenu::mouseReleaseEvent(QMouseEvent*) () at > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #29 0x73234dc8 in QWidget::event(QEvent*) () at > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #30 0x733531f3 in QMenu::event(QEvent*) () at > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #31 0x731f446c in QApplicationPrivate::notify_helper(QObject*, > QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 > #32
Re: Quest for a Working AppImage...
On Friday, March 16, 2018 7:41:22 PM CET, Harald Albrecht wrote: So, the 17.08.3 AppImage doesn't eat memory like mad, but then it does not load pngs; neither ones created with gimp, nor inkscape, nor its own extracted png frames. Someone an idea of a working Kdenlive AppImage version to try that doesn't eat memory and does load pngs, especially its own...?? Hello Harald, As Vincent pointed out, there was a recent report and fix for memory usage in MLT. I am currently uploading an AppImage using the MLT from git and Kdenlive's latest git master code (that will become 18.04) that does not contain the refactoring code. So this should be the best of the stable code we have. Pngs work fine in my tests and memory usage should be under control. Feedback is welcome. AppImage is here: https://files.kde.org/kdenlive/unstable/kdenlive-18.04-beta.AppImage.mirrorlist For those interested in testing, I have also uploaded the latest refactoring AppImage: https://files.kde.org/kdenlive/unstable/kdenlive-18.08-beta1.AppImage.mirrorlist I am also in contact with the KDE sysadmins to automate the AppImage creation which should hopefully improve the overall quality and frequence of the builds. Regards jb
Kdenlive v17.12.3 crashes with Title Clips
Hello list, Kdenlive v17.12.3 (also tried latest master, same effect) both crash reproducibly on my machine (x86_64, Ubuntu Mate Artful) with memory corruption when clicking "Add title clip". In seldom cases (about 1 in 10) the Title dialog actually opens. In these cases, kdenlive crashes when hitting "OK" on the Title dialog. In the terminal I see: *** Error in `kdenlive': corrupted size vs. prev_size: 0x558cbee63b80 *** Aborted (core dumped) I'm using mostly git master HEAD versions of packages (vid.stab, libvpx, x264, swfdec, libepoxy, movit, frei0r, FFmpeg, mlt) with the exception of lame (3.99.5), libx265 (2.7), liboil (0.3.17) and libeigen (3.2.4). When running in gdb, I see the following stacktrace: #0 0x704290bb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7042af5d in __GI_abort () at abort.c:90 #2 0x7047328d in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7059a528 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x7047a64a in malloc_printerr (action=, str=0x70596dee "corrupted size vs. prev_size", ptr=, ar_ptr=) at malloc.c:5426 #4 0x7047ea15 in _int_malloc (av=av@entry=0x707ccc20 , bytes=bytes@entry=400) at malloc.c:4035 #5 0x70480f3e in __GI___libc_malloc (bytes=400) at malloc.c:3086 #6 0x771fd982 in mlt_properties_add (name=0x7fffb120 "0", self=0x59006270) at mlt_properties.c:553 #7 0x771fd982 in mlt_properties_fetch (self=self@entry=0x59006270, name=name@entry=0x7fffb120 "0") at mlt_properties.c:587 #8 0x771fd9d1 in mlt_properties_set_data (self=self@entry=0x59006270, name=name@entry=0x7fffb120 "0", value=value@entry=0x58ff03a0, length=length@entry=0, destroy=destroy@entry=0x77201de0 , serialise=serialise@entry=0x0) at mlt_properties.c:1146 #9 0x77202382 in mlt_events_listen (self=self@entry=0x58fb6930, service=service@entry=0x58fb6930, id=id@entry=0x7fffb5f58675 "service-changed", listener=listener@entry=0x7fffb5f57840 ) at mlt_events.c:280 #10 0x7fffb5f5845e in filter_deinterlace_init (profile=, type=, id=, arg=0x0) at filter_deinterlace.c:351 #11 0x7720f05a in mlt_factory_filter (profile=profile@entry=0x58ffdf90, service=service@entry=0x58ffc1e0 "deinterlace", input=0x0) at mlt_factory.c:370 #12 0x7fffb6fd0604 in create_filter (profile=profile@entry=0x58ffdf90, producer=producer@entry=0x58f75480, effect=, created=created@entry=0x7fffb27c) at producer_loader.c:170 #13 0x7fffb6fce092 in attach_normalisers (profile=profile@entry=0x58ffdf90, producer=producer@entry=0x58f75480) at producer_loader.c:206 #14 0x7fffb6fd07c3 in producer_loader_init (profile=0x58ffdf90, type=, id=, arg=) at producer_loader.c:231 #15 0x7720ef3a in mlt_factory_producer (profile=0x58ffdf90, service=0x5660c0b0 "loader", service@entry=0x0, resource=resource@entry=0x58fabed8) at mlt_factory.c:342 #16 0x76fdfbbf in Mlt::Producer::Producer(Mlt::Profile&, char const*, char const*) (this=0x58fc1d50, profile=..., id=, service=0x0) at MltProducer.cpp:41 #17 0x55afd822 in KThumb::getImage(QUrl const&, int, int, int) () #18 0x55a18956 in TitleWidget::refreshTitleTemplates(QString const&) () #19 0x55a1749d in TitleWidget::TitleWidget(QUrl const&, Timecode const&, QString const&, Render*, QWidget*) () #20 0x55893cc2 in ClipCreationDialog::createTitleClip(KdenliveDoc*, QStringList const&, QString const&, Bin*) () #21 0x55ab4109 in Bin::slotCreateProjectClip() () #22 0x55b5ccce in Bin::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () #23 0x711668e5 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x731edd82 in QAction::triggered(bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x731f046c in QAction::activate(QAction::ActionEvent) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x73348e1c in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7335018b in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x73350fd3 in QMenu::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x73234dc8 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x733531f3 in QMenu::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x731f446c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x731fc28f in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x71137de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x731fb262 in
Re: Custom build has effects missing (and named strangely)
Heya Jean-Baptiste, On 18.03.2018 14:48, Jean-Baptiste Mardelle wrote: > Kdenlive effects are described in xml files. The problem you describe > clearly means that Kdenlive cannot find the xml files. Did you install > your custom Kdenlive build ? It probably requires to be installed in > /usr to properly find the xml files. I did run "make install" on kdenlive, but your diagnosis was spot-on: kdenlive only searches in /usr but also in ~/.local/$somewhere. I did an strace on kdenlive to find out the ENOENTS and spotted some "rc" files that were required. So I've improved the build scripts to create/verify symlinks: ~/.local/share/kdenlive -> PREFIX/bin/share/kdenlive and ~/.local/share/kxmlgui5/kdenlive -> PREFIX/bin/share/kxmlgui5/kdenlive With this, kdenlive now works properly. It would be nice if kdenlive would also search in the PREFIX subdirectories, but this works for now. Thanks a lot for your quick help, Johannes
Re: Custom build has effects missing (and named strangely)
On Sunday, March 18, 2018 12:35:50 PM CET, Johannes Bauer wrote: Hi list, I'm trying to get a custom kdenlive build to work. After build-kdenlive.sh wouldn't work for me anymore (https://forum.kde.org/viewtopic.php?f=269=151446) I decided to build my own kdenlive build script (https://github.com/johndoe31415/mkkdenlive). With it, I'm able to successfully create a kdenlive build (and all dependencies that build-kdenlive.sh also builds). However, while the final version works, the effects are somehow messed up: - When I right-click a video snippet that I pulled in the timeline, the "Effects" submenu is empty. - When I load an old kdenlive file in which I've used the pan/zoom effect, kdenlive complains upon loading: "Effect affine:pan_zoom not found in MLT, it was removed from this project" -- in fact it complains about a lot of other missing filters as well (see [1]). - The names of the effects in the effect stack seem to be "raw" identifiers (e.g., "Zoompan" instead of "Zoom and Pan" or similar). - When I try to apply "Zoompan" to a clip, it doesn't have any settings that I could modify. I'm pretty certain that I'm almost able to create a fully working build, but haven't been able to figure out why this happens. Any help would be greatly appreciated. Hello Johannes, Kdenlive effects are described in xml files. The problem you describe clearly means that Kdenlive cannot find the xml files. Did you install your custom Kdenlive build ? It probably requires to be installed in /usr to properly find the xml files. Hope it helps, Regards Jean-Baptiste Thank you very much, Johannes [1] Example: Effect volume:normalise not found in MLT, it was removed from this project Effect volume:fadein not found in MLT, it was removed from this project Effect volume:fadeout not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:fadein not found in MLT, it was removed from this project Effect volume:fadeout not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect affine:pan_zoom not found in MLT, it was removed from this project Effect affine:pan_zoom not found in MLT, it was removed from this project Effect affine:pan_zoom not found in MLT, it was removed from this project Effect affine:pan_zoom not found in MLT, it was removed from this project Effect frei0r.brightness:frei0r.brightness not found in MLT, it was removed from this project Effect frei0r.brightness:frei0r.brightness not found in MLT, it was removed from this project Effect brightness:fade_from_black not found in MLT, it was removed from this project Effect brightness:fade_to_black not found in MLT, it was removed from this project Effect brightness:fade_to_black not found in MLT, it was removed from this project Effect brightness:fade_from_black not found in MLT, it was removed from this project Removed invalid transition: transition37 Removed invalid transition: transition36 Removed invalid transition: transition35 Removed invalid transition: transition34 Removed invalid transition: transition33
Custom build has effects missing (and named strangely)
Hi list, I'm trying to get a custom kdenlive build to work. After build-kdenlive.sh wouldn't work for me anymore (https://forum.kde.org/viewtopic.php?f=269=151446) I decided to build my own kdenlive build script (https://github.com/johndoe31415/mkkdenlive). With it, I'm able to successfully create a kdenlive build (and all dependencies that build-kdenlive.sh also builds). However, while the final version works, the effects are somehow messed up: - When I right-click a video snippet that I pulled in the timeline, the "Effects" submenu is empty. - When I load an old kdenlive file in which I've used the pan/zoom effect, kdenlive complains upon loading: "Effect affine:pan_zoom not found in MLT, it was removed from this project" -- in fact it complains about a lot of other missing filters as well (see [1]). - The names of the effects in the effect stack seem to be "raw" identifiers (e.g., "Zoompan" instead of "Zoom and Pan" or similar). - When I try to apply "Zoompan" to a clip, it doesn't have any settings that I could modify. I'm pretty certain that I'm almost able to create a fully working build, but haven't been able to figure out why this happens. Any help would be greatly appreciated. Thank you very much, Johannes [1] Example: Effect volume:normalise not found in MLT, it was removed from this project Effect volume:fadein not found in MLT, it was removed from this project Effect volume:fadeout not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:fadein not found in MLT, it was removed from this project Effect volume:fadeout not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect volume:gain not found in MLT, it was removed from this project Effect affine:pan_zoom not found in MLT, it was removed from this project Effect affine:pan_zoom not found in MLT, it was removed from this project Effect affine:pan_zoom not found in MLT, it was removed from this project Effect affine:pan_zoom not found in MLT, it was removed from this project Effect frei0r.brightness:frei0r.brightness not found in MLT, it was removed from this project Effect frei0r.brightness:frei0r.brightness not found in MLT, it was removed from this project Effect brightness:fade_from_black not found in MLT, it was removed from this project Effect brightness:fade_to_black not found in MLT, it was removed from this project Effect brightness:fade_to_black not found in MLT, it was removed from this project Effect brightness:fade_from_black not found in MLT, it was removed from this project Removed invalid transition: transition37 Removed invalid transition: transition36 Removed invalid transition: transition35 Removed invalid transition: transition34 Removed invalid transition: transition33
Re: Kdenlive woes: libthumbnail going nuts
Le vendredi 16 mars 2018, 21:18:19 CET Harald Albrecht a écrit : > Hm, difficult to say at this time. I'm not seeing any out-of-mem error, but > heavy swapping, making the system unusable. > > Am 16.03.2018 um 21:16 schrieb farid abdelnour: >> Check this thread out: >> https://sourceforge.net/p/mlt/mailman/message/36222747/ >> Could it be related? Hi Harald, Sorry that Kdenlive gives you some extra stress :( Strange that 17.12.0 works better than 17.12.3 as there have been very little changes in this cycle, probably the problem came from dependencies updates in AppImage (switch to sdl2 with MLT 6.6 ? Qt / KF5 ?). I would say swapping is the same problem as out of mem, the config just pushed the problem by using hard disk... The thread pointed by Farid seems very relevant, as you explained in your refactoring test that your projects use affine CT, and Dan namely optimized affine memory consumption... And getting rid of mlt_pool will help a lot in debugging memory consumption with standard tools (valgrind/massif...) I uploaded latest MLT fix to PPA (all variants), and took the opportunity to update kdenlive too /o\ If this doesn't fix your problem, then we will need to have a look at numbers from libthumbnails... BR, Vincent