4 ms·

At a glance it looks good to me, I can see you made it for audio books. Most of my tagging is done for Music. I know it seems fairly out of scope for this proj

• sandreas 4y ago
  > At a glance it looks good to me, I can see you made it for audio books. Thanks for you feedback. Yes, audio books are the main purpose, but it should also work for music and even video in some cases (e.g. mp4). > Most of my tagging is done for Music. I know it seems fairly out of scope for this project, but do you have any plans to integrate updating tags from online sources eg. MusicBrainz, GoodReads etc. Yes, I have indeed. Since online resources are sometimes problematic regarding legal issues, I have to further investigate this, but things I plan to implement natively are: Audible, MusicBrainz, GoodReads, Bookbeat, Librevox, Opf (https://docs.fileformat.com/ebook/opf/ https://docs.fileformat.com/ebook/opf/), Cue-sheets, OverDrive and more > I didn't read further enough, I like the custom tagger support. Some curation or perhaps a collection of "official" plugins for popular providers would probably help with adoption. Yeah that would be awesome... tone is pretty new, but in the long term I plan native C# plugins to support: - custom taggers - custom dump (information output) - custom shell execution (ffmpeg to split, merge and apply filters to audio) As well as extensive scripting with JavaScript. Let's see how it goes :-) What also often helps a lot is the --path-pattern stuff. You can transfer filenames into tags that way very easily. A "rename" command would help to also rename files by tags. The following commands are planned on my list: *dump - show metadata in different formats (done) *tag - modify metadata by different sources (done) rename - rename files by tags split - split a file by chapters merge - merge multiple files to one with chapters convert - convert files to other formats keeping metadata