m4b-tool

valonia UI is just not there yet, I'm currently switching to flutter. [1]: https://github.com/sandreas/m4b-tool [2]: https://github.com/sandreas/tone

l interface is hard to beat in terms of audio books. Unfortunately repairing iPod Nanos is really tough compared to the iPod classic 2009 (even this device already supports the cable headphone controls). Currenlty I'm trying to mod an iPod Nano 7G to have a 600mah battery by milling out the backplate, keeping the original BMS and placing an iPod Mini Battery (which fits perfectly in size, when the backplate is milled out). This way I hope I will have the only iPod Nano 7G with interchangeable batteries ;) The best alternative I found so far is the Unihertz Jelly 2(e) Phone with selfhosted Audiobookshelf and different player / sync apps, but the experience is nowhere near the iPod... It's bigger, way thicker and the headphone controls are "unstable". Not to talk about the app crashes, unsupported android background service playing and missing / non-working chapter controls. Disclaimer: I'm the developer of m4b-tool[1] and tone[2], so I know what I'm talking about :-) [1]: https://github.com/sandreas/m4b-tool [2]: https://github.com/sandreas/tone

` to `m4b` and edit metadata: - AudioBookConverter - https://github.com/yermak/AudioBookConverter (GUI, cross platform) - Chapter and Verse - http://lodensoftware.com/chapter-and-verse/ - m4b-tool - https://github.com/sandreas/m4b-tool (command line, cross platform) - tone - https://github.com/sandreas/tone (command line, cross platform) Note: I'm the author of the last two tools.

early shipping is good, but automatic deployment and versioning is nearly as important. Thats why I decided to invest some time and simply release `tone` based on git tags with github actions... that was a very good decision so far. So to conclude: Build something, that you use (and want to improve) yourself Ship early Go for auto-deployment / CI as soon as possible Do some "marketing" for high quality feedback (e.g. on hackernews) Cover your ass with automatic tests as soon as possible [1]: https://github.com/sandreas/m4b-tool [2]: https://github.com/sandreas/tone

g the files and getting metadata from online sources is... lets say a huge project. And NOT getting metadata would mean, that I cannot move the files while another app manages the metadata. So I took another path - scanning an existing and well tagged library (that I manage with beets[3] for music and m4b-tool[4] / tone[5] for audio books). My current Idea is to have a file indexer that: - can run on multiple sources - runs one full index scan after starting the app - registers a filesystem watcher for every file source and reacts to events - To ensure, no filesource is blocking others, each source is processed by a fixed batch size and then move on the the next file source - If sources are modified (added, changed, deleted), there is a decision, what to do with already running indexers and registered file watchers (added just go to the queue, changed and deleted cancel already running tasks only for this source) - All files are hashed (content only) to ensure, a change of metadata or tags will not change the hash, and if a file is moved, it will recognize this and update instead of delete and insert The database will contain Tag-Values for every possible value. E.g. File.Location music/album/AC_DC/Back in Black/01 - Hells Bells.mp3 FileTag.Type Artist Tag.Value AC/DC That way I can add a fulltext index on the Tags.Value field containing a searchable value while maintaining the FileTag.Type for recommendations. Let's say I search for `AC/DC`, it will provide an auto-complete for all FileTags.Type values, that show a match + a generic one for searching ALL values: Artist: AC/DC FullText: AC/DC Searching for 2010 will show: Released: 2010 Title: 2010 FullText: 2010 because it contains matches in Releasedate and title. There may be a lot to optimize, but I think my current plan goes pretty well. Let me know what you think about this approach :-) [1]: https://www.navidrome.org/ [2]: https://www.audiobookshelf.org/ [3]: https://beets.io/ [4]: https://github.com/sandreas/m4b-tool/ [5]: https://github.com/sandreas/tone/

us module) + Audiobookshelf + Substreamer - Pro: Formats, Battery, Storage, Bluetooth/Wifi/NFC, Hackable - Con: Size, UI (I did not find a Server/App nearly as good as iPod) 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

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

re planning on implement by requiring ffmpeg _AND_ using another library just to wrap it? I'd do in native code and, as a result, performance would be orders of magnitude better. Yes, I plan to use `ffmpeg` for the first part, but also include `fdkaac` and maybe `sox` or other audio specialist tools to provide better audio. My plan is also to integrate a dependency downloader, that does not want you to install the dependencies yourself, but does everything for you. I'm the author of `m4b-tool`[1], which has also split, merge and silence detection, so I have a little experience in exactly this topic you are talking about (tone is planed as long term successor of m4b-tool, but this will take time). I will use a library called CliWrap[4] to integrate shell execution though, but do it multithreaded to provide more performance. > I don't use windows (at least, I'm not willing to use windows for any 'pro bono' work ;-) ) but if you were to write your tool in C or C++ instead, or perhaps... have a common API layer of sorts... If I understood this correctly: C# is not Windows-Only any more, and it is pretty fast on all platforms. It provides Ahead of Time Compilation and a so called self-contained binaries working without any C# runtime or VM... using github actions I provide a full featured monolitic executable binary, but I could also provide a library. C# is even capable of and using unmanaged code, writing drivers and embedded stuff, like RPi... I think it is not a bad language to start such a project, but at least the best I know well enough ;) > and actually enjoy, helping you out by "gifting" some fast and MUCH leaner solutions for any and all of the audio processing work It would really be nice to find some collaborators, thank you. There are some C# audio processing libraries out there (like NAudio[2] or cscore[3]), but currently windows only or pretty complex. We'll see... :-) This was very helpful. Thanks again. [1]: https://github.com/sandreas/m4b-tool [2]: https://github.com/naudio/NAudio [3]: https://github.com/filoe/cscore [4]: https://github.com/Tyrrrz/CliWrap