Page 1 of 1

Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!

Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.

Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!

RMTVS .nfo format
Clear all

RMTVS .nfo format

2 Posts
2 Users
0 Reactions
Joined: 1 second ago
Posts: 0
Topic starter  

One of your features I love (and hate) is the episode synopsis .nfo

Love it because it reminds me of the episode and Hate because of its format.

<title>Good Luck, Father Ted</title>

You do such a great job in the main display and not here.

Is there supposed to be a reader for this format? 

I also question the use of .nfo.  Shouldn't that be .txt?

.nfo is used for system files and some source people use it for an ASCII graphic. 

You could use [RMTVS].txt and/or [TVDB].txt at the end to give you some advertisements. 

Since you are working with the TVDB, can you get any other information from them?

Cast and crew, Artwork, etc.

You might have to put it in a separate directory to capture the images.

Add a folder to contain it with the Banner.jpg and

Thanks again for a great program!  

If you want coffee, tell me the brand and flavor, and I'll send you a case (or maybe just a bag)  

           Select from any YouTubers host site supplier. They need support as well. 


Windows 10/11 

Rename My TV Series (2.0.10 (Build 8))
OS: Windows (64-bit), Windows 10.0, i386 (32-bit application) 

(Why do many people equate 32-bit with x86) 


P.S. Can you give us a Q&D (quick and dirty) program to convert the old .nfo to a readable .nfo/.txt file?

Unless you add the Cast/Crew info to it, you wouldn't even need to access the internet.

Input a directory of many, many shows and have it find all the .nfos to fix.

It would be a royal pain to do all these one at a time (again).

This topic was modified 2 months ago by Anonymous

Topic Tags
Famed Member Admin
Joined: 11 years ago
Posts: 2705

Hi Wyrmsworth ! 😊 

Thank you for the compliment and suggestions. 

The NFO format:

Well, it's an almost XML (not proper) formatted file format which is commonly used by most media managers to import/export/share metadata for about 2 decades already. It may even go back to the first KODI version - which was called XBMC in 2002 and created for the original XBox.
For example KODI and JellyFin (and others) in some fashion work with these files. See also the documentation on NFO files for Kodi and JellyFin.

I have kept the implementation to a bare minimum since there seem little demand for it (you're honestly the first person even asking about it) and I wanted to keep the data uniform and supported by the other data providers as well (at that time - it's been in RMTV for quite a while now).

My best guess why people don't ask about it: Most users probably rely on their other tools to deal with this (like Sonarr, Plex, JellyFin, Kodi, Emby, Tiny Media Manager, etc).

You're right about the NFO extension being used for other purposes on the Windows platform as well. And it's used for ASCII drawing like files as well. See also this Wiki page. Unfortunately, I didn't define this "standard", and if it were up to me I'd pick real XML or even better: JSON - but at the time of conception I suppose neither file format was very commonly used.

Dumping it as a TXT file: what format would one use?
I mean; it wouldn't be impossible to implement this in a new release of RMTV.
May not even be all that tricky to clean up with a tiny tool - I'd have to write one though.
In essence:
- Remove all "</*>" tags
- Replace "<tag>" with "tag: "

Assuming your example:

<title>Good Luck, Father Ted</title>

What would you like this to look like? Something like this?

Title: Good Luck, Father Ted
Season: 1
Episode: 1

Note: since NFO's are not following proper XML formatting, most XML-2-TXT converters will probably fail.

Note: before modifying these files, better make sure NFO files are not used by you software. RMTV doesn't use NFO files by itself, but does generate them (if set) for other applications.



As for coffee - oh wow you went all pro there 🤣 .
Honestly, I've never realized there would be YouTube host suppliers?
I used to get my favorite coffee from Minneapolis, but that has been more than a decade ago now. 😜 


x86 32 bit

Why x86 is being referred to as 32 bit? I suppose because x86 was based on the 80386 and 80486 Intel CPU's, which are 32 bit processors, with a 32 bit instruction set. Hence x86. I can argue though that this not to be entirely correct, but who am I to argue that there as also 8086, 808186 and 808286 and those were 16-bit.
The x64 bit term, was originally called x86–64 or AMD64 (since it's using the AMD 64 bit instruction set, not to be confused with Intels failed Itanium 64 bit instruction set). I suppose people got lazy. 😉 

Anyhoo - for the Windows platform I'm sticking with 32 bit for now, just so it keeps running on [very] old PCs.
Just thinking that won't harm anyone, since 32 bit applications run very well in 64 bit Windows versions (Intel or ARM CPU).
There will be a 64 bit in the future of course now that the 32 bit market share drops to almost zero.