tone VS Simula

Have you tried using ABP's own metadata tool and then using that to embed the metadata? They use tone. Not sure if it will help you with the m4bs containing mp4 streams - I've never tried dealing with that.

[2]: https://github.com/sandreas/tone#custom-scripted-taggers-experimental

Feedback is highly appreciated.

[1]: https://github.com/sandreas/tone

- LG G5 H850 (optional with Bang & Olufsen Hifi-Plus module) + Audiobookshelf + Substreamer

Let me cite my comment from https://news.ycombinator.com/item?id=32042780:

I use m4b-tool[1], tone[2] and audiobookshelf[3] together with an LG G5 H850 smartphone[8] with Bang & Olufsen Hifi-Plus Module for Audio Only and I am pretty happy with this config. For Music I use Navidrome[5] and Substreamer App[7]. Maybe I'll try out Jellyfin[4] or maybe Plex[6], but I really don't wanna go closed source.

I also thought about writing something self hosted in C# to have ONE solution for audiobooks, podcasts and music and started a small private project, but this will take a while until it is ready to release something...

You may ask: Why an LG G5 H850? Well, its relatively small and cheap (about 50 - 80 bucks used) it has an audio Jack, USB-C, you can change the battery, it can hold up to 2TB microSD storage, has an HiFi Plus module for audio enthusiasts and a descent screen. Besides that it can run lineage os...

Note: I'm the author of the first two projects :-)

[1]: https://github.com/sandreas/m4b-tool

[2]: https://github.com/sandreas/tone

[3]: https://github.com/advplyr/audiobookshelf

[4]: https://jellyfin.org/

[5]: https://www.navidrome.org/

[6]: https://www.plex.tv

[7]: https://substreamerapp.com/

[8]: https://en.wikipedia.org/wiki/LG_G5

> Very neat, I love it, I used to have a tool to do this but it's been ages and is now unmaintained.

Thank you :-) Glad to hear that.

> Just be sure to do input santization, since if someone else uses your code it could go from a very cool project to a backdoor that ends up on the front page for all the wrong reasons :-)

Good point. I think that the "scriptable" part needs special care regarding security issues, as well as the metadata-readers and JSON parsers. I don't want that to bite me in the neck because of a "malicious" file. Maybe it is worth to provide a responsible disclosure email and make a plan for security issues.

See https://github.com/sandreas/tone/issues/12

- https://github.com/rochus-keller/Smalltalk/ Parser, code model, interpreter and navigable browser for the original Xerox Smalltalk-80 v2 sources and virtual image file

- https://github.com/rochus-keller/Som/ Parser, code model, navigable browser and VM for the SOM Smalltalk dialect

- https://github.com/rochus-keller/Simula A Simula 67 parser written in C++ and Qt

> do you regret those endeavours?

No, not in any way; the projects were very entertaining and gave me interesting insights.

The meta object concept of Python (both the 2 and 3 version) is rather different than the one of Smalltalk-80. Actually Smalltalk-76 and 80 have more in common with Simula (67) than the first Smalltalk (72) version. I implemented both Simula 67 and Smalltalk-80 (see https://github.com/rochus-keller/Smalltalk/ and https://github.com/rochus-keller/Simula/). Smalltalk implemented a lot of great ideas, but its influence on other languages (such as Python, Java, C++, etc.) is generally overestimated.