Server Version#: 1.40.1.8227 (Synology NAS)
Player Version#: 10.13.0.466 (cf77d59a) (Android Mobile)
When forcing a transcode using a predefined resolution, it seems the video produced is limited on the horizontal to the resolution, not the vertical as would be expected.
For example here, for a 1080p source selecting 720p HD 3Mbps I’d expect a 720p vertical/rows (1280 horizontal/columns on a 16:9 source ratio), however the reported, and visual size is much smaller (when viewed ‘original’) with 404 vertical and 720 horizontal.
It seems pretty clear that the 720 limitation is being applied to he wrong axis, or am I missing something?
Edit: maybe this should be filed under Server rather than Player??
I’ve had a bit of time to look through console logs and it is definitely limiting the width, as shown here:
but I don’t really know why… There is a log item mentioning “Streaming Resource: Required bandwidth unknown (media requires deep analysis) Changing decision parameters provided by client to fit bandwidth limit of 3000kbps” which to me suggests the media needs deeper analysis to be able to keep 720p (vertical) with 3000kbps however I do have, and always have had the “Perform extensive media analysis during maintenance” scheduled task enabled so I’d expect it to have the necessary information for that…
Sorry to tag you in on this @BigWheel but would you be able to confirm if any of this is the expected behaviour, or not?
No worries about ping. Based on what you are showing that does look to be wrong. Thank you for reporting
Great. Thanks. Let me know if you’d like some logs grabbing (and which)
@BigWheel I see:
- (Transcoder) Corrected quality parameter for devices without rate control. (#14885)
In the latest beta server release notes, is this a change relating to this issue?
Sorry it is not. From what I was told the issue is in the request the Android client is making to the server so when there is a fix it will be in the Android client release notes
I’m seeing this issue as well. The resolution cap aligns with 720p (1280) in my log message. Trying to get to the bottom of it with testing various scenarios. Not sure if this started with a recent server release or not.
