Bug 370746 - Export clip zone exports wrong zone when clip fps differs from project fps
Summary: Export clip zone exports wrong zone when clip fps differs from project fps
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Display & Export (show other bugs)
Version: 17.04.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-14 15:11 UTC by oluja
Modified: 2021-05-04 04:33 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: Brainstorm+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description oluja 2016-10-14 15:11:16 UTC
When define a inpoint and outpoint in the clip monitor and drag this file to te timeline, this is working well. But using the feature "extract zone" an completly different part of the video will be extracted.

Reproducible: Always

Steps to Reproduce:
1. mar in adn outpoint in the clip monitor
2. right click and choose "extract zone"
3.

Actual Results:  
wrong part of the video is extracted

Expected Results:  
correct part should be extracted

ubuntu 16.04.1 LTS (brand new installation)
kdenlive 16.08.2 (cant choose this version in the bugtracker)
Comment 1 Wegwerf 2016-10-16 16:55:23 UTC
Can you please supply more details, such as project profile and which clips you were using? Especi6the frame rate might be important.
Comment 2 oluja 2016-10-17 05:13:42 UTC
Hello Wegwerf,

your comment opened my eyes. The project was set to 720 p and 24 frames but the video was 720p and 30 frames. I dont thought that this have impact on the extracted zone. Especially because kdenlive extracting an part from the beginning. so i dont have the idea the the project settings cant be the problem.
But, i changed it to the same settings and it is WORKING now.
So great. Im very happy now!

Maybe you can add an info that when somebody extracting a zone but the project settings fit not the video resolution/framerate.

Thank you for your comment which help me to fix this. :-)

Can i close this somehow or must this be made by your side?

Regards, Oluja!
Comment 3 Wegwerf 2016-10-17 05:59:38 UTC
Thank your for reporting back. Glad you could solve the issue. I suggest that we keep the bug report open, so JBM can look into the underlying issue. I would suspect that this is still a bug, as the export should correctly handle such situations where project and clip frame rates differ.
Comment 4 drew 2017-06-27 08:47:56 UTC
I'm on Mint 18.1 with kdenlive 17.04.1 and was pulling my hair out over the extract zone mismatch.

My project was Full HD 1080 > HD 1080p 30fps profile by default, but my clip from a Sony Handicam was 1080p 25fps MTS format.

The zone delineated in the preview window and the resulting extracted clip were consistently offset.

Changing my project fps to 25 immediately solved the issue.

If it is not practical to fix the extraction function, I recommend that kdenline implement a notification of fps mismatch when importing a clip and a reminder that the extract tool will not work.
Comment 5 Julius Künzel 2021-04-04 09:48:34 UTC
I tested with 20.12.3 and can not reproduce anymore. Can you please update to the latest version (20.12.3 at the moment, https://kdenlive.org/en/download/) and report here whether this is still happening?
Comment 6 Bug Janitor Service 2021-04-19 04:33:14 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 7 Bug Janitor Service 2021-05-04 04:33:36 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!