https://bugs.kde.org/show_bug.cgi?id=491601

            Bug ID: 491601
           Summary: Transcoding from VFR to CFR does Nothing
    Classification: Applications
           Product: kdenlive
           Version: 24.05.1
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: Video Display & Export
          Assignee: j...@kdenlive.org
          Reporter: ammarzawar...@gmail.com
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
When it tries to transcode a video from VFR to CFR via 'Lossy x264 | frame
only', it doesn't do anything.

STEPS TO REPRODUCE
1.  Import any framerate with a variable framerate.
2.  Kdenlive will say that this you need to transcode it into a constant
framerate video. Let it transcode with 'Lossy x264 | frame only'.
3.  Now let it transcode.

OBSERVED RESULT
The video makes a copy of itself, with the original name and the new framerate
appended to it. Kdenlive automatically replaces the old one with the copy, but
the framerate is completely unchanged, so it's still VFR. Kdenlive recognizes
this, and tells you to transcode it to CFR, causing an unending cycle of failed
transcoding.

EXPECTED RESULT
The video makes a copy of itself, with the original name and the new framerate
appended to it. Kdenlive automatically replaces the old one with the copy, and
since it's now CFR there are no more issues.

SOFTWARE/OS VERSIONS
Windows: Windows 11 Home, Build 22631
KDE Frameworks Version: Version 6.3.0
Qt Version: Version 6.7.1 (built against 6.7.1)

ADDITIONAL INFORMATION
CPU: AMD Ryzen 5 3600
GPU: Nvidia RTX 3060
RAM: 12 GB
They also get bigger for some reason.

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

Reply via email to