Bug 408198 - Export Image Sequence First Frame stuck on 60
Summary: Export Image Sequence First Frame stuck on 60
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Animation (show other bugs)
Version: 4.2.0-beta
Platform: unspecified Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-02 02:39 UTC by Ricardo
Modified: 2019-09-05 08:21 UTC (History)
1 user (show)

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


Attachments
Start Value cant go lower than 60 despite having animation from 0 to 130 (58.99 KB, image/jpeg)
2019-06-02 02:39 UTC, Ricardo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ricardo 2019-06-02 02:39:34 UTC
Created attachment 120491 [details]
Start Value cant go lower than 60 despite having animation from 0 to 130

SUMMARY
I made a animation sequence from 0 to 130 frames.
when I tried to export the image sequence I could only export 60 to 130.
I am not sure how well it is possible to reproduce this bug.

STEPS TO REPRODUCE
1. make animation with 0 to 130 frames
2. export image sequence
3. Try to export the full sequence

OBSERVED RESULT
export from 60 to 130 frames

EXPECTED RESULT
export from 0 to 130 frames

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Ahab Greybeard 2019-06-02 06:54:55 UTC
This is probably caused by your Animation Docker having a start frame number set to 60. Can you check that?

The last frame number of Rendering is not limited in a similar way.

I think this is a Usability bug.
Comment 2 Halla Rempt 2019-06-03 14:09:51 UTC
Git commit b5e9fba81967da7450c2d567a7375a89cdc2295e by Boudewijn Rempt.
Committed on 03/06/2019 at 14:08.
Pushed by rempt into branch 'master'.

Allow the animation render to start at 0 at all times

We probably should warn the user that they are rendering from a
different place than the animation starts, but we should not
forbid it, so we need to think of how we might implement that
warning.

M  +1    -1    plugins/extensions/animationrenderer/DlgAnimationRenderer.cpp

https://invent.kde.org/kde/krita/commit/b5e9fba81967da7450c2d567a7375a89cdc2295e
Comment 3 Halla Rempt 2019-06-04 15:21:33 UTC
Git commit 6e19515de1d9401ad764ffb966311309d6fbe929 by Boudewijn Rempt.
Committed on 04/06/2019 at 15:19.
Pushed by rempt into branch 'krita/4.2'.

Allow the animation render to start at 0 at all times

We probably should warn the user that they are rendering from a
different place than the animation starts, but we should not
forbid it, so we need to think of how we might implement that
warning.

M  +1    -1    plugins/extensions/animationrenderer/DlgAnimationRenderer.cpp

https://invent.kde.org/kde/krita/commit/6e19515de1d9401ad764ffb966311309d6fbe929
Comment 4 Ricardo 2019-06-05 01:04:28 UTC
I checked it and yes it was my start frame set to 60 =0!

I am so sorry to have reported this as a bug I really do not recall myself setting the start frame to 60 at all.

I am so sorry and thank you so much to have helped me out with this *embarassed*
Comment 5 Ahab Greybeard 2019-06-05 05:04:55 UTC
@Ricardo: As a result of you making this bug report, krita has been improved and now gives a better user experience :)