[MUSIC] Jellyfin .nfo file Creation

[Stewart]

Hi All

Can FileBot create Artist.nfo and Album.nfo files for Jellyfin?

The reason I am asking is I don't want to have metadata embedded in my audio files.
I want to use "Hardlinks" for different albums with same song in them.

Regards

Stewart

[rednoah]

Yes, assuming that we know all the information you want to put into these *.nfo files, but we would have to create a Custom Post-Processing Scripts first. Maybe something like Generate custom NFO files will get you started.


One potential issue that I could foresee is that FileBot doesn't actually know much about music files other than the ID3 metadata that you already have in the file itself. We could easily export that information into external *.nfo files, but getting additional information might be tricky since FileBot isn't well set up for that kind of use case when it comes to audio files / music information.

[Stewart]

Hi rednoah

I’m thinking that when i use filebot to rename and find metadata with movies and tv shows without any metadata embedded in there files

Perhaps filebot could do the same with music using for example jellyfin uses musicbrainz

Regards

Stewart

[rednoah]

I’m thinking that when i use filebot to rename and find metadata with movies and tv shows without any metadata embedded in there files

Yep, for Movies and TV Shows we have very extensive support for fetching additional information that is exposed to scripting as well.

Perhaps filebot could do the same with music using for example jellyfin uses musicbrainz

As for music, if AcoustID is used, then we might have some additional information, but very little of that is currently exposed to custom format or post-processing scripts. The MID is exposed via {id} though I think, so if the MusicBrainz API is easy to use via HTTP requests that returns JSON or XML then that would make it quite easy to get additional information in a post-processing script.

EDIT

FileBot r10837 and higher now ensure that {id} returns the MusicBrainz recording ID instead of the search result ID. The former is more useful for API lookups to request more information:

Format: Select all

{
	xml("https://musicbrainz.org/ws/2/recording/${id}?inc=releases")
}