Bug 388502 - Composite and transform: Stopped working
Summary: Composite and transform: Stopped working
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Effects & Transitions (show other bugs)
Version: 20.08.1
Platform: Mint (Ubuntu based) Linux
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-03 22:18 UTC by Tuomo Sipola
Modified: 2020-10-07 11:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: Brainstorm+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tuomo Sipola 2018-01-03 22:18:12 UTC
Composite and transform transition effect: Cannot set coordinates higher than 99000 or smaller than -99000 from the GUI.

To reproduce:
Video track 1: any video
Video track 2: a long image that is supposed to scroll at the bottom, like news headlines or stock tickers
Add Composite and transform transition to video track 2. 
Try to set transform coordinates X, Y or width W or height H to a number bigger than 99000 or smaller than -99000. 

What I expected: Be able to use big numbers in X, Y, W and H.
What I got instead: the maximum is 99000 and minimum is -99000.

Note: it works correctly (but still shows the maximum numbers) if changed from the XML save file, so it is just an arbitrary GUI restriction on the coordinates. Setting it manually to, e.g., 500000 works fine.
Comment 1 Vincent PINON 2018-01-07 21:42:26 UTC
Hello,
True that our widgets ask for a limit, we believed these would never be reached ;)
Isn't memory consumption jumping too high with very large images?
I've seen such problems with MLT allocating a frame buffer of the largest coordinates on a track...
Maybe using the titler to do the scrolling (even on an image) could be a better solution?
Comment 2 Tuomo Sipola 2018-01-08 07:34:56 UTC
(In reply to Vincent PINON from comment #1)
> Hello,
> True that our widgets ask for a limit, we believed these would never be
> reached ;)
> Isn't memory consumption jumping too high with very large images?
> I've seen such problems with MLT allocating a frame buffer of the largest
> coordinates on a track...
> Maybe using the titler to do the scrolling (even on an image) could be a
> better solution?

I thought that you might comment something like that :D
I didn't experience any memory problems that I know of. The image itself is just a few MB. 
I tried to research options and found the Composite and transform the easiest (and only) one that could scroll and scale the image. I'll have to give the titler a look.
Comment 3 Christoph Feck 2018-10-10 20:20:47 UTC
> The image itself is just a few MB.

On disk? In memory, an image needs 4 bytes per pixel, so if you have 1920x200000 pixels, it would already be 1.5 GByte.
Comment 4 Elifaz 2020-09-29 17:18:47 UTC
composite and transform just stopped working, the other functions are OK, but when inserting a composition it just doesn't work.
I've reinstalled, but the problem remains, please can someone help me ??
Comment 5 emohr 2020-09-29 18:42:09 UTC
Please check with the daily AppImage. https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/

Please upload your project file here so we can have a look.
Comment 6 Elifaz 2020-10-05 13:54:16 UTC
Good morning, thank you friend, the problem has been solved! I found that the effect actually needs to be "linked" to a layer. My mistake was not to fix the layer to the effect, so it didn't work.
Thank you very much for your attention!
Comment 7 emohr 2020-10-07 11:44:57 UTC
Thank you for the feedback. Glad to hear it works. 

We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.