1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
This is a "plugin" for the Video Disk Recorder (VDR).
Written by: Frank Schmirler <vdrdev@schmirler.de>
Project's homepage: http://vdr.schmirler.de/
Latest version available at: http://vdr.schmirler.de/
See the file COPYING for license information.
Description:
------------
Display the menu of a remote VDR as submenu item of your local VDR menu.
Requirements:
-------------
Local (client) VDR:
- plugin remoteosd
- plugin svdrpservice
Remote (server) VDR:
- plugin svdrposd (formerly svdrpext, which is also supported)
All three plugins are available at http://vdr.schmirler.de
Installation on client VDR:
---------------------------
Straightforward:
- cd VDR/PLUGINS/src
- tar xzf vdr-remoteosd-<VERSION>.tgz
- ln -sf remoteosd-<VERSION> remoteosd
If you want to replace the VDR mainmenus "Schedule" or "Timers" by
the respective remote menus, you must apply the MainMenuHooks patch
to VDR before compiling remoteosd. The MainMenuHooks patch is included
in the patches directory of the remoteosd sources. See the patch file
for more information and instructions.
Now compile and install remoteosd (and svdrpservice) as usual and add
both plugins to the script starting your VDR (e.g. runvdr). No options
required, so simply append:
-P remoteosd -P svdrpservice
Since svdrpservice-0.0.4 you can already specify the server IP and port
on the commandline. It will then serve as the default for all plugins
using svdrpservice:
-P remoteosd -P 'svdrpservice 192.0.2.1:6419'
Finally check the file svdrphosts.conf on the remote VDR: The IP of the VDR
running remoteosd must be listed or otherwise the connection will be
refused.
Installation on server VDR:
---------------------------
Just about the same:
- cd VDR/PLUGINS/src
- tar xzf vdr-svdrposd-<VERSION>.tgz
- ln -sf svdrposd-<VERSION> svdrposd
Compile, install and add the following parameter to the startup script:
-Psvdrposd
Check your svdrphosts.conf file: The clients must be listed or otherwise
the SVDRP connection will be refused.
Configuration:
--------------
Before you can connect you have to configure the IP address of the
remote VDR, unless your svdrpservice plugin has been told about a
default IP.
The remoteosd setup menu offers the following options:
- Hide mainmenu entry
Keeps your girl friend off the server menu ;-)
- Replace mainmenu "Schedule"
When enabled, each call to the local VDR Schedule menu will give you
the remote Schedule menu instead. Only available if MainMenuHooks patch
has been applied to VDR before compiling remoteosd.
- Replace mainmenu "Timers"
Dito for Timers menu.
- Server IP
IP address of SVDRP server. Leave empty or enter 0.0.0.0 if you want to
use the default IP configured in the svdrpservice plugin.
- Server port
SVDRP port on server. Since VDR 1.7.15 the default port is 6419, before
it was 2001. The special value 0 uses the default port configured in
svdrpservice.
- Tune server channel
Tries to tune the server to the same channel the client is currently
viewing. So when entering e.g. the remote schedules menu, the expected
channel will be highlighted. Usually this option makes sense only if
you are running a headless server. In this case I recommend to install
the dummydevice plugin on the server. Otherwise the server might not
be able to switch channels as expected.
- Number of lines per page
This parameter controls how a long list of items is split into pages.
The special value 0 uses the client's idea of the OSD size. However the
server OSD size determines how many items you skip when hitting a "Page
Up/Down" key. You might want to adjust the number of lines if client
and server have different OSD sizes. If the client can display more
items than the server, you should enter the server's size. If however
the server can show more items, you should consider to reduce its OSD
size in menu Setup -> OSD.
- Remote menu theme
Some skins support themes. If you want to avoid ambiguities, remoteosd
can use a different theme while you're in the remote menu. As the new
theme is loaded while the OSD menu is open, not all colors of the new
theme might show up. It depends on the way the actual skin implements
themes. The ST:TNG theme for example will not change the color of the
frame.
It's not a bug...
-----------------
Limitations of the VDR SVDRP interface
- An SVDRP connection is used to retrieve the OSD status of the remote
VDR. Currently, SVDRP cannot interact with multiple clients at a time.
As long as the SVDRP port on the server is busy, the remoteosd client
will not work. The menu will be closed after a short timeout. The other
way round, remoteosd will block the SVDRP port as long as its menu is
open. The SVDRP connection will be established whenever you open the
remoteosd mainmenu entry and it will be closed when leaving it.
- VDR polls for new SVDRP connections about once every second. You will
notice a delay of up to one second until the menu will show up.
Limitations of the VDR status interface
- Viewing a schedule entry, you will only see the text body. VDR does
not export the corresponding title and subtitle.
- The status interface doesn't tell you if an item is selectable or not.
Therefore serverside scrolling is required (which is slow) and on the
client you don't get the different color for non-selectable items.
|
