[solved] Configuration of VDR remotetimers

[rebelkiller]

Hello there! 

I'm using LMCE 12.04 with VDR 2.0.6 with a (non-graphic) Core and 2 diskless MDs. VDR is working properly, except remotetimers.

I want to use central recordings and timers on the core. How do I configure remotetimers-plugin to do that? Which directories are getting used and where do I put them?

e.g.
- /var/lib/video.00
- /home/public/data/pvr


Thanks for some hints!

Bernd

[Marie.O]

remotetimers per se has nothing to do with where to put the directory for VDR to record to. Whatever you choose, just make sure the moons can access it at the same place.

I have my VDR recordings happen on a designated disk device,i.e. my /etc/vdr/default has a line like this on every moon and the core:

VIDEO_DIR="/home/public/data/pvr/Another\ Internal\ 4TB\ \[898\]/"

The relevant stuff for remote timers should already be setup in vdr setup.conf.

[rebelkiller]

@posde:
ok, thank you. This works for me. But when I start VDR as user "VDR" the user has no access to this directory and so the VDR daemon quits at startup. When I start VDR as user "ROOT" this works.


1. Do you start VDR as "ROOT"? (set in /etc/default/vdr)
2. How is your remotetimer-plugin configured? Timers, Recordings, Timeshift  "server" or "local"?

All the best!

bernd

(wir könnten doch auch in Deutsch schreiben  )

[Marie.O]

My vdr runs as root.

My remote timer is configured like the pluto-vdr package configures the setup.conf. Can't remember what exactly the settings.

[rebelkiller]

My solution:

- I set VIDEO_DIR as  "/var/lib/video.00/". My "video.00" is a link to "/home/public/data/pvr/whatever" on all MDs.
- In runvdr I set "user=root". Setting it to user "vdr" results in not starting vdr-daemon because of missing the right permissions of the mentioned directory.

Now I can see my recordings in VDR under "Recordings" on every MD.


It works. Problem solved. Thanks for your hints!

Greets!

Bernd

[Marie.O]

Glad that you sorted stuff out. What is the output of dpkg -l vdr on your systems. I might have a small plugin, that does wonders to your Orbiter display...

[rebelkiller]

 vdr 2.0.6-6yavdr1

[Marie.O]

get http://deb.linuxmce.org/possy/vdr-status-plugin.tgz and move the .so's into /usr/lib/vdr/plugins, move the .conf file into /etc/vdr/plugins and amend according to your setup, and see if your Orbiter will be able to give you back information about what's currently playing.

[rebelkiller]

Plugin is running but i can't see any differences. What does parameter "-d 306" do?

[Marie.O]

-d xxxx defines the device of your VDR player.

vdr --help

is quite helpful to tell you about all the commandline parameters that exist.

[rebelkiller]

### = device-id of "VDR" device in webadmin (in the "OnScreen Orbiter" tree of the specific MD)?

installation on MD, on core or on both machines?

[Marie.O]

Did you even run vdr --help? Among other information it would have given you this:

Code: [Select]

status (0.4.0) - Status monitor test

  -r dcerouter,   --RouterAddress=dcerouter      IP address or DNS name of DCERouter (defaults to dcerouter)
  -d device-id,       --DeviceID=xxx       Device ID of local VDR Player device


[rebelkiller]

Yes I did.

But I am asking again:
### = device-id of "VDR" device in webadmin (in the "OnScreen Orbiter" tree of the specific MD)?

There is another VDR entry unter DCERouter so would you please simply answer my question?
I put in the # of my VDR entry unter "OnScreen Orbiter" but it did not do anything.

The second question you did not answer either.

Thanks.

[Marie.O]

What is so hard to understand from "local VDR player device"?