Bug 433042 - Intrack transition doesnt work properly
Summary: Intrack transition doesnt work properly
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: Effects & Transitions (show other bugs)
Version: 20.12.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-17 02:43 UTC by Mohammed
Modified: 2021-09-04 04:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Kdenlive report from terminal output (43.44 KB, text/plain)
2021-02-17 02:43 UTC, Mohammed
Details
Same-track-transition_crash (40.41 KB, text/plain)
2021-03-10 18:32 UTC, emohr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mohammed 2021-02-17 02:43:34 UTC
Created attachment 135748 [details]
Kdenlive report from terminal output

SUMMARY
when I tried to use in-track transition it doesn't work 

STEPS TO REPRODUCE
1. put the first video on timeline v1.
2. put the other video after that video.
3. press on the video
4.press "u" or on the icon.
5.nothing happened.
6. try to cut part of the video and repeat , sometimes works ,but not every time. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Vincent PINON 2021-02-17 06:57:55 UTC
There should be a warning message in the status bar that to create a cross-fade you need extra-frames available after the end of 1st clip and before the beginning of 2nd clip, so both must have been cut before trying to apply the fade...
Comment 2 Mohammed 2021-02-17 08:48:45 UTC
(In reply to Vincent PINON from comment #1)
> There should be a warning message in the status bar that to create a
> cross-fade you need extra-frames available after the end of 1st clip and
> before the beginning of 2nd clip, so both must have been cut before trying
> to apply the fade...

Hi Sir:-
Why should I cut both clips?
sometimes I had no warning.
Comment 3 Julius Künzel 2021-03-08 23:09:55 UTC
You have to cut both clips because kdenlive extends the clips to create the transition, but clips can only be extended if there is footage left in the clip and that is the case if you cut (enough!!!) of clip.

The workflow is described here: https://userbase.kde.org/Kdenlive/Manual/Timeline/Editing#Same_track_transitions

Please check whether this solves your problem and close this report if so. Also check with the latest version (20.12.3 at the moment)
If this is not solved set the status to REPORTED again please.
Comment 4 Mohammed 2021-03-09 02:58:48 UTC
If the resolution of the two clips is different it doesn't work even if I cut both clips.

I have two clips one is 1920x1080 ,the other is 426x240 ,it doesn't work with them.

I noticed that it works with the same clip if cut it into more than a part.
Comment 5 emohr 2021-03-10 18:32:37 UTC
Created attachment 136561 [details]
Same-track-transition_crash

I can produce a crash as well. Add a 1920x1080 clip; the other is 500x451 animated gif. Shorten the 1920x1080 on the right and shorten the 500x541 on the left. Add a same track transition. Move the 500x541 back and forth and lengthen and shorten it. Upon some shorten Kdenlive crash.
Comment 6 emohr 2021-03-10 18:36:32 UTC
added to: https://invent.kde.org/multimedia/kdenlive/-/issues/796
Comment 7 Jean-Baptiste Mardelle 2021-08-04 19:51:16 UTC
I cannot reproduce the issue anymore on 21.08 or master branch. Several changes were made recently to mixes that might have fixed this. Please test again with a recent AppImage to see if issue is reproducible for you.
Daily Appimage is available here:
https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/
Comment 8 emohr 2021-08-05 14:36:41 UTC
With the Windows daily build 844 I cannot reproduce the crash anymore.
Comment 9 Bug Janitor Service 2021-08-20 04:36:30 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 10 Bug Janitor Service 2021-09-04 04:35:54 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!