Bug 377492 - Video Profiles vs Project settings issues
Summary: Video Profiles vs Project settings issues
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: 18.08.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords: junior-jobs
Depends on:
Blocks:
 
Reported: 2017-03-11 11:49 UTC by Peter
Modified: 2021-03-27 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
fritzibaby: low_hanging+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2017-03-11 11:49:29 UTC
Hello I'm having issues with the Project Settings dialog for changing Video Profiles.

This is starting with a fresh install of kdenlive-16.12.3 in Antergos (have selected Arch and 16.12.2 as these were closet - problem also exists on 16.08.3, which is also not available to select).

So the use case is that I have video that is 640x480@(60000/1001). The produced video should be 1440x1080, so the video is upscaled, but title cards etc. can be the full 1440x1080.

My expectation was to be able to go into Project Settings and select a Profile of 1440x1080@60000/1001.

However, the Video Profile option offers resolutions instead. 1440x1080's not there, so I select custom. However with this fresh install, with custom, 60000/1001 isn't available. Also the available frame sizes, display ratio, sample ratio, colour space, and frame rate are not independent, so for example, if you select a frame rate of 23.98, you have no choice other than 720x486, 4:3, 8:9 and ITU-R 601.

The Resolution drop-down has a Properties button next to it however. So that brings up the Profiles dialog. Here I can create new Profiles, but the list is completely different from the one in Project Settings. Even the conventions are different.

Project Settings vs Profiles:

Resolution vs Description
Frame Size vs Size
Display Ratio vs Display aspect ratio
Sample Ratio vs Pixel aspect ratio
Colour Space vs Colourspace
Frame Rate is the same in both, but Project Settings uses decimal (23.98) and Profiles uses ratio (24000/1001) and also has decimal for Fields per second
Interlaced checkbox vs Progressive checkbox

In the Profiles dialog, I can create exactly what I want for the project. I can base a new one off of "HD 1080p 59.94", call it "HD 1440x1080p 59.94" and set all the things I need independently. I can save it. I can then select to "Use as default". This neither selects it, nor makes it available in the Project Settings as a Profile.

I can now select the frame rate, and then that fills out the rest for me, so success!

So the bugs are:

Conventions should be the same in all dialogs. My personal preference is ratios for frame rate (decimal is ambiguous. 29.98, could mean 29.98/1 or 30000/1001).

Custom resolution should allow independent entry, entering a frame rate should not change the other values. Where a value isn't in the drop down, there should be an option to enter a free value. There should also be more options in the drop downs. 60000/1001 and 60/1 should be there as they are common, also the 120fps equivalents.

Changing the Profile in the Profile dialog and then closing the dialog should set the Project Settings to match the Profile just closed. Alternatively, give it a standard OK button that when pressed sets the Video Profile settings in the Project Settings dialog.

'use as default' I would expect to not only set the Video Profile in the Project Settings but also make those settings the default project settings when I start the program. All of this should apply to using the Manage Project Profiles button in the Configure dialog too, rather than setting a Profile as default and then needing to then select custom and the frame size and then saving that separately.
Comment 1 Peter 2017-03-11 11:59:06 UTC
Oh, 'use as default' will sometimes affect the kdenlive starting profile even though the default profile in configure is set to something else. This shouldn't happen.
Comment 2 emohr 2018-10-20 13:10:35 UTC
I'm not sure if this is fixed with 16.04. But you used 16.12

Please try with the actual Kdenlive version 18.08.2
Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage
Should be fixed with Kdenlive version 16.12
Comment 3 Peter 2018-10-20 21:23:58 UTC
I didn't really understand your comments about versions, how this should have been fixed in 16.12 and 16.04 when I tested with 16.12? Or what you mean by 'actual' kdenlive?

I tested against 18.08.02 appimage version and yes, the bugs detailed are still present, but the Project Settings dialog works differently so I guess the bit about setting fps / resolution is no longer valid as Project settings drop-downs now just filter the viewable profiles.
Comment 4 Julius Künzel 2021-02-25 20:03:10 UTC
This bug is related to a very old version of kdenlive. Can you please update to the latest version (at the moment 20.12.2, https://kdenlive.org/en/download/) and report here whether this is still relevant?
Comment 5 Bug Janitor Service 2021-03-12 04:33:32 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2021-03-27 04:33:37 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!