Crashing (always) in Preset under "Size Position Rotation"

[Klaus-Nomi]

Hello Dan,

regrettably I found an replicable error in Shotcut

which always leads to a crash without prior warning.

I hope it was not mentioned before from another member.

If you want to follow me, please go to Shotcuts very upper

left of the screen and ..

1.) click on FILE
2.) then choose OPEN OTHER
3.) then choose COLOUR (no matter what color you take)
4.) then choose ADD TO TIMELINE
5.) then expamd the timeline to the millisecond-range
so that you can see the small item and expand it
to 2 or 3 seconds to make sure you can see it.
6.) mark the little thing and then choose FILTER and
7.) choose “SIZE, POSITION, ROTATION” as a filter.
8.) then choose (inside the Filtersystem) “PRESET”
9.) if you now choose “SLIDE IN FROM RIGHT”
the whole Shotgun-System crashes. Always.
If you choose any other option of the many
options (for example slide in from the left)
the command is executed or at least tolerated.

I still do not fully understand the keyframe-concept.
I have mental shortages to draw lines and rectangles
in a smooth and elegant way with Shotcut and possibly
spent way too much of my remaining tine with it.

Nonetheless, kind regards

Thomas

Attachments: 2 printscreen-Images.

[Klaus-Nomi]

to illustrate I attach two screenshots:

[Hudson555x]

I have tried to duplicate this issue, but could not make Shotcut crash.

@Klaus-Nomi

5.) then expamd the timeline to the millisecond-range
so that you can see the small item and expand it
to 2 or 3 seconds to make sure you can see it.

Zooming in on the timeline does not change the length of the clip. I only state this for clarification.

In your screenshot, it shows that you have a clip length .640 of a second. The stock presets are set for 1 second (1.000). It would only slide the clip so far and then stop, as shown in my screenshot.

Have you tried a clip length of 1 second or more?

I have tested with Shotcut version 25.12.31, Windows 10 Home.

[MusicalBox]

Hi @Klaus-Nomi

Tell me if I did something different from what you explained.
I don’t experience crashes when following your steps

Note: You mention that you also expand the color clip. I don’t do it in the clip above, but even with that step, still no crashes.

I’m using version 25.12.31 on Windows 10.
It would help the developers if you also provide your operating system and Shotcut version.

[MusicalBox]

@Hudson555x

In your screenshot, it shows that you have a clip length .640 of a second.

I didn’t catch that.

But even with a 00:00:00.040 clip, still no crash for me either.

[Klaus-Nomi]

I am using:

Lx Mint 7.0.7.1
Shotcut 25.10.31

Hello Dan, I received your e-mail and I will try
your recommendation to expand the duration of it
on timeline and check if Shotcut still crashes
once I prolong it to 2 or 3 seconds given to it.

If Shotcut NOT crashes on your windows 10 home,
then it might be that my Linux Mint is a reason?

But I had a basic problem already in my Shotcut preversion.
Every sober user would suggest to use Glaxinate for this
kind of work, but Glaxinate is .. bloody complicated.

If you want to follow my “basic” problem too, please go to
Shotcuts very upper left portion of the screen and ..

1.) click on FILE
2.) then choose OPEN OTHER
3.) then choose COLOUR (to calm the mind choose dark green FF 00 55 00)
4.) then please give the command “ADD TO TIMELINE”
5.) to be able to view the tiny item now on the timeline
you need to expamd the timeline into the millisecond-range
and then enlargen the tiny thing.

6.) mark the now enlarged item (it is red framed after being marked) and
choose filter “SIZE, POSITION, ROTATION” to which I refer to as SPR-Filter.
7.) What you see then is what you expect to see (see attached screen-shot 1)

8.) Now simply apply another (a second) SPR-Filter on the same item and the
anomaly occurs instantly. It is the little pit (see attached screen-shot 2)
which occurs in all 3 modi of the “SIZE MODE” section. This little pit
is the reason for lots of other problems which I will shut (not shot) up on.

I do not understand that this pit occures and I have not heard from
anyone or anywhere that this even happened to someone else.

What I know is that I lost too much time with my obsession to search
for the reason of this pity to circumvent it. I failed and I am exhausted.

Even an idiot like me knows it is a banality, a nothingness. Was it worth this?
Certainly not. And yes, I have given up on it. Therefore call me loser (haeh haeh).

Thomas

Attachment(s): 2 printscreen-Images.

[Hudson555x]

@Klaus-Nomi

I do not understand that this pit occures and I have not heard from
anyone or anywhere that this even happened to someone else.

That is a filter handle you had circle in yellow. Something for you to grab with the mouse and drag where you want. It will not show in your exported file.

You can deselect the filter. Filter remains as you had set it. To adjust, click on the filter again to reselect it. All settings remain unchanged.

[dimadjdocent]

I’m also running Linux Mint 22.2.
I’m not having any problems. Maybe I did something wrong? Try changing the application interface language to English; that might be the issue.

[Klaus-Nomi]

Hello Hudson 555,

my first attached screenshot (the one with my big yellow comments)

shows in the large circle on the right side a gap between the right

edge and the FULL size of 1920 that should end on the thin grey

line on its right side. The drawn green line ends approx 20 oixels

before its supposed end at 1920. The handle normally has no

influence on the length of the line.

I will immediately send an expansion or

addition to my message from yesterday.

Thank you very much.

[Klaus-Nomi]

Hello everyone,

I must admit that Dan´s recommendation was crucial.
Prolonging the runtime to 1,5 seconds Shotcut works
flawlessly. This adds to my shame since this problem
existed only with a TOO SHORT runtime for the item.

I even cannot reconstruct the problem now and
that perplexes me even more.

To my shame I must confess that I would have never
asked this forum to care about my second problem
which I described yesterday the first time and which

was answered by Herderson 555 already. But it is

unlikely that the handle of the SPO manipulator is the error.

It is really very weird. While the first problem
(a hard crash) seemed to be crystal-clear.

In yesterdays list to describe “the real” error
that bothers me since weeks and on which I worked
so very long in vain I committed another mistake.

Between the points 7 and 8 I should have added
further text that you missed. It should have said:

7-8.) Now please select (or click) in the
“Size Mode” box first the command “Distortion”
and then enter these numbers into the boxes:

      0      530
   1920       20

(into the 2 position- and 2 size boxes) to obtain the
image shown in my first screenshot which shows a perfect
thin green horizontal line in the middle of the screen.

Ashes over my head.

But the rest is not a phantasy.

Thank you soo much, thank you.

Thomas from Portugal

[Hudson555x]

@Klaus-Nomi I was mistaken in understanding what you were talking about.
While your word “pit” was close enough, I had failed to read it properly. Others may call this a gap.

It has something to do with how the second filter added affects the first. I admit, I do not understand it myself, and know the highly intelligent folks in here might be able to explain it.

Is there a specific reason for the 2nd SPR filter?
What are you trying to accomplish?

[Hudson555x]

You could try this instead:
First filter: Crop: Source - Top set to 1060 (20px left)
Second filer: SPR, no adjustments as in your screenshot
No gap, or as you call a pit.

[Klaus-Nomi]

Thnky Hudson555x,

excuse me for greeting you as Henderson555 the last time. Your name

is Hudson like the river in N.Y. and like the explorer who gave the river his name.

Yes, I explain what I intended to do. The 2nd filter should be completed with one

command. With one command from the rich filled preset-box which contains

so many pre-fabricated functions and is situated directly above the box with

the number 0 1920 530 and 20. - It is easy. If you pick out “slide in from the left”

the small line starts to work its way to the right side. You can fine tune this in

the keyframe box, but it works normally instantly. But the problem is the gap,

as you rightly expressed it. The line stops before it has completed its

full rum to the right and it stops appromimately at 1900 or at 1895 and

NOT at 1920. That hinders me to set up another, third, filter, because

the whole construct is now inconsistant, so to speak.

This works in the vertical way without problem, by the way.

From top to bottom and from bottom to top. If you export these

lines you can build a kind of toolbox with these running lines in

various colours and thicknesses.

But with this gab I cannot prefabricate (compile or export) my

prefabricated horizontal lines which I intended to use for all kinds

of text- and line- related effects.

If no one knows where the errors hides I will give up on it.

Thank you very much for your attention.

Thomas

[Klaus-Nomi]

@Hudson555x

You could try this instead:
First filter: Crop: Source - Top set to 1060 (20px left)
Second filer: SPR, no adjustments as in your screenshot
No gap, or as you call a pit.

Yes, I copied your above explanation and will check

if it works out. I come back tomorrow, thank you.

Klaus-Nomi

[Klaus-Nomi]

Now I see it has been a week since I told you to “come back tomorrow”, sorry,

Yes, your workaround is possible, there are some other workarounds if it would

be the only goal to compile (or export) just the building up of such a horizontal line.

But on the other hand it is a “cul de sac”, or “dead end” in english, because a

further build-up of the development of that line is then undermined.

But as I said, I have given up. It is not worth to spend more time on this trifle.

But one question I still have from a former existential Shotcut problem.

I still shy away from upgradimg to KDE Application Platform 6.10 because

I fear that I will then run again into the trouble with the Shotcut’s textboxes.

Or has this problem been somehow cleared by acclaimed developers?

Beside that question, and as far as I’m concerned,

you can delete this helptopic now.

Thanks, to all of you. Eventually I will contribute again some money, since I am

working on a film with which I want to sell my apartment here. Once done I will

do so (again), but then surely a higher sum. I love Shotcut.

Behave yourselves

Thomas

[shotcut]

@Klaus-Nomi

I fear that I will then run again into the trouble with the Shotcut’s textboxes.

That problem is fixed in Qt 6.10.1, released Nov. 20 2025, which we started using in some of our builds such as Flatpak and Windows. It might still be too new for a distribution that updates conservatively.