If I have a piece of footage that I want to both stabilize and slow down, I can do it today by slowing down the footage first, then rendering the .mlt file, and then running the stabilizing clip job on it. What is stopping us from running a clip job on an .mlt file? Conceptually I don't see anything preventing nested .mlt files, it would be almost like loading a saved project as a clip, no? Reproducible: Always
Evert, as there recently have other reports touching mlt and proxies: is this report still valid or stale? Or am I on the wrong track here and this handling of MLT files in clip jobs is still open?
Not stale at all. Apply speed clip job, get .mlt file in the Project Bin. Try to stabilize the .mlt file. I get an error message: "No valid clip to process" Why can't we stabilize .mlt files? -Evert-
Hi Evert, thanky for your reply. It helps me to better understand the issue. My (limited) understanding is that vid.stab uses ffmpeg for decoding the unstabilized video, and then ffmpeg again for encoding the stabilized result video. But ffmpeg can't handle MLT files as it doesn't understand them. MLT sits on top of ffmpeg, but ffmpeg doesn't know about MLT. One way might be to first transcode from MLT to some video format that vid.stab and ffmpeg can reread later when running the stabilization.
Erm, but as vid.stab generates a MLT output file, at least vid.stab is run from inside MLT it seems...
It would be a nice shortcut on .mlt clips only to be able to render the .mlt clip at it's input resolution and quality settings, and add the resulting clip into the Project. -Evert-
Hi Evert about 4,5 years later: can you please check if this feature request is still relevant (especially after the job manager rewrite)?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!