Web-ui for transcoder bitrate

The standard web-ui has selections for the bitrate of the transcoder. On mobile, however, this section of the webpage is not available.

Depending on cellular reception, I might be able to stream anywhere from 1mbps up to 10mbps. A useful place to have such a setting would be on the cellular phone web-ui.

It should be there, just like on the desktop. What browser are you using? You may need to refresh the page and wait a few seconds for it to load in.

its an iphone 7 plus, using safari. I am not referring to the HDHR transcode, I want to adjust the web transcoder.

I understand. The web transcoding settings should be at the bottom of the page. It looks like there’s an error happening that’s preventing all the DVR specific settings from showing up for you.

Also FYI, the web transcoder settings are currently ignored when you have an EXTEND. The DVR will automatically use the EXTEND’s mobile transcoder instead of using the DVR transcoder.

If I adjust the web transcode on my DVR settings from the desktop web-ui, the stream changes when I access it on any device. It is definitely running the transcoder for both recordings and live.

Live stream does use the HDHR mobile setting, though.

transcoder settings are available on Chrome via mobile, so it appears to be only an issue with Safari.

I can see the settings on my iphone 6s safari browser

Maybe it is a synology issue then, bc it also doesn’t work on my wife’s iPhone 6S plus Safari.

it works fine on an iPhone 5 Safari. So this issue is limited to Safari on iPhones with larger screens.

I can see the transcoder settings on my 7 Plus in Safari.

thanks. I had to clear history and website data. Unfortunately, iPhone does this for all of iCloud. But, after that, the transcoder settings loaded correctly.

This is a race condition bug which makes the DVR settings not load sometimes. Usually refreshing the page is enough to make it show up. I will make a note to find a fix.

1 Like

Figured out why this was being weird- a bug was introduced a couple days ago. It has been fixed in v2017.02.03.0335.

1 Like