Unfortunately, versions 1.9.1 and 1.11 are not binary compatible, see this post for the original problem (it contains links to a few images showing that unicode text is garbled).
To summarize: A binary incompatiblity was introduced in the String constructor between versions 1.8 and 1.9. In version 1.10, this change was reverted. This makes TagLib 1.11 binary compatible with versions 1.10, 1.8, ..., but not 1.9 and 1.9.1.
I still think that 1.11 is one of the best TagLib releases so far, but if you make the transition from TagLib 1.9.1 to TagLib 1.11, should should recompile everything which was built against TagLib 1.9.x.
Unfortunately, versions 1.9.1 and 1.11 are not binary compatible, see this post for the original problem (it contains links to a few images showing that unicode text is garbled).
https:/ /mail.kde. org/pipermail/ taglib- devel/2015- November/ 002798. html
See my answer
https:/ /mail.kde. org/pipermail/ taglib- devel/2015- December/ 002800. html
To summarize: A binary incompatiblity was introduced in the String constructor between versions 1.8 and 1.9. In version 1.10, this change was reverted. This makes TagLib 1.11 binary compatible with versions 1.10, 1.8, ..., but not 1.9 and 1.9.1.
I still think that 1.11 is one of the best TagLib releases so far, but if you make the transition from TagLib 1.9.1 to TagLib 1.11, should should recompile everything which was built against TagLib 1.9.x.