barefootstache @barefootstache@qoto.org

#DailyBloggingChallenge (280/300)

There are definitely much more examples until one gets to highways.

Although most highways are more convenient than the previous mentioned examples, one factor one needs to consider by them is personal safety factor.

#DailyBloggingChallenge (279/300)

Depending on the season farmland can be either more or less convenient than a forest. The same can be said for heath, grassland, or meadow.

Scree, rock, and sand depends if an incline exists as an inconvenience factor.

#DailyBloggingChallenge (278/300)

The least convenient for most is water crossings; anything from large bodies of water like lakes or rivers all the way down to ditches or wetlands.

Next would be either a man-made barrier like a wall or building or a plant matter wall like scrub.

#DailyBloggingChallenge (277/300)

Let us take the case that one is planning to explore a new region via foot using #OpenStreetMap data. Then what should be the first amenities that should be mapped?

The first amenities should be anything that inconveniences travel while being outside of one's comfort realm.

#DailyBloggingChallenge (276/300)

To extract the icon copy the outer #HTML (clip) of the embedded #SVG and save it in such a file.

Via the #terminal

```
echo '<clip>' > icon.svg
```

Open the newly created SVG with #Inkscape and modified as desired and extract as #PNG (alpha values required). Optionally instead WEBP or AVIF can be used.

#DailyBloggingChallenge (275/300)

Let's we want to create a shortcut to #Odysee using #Firefox and #Alacarte. Then the command is

```
firefox https://odysee.com/
```

The icon can either be found on the web or directly extracted from their website.

#DailyBloggingChallenge (274/300)

Due to the execution via the #terminal one can directly use #Alacarte to make shortcuts to web applications.

All one needs is the execution code for the browser like `firefox` for #Firefox and the location of the #WebApp.

```
firefox <location>
```

#DailyBloggingChallenge (273/300)

Do you know of #Alacarte the menu editor for #GNOME?

It is practical in renaming and/or hiding/adding new items to the menu.

One thing one will notice when making such an item is that the execution is done via the #terminal.

#DailyBloggingChallenge(272/300)

One nice thing that #Gimp provides is the option to crop all layers at once. This can also be done with #FFMPEG to crop the _output.mp4_.

Just follow this guide: [How can I crop a video with ffmpeg](https://video.stackexchange.com/a/4571)

Gimp or any other image editor app can be used to get a reference area for the crop area.

Hypothetically one combine step [265](https://qoto.org/@barefootstache/112319462127053043) and this one in one command.

#DailyBloggingChallenge(271/300)

One would have hoped that one came full circle, though one came fully around with less data than before.

Let's start again from the beginning and use the method described in [265](https://qoto.org/@barefootstache/112319462127053043) without using #Gimp. The only thing that is required is that the file names are in consecutive order. This can be done via

```
ls -1prt | grep -v "/$" | cat -n | while read n f; do mv -n "${f}" "$(printf "%06d" $n).${f#*.}"; done
```

#DailyBloggingChallenge(270/300)

The issue with this approach is that when extracting the frames via #ImageMagick one will only get the changes and the rest will be the alpha channel.

Thus when building the MP4 with #FFMPEG won't look as expected.

One could go back in #Gimp and merge each frame to the base layer (the first frame). Or just use the reference images.

#DailyBloggingChallenge(269/300)

One option to handle the #WEBP case is to follow this [guide](https://superuser.com/a/1688890). There are some modification that should be taken.

First extract the frames using #imagemagick

```
magick input.webp frames.png
```

Then use #FFMPEG to build a MP4 video from the extracted frames

```
ffmpeg -r 1 -i frames-%0d.png -c:v libx264 output.mp4
```

#DailyBloggingChallenge(268/300)

Not only do #WEBP have the animation halt in the #Fediverse though so do #GIF.

To overcome this issue, one can convert the specific file extension to a MP4.

For GIF one can run via #FFMPEG this

```
ffmpeg -i input.gif output.mp4
```

Sadly, currently the same cannot be done with WEBP, since [decoding animated WEBP](https://trac.ffmpeg.org/ticket/4907) has not yet been implemented.

#DailyBloggingChallenge(267/300)

#Gimp also permits to export the animation as a #WEBP. This will nullify the artefacts issue introduced by #GIF.

The only issue is if one wants to upload the result to the #Fediverse the animation won't be registered.

#DailyBloggingChallenge(266/300)

The #Gimp guide suggests to export the animation as a #GIF with a 1 frames per second.

This approach is fine if one is dealing with images that use less than 256 colors. Otherwise one will notice some compression artefacts.

#DailyBloggingChallenge (265/300)

Now with the layers as frames one can use #FFMPEG to merge them together to create a desired animation file.

```
ffmpeg -r 1 -i %06d.png -c:v libx264 out.mp4
```

This will create a MP4 with 1 frame per second. It is important the import naming `-i %06d.png` aligns with the export of layers modal.

To have a smooth looping experience, make sure to set the starting and ending frame be the same image. Just copy and past the start image and rename it so that it becomes the ending image.

#DailyBloggingChallenge (264/300)

If one continues to use #Gimp for sorting the images for the animation, then the [export-layers-plus tool](https://www.gimp-forum.net/attachment.php?aid=7309) can ease the process of exporting all layers at once.

The user script can be saved in the _script-fu_ directory. The directory can be found by visiting `Edit > Preferences > Folders > Scripts`.

It is recommended to pad the layer number with zeroes. The suggested one is `%6i`, which will pad the number with zeroes until the number has a length of 6.

Script from the [Gimp forum](https://www.gimp-forum.net/Thread-exporting-all-the-layers)

#DailyBloggingChallenge (263/300)

The #Gimp guide still has its place when dealing with images that are minorly misaligned. This is because on will need to adjust the images in such a manner that they overlap on top of each other.

This practice can be extended to the point that once a set of standardized images exist, then the ones that are misaligned can be filled and cropped to align with the standard.