Bug 363363

Summary:	Speed effect in 16.04.1 has absolute path to video file, leads to INVALID clips (breaks project conversion from 15.x to 16.04.1)
Product:	[Applications] kdenlive	Reporter:	bugs
Component:	Video Effects & Transitions	Assignee:	Vincent PINON <vpinon>
Status:	RESOLVED NOT A BUG
Severity:	major	CC:	wegwerf-1-2-3
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description bugs 2016-05-21 08:39:07 UTC

Hello,

I have a project which I started with kdenlive 15.12.0 that contains clips with speed set to for example 400%. With the new feature in 16.0.4.(1) that speed clips may keep their audio track, the corresponding xml is generated differently.

It now contains a resource and a warp_resource for the speed effect, but resource is set to an ABOSLUTE path in the filesystem, whereas warp_resource is the relative path.

This works for a newly created project with 16.04.1. Which makes me believe that the path now has to be absolute?

BUT if i open the project created with 15.x and it gets converted, BOTH resource AND warp_resource contain a relative path. While rendering this leads to INVALID texts shown wherever there is a speed effect applied.

To sum up, I guess there are 2 problems:

1. 16.04.1 creates ABSOLUTE paths for the resource property of a clip with an applied speed effect
2. while converting a project from 15.x to 16.04.1 the resource stays relative.

So why do relative paths in clips with speed effects not work with 16.04.1 anymore?

Cheers,

Stefan

Comment 1 Wegwerf 2016-10-08 15:41:57 UTC

Stefan, can you please supply the project files? In particular, what is the root attribute of the mlt element which is at the root of the kdenlive project file? It should not matter whether the resource paths are relative or absolute. Do you start Kdenlive always in the same way? From which path?

Comment 2 bugs 2016-10-08 15:47:42 UTC

I am sorry, this is now almost 5 month ago and by that time I fixed it using scripts that used xpath to change the corresponding xml nodes so they worked for me.

I do not have the old broken project files anymore.

Comment 3 Wegwerf 2016-10-08 15:49:42 UTC

Hi Stefan, thanks for the quick reply. So we can close this report.