mencoder half-green screen issue with x265 encodings and overscan compensation

[mik_s]

I don't know much about the actual transcoding command so can't tell if anything is wrong with that.

Ideally you want to avoid overscan compensation by having your TV to the right picture size where it is not needed.
On my Samsung I have it on "Screen Fit". There must be a similar option on yours. What make and model is your TV?

There are options in the PS4 settings that should fix this if you can't do it on your TV, then you won't need to add compensation in UMS.
Look in "Sound and screen" for "Display Area Settings" and you can move the box to what can be displayed.

One thing I noticed that may be causing the problems is the network speed to your PS4 is only 1.7mb/s.

Code: Select all

Renderer PlayStation 4 has an estimated network speed of 1.7160480551800499 Mb/s

This is limiting the transcoding that is possible and may be the cause of your other problems too. All your videos are marked to transcode even though they are supported to stream because the bitrate is too high for your network.
Some renderers need the bitrate to be half of the network's maximum bitrate in order to have smooth playback, and this option is set in the conf for the PS4 which only gives you 0.85mb/s for your PS4.

Code: Select all

Using video bitrate limit from PlayStation 4 configuration (1 Mb/s) because it is lower than the general configuration bitrate limit (90 Mb/s)
File "La.mpg" will not be streamed because the bitrate (5791487 b/s) is too high (0 b/s).

How is your network set up? Is the PS4/computer connected to the network wirelessly?

[mik_s]

I think the screen mode you want is "Wide Fit" but being a DLP TV I don't think you can avoid the overscan unless, like you say, you can reposition the projector.
It may actually be possible to do in the TVs service mode but could mess up alignment. I did find the service manual for it here. Using an adblocker I was able to get rid of the popup saying you need to buy it to view.

I did a little searching and found this

I have since found that in order to adjust for overscan by renaming HDMI1 to PC the input source must be 720p, not 1080i.

That was just one page in a long thread so there may be better solutions if you have a look through.

I think I have seen somewhere that mencoder has a problem with 10 bit, but it may have been HDR related. I don't know if 12 bit is supported.

It may be better to use FFmpeg instead and can add custom options to the transcoding command from the renderers conf file to add padding that would add the compensate for the overscan. This is from the defaultrender.conf

Code: Select all

# Overrides the FFmpeg custom options in UMS for this renderer. Default is
# empty, which means the UMS settings will be used.
# All setting for output formats, codecs, bitrate e.g. can be used except video,
# audio and subs mapping (-map).
# Do not use it to override -vf; use OverrideFFmpegVideoFilter instead.
# Default: ""
CustomFFmpegOptions =

I don't know what options to use or how, its something you will have to experiment with. I did find this that may be helpful or at least give you an idea on what to look for. There is a test video there you can use to find out exactly how much overscan you have.
This might be better for a general formula to add padding.

You will have to make sure your modded conf is being used though. I usually add -mod to the renderer name and the .conf filename so I know if it is being used and it will not be overwritten when you update UMS. I also set "LoadingPriority =" to a higher number so that it will take precedent over the original conf.

One downside of adding this padding is that every video, even supported ones, will have to be transcoded and not streamed. On some renderers this could mean loosing the ability to seek but the PS4 can handle this. Shame the PS4 setting for overscan does not work in apps, it may be only for games.

If you are using a custom conf made from the option in the old GUI I think it may be broken in recent versions, it might be fixed now but may not be in the current public release yet. Best to keep your conf in the main renderers folder where UMS is installed.

For your network speed it might have been due to eSET blocking things so UMS was unable to get the correct speeds.
Now you have that sorted out if you still have problems make new logs and I might be able to see something.

[mik_s]

If you were using an IP address instead of a UUID in that custom conf then due to a bug in recent versions UMS will ignore it.
Someone else was using IPs in custom confs to identify which renderer was which as they did not use a UUID, but it stopped working for them too after an update. You can read about it here

It has just be fixed and confirmed working but you will have to wait a while until a proper release as I don't think that test version is still online, or if it is probably won't be for long as it has been marked solved.

I personally prefer to make a new conf and just put it in the main renderers folder so I know it will be used.

[mik_s]

Glad that worked, its much less hassle if you can deal with overscan on the TV itself. If is is doing any scaling then the change in quality might be just about the same as transcoding so hopefully you should not notice any difference. When I had my old Plasma I could not tell the difference between 720p and 1080i.

Your network speed to the PS4 has improved but I don't know why it is so low. Something must still be blocking some traffic.
While I was looking at the speed results I noticed that an unknown renderer on 10.0.0.10 is showing as NaN as there is no reply to the ping.
From what I can tell that IP is that of your computer, usually windows media player, and should have a very high speed (I get over 700Mb/s) as it is basically a loopback test.
There is another unknown renderer on 10.0.0.7 which looks to be Serviio which does have a good speed test with over 90Mb/s. I don't know anything about that except it is a similar media server so it maybe interfering with UMS, though being on a different computer it shouldn't.

I still suspect eSET is doing something but no idea what to look for.
I've tried to search for any other ports that may be used and found references to ports 1044, 5002, and UDP 1900 in various places but no concrete information on them or if they are being used. All I know for certain is that by default UMS uses 9001 for the web GUI, 9002 for the standalone web player, and 5001 for the server. These can be changed in the settings though.

For your custom conf not working I am sure it is because of that bug where it not using the renderers IP. Try to see if the test version is still active in that link in my last post.
As that conf was not being used it was not added to the zip file so can't tell if anything is wrong with it, if you attach it separately I'll give it a look. I can see it being loaded in your previous logs but not in this one.

I would not worry about the filters being missing as that will only apply to AviSynth which you are not using. This is something I know nothing about though.