Stopmotion thread

I’d like to announce the release of the Stopmotion animation app, Stopmotion :slight_smile: It’s already available at:
Stopmotion | OpenRepos.net — Community Repository System but should be coming to the Jolla store and chum soon.

In short, it’s an app to make timelapse series of photos, assemble them into scenes and produce a stopmotion animation/video. You can get an idea of what final output looks like with: https://github.com/poetaster/harbour-stopmotion/raw/main/Legovsschleich.mp4

Think: Jan Švankmajer - Wikipedia claymation, Wallace and Gromit, etc, etc.

Currently, you can select a camera (selfie camera can be flaky), set interval and choose where to store the series of name that you specify. With the ‘slideshow’ view (thanks @pinniini !) you can assemble as scene/series with a picker. You can preview that with the ‘Start Slideshow’ pully, step through the images, and finally return to save. The output fps can be specified. Currently saves to /home/$/Videos.

It’s still in the late alpha stage. So I’d love feedback. Some things that are in the works:

  1. Add more that one scene (creat an entire animation film on your summer vacation).
  2. create sub-dirs for scene/series automatically
  3. select resolution (currently locked to hd)
  4. etc.
8 Likes

It’s in chum, thanks @rinigus !

2 Likes

Thanks poetaster, this looks fantastic…at least potentially. I just did a little trial, the ‘Start slideshow’ wasn’t easy to find! (typo alert, it says ‘Sart’)…and I think it would be better if it didn’t automatically repeat.
I installed from openrepos, the ‘installing’ spinner never stopped spinning. The work in progress features look great.

Thanks! You mean the pully wasn’t easy to find? I’m mixing a few too many interface styles, perhaps?

I’m not sure why the installing never stops spinning, but I did make ffmpeg a requires so maybe that’s an issue? I’ll see if I can debug it…

As usual the pulley is easy when you know it’s there. A useful addition would be more FPS options, especially slow ones like 1 frame every 5 seconds.
The spinner does that frequently, I don’t know if it’s a store thing or particular to the xz2c.

Quite sure that’s not app-specific, rather a bug/issue with Storeman. I see it often.

Also, as packagekit will install all available app updates on any install action, triggering a single install can cause many downloads and install events to happen - which can take longer than expected.

and packagekitd lets clients wait in a queue, so if there’s a pkcon refresh happening while issuing an install command, it may also take a longer time than one would think.

1 Like

It’s in the works. I wanted to implement those in the ‘slideshow’ preview and haven’t gotten to it yet…

The Stopmotion package is small, but I also install ffmpeg which is 3.7 MiB in size. I also include ffmpeg-tools, which is only 134 KiB, but might also be an issue with the call-backs to the ui ‘timing out’ improperly?

I’ve implemented Seconds per frame / Frames per second choosing, a loop toggle and a canvas based display for fast animations. Anything about about 9/10 FPS can’t be rendered cleanly using Image. Sadly, the canvas suffers from the famous RGB channel swapping issue. I have a version with a custom image provider in the works to fix the canvas slide show mode.

Updates should come in over the course. of the day.

Because I’m piqued I implemented the c++ ImageProvider and nemoimagemetadata classes on a second branch:

This will do fast animations (only tested to 30 fps) without artifacts. It also reads the image data correctly so that the orientation AND the color values apply.

some more thoughts: would it be possible to select advanced camera instead of native? - the exposures are better.
Also, the time intervals are critical at the lower end, there’s a big difference between 1 and 2 seconds but not much between 8 and 9. The ideal would be select your own.
This is shaping up to be a great app.

When I get to using other backends than the declarative. It’s in the works.

I’d like to get under a second. This is not possible with declarative snapping and writing to disk. So, again, backend work. I’m hoping to use @karry work but it’ll take some time. And the intervals SHOULD (EDIT!) be fixed, it’s still a hack. As is the folder selection interface.

Thanks, it’s fun to do!