From the very start of this thread, your posts have come across as confrontational and rude. If you re-read the replies, you might feel a little stupid because your question has been answered many times over. You just can't or won't understand.
Now if you have such an issue with it, go get a NAS box and ditch Unraid.
Seriously, what is wrong with some people!

For me the other almost imperitive addition would be to be able to automatically add a string to the converted filename (something like "re-encode") which will then force Radarr/Sonarr to reanalyse the file and note the new codec.
Without the renaming option, Radarr and Sonarr wont re check the file and will still think it is h264 or mpeg4 and when a h265 file is available, re-download it which is a waste of time.

@Josh.5 I have found a small bug. Where the file-type (therefore extension) differs pre and post conversion, the file gets re-added back into the queue on next scan. See below where the same three files previously encoded have been re-added because the original was MP4 or TS or AVI
Edit: It seems to add new files without checking whether conversion is necessary. I recently upgraded a movie to 4k HEVC and it has added that to the queue.

Yes, but the container is not saving the settings and on further looking into the logs, i can see this when i try to set that setting:
2019-02-11T11:51:05:ERROR:Unmanic - [FORMATTED] - Exception in writing settings to file: - Object of type 'Logger' is not JSON serializable

Hi @Josh.5, The latest commit takes a long time to build any sort of queue and sits idle. It does eventually (maybe an hour) start to build one and start encoding. The following entry appears in the log:
2019-02-11T10:41:20:ERROR:Unmanic - [FORMATTED] - Exception in reading saved settings from file: - Expecting value: line 56 column 15 (char 1519)