|Anonymous | Login | Signup for a new account||2014-09-16 21:40 CEST|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003337||Kdenlive||Rendering||public||2014-07-08 11:32||2014-08-23 13:52|
|Platform||x86_64||OS||Arch Linux||OS Version||Rolling|
|Product Version||Recent git|
|Target Version||Fixed in Version|
|Summary||0003337: Clip stabilize jobs operate on proxies.|
|Description||If proxies are enabled for a project, running a clip stabilize job makes a .mlt file that refers to the proxy, instead of to the source file. |
When proxies are enabled they are automatically generated, and so the only time to do the clip stabilizations is after the proxies have been made.
|Steps To Reproduce||1. Enable proxies.|
2. Load a high resolution clip
3. let kdenlive make a proxy
4. stabilize the clip with any of the clip stabilization jobs.
5. add the mlt to your project.
6. disable proxies
7. delete proxies
8. add stabilized .mlt to timeline
10 watch "INVALID" bounce around the screen.
|Additional Information||This is an old one, and one of the reasons I don't use proxies. |
|Tags||No tags attached.|
|Build/Install Method||Manual build from Git|
Uploaded an .mlt file with the issue.
As you can see from that file, this line in the .mlt file is the issue:
When the renderer reads this file, it renders that proxy. Even worse, it uses the proxy for motion detection, and gets it terribly wrong, too.
A quick workaround:
1. Disable proxies for the clip you want to stabilize.
2. Run stabilze job.
With project proxies enabled, the newly created .mlt also get's it's proxy generated.
just tried a fix, please check whenever possible on next daily builds…
The behaviour certainly has changed.
Proxies from the .mlt file are now generated from the High resolution original, rather than the proxy of the original. This can be seen from the time it takes to generate the proxy of the stabilized video.
However, there is still another problem.
For some reason it still needs the proxies when rendering the final video.
To test this,
enable proxies for a project.
Add a clip, then stabilize it.
Add the stabilized clip to the project, and watch how the proxy generation now takes much longer as the proxy is now generated from the original, rather than the proxy of the stabilzed clip.
Now, add the stabilized clip to the timeline.
Then, go into project settings, and delete proxies.
This will also disable proxies for the project.
Render the video.
It now says "Invalid" in the rendered video, as if it was trying to render off a proxy, rather than the .mlt file.
The renderer actually renders from the stabilized original, which I tested by making an extremely low resolution (180 x 120) profile for the proxies, and comparing the output from rendering the original and the stabilzed clips with proxies enabled versus having proxies disabled.
So, why would the renderer need the proxies to be present when rendering off the original footage?
|2014-07-08 11:32||evorster||New Issue|
|2014-07-08 22:18||evorster||Note Added: 0010128|
|2014-07-08 22:40||evorster||Note Added: 0010129|
|2014-08-06 00:20||vpinon||Assigned To||=> vpinon|
|2014-08-06 00:20||vpinon||Status||new => assigned|
|2014-08-19 00:27||vpinon||Note Added: 0010248|
|2014-08-19 00:27||vpinon||Status||assigned => feedback|
|2014-08-23 13:52||evorster||Note Added: 0010272|
|2014-08-23 13:52||evorster||Status||feedback => assigned|
|Copyright © 2000 - 2014 MantisBT Team|