| Summary: | The clip monitor should show the clips in the timeline | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | Guido <guido.iodice> |
| Component: | User Interface & Miscellaneous | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | julius.kuenzel |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | All | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Guido
2021-09-04 09:00:03 UTC
Thanks for your report! There is already an action to raise the selected clip in the project bin and project monitor ("Clip in Project Bin"). You can define a custom shortcut via menu Help > Configure Keyboard Shortcuts… and you can reach it on the context menu of a timeline clip.
I am not sure if you are aware about all the different ways of applying an effect, because usually it only depends on the clip shown in the clip monitor if you want to apply it on bin level. In Kdenlive you can add effects on multiple levels: to a timeline clip (most common), to a track (or track region), to everything (master) or to a bin clip (affects all the children in the timeline).
I don't think it makes much sense to raise the selected timeline clip automatically as it would brake several other workflows, I guess.
Please check if my tips help you with your workflow and if this report can be closed. Otherwise please give more details on the workflow you requested this for…
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! 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! |