The basic settings for iVDRclient can be made in the "Settings" app.
In general, iVDRclient does not use any location services.
Updating data and saving data may cause problems even if the app is running in the background. If notifications are allowed, iVDRclient notifications are displayed according to the notification settings, even if the app is not in the foreground.
This setting allows the use of mobile data. This setting should be carefully used as video streaming can result in extremely high data volume. Only recommended with mobile data flat rate.
When demo mode is activated, the option "Demo" is offered on the iVDRclient start page. The app can be tried in this way without connection to the VDR. All functions for which a connection to the VDR is necessary are not testable in this mode. The normal use of the app is not affected by the activated demo mode. If the mode is deactivated the option from the start page is hidden.
Automatically connect to VDR
The app automatically connects to the VDR as soon as a profile is selected on the home page.
Automatically update data
The app automatically updates all data when a profile is selected when this option is enabled. The option is only active if the "Connect to VDR" option is activated.
The app waits for a response from the VDR during connection initialisation for the set time. In fast networks, 3 seconds should be sufficient, and 10 seconds can be the right setting when connecting via a VPN from a slow network. If in doubt, the value should be set to a high value.
Profile set up
With iVDRclient, any number of VDRs can be controlled. For each VDR, the necessary settings can be adjusted separately so that the VDR itself does not have to be tampered with.
The following parameters can be changed.
The set value is used as profile name in the profile overview.
The IP address of the VDR is set here. The use of the computer name (hostname) is currently not possible.
If the IP address is not known, it can be determined with the following command in a VDR shell:
You will receive an output similar to the following:
eth0 Link encap:Ethernet HWaddr 00:22:4d:xxxxxxxx
inet addr:192.168.xxx.xxx Bcast:192.168.xxx.xxx Mask:255.255.255.0
inet6 addr: fe80::222:xxxx:xxxx:xxxx:bd65/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:288 errors:0 dropped:6 overruns:0 frame:0
TX packets:250 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:37556 (37.5 KB) TX bytes:44417 (44.4 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:5263 errors:0 dropped:0 overruns:0 frame:0
TX packets:5263 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:152870062 (152.8 MB) TX bytes:152870062 (152.8 MB)
The IP address can be found in this example in the second line of the output:
There are currently problems with the use of DHCP. Since the hostname cannot be used, it must be ensured that the VDR is always assigned the same IP address via DHCP.
The user name for the connection via ssh.
The password for the connection via ssh.
The port for the connection via ssh.
Port 22 is the default port for ssh and does not normally need to be changed.
The time set here is the pre-setting for timers. For example, if you set this value to 10 minutes, the VDR will start recording at 20:05 when you program a start time of 20:15.
The time set here is the pre-setting for timers. For example, if you set this value to 20 minutes, the VDR will end recording at 22:20 when you program an end time of 22:00.
To download channel logos the skinelchi-Logos or VDR Skin nOpacity must be installed on the VDR. The VDR does not necessarily have to be started with skinelchi or skinnopacity in order to use the logos for iVDRclient. Default is here elchi, to be compatible to older installations of iVDRclient. It is possible to switch between the two settings at any time, the logos are loaded and stored independently for both settings.
Logo Source Directory
To download channel logos, the skinelchi logos or VDR Skin nOpacity must be installed on the VDR. Default directory for skinelchi is:
Default directory for skinnopacity is:
Web Server Directory
HTTP Live Streaming requires a directory in which the generated stream segments can be saved and provided for download. In the simplest case, the home directory of the ssh user is used. This is the default:
It is checked whether the web server directory has the suffix "$USER/public_html". If this is not the case, it is assumed to be a directory outside the user's home directory.
Please note: The VDR user needs in any case write permissions for this directory, since all stream segments as well as logo files are stored.
When you download the channel logos temporary files are created in an intermediate step in the format JPG. The directory set here is used for this purpose. Also, log output from vlc is stored in this directory.
Streamdev Server Port
The streamdev plugin binds to port 3000 as standard.
VDR binds to port 6419 by default.
When loading the EPG data several tens of thousands of EPG entries may be transferred from VDR to iVDRclient. This can in some cases cause twitching when scrolling in the views of iVDRclient. This setting can be used to limit the number of days for which EPG entries should be stored in the app.
Some broadcasters offer EPG information only two days in advance, in particular public broadcasters often offer program information for up to 14 days in advance.
When loading the EPG data several tens of thousands of EPG entries can easily be transferred from VDR to iVDRclient. This can in some cases cause twitching when scrolling in the views of iVDRclient and can take very long with a long channel list. This setting can be used to limit the number of channels for which EPG entries should be stored in the app. The fewer channels are updated, the faster the EPG information is updated.