[kdenlive] [Bug 465138] Make external proxies more flexible

2023-02-01 Thread Hyuri
https://bugs.kde.org/show_bug.cgi?id=465138

--- Comment #3 from Hyuri  ---
(In reply to Hyuri from comment #2)
> Also, if we are going to use external proxies that keep the original file
> name, it would only make sense and be really useful to also have the proxies
> Kdenlive generates also keep the original file name with additional suffix,
> instead of the current random string of letters and numbers.
> 
> Example:
> - Original file: "CLIP_0001.mp4"
> - Proxy generated by Kdenlive: "CLIP_0001_Proxy.mov"

This format even provides compatibility with proxies generated for Premiere
Pro. Premiere uses a "_Proxy" suffix for proxies, which would mean that proxies
generated for Kdenlive could also be attached to Kdenlive projects.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 465138] Make external proxies more flexible

2023-02-01 Thread Hyuri
https://bugs.kde.org/show_bug.cgi?id=465138

--- Comment #2 from Hyuri  ---
Also, if we are going to use external proxies that keep the original file name,
it would only make sense and be really useful to also have the proxies Kdenlive
generates also keep the original file name with additional suffix, instead of
the current random string of letters and numbers.

Example:
- Original file: "CLIP_0001.mp4"
- Proxy generated by Kdenlive: "CLIP_0001_Proxy.mov"

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdenlive] [Bug 465138] Make external proxies more flexible

2023-02-01 Thread Hyuri
https://bugs.kde.org/show_bug.cgi?id=465138

--- Comment #1 from Hyuri  ---
Reasons why it's useful to allow proxies generated outside of Kdenlive and be
able to manually choose the proxies folder location:

1. Dedicated [open source] transcoding apps, such as Shutter Encoder and Hand
Brake, offer a much simpler and specialized workflow to create proxies in a
variety of edit-friendly formats;

2. These apps allow us to burn-in titles and timecode onto the proxies, make
color and other image adjustments, apply LUTs, change other settings, affording
us much more control over the proxies we generate;

3. Shutter Encoder, for example, has a "watch folder" feature, that lets you
configure a folder to watch for new footage so that you can just drop a folder
with new footage in there and Shutter Encoder automatically starts transcoding.
We don't have to open Kdenlive, set up a new project, save it somewhere, import
all the footage, and enable the proxy generation. Plus, proxy generation in
Kdenlive has failed on me before with an .mkv source;

3. Sometimes we get proxies already generated from a production, so it doesn't
make sense to re-generate them inside Kdenlive, we should be able to just
link/attach the existing proxies (Premiere Pro behaves like this, as an
example);

4. Project files, media files, and temporary files (proxies & cache) are
usually placed in different drives, to optimize performance and maintenance. So
I rarely want the proxies inside the project folder — except in small or
personal projects edited in my own notebook;

5. When external apps like Shutter Encoder generates proxies, it keeps the
original file name and gives you options to add a suffix (like "_Proxy") to all
the files. This is really helpful to know which files are proxies and which
files are not. The proxies Kdenlive generates are named a random string of
characters and numbers, so it makes it very hard to manage and send them to
other editors to re-link if needed (this last scenario will probably not happen
now because Kdenlive isn't commonly used in the industry yet, but it might
start happening as it matures and more people and production companies adopt it
like happened with Blender).

So, for those reasons, it's important to offer some flexibility when it comes
to attaching and using external proxies.

-- 
You are receiving this mail because:
You are watching all bug changes.