Would like to have a clip job that renders a .mlt file with the project's quality settings, and add it to the project. Reproducible: Always This is a quite longstanding wish, actually. What I propose is a special clip job, only for .mlt files that are in the Project bin. What it should do is to render the .mlt file using the project settings. Sort of the same method used to create the .mlt file in the first place. What we will get from this is clips that can be used on the timeline without the performance impact of the .mlt, and also have the ability to apply successive clips jobs to one clip, and have proxy clips available for the effect and so on.
Evert, can you please give the report a descriptive title? I'm afraid that "git master" isn't exactly helpful at the moment. I'm not exactly clear as to what you want to achieve here; maybe your description is a little bit terse. Do you want to render part of an Kdenlive project to a single clip, and then add this clip to the project again? Could the existing timeline preview rendering mechanism solve this also?
My bad. Heading has been updated. No, the existing timeline preview rendering does not allow for many nested .mlt files. Proxy clips are not supported on .mlt files. (Does not prevent the proxy generator from trying, though) .mlt files the automatic audio split out does not work properly... Sometimes it is just simpler to render the .mlt and use the resulting clip in the timeline. Currently that requires me to start a new project, import and render the .mlt, and then open that rendered file in the original project.
This wish is still here. It would be super-awesome to be able to render an .mlt file at the project settings and add it to the project bin. Right now, that requires opening another project, dragging the .mlt file into it, rendering it, and then adding the output back into the first project. So tedious. Conceptually this would be really easy to do as a clip job in the project bin. As we all know, mlt files have issues. They are CPU intensive to display, and cause their own class of bugs in kdenlive. In my mind there is not much difference between rendering a clip once and using that, and rendering it every time you want to look at it, apart from the CPU used. If you want to be purist about it, one can use a lossless profile for in-project renders...
To understand correctly. The goal would be that we have no MLT files in the project anymore. Like: clip job -> stabilize would not create a MLT file but a MP4 or MOV file with the project settings instead. Correct?
Not quite... If one has no problems with .mlt files, you can continue as normal. However, it would be nice to have the option to render the .mlt files in project and add them to the project automatically. The easiest way to achieve this, in my humble opinion, is to add a clip job, just for .mlt files, to render the file and add it to the project. Rendering can be done at the project settings, lossless, or custom.
Just made a test: Settings -> Configure Kdenlive -> Transcode -> add in field name: MP4, extension: mp4, parameters: f=mp4 movflags=+faststart vcodec=libx264 progressive=1 g=15 bf=2 crf=%quality acodec=aac ab=%audiobitrate+'k' -> add profile. So I added a new transcode profile. Right click the MLT file -> transcode -> choose MP4 and it generates a new MP4 file. Is that solving the issue?
Ah, that DOES work, and perfectly, I have to admit. Wonder why I have never thought of doing it like that? Thanks for pointing out this method.
Created attachment 120952 [details] Render-window Glad to hear it works. I just copied the parameter out of the render window. So you can make transcodes as you like. I would say in german: Even a blind chicken picks up a grain now and then.