Hi folks,
with a few days to spare, the "third anniversary" release of Talefish is now ready to be checked out.
To celebrate this and because of huge changes under the hood, I've decided to push the version number from 0.0-14 to 0.1-1.

As usual, I'd be really happy if some of you are willing check this out and report back what works and what does not.
There are countless different configuration and file type variations – so I may have overlooked some.

condensed change log:
* Sun Dec 30 2018 velox 0.1-1
- enhancement: integrate taglib
- performance: optimize file loading workflow
- enhancement: add support for (some) cover images integrated in media files
- enhancement: make "first start message" more readable
- various small bugfixes


A little more about what changed:
The thing that bugged me (and many users) most was the slow and cumbersome way that, after opening a directory or file,
a lot of time was wasted with transitions back to the player interface, opening a new dialog for scanning durations and finally
reverting back to the player interface and loading the files.
While it is still necessary to use the scanner dialog, there are way less cumbersome transitions now. It's just the next page after accepting the open dialog.

Also, getting the duration of opened files was mostly slow and horrible. This changed a bit with 0.0-11
if users had the mediainfo application installed, but the vanilla experience lacked in many areas.
The fact that mediainfo wasn't available for the Tablet did not make it better.
This is why I've integrated the system's taglib in c++. It is pretty fast and works mostly without
lock ups, because it avoids heavy work in the render thread when possible.
It does not work for all files (I am looking at you, mka and aac!), but both the mediainfo hack and the
horribly slow QML method are still implemented as fallbacks. While some other information than duration
is read (and displayed in the file chooser to aid in finding the right thing to open),
the player interface also still just uses file names, because I wanted the main experience
to mostly stay the same.
I am open to suggestions like "please show artist/album on the first, track name on the second line if available", though.

Last, but not least:
The integration of taglib enabled me to integrate simplified support for cover images that are embedded in media files. This image provider gets used if no dedicated cover images are found in the opened folder.
Why simplified? I'm glad you asked!
It's only supported for mp3, m4a (or m4b, as long as it is audio/mp4), flac and ogg vorbis.
Also, it mostly just displays the first found image (which technically could be a back cover or inlay) and
for file types with more than one method of storing images, generally only one is implemented.

A happy year increment to all of you!

Cheers!