https://bugs.kde.org/show_bug.cgi?id=364655
Bug ID: 364655
Summary: git master 2016-06-22 - re-creation of proxy files...
Product: kdenlive
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: evert.vors...@yandex.com
Hi there.
It seems that the default for creating proxies has changed. Previously, once a
proxy was generated, it stayed generated, and re-used whenever that clip was
loaded into another project. This was a great time saver, especially on GoPro
footage that tends to be hours long.
The current solution is sub-optimal for my use case, as I tend to re-use GoPro
footage often.
In my mind, a proxy should be generated for a clip, and stored together with
the clip, much like the extracted .mlt files for stabilization, or clips that
are generated when a zone is extracted, etc.
Then, when a clip is loaded, it would be easy to check for the existence of a
proxy, and then check to see if the proxy matches the desired resolution. It
might even be an idea to incorporate the proxy profile name into the filename
of the proxy.
For instance, if you have a clip called GoPro0001.mp4, and your proxy profile
is called 720p, then the proxy name could be:
GoPro0001.Proxy_720p.mp4
This would even allow keeping various versions of the proxy, like
GoPro0001.Proxy_360p.mp4
GoPro0001.Proxy_1080p.mp4
and so on.
I think that keeping proxies are valuable, as they don't change, unlike the
project's temporary renders, thumbnails, etc.
It may even simplify hunting down errors where proxies are used in final
renders instead of the original.
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
