Summary: | The tool to change the speed of the project folder does not work well | ||
---|---|---|---|
Product: | [Applications] kdenlive | Reporter: | rafamar.mm.ig |
Component: | User Interface | Assignee: | Jean-Baptiste Mardelle <jb> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fritzibaby |
Priority: | NOR | Flags: | fritzibaby:
Brainstorm+
|
Version: | 19.04.2 | ||
Target Milestone: | --- | ||
Platform: | Mint (Ubuntu based) | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | speed-job_18-12_19-04 |
Description
rafamar.mm.ig
2019-06-13 12:54:46 UTC
Created attachment 120887 [details]
speed-job_18-12_19-04
Do you mean: clip job -> duplicate clip with speed change?
(In reply to emohr from comment #1) > Created attachment 120887 [details] > speed-job_18-12_19-04 > > Do you mean: clip job -> duplicate clip with speed change? The tool of version 18.12 never gave me problems, towards bin their work, I do not see any improvement in the new tool. I tested with a value of 50% in version 19.04 and it does not work, it creates the new clip but it does not change the speed. It only serves to accelerate. Thank you for reporting. I opened 2 issues: - https://invent.kde.org/kde/kdenlive/issues/261. The behavior you have is confirmed already and I get a crash applying speed change. - https://invent.kde.org/kde/kdenlive/issues/262 for re-implementing the destination possibility from 18.12. (In reply to emohr from comment #3) > Thank you for reporting. I opened 2 issues: > > - https://invent.kde.org/kde/kdenlive/issues/261. The behavior you have is > confirmed already and I get a crash applying speed change. > > - https://invent.kde.org/kde/kdenlive/issues/262 for re-implementing the > destination possibility from 18.12. ok thank Issue https://invent.kde.org/kde/kdenlive/issues/261 is fixed. You can try with the daily build: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ Yes, now it seems to work with values lower than 100% but still can not choose the location and name of the mlt file in case you want to create several versions at different speeds, perhaps the solution would be an automatic rename incremental or that the file included in the name the numerical percentage used. Currently if I make a version but then I decide to do another with another percentage what happens is that the application closes suddenly (crash) Issue 261&261 should be fixed. Please try with the daily build: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ As https://invent.kde.org/multimedia/kdenlive/-/issues/262 is implemented as well we close this issue. If it still appears in the latest version, please feel free to re-open it and update the affected version number. |