Bug 477984 - 9:16 video can't display subtitle correctly
Summary: 9:16 video can't display subtitle correctly
Status: RESOLVED DUPLICATE of bug 480350
Alias: None
Product: kdenlive
Classification: Applications
Component: Rendering & Export (show other bugs)
Version: 23.08.4
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-03 12:44 UTC by red_Arti
Modified: 2024-01-26 02:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
subtitle-bug (17.25 KB, application/zip)
2023-12-03 12:44 UTC, red_Arti
Details

Note You need to log in before you can comment on or make changes to this bug.
Description red_Arti 2023-12-03 12:44:39 UTC
Created attachment 163813 [details]
subtitle-bug

SUMMARY
I'm reporting bug. I'm not sure that's one bug or several bugs.

Create a project in this format:
Frame size: 1080 x 1920 (9:16)
Frame rate: 25 fps
Pixel aspect ratio: 1
Color space: ITU-R 709
Interlaced: no

STEPS TO REPRODUCE
1. Create project in above 9:16 format
2. In Sequence 1, add a subtitle line by `shift+s`
3. Add a picture to video track
4. Create a new Sequence 2
5. In Sequence 2, drag Sequence 1 to add 1 into 2's track

Bug: Now you can see in sequence 2 it fails to display Sequence1's subtitle

6. Save project (as I upload the zip file)
7. Close Kdenlive

Now 
- If you open Kdenlive first then open the project from "Recent", the subtitle line can be seen in Sequence 1 only. 
- If you double-click the project file in filemanager to open it with Kdenlive, you can't see the subtitle line in neither Sequence 1 nor 2.

And... The generated .srt file seems not bound to any sequence

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Kdenlive 23.08.3 Flatpak on Linux x64

ADDITIONAL INFORMATION
Comment 1 red_Arti 2024-01-26 02:05:26 UTC
Closing this. It turned out nothing to do with video ratio.
I open another https://bugs.kde.org/show_bug.cgi?id=480350 to describe the real bug

*** This bug has been marked as a duplicate of bug 480350 ***