Absolute path needed to render with kdenlive about gyroflow-frei0r HOT 5 OPEN

Hmm, that sounds like Kdenlive bug, beause in the plugin code, the path is not altered at all, never, it's just always treated as a string. The parameter is just string too, not path. The Path parameter type is created and handled by Kdenlive (based on the xml)

from gyroflow-frei0r.

Yeah, that was my first thought too, but after a bit of digging, the project file xml does seem to be quite consistent about making paths under the <mlt root=''> relative to it, and I found this report against mlt mltframework/shotcut#710 which seems to indicate this is intentional.

I couldn't find another effect which uses a path to see how it handled this, but it would seem a little odd to have the path in the xml project file to the .gyroflow file be absolute when the path to the video source is relative. I'm seeing:

<property name="Project">footage/PRO_VID_20240410_064418_018.gyroflow
<property name="kdenlive:originalurl">footage/PRO_VID_20240410_064418_018.mp4
<property name="kdenlive:original.resource">footage/PRO_VID_20240410_064418_018.mp4

Can we access the mlt root parameter in lib.rs to create a full path there, or do we really need kdenlive (actually mlt in this case) to pass us something more?

I can open an issue on the kdenlive side, but if we can fix it on this side by normalising the Project path if it is relative, that does seem like the most robust answer to my current (slim) understanding of what's happening in this code.

from gyroflow-frei0r.

There's really nothing I can do on my side, the frei0r interface is dead simple and doesn't have any control over host application or anything host-specific. All that gyroflow plugin handles in lib.rs is a single String. The interpretation of it as a path is entirely on the host side and invisible to the frei0r plugin

from gyroflow-frei0r.

Ok, thanks for clarifying that. I started out looking at whether the parameter type for Project needed to be something other than 'url' in frei0r_gyroflow.xml, but then I wasn't sure if we also had access to more than just those parameter values. I'll leave this open here for now so we've got somewhere to track this side of the discussion, and if we need to bounce some more questions off you, but I'll take it up on the kdenlive side and figure out what needs to be done there. Thanks for the fast response!

from gyroflow-frei0r.

In theory it would work if you could set the parameter in xml to string and just type the full path there manually, but it appears that there's no such type in the effect xml

from gyroflow-frei0r.