Bug 487065

Summary: effects inside child-sequence do not render for parent sequence
Product: [Applications] kdenlive Reporter: Die4Ever <die4ever2005>
Component: Rendering & ExportAssignee: Jean-Baptiste Mardelle <jb>
Status: REOPENED ---    
Severity: major    
Priority: NOR    
Version First Reported In: 24.02.2   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: project file
screenshot

Description Die4Ever 2024-05-15 17:06:40 UTC
Created attachment 169508 [details]
project file

SUMMARY
I'm doing side by side videos, so I have a sequence "ramisme" with the video having a transform for 50% size and placement to the left, and a sequence "nitram" with 50% size and placed to the right. Sequence 1 has both seqeuences together, but the one on top (nitram) is full screen instead of 50% size. I tried this on 24.02.2 and the daily build 24.07.70

I've attached the project file, maybe this is reproducible with any other (1080p) video files.

STEPS TO REPRODUCE
1. make sequence named ramisme with transform for 50% video size and placed to the left
2. make sequence named nitram with transform for 50% video size and placed to the right
3. add ramisme and nitram to Sequence 1

OBSERVED RESULT
Nitram is taking up the full screen in both the preview and in renders

EXPECTED RESULT
it's supposed to give a split-screen result

SOFTWARE/OS VERSIONS
Windows: 10
Comment 1 Die4Ever 2024-05-15 17:10:46 UTC
Created attachment 169509 [details]
screenshot

interesting, the thumbnails on the tracks are correct, here's a screenshot
Comment 2 Die4Ever 2024-05-15 17:20:51 UTC
deleting and recreating the transform effect didn't seem to help
Comment 3 Die4Ever 2024-05-15 17:22:51 UTC
deleting the transformed videos in the child-sequences and moving them to the parent-sequence didn't work at first, it seemed like the parent-sequence had some cached info about the cihld-sequences. I deleted the cachefiles folder and restart the program, it asked me to recreate proxies and I did. Still had the same issue with the parent-sequence having cached data for the child-sequences. So deleted the child-seqeuences from the parent-sequence's timeline and readded them, and it's working now. But this is definitely a workaround, I would prefer to have kept these videos organized into child-sequences.
Comment 4 Jean-Baptiste Mardelle 2024-05-16 04:48:40 UTC
Oh, interesting! Looks like the fact that the track is locked in the main sequence prevents the update of the ramisme and nitram sequences. Unlocking the tracks (V1 and V2) in the main sequence and making a small change in the sequences (resize a clip), then sqitch back to the main sequence and all looks fine.

Will look into it.
Comment 5 Jean-Baptiste Mardelle 2024-05-16 06:50:13 UTC
Git commit b86f3740eed1d34e75e9bd52709c4ad9650d94c2 by Jean-Baptiste Mardelle.
Committed on 16/05/2024 at 06:49.
Pushed by mardelle into branch 'release/24.05'.

Fix sequence clip inserted in another one is not updated if track is locked.

M  +3    -2    src/timeline2/model/timelinemodel.cpp
M  +7    -10   src/timeline2/model/trackmodel.cpp
M  +2    -2    src/timeline2/model/trackmodel.hpp

https://invent.kde.org/multimedia/kdenlive/-/commit/b86f3740eed1d34e75e9bd52709c4ad9650d94c2
Comment 6 Die4Ever 2024-09-28 01:36:27 UTC
I just had the same issue happen again on a recent daily build. The transform effect wasn't applied in the render or in the monitor, no locked tracks at all. I think this is the 2024-09-15 daily build kdenlive-master-8820-windows-gcc-x86_64.exe and the About page says 24.11.70

It was an image clip and I was using the transform to make it smaller but in the render and on the monitor it took up the full screen.

Even restarting the program didn't help. I had to modify the child sequence in order for the parent sequence to correctly read the transform effect.

Could it be due to me copying the project file and making a 9:16 version of it inside the same project folder? They would've shared cache files?

I will say the issue seems less common now!