Posts by Rene

    Any idea when the dead links will be brought back to life? The search-engines are full of dead links, and all old posts with links end up nowhere like eg. this link:


    Code
    1. https://www.vdr-portal.de/board17-developer/board21-vdr-plugins/p1293244-streamdev-plugin-f%C3%BCr-vdr-2-3-x/#post1293244


    :-(

    Hi,


    Thanks! Great to see that it's not a forgotten skin. I got though the following error when compiling it:

    Hi,


    Is there an updated version somewhere for the Skinenigmang-plugin so it would compile against VDR-2.3.x? I can't change the skin to something else, because the rest of my family would not accept it :-( It would suck if i could not upgrade to the 2.3.x-version of VDR :-(

    fnu

    Ok. I'll try with an upgrade...


    When i earlier tried to upgrade from precise to thrusty, i got issues with having a choppy experience of anything that i watched live or recorded... I have though upgraded my mb + processor since then, so maybe this time it may work. Maybe i even try to return back to Gentoo :-)

    Hi Guys,


    Sorry to disturb with english in a german thread..


    I get the same error

    as jv16Bar got. This is an (old Ubuntu Precise) distro with a more recent kernel. This error appears since 2.3.4 in all VDR-versions. I run a 3.13 version of the kernel.

    Code
    1. uname -a
    2. Linux htpc 3.13.0-117-generic #164~precise1-Ubuntu SMP Mon Apr 10 16:16:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

    In the releasenote is mentioned about DVB API 5

    Quote

    - Signal strength and quality (CNR) are now determined via DVB API 5 (if available).


    Fallback is the old DVB API 3 method.


    But according to the note at linuxtv.org, https://linuxtv.org/docs/libdvbv5/ the dvb5api should be in kernels since kernel-version 3.3.. It would be great if someone could help me (us) out :-)

    Hi all!


    sorry for my lousey german, but i hope you'll get it :-)


    Ich habe seit viele jahre die xmltv+xmltv2vdr.pl benuzt, und bis funktioniert gut. Ich möchte aber die xmltv2vdr-plugin probieren, aber ich verstehe nicht genau was ich noch tun soll... Ich habe die xml-daten von xmltv (mit tv_grab_fi geholt). Ich habe habe auch die kontrol-daten gebastelt, und die files sind in /var/lib/epgdata

    Code
    1. root@htpc:/var/lib/epgsources# ls -la
    2. total 4072
    3. drwxr-xr-x 2 root root 4096 2012-08-07 09:50 .
    4. drwxr-xr-x 74 root root 4096 2012-08-06 22:15 ..
    5. -rw-r--r-- 1 root root 294 2012-08-07 10:31 epg_utf8
    6. -rw-r--r-- 1 root root 4025327 2012-08-06 22:15 epg_utf8.xmltv
    7. root@htpc:/var/lib/epgsources#



    Die epg_utf8.xmltv-file ist hier nur als muster das es handelt sich um richtige inhalt.

    XML
    1. <?xml version="1.0" encoding="UTF-8"?>
    2. <!DOCTYPE tv SYSTEM "xmltv.dtd">
    3. <tv source-info-url="multiple" source-data-url="multiple" generator-info-name="XMLTV" generator-info-url="http://xmltv.org/">
    4. <channel id="imdeutschewellet.telvis.fi">
    5. <display-name lang="fi">Deutsche Welle</display-name>
    6. </channel>
    7. <programme start="20120806050000 +0300" stop="20120806051500 +0300" channel="imdeutschewellet.telvis.fi">
    8. <title lang="fi">Journal - News</title>
    9. </programme>
    10. </tv>


    Die Mapping habe ich auch gemacht, und sieht aus daß es in ordning sein soll in vdr:s setup.conf:


    Bei umstart von VDR bekomme ich aber die volgende fähler in syslog:


    Mit selbe timestamp "Aug 7 10:39:52" gibt 50 wiederholungen mit "ERROR (script) sh: epg_utf8: not found"


    Wozu sucht es ein epg_utf8 script? Warum brauche ich es wenn ihch die xmltv xml-daten schon habe?


    Viele Grüße,


    René


    ps. Köntte man ein parameter vür das plugin geben wo man die "/var/lib/epgdata" ändern köntte? Ich habe alle meine vdr-daten unter /data/ habe..

    Oh, silly of me.. Indeed the patch updated the Make.config :-)


    Unfortunately i get now compilation errors:


    Do you know what these errors mean? I try to compile this on Ubuntu 11.10

    Hallo,


    Mir passt Deutsch ebenso gut. Ich versteche und spreche deuch fliesend (mit grammatik fehlers ;-) Meine Deutsche rechtscreibung ist auch nict die beste ;-) Leichter ist es mir Engslish schreiben :-)


    I tried the SoundGraphs iMon remote (imon-mce and imon-pad), but that did not give me any joy when runningn ir-keytable -t and pressing buttons. Did you maybe use an other profile? If you could please post me the path you took in the logitech config app to find the right remote..


    I use btw Gentoo, so but i'll check out yhat post you recommended and see what that brings me :-) Thanks!!

    Ist es Jemanden gelungen ein Harmony 525 oder Harmony 895 programmieren so das alle tasten funktionieren mit die Antec Fusion Remote Max gehäuse? Leider habe ich bis jezt nur problemem.. Die einzige remote wo am meisten tasten funktionieren ist die "COmputer->Media Center Pc -> Microsoft -> MCE-500". Leider sind hier die Ok, Prev und Menu-tasten mit die selven key-koden.. :-(

    You got it additionally w/ our VDR 1.7.20 packages for yaVDR 0.3.1, isn't it? So, maintaining it, doesn't mean to like it ...


    The last versions of the VDR package I was the one who had to maintain it and I can't express how much I hate the livebuffer patch. It generates a enormous workload and the fact that I even don't use it doesn't make it easier.

    Hi guys!


    Sorry for being late with my reply. Had a pretty tough 2 weeks, and did not get the time to check in here.


    I think it's no point that I to try to explain why the livebuffer-patch is so great :-) My wife and myself use it a lot :-)


    Could you please help me out in extracting the patch you have in the yavdr-repo. I'm not so good with this kind of things :-) I'm good in following instructions :-)


    I whish you all a Guten Rutsch ins neue Jahr! :-)

    Hi folks!
    I have still not been succesful with getting VDR to run on the VIP. It makes me wonder if anyone is really successful with their setup, and can use VDR?


    Could you please shere with me which Flash-version of the system you are using... Are you using a stripped down version of the default kernel-1710, or have you compiled a new kernel?


    I have been using the debug-kernel for booting up the box over a nfs-root share, and i wonder if there could be some switches that the default debug-kernel is using that makes VDR fail to run..

    Does anyone know what these errors mean when starting vdr on the vip?


    Code
    1. vip1710: 19:21:27 vip1710: PlayTs written=0 error=9:Bad file descriptor
    2. vip1710: 19:21:27 vip1710: PlayTs written=0 error=9:Bad file descriptor
    3. vip1710: 19:21:27 vip1710: PlayTs written=0 error=9:Bad file descriptor
    4. vip1710: 19:21:27 vip1710: PlayTs written=0 error=9:Bad file descriptor
    5. vip1710: 19:21:27 vip1710/player: fatal error during select(), exiting
    6. vip1710: 19:21:27 vip1710: PlayTs written=0 error=9:Bad file descriptor
    7. vip1710: 19:21:27 vip1710: PlayTs written=0 error=9:Bad file descriptor
    8. vip1710: 19:21:27 vip1710: PlayTs written=0 error=9:Bad file descriptor
    9. vip1710: 19:21:27 vip1710: PlayTs written=0 error=9:Bad file descriptor


    And this goes on.. :-(