So I cannot set custom external proxies for kdenlive for Windows.
I may be missing something I don’t know.
I have a bunch of proxy .mov files created with the blackmagic proxy generator and I just want kdenlive to be able to use them but it won’t recognize them.
The original file is .MP4, I put the proxy file with the same name on the same folder and one would think that creating a custom proxy profile with suffix of clip to be .MP4 and suffix of proxy to be .MOV would do the job but it does nothing.
AI chatbots keep talking about editing the file externalproxies.rc
I’m telling them that kdenlive has interface to make custom proxy profiles inside the program and that I shouldn’t need to edit no file but they don’t seem to get it.
Plus I am not sure if that file does something.
All the new custom profiles I created are not in that file and if I delete the file, the default profiles still exist.
So I am really not sure if that file does something or not.
There was a bug with adding new ‘complex’ proxy profiles (multiple filename patterns and/or multiple locations) via the UI dialog that was fixed in 24.12.2 - which before that you could workaround by editing the externalproxies file manually.
But this definitely does work with the linux appimage, and so should work on windows, though I can’t offhand tell you what/where the corresponding file is found there - or from this description exactly what it is that you’re missing here.
Have you filled in all the fields in the edit dialog? It needs to know the relative paths from clip to proxy and vice versa even if they are in the same dir.
Well I have the latest version…just downloaded it.
And here it is: Same folder, same name, I set the suffix of clip to .mkv and the suffix of proxy to .mov, I hit OK, I reload the project and nothing. I don’t get it.
If that file system is case sensitive, you might need to match the .MKV in the profile to .mkv in the filename …
But you know you also need to explicitly enable the “Proxy clip” option for each clip you want proxied? See the bin context menu for the clip. That doesn’t change if you configure external proxy options - they only tell it where to look for them iff you select using them for a clip.
This is Windows filenames are not case sensitive but I changed it to lowercase just to be sure and still nothing.
What I am expecting is to see the P mark on the clip indicating that it has proxy, but nope!
I know about the “Proxy clip” option but if I check it kdenlive just begins to create a new proxy file, so I assume that I better leave it unchecked.
Yeah, I figured it was probably case insensitive - but as they go ever further down the road of Look, We Can Be A Linux Distro Too, it seemed worth being sure, because there’s not a lot to go wrong here.
When you enable the Proxy clip option it will first look for an external proxy matching the enabled profile, then if it doesn’t find one it will create one according to the parameters you configured for doing that. So if you only have proxies for some clips it will still work as expected for all of them - but if it’s generating one when you think it shouldn’t, that’s when there’s Something Wrong with your selected external proxy config.
Glad it’s all sorted! Is there something we could have said in the docs to make this a bit clearer?
You misunderstood. Windows are case insensitive…but kdenlive is not. That was the problem.
As for the docs…they don’t really say much there…and from my experience with other video editors I am not really surprised.
Now I am trying to figure out how to set proxies that are on different folder than the clip.
I guess that on the “Relative path from clip to proxy” I put ./Proxy/
But on the “Relative path from proxy to clip” I am really not sure, neither I know why that field should even exist.
Oh, yeah I can see how that might bite people. Always assuming something will be case sensitive is a pretty good practice - the windows legacy of character handling isn’t its finest contribution.
There was a bug with editing those in the dialog, but we fixed that in 24.12.2 - so if you’re not using an earlier version that should work. First guess would be you’ve got the field orders mixed up. See what standard profiles do, there’s a few of those that use multiple profiles.
You definitely need both relative paths. One is where you find the proxy if you know the clip path, the other is where you find the clip if you know the proxy path.
This is one I have for a project dir layout that looks like:
It needs the same number of ‘;’ separated fields for each item.
It could be that you’ve given it two identical mappings but with different paths? ie. if I have a foo.mov should I look in . or ./Proxy for it?
You might need to distinguish them by prefix - but what exactly are you trying to do here with the multiple options? This isn’t about setting up multiple search paths for any file, it’s mapping $prefix$name$suffix$clip to $prefix$name$suffix$proxy …
Well I was actually trying to see if multiple sets worked.
It didn’t go very well.
Here is something that it could have actual use for me.
Alas only the first set (mp4) works not the second.
There’s a couple of default profiles using this, and I have several custom ones which all work. I haven’t dug into that code to say exactly what it’s doing, but all of those have unique prefix and suffix combinations to identify each mapping. Your last one is still ambiguous about what a *.mov should map to. I certainly wouldn’t be entirely surprised if multiple mappings requires that.
Take for example what resolve does.
You have the folder with the clips.
And inside that folder you have a subfolder named Proxy.
And in there are the proxies…with the same name.
So it connects them automatically.
What I am trying to do here.
