Bug 499632 - Timeline clip doesn't come in Glaxnimate background
Summary: Timeline clip doesn't come in Glaxnimate background
Status: RESOLVED DUPLICATE of bug 473036
Alias: None
Product: kdenlive
Classification: Applications
Component: Timeline & Editing (other bugs)
Version First Reported In: 24.12.1
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-07 05:52 UTC by ABRAR Shariyar Sabit
Modified: 2025-03-26 08:55 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ABRAR Shariyar Sabit 2025-02-07 05:52:55 UTC 
When a Glaxnimate animation file is opened from kdenlive timeline, clip which is behind the animation file doesn't come in Glaxnimate background. After closing and reopening both Kdenlive & Glaxnimate, it works.

Again & again closing-opening is very disturbing.
Comment 1 sherkhan30452 2025-02-15 07:31:03 UTC 
Please note: This is a duplicate of bug [473036](https://bugs.kde.org/show_bug.cgi?id=473036) but for older version of Kdenlive

Additional notes (important):
This bug occurs "ONLY" for windows OS (confirmed on Win10), but "NOT" on Linux OS (confirmed on Linux Mint 22.1 cinnamon 64 bit [AppImage])
Comment 2 sherkhan30452 2025-02-15 07:56:42 UTC 
Update:
Tested AppImage of Kdenlive and Glaxnimate; tldr - now works for linux but not for windows OS

No need to restart kdenlive in order for glaxnimate to show timeline. Also moved animation clip in kdenlive and double tapping the clip opens glaxnimate, shows updated timeline of kdenlive.

Under linux (working)
Kdenlive: 24.12.1
MLT: 7.28.0
FFmpeg
KDE Frameworks: 6.9.0
Qt: Using 6.8.0 and built against 6.8.0
Linux Mint 22.1 (Xcb)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.8.0-52-generic

Glaxnimate: 0.5.4+appimage-dc26f367
Comment 3 Jean-Baptiste Mardelle 2025-03-26 08:55:32 UTC 

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