VDR Plugin

    • OMV 1.0

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • OK after updating to glibc version from Jessie the vdr 2.0.6 version installs just fine. However I was on a hurry and wasn't able to start vdr - unknown service...I guess it has to be registered somewhere.

      I wonder if the etobi 2.2 version from Jessie will also install now mhh gotta test that out when I got time...

      The post was edited 1 time, last by blublub ().

    • I managed to install the mcli-plugin but vdr exits due to missing dvb-devices, although i started vdr by cli:

      Source Code

      1. vdr -P"mcli --ifname eth1 --dvb-s2 2"


      I got this result (syslog):
      Display Spoiler
      Oct 2 14:58:26 omv vdr: [38434] VDR version 2.0.3 started
      Oct 2 14:58:26 omv vdr: [38434] codeset is 'UTF-8' - known
      Oct 2 14:58:26 omv vdr: [38434] found 28 locales in /usr/share/locale
      Oct 2 14:58:26 omv vdr: [38434] loading plugin: /usr/lib/vdr/plugins/libvdr-mcli.so.2.0.0
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/setup.conf
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/sources.conf
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/diseqc.conf
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/scr.conf
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/channels.conf
      Oct 2 14:58:26 omv vdr: [38434] ERROR: too many CA ids!
      Oct 2 14:58:26 omv vdr: [38434] ERROR: too many CA ids!
      Oct 2 14:58:26 omv vdr: [38434] ERROR: too many CA ids!
      Oct 2 14:58:26 omv vdr: [38434] ERROR: too many CA ids!
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/commands.conf
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/reccmds.conf
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/svdrphosts.conf
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/keymacros.conf
      Oct 2 14:58:26 omv vdr: [38435] video directory scanner thread started (pid=38434, tid=38435, prio=high)
      Oct 2 14:58:26 omv vdr: [38434] registered source parameters for 'A - ATSC'
      Oct 2 14:58:26 omv vdr: [38436] video directory scanner thread started (pid=38434, tid=38436, prio=high)
      Oct 2 14:58:26 omv vdr: [38437] epg data reader thread started (pid=38434, tid=38437, prio=high)
      Oct 2 14:58:26 omv vdr: [38434] registered source parameters for 'C - DVB-C'
      Oct 2 14:58:26 omv vdr: [38437] reading EPG data from /var/cache/vdr/epg.data
      Oct 2 14:58:26 omv vdr: [38434] registered source parameters for 'S - DVB-S'
      Oct 2 14:58:26 omv vdr: [38436] video directory scanner thread ended (pid=38434, tid=38436)
      Oct 2 14:58:26 omv vdr: [38435] video directory scanner thread ended (pid=38434, tid=38435)
      Oct 2 14:58:26 omv vdr: [38434] registered source parameters for 'T - DVB-T'
      Oct 2 14:58:26 omv vdr: [38434] no DVB device found
      Oct 2 14:58:26 omv vdr: [38434] initializing plugin: mcli (0.9.2): NetCeiver Client Application
      Oct 2 14:58:26 omv vdr: [38437] epg data reader thread ended (pid=38434, tid=38437)
      Oct 2 14:58:26 omv vdr: [38434] new device number 9
      Oct 2 14:58:26 omv vdr: [38443] section handler thread started (pid=38434, tid=38443, prio=low)
      Oct 2 14:58:26 omv vdr: [38434] new device number 10
      Oct 2 14:58:26 omv vdr: [38444] section handler thread started (pid=38434, tid=38444, prio=low)
      Oct 2 14:58:26 omv vdr: [38434] new device number 11
      Oct 2 14:58:26 omv vdr: [38445] section handler thread started (pid=38434, tid=38445, prio=low)
      Oct 2 14:58:26 omv vdr: [38434] new device number 12
      Oct 2 14:58:26 omv vdr: [38446] section handler thread started (pid=38434, tid=38446, prio=low)
      Oct 2 14:58:26 omv vdr: [38434] new device number 13
      Oct 2 14:58:26 omv vdr: [38447] section handler thread started (pid=38434, tid=38447, prio=low)
      Oct 2 14:58:26 omv vdr: [38434] new device number 14
      Oct 2 14:58:26 omv vdr: [38448] section handler thread started (pid=38434, tid=38448, prio=low)
      Oct 2 14:58:26 omv vdr: [38434] new device number 15
      Oct 2 14:58:26 omv vdr: [38449] section handler thread started (pid=38434, tid=38449, prio=low)
      Oct 2 14:58:26 omv vdr: [38434] new device number 16
      Oct 2 14:58:26 omv vdr: [38450] section handler thread started (pid=38434, tid=38450, prio=low)
      Oct 2 14:58:26 omv vdr: [38434] setting primary device to 1
      Oct 2 14:58:26 omv vdr: [38434] device 1 has no MPEG decoder
      Oct 2 14:58:26 omv vdr: [38434] assuming manual start of VDR
      Oct 2 14:58:26 omv vdr: [38434] setting current skin to "lcars"
      Oct 2 14:58:26 omv vdr: [38434] loading /var/lib/vdr/themes/lcars-default.theme
      Oct 2 14:58:26 omv vdr: [38434] starting plugin: mcli
      Oct 2 14:58:26 omv vdr: [38434] Mcli v0.9.2 started
      Oct 2 14:58:26 omv vdr: [38434] remote control KBD - learning keys
      Oct 2 14:58:26 omv vdr: [38452] KBD remote control thread started (pid=38434, tid=38452, prio=high)
      Oct 2 14:58:26 omv vdr: [38452] cTimeMs: using monotonic clock (resolution is 1 ns)
      Oct 2 14:58:26 omv vdr: [38434] ERROR: no OSD provider available - using dummy OSD!


      Does it work on streamdev? Nope - only at :3000 i can see the channels. vdradmin :8001 doen't even work.

      Where do i put in the params for mcli? There is no mcli.conf in /etc/vdr/plugins.
      When i write

      Source Code

      1. -P"mcli --ifname eth1 --dvb-s2 2"
      into omv-vdr-screen \Extra-Options, i get an error-message.

      What can i do?

      regards
      Erik.
      Auch das geht vorbei ...
      OMV-servant
      HP Microserver Gen8, E3-1265Lv3, 16GB, OCZ-Vertex3 256GB OS, OMV 3.0, 4x 2TB, IBM-Raid5

      The post was edited 2 times, last by Pfeifenraucher ().

    • Source Code

      1. root@NAS:~# dmesg | grep -i dvb
      2. [ 4.708708] smipcie: disagrees about version of symbol dvb_dmxdev_init
      3. [ 4.708716] smipcie: Unknown symbol dvb_dmxdev_init (err -22)
      4. [ 4.708756] smipcie: disagrees about version of symbol dvb_register_adapter
      5. [ 4.708758] smipcie: Unknown symbol dvb_register_adapter (err -22)
      6. [ 4.708766] smipcie: disagrees about version of symbol dvb_dmx_swfilter_packe
      7. [ 4.708768] smipcie: Unknown symbol dvb_dmx_swfilter_packets (err -22)
      8. [ 4.708783] smipcie: disagrees about version of symbol dvb_dmx_release
      9. [ 4.708785] smipcie: Unknown symbol dvb_dmx_release (err -22)
      10. [ 4.708808] smipcie: disagrees about version of symbol dvb_net_init
      11. [ 4.708810] smipcie: Unknown symbol dvb_net_init (err -22)
      12. [ 4.708816] smipcie: disagrees about version of symbol dvb_dmxdev_release
      13. [ 4.708818] smipcie: Unknown symbol dvb_dmxdev_release (err -22)
      14. [ 4.708831] smipcie: disagrees about version of symbol dvb_net_release
      15. [ 4.708833] smipcie: Unknown symbol dvb_net_release (err -22)
      16. [ 4.708855] smipcie: disagrees about version of symbol dvb_unregister_adapter
      17. [ 4.708857] smipcie: Unknown symbol dvb_unregister_adapter (err -22)
      18. [ 4.708860] smipcie: disagrees about version of symbol dvb_dmx_init
      19. [ 4.708862] smipcie: Unknown symbol dvb_dmx_init (err -22)
      Display All


      Eyery few month, my VDR is not working anymore, which is quite annoying. Seems that I again need to re-install TV - card driver. Could it be that it has to do with linux headers, respectively new OMV versions? If yes, ist there any chance to protect?
    • I was using vdr plugin with OMV 2.x and kernel 4.1.7 for a while without any problems.
      Now I updated to OMV 3.0.4 with vdr plugin 3.0 and when I try to search for channels it says: 'main:3107: FATAL: UNKNOWN VDR VERSION'
      I wanna report it and ask if anyone tried it with success....
      My business server: OMV 3.0.91 | intel J2900 + 4GB DDR3 | 64GB SSD OS Disk | 2x1TB WD raid data disks
      Home Server: File server, FTP, Printing server, Plex, Logitech Media Server, VDR, Minecraft Server, Ark Survival Server, jDownloader: OMV 3.0.91 (kernel 4.10 custom
      ) | MSI B150M PRO VDH | i5-6600T 35W | 16GG RAM DDR4 2133 | 60GB SSD OS disk | 120GG SSD Games (Minecraft+Ark)| 1x4TB+2x2TB WD NAS RED HDDs
      Home automation server: OMV 3.0.63 (kernel 4.x) | RaspBerry Pi 3 | 32Gb microSD Sandisk Xtreme | USB-RS485 | mbusd MODBUS TCP<->RTU GATEWAY | HMI SCADA myscadaHome
    • That is risky running 3.x with that many services... I would use the backports 4.3 kernel. I know I don't test with a self compiled kernel so that would just take one more thing out of the equation when fixing bugs.

      Two things... make sure the external vdr is NOT in the sources anymore and make sure the package you installed is from the debian repos.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      That is risky running 3.x with that many services... I would use the backports 4.3 kernel. I know I don't test with a self compiled kernel so that would just take one more thing out of the equation when fixing bugs.

      Two things... make sure the external vdr is NOT in the sources anymore and make sure the package you installed is from the debian repos.


      Yes, I'm running on the 4.3 backports kernel. VDR installed from plugin manager.....
      My business server: OMV 3.0.91 | intel J2900 + 4GB DDR3 | 64GB SSD OS Disk | 2x1TB WD raid data disks
      Home Server: File server, FTP, Printing server, Plex, Logitech Media Server, VDR, Minecraft Server, Ark Survival Server, jDownloader: OMV 3.0.91 (kernel 4.10 custom
      ) | MSI B150M PRO VDH | i5-6600T 35W | 16GG RAM DDR4 2133 | 60GB SSD OS disk | 120GG SSD Games (Minecraft+Ark)| 1x4TB+2x2TB WD NAS RED HDDs
      Home automation server: OMV 3.0.63 (kernel 4.x) | RaspBerry Pi 3 | 32Gb microSD Sandisk Xtreme | USB-RS485 | mbusd MODBUS TCP<->RTU GATEWAY | HMI SCADA myscadaHome
    • @hammondb4: Did you get it to work? I have the same problem with the plugin "openmediavault-vdr 3.0.2" from the omv-extras.org repos.

      Source Code

      1. w_scan version 20130331 (compiled for DVB API 5.9)
      2. using settings for 19.2 east Astra 1F/1G/1H/1KR/1L
      3. scan type SATELLITE, channellist 67
      4. main:3107: FATAL: UNKNOWN VDR VERSION.Done ...


      Greetings Hoppel
      Images
      • vdr_plugin.PNG

        31.3 kB, 1,216×420, viewed 144 times
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------
    • hoppel118 wrote:

      @hammondb4: Did you get it to work? I have the same problem with the plugin "openmediavault-vdr 3.0.2" from the omv-extras.org repos.

      Source Code

      1. w_scan version 20130331 (compiled for DVB API 5.9)
      2. using settings for 19.2 east Astra 1F/1G/1H/1KR/1L
      3. scan type SATELLITE, channellist 67
      4. main:3107: FATAL: UNKNOWN VDR VERSION.Done ...


      Greetings Hoppel


      That issue is because w_scan is called with the argument -o 7 which is for VDR 1.7, in Jessie that option doesn't accept that value anymore. It's fixed in the master branch but that won't be released until the next version of the openmediavault package is released.
    • Ok, thanks for the information. Which openmediavault package exactly do you mean?
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------
    • hoppel118 wrote:

      @hammondb4: Did you get it to work? I have the same problem with the plugin "openmediavault-vdr 3.0.2" from the omv-extras.org repos.

      Source Code

      1. w_scan version 20130331 (compiled for DVB API 5.9)
      2. using settings for 19.2 east Astra 1F/1G/1H/1KR/1L
      3. scan type SATELLITE, channellist 67
      4. main:3107: FATAL: UNKNOWN VDR VERSION.Done ...


      Greetings Hoppel

      The core openmediavault package. There's no ETA for when it'll be released, but probably not soon. However, if you want to scan manually it isn't that difficult. Basically you run w_scan [options] > /etc/vdr/channels.conf. To find what options you need just execute w_scan -h.
    • Ok, thanks. I will get it to work. One last question. This is beta software and officially not supported by the forum. Where is a good place to talk about errors?

      Greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------
    • hoppel118 wrote:

      Where is a good place to talk about errors?


      For third party plugins, its each respective issue page on github for the plugins. For the core its bugtracker.openmediavault.org

      Please do proper reports thought ;)

      Be aware that the next update of the 3.0 version will introduce a massive amount of changes, things will likely be broken all over the place. So be warned if you use this on any kind of production system.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Hi,

      ok, this was easy. I got the omv-plugins "openmediavault-vdr 3.0.2" and "openmediavault-vdr-vnsiserver 3.0.0" (vnsi server v1.3.1) to work with kodi (jarvis 16.0 - vnsi client 1.11.14) on a windows 10 machine. I like this kind of plugins! ;)

      The only thing I had to do was to modify the owner and the prvilileges of the recording directory.

      Now I want to have look for time shifting.

      Greetings Hoppel
      ---------------------------------------------------------------------------------------------------------------
      frontend software - android tv | libreelec | win10 | kodi krypton
      frontend hardware - nvidia shield tv | odroid c2 | yamaha rx-a1020 | quadral chromium style 5.1 | samsung le40-a789r2 | harmony smart control
      -------------------------------------------
      backend software - debian | kernel 4.4 lts | proxmox | openmediavault | zfs raid-z2 | docker | emby | vdr | vnsi | fhem
      backend hardware - supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x4tb wd red | digital devices max s8
      ---------------------------------------------------------------------------------------------------------------------------------------