Bug 480073 - please get rid of auto fade in/out when clicking on an end of a clip in a timeline track intending to stretch/shrink it
Summary: please get rid of auto fade in/out when clicking on an end of a clip in a tim...
Status: REOPENED
Alias: None
Product: kdenlive
Classification: Applications
Component: Timeline & Editing (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2024-01-19 23:49 UTC by djhbrown
Modified: 2024-12-24 08:25 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description djhbrown 2024-01-19 23:49:38 UTC
it is not always desired and often happens because not all users have giant screens, 20-20 vision, and tiny fingers for precision mouse control
Comment 1 emohr 2024-12-22 20:03:47 UTC
Are you using Kdenlive on a touchscreen without using a mouse?
Comment 2 djhbrown 2024-12-22 21:14:34 UTC
emohr: i guess it must be hard to imagine what it might be like to be someone else with different eyes and fingers, but for the record, my environment is 1920x1024 display full screen mode when using kdenlive; wireless logitech optical mouse on a flat surface.   Aside from my defective physical precision dexterity and imperfect optical acuity which make me unlikely to succeed as a professional darts player or concert violinist, it is not even 50% of the time that one wishes to fade in or out a clip, so it should not be a default action.
Comment 3 Bernd 2024-12-22 23:47:43 UTC
(In reply to djhbrown from comment #2)
> emohr: i guess it must be hard to imagine what it might be like to be
> someone else with different eyes and fingers, but for the record, my
> environment is 1920x1024 display full screen mode when using kdenlive;
> wireless logitech optical mouse on a flat surface.
I have an old laptop with 1600x900 and a touchpad, so my environment is less suitable for video editing than yours.

> Aside from my defective
> physical precision dexterity and imperfect optical acuity which make me
> unlikely to succeed as a professional darts player or concert violinist, it
> is not even 50% of the time that one wishes to fade in or out a clip, so it
> should not be a default action.
I am sorry for your personal circumstances and can understand that your mouse may stray to the top right corner of the clip when trying to just grab the edge of the clip or clicking it. Here my suggestions: a) click on the clip closer to the center to avoid hitting the corners, then grab the edge to drag it; b) make the track taller by dragging the bottom edge of the track down, you can always collapse that track when working on another one; c) zoom into that area of the timeline to make the clip wider for more precise control of your actions.
Comment 4 djhbrown 2024-12-23 01:45:33 UTC
at the risk of belabouring the obvious, with typically 8 or more tracks, even 1024 pixels is not enough to accommodate them all, let alone make it worse by expanding or zooming to skirt around design flaws.  your suggestion is akin to flooding the screen with bugspray to stop bugs that don't need to be there in the first place.  my clip is done; i now fade out ad aeternum.
Comment 5 Bernd 2024-12-23 15:24:44 UTC
(In reply to djhbrown from comment #4)
> at the risk of belabouring the obvious, with typically 8 or more tracks,
> even 1024 pixels is not enough to accommodate them all, let alone make it
> worse by expanding or zooming to skirt around design flaws.  your suggestion
> is akin to flooding the screen with bugspray to stop bugs that don't need to
> be there in the first place.  my clip is done; i now fade out ad aeternum.
Thanks for your reply. I just tried to help by offering ways to work around this issue. The hot spots (dots or circles) in the clip's corners are not going away as they are a great feature and not a problem for the vast majority of the users. I am sorry that in its default state it causes difficulties for you, that's why I suggested a few things you can do to improve the situation. But no obligation to use them, of course.

I am closing this bug report. You may reopen it any time.
Comment 6 Bernd 2024-12-23 20:46:25 UTC
Set to "wishlist"
Comment 7 djhbrown 2024-12-23 21:18:25 UTC
whereas my normal predilection is to simply give up in the face of obstinacy because it's not worth the effort, and had already done so,  on second thoughts in this case i will persevere in a Christmas spirit of self-sacrifice for the common good.
1) whereas i am not a famous computer programmer, i have published post-doctoral research on human-computer interface design and taught it at university for over 9 years - see "Adopt, Adapt, Improve" https://www.youtube.com/watch?v=Nc4GIaPT61I&list=PL4y5WtsvtduozO-9oG5nZZI8IPUD6EDif&index=9&t=386s&pp=gAQBiAQB - which refers to MIT's HCI open courseware so my opinions on this matter are not purely subjective.
2) as a matter of principle, an issue such as a bug or design flaw (two different kettles of fish, but which both stink) cannot be resolved by a perpetrator of that flaw, but only by common consent, unless kdenlive is an autocracy (which of course, in practice, it is).  So it is the duty of the bug filer to declare it resolved, not the right of a heavy-handed opinionated developer or onlooker.
3) whereas taste is by definition a matter of taste, usability is not.
4) lack of complaints does not imply satisfactory.  it only implies apathy or desertion to another video editor.
5) i have only about 10 man-years of kdenlive use experience, but i submit that only a highly trained diminutive chinese female teenager seamstress has eyes sharp enough and fingers dextrous enough to routinely avoid the clunky and **entirely unnecessary** "hot spot" every time.  i hadn't complained to bug reports about this "feature (aka flaw)" for 10 years, but it was an irritation even before my now aged eyes worsened.
6) my case is laid out in this and my preceding comments, and Bernd has laid out his case against my case in his comments, so neither of us has anything more profound to share with the bug report community.  It is for others to have their say, until such time as a clearer picture evolves, or a developer takes matters into his own hands and does the right thing by eradicating the bug.  If you want a clip faded, fade it.  But it shouldn't be an effectively default setting.
7) It should be obvious to all that i cannot convince Bernd and he cannot convince me.  I am only going to repeat (since it didn't get through to him the first time) that Bernd's workarounds are impractical, because it takes too much effort to zoom in and back or widen and narrow every time an unnecessary  hotspot gets accidentally trodden on.  A hotspot that shouldn't be there, because it's less than half the time that anyone wants a clip to fade in or out.  That should be obvious to everyone, but it obviously isn't obvious to Bernd.
8) Therefore, Bernd and i should both shut up now and let the rest of you have your say, if you give a damn, which i expect most of you don't.
9) When is a bug not a bug?  When it's a wish??  A wish for a usability bug to be squashed!  It's not only computers that have bugs, people's design ideas have them too.  I recommend heartily the MIT courseware's "rogues gallery", to which should be added this kdenlive design flaw.
Comment 8 djhbrown 2024-12-23 21:24:57 UTC
talking of design flaw bugs, i can't edit the my fault error in my previous comment, which takes a clicker to the end of the video instead of the beginning, because that's what Google thinks is appropriate because that's where i left off last time.  ok, i give up.  usability is lost and gone for ever everywhere.
Comment 9 emohr 2024-12-24 08:25:01 UTC
We could implement on the settings page a tick to enable/disable the dot on the clip for:
-	Fade in / fade out
-	Composition