[ANNOUNCE] VDR developer version 2.3.4

  • Frage (ohne testen zu können):


    +#ifdef DEBUG_SIGNALSTATS
    + fprintf(stderr, "FE %d/%d: API5 %04X", adapter, frontend, Valid);
    + if ((Valid & DTV_STAT_VALID_STRENGTH) != 0) fprintf(stderr, " STR=%1.1fdBm", *Strength);
    + if ((Valid & DTV_STAT_VALID_CNR) != 0) fprintf(stderr, " CNR=%1.1fdB", *Cnr);
    + if ((Valid & DTV_STAT_VALID_BERPRE) != 0) fprintf(stderr, " BERPRE=%1.1e", *BerPre);
    + if ((Valid & DTV_STAT_VALID_BERPOST) != 0) fprintf(stderr, " BERPOST=%1.1e", *BerPost);
    + if ((Valid & DTV_STAT_VALID_PER) != 0) fprintf(stderr, " PER=%1.1e", *Per);
    + fprintf(stderr, "\n");
    +#endif



    %1.1f als Format gibt die gesamt Anzahl der float digits als '1' an sowie eine Nachkommastelle.
    Wäre für beispielsweise STR '-100.0' [dBm] nicht %6.1f bzw. CNR %5.1f [dBc] sinnvoller? Oder übersehe ich was?

  • What am I doing wrong?

    Code
    1. dvbdevice.c: In member function ‘bool cDvbTuner::GetSignalStats(int&, double*, double*, double*, double*, double*) const’:
    2. dvbdevice.c:585:19: error: ‘DTV_STAT_SIGNAL_STRENGTH’ was not declared in this scope
    3. dvbdevice.c:586:19: error: ‘DTV_STAT_CNR’ was not declared in this scope


    This is a Raspi 2 with raspbian without dvb device.

    Server: Celeron J1800M-D3P, 6x DVB-S2 adapter, 6x Inverto quad LNB.
    Client 1: RPi 2 model B, rpihddevice, Sharp 42" LC40LE600, Client 2: RPi 1 Model B, rpihddevice, Asus Led HD monitor, Client 3: RPi 1 Model A, rpihddevice, CRT TV, Client 4: RPi 3, rpihddevice, in test.
    VDR user since: 2005-11-27 (#1199)

  • Code
    1. pi@rpi2B ~ $ uname -a
    2. Linux rpi2B 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux

    Server: Celeron J1800M-D3P, 6x DVB-S2 adapter, 6x Inverto quad LNB.
    Client 1: RPi 2 model B, rpihddevice, Sharp 42" LC40LE600, Client 2: RPi 1 Model B, rpihddevice, Asus Led HD monitor, Client 3: RPi 1 Model A, rpihddevice, CRT TV, Client 4: RPi 3, rpihddevice, in test.
    VDR user since: 2005-11-27 (#1199)

  • Bei mir sieht das so aus:

    Code
    1. root@raspberrypi:~# uname -a
    2. Linux raspberrypi 4.9.22+ #987 Fri Apr 14 23:13:48 BST 2017 armv6l GNU/Linux


    vdr-User-# 755 to_h264 chk_r

  • kls


    Vielen Dank für die neue Developer Version und Deine Mühen!


    JV16Bar


    Yepp, you may try to run "sudo rpi-update" ... mine looks with Raspbian like this:


    Code
    1. rpi2-pi:/home/pi> uname -a
    2. Linux rpi2 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux


    Regards
    fnu

    HowTo: APT pinning

  • Thank you for the hint, I upgraded my kernel, and now I have:

    Code
    1. pi@rpi2B / $ uname -a
    2. Linux rpi2B 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017 armv7l GNU/Linux


    But when I compiling vdr-2.3.4, I'm getting the same error.

    Server: Celeron J1800M-D3P, 6x DVB-S2 adapter, 6x Inverto quad LNB.
    Client 1: RPi 2 model B, rpihddevice, Sharp 42" LC40LE600, Client 2: RPi 1 Model B, rpihddevice, Asus Led HD monitor, Client 3: RPi 1 Model A, rpihddevice, CRT TV, Client 4: RPi 3, rpihddevice, in test.
    VDR user since: 2005-11-27 (#1199)

  • Hmm, only rough guess I have is, that this fallback may not work properly ...


    Code
    1. - Signal strength and quality (CNR) are now determined via DVB API 5 (if available).
    2. Fallback is the old DVB API 3 method.


    VDR 2.3.3 did work for you? Even with your older kernel version?


    Regards
    fnu

    HowTo: APT pinning

  • Well, 2.3.3 I did not try, I used 2.3.1 on this raspi.
    But I have another raspi (3 B) which runs 2.3.3 fine.


    I will try 2.3.4 on raspi 3 tomorrow.

    Server: Celeron J1800M-D3P, 6x DVB-S2 adapter, 6x Inverto quad LNB.
    Client 1: RPi 2 model B, rpihddevice, Sharp 42" LC40LE600, Client 2: RPi 1 Model B, rpihddevice, Asus Led HD monitor, Client 3: RPi 1 Model A, rpihddevice, CRT TV, Client 4: RPi 3, rpihddevice, in test.
    VDR user since: 2005-11-27 (#1199)

  • I will try 2.3.4 on raspi 3 tomorrow.

    Don't think there's a difference, if this is also on Raspbian, it's the same kernel from my point of view.


    Regards
    fnu

    HowTo: APT pinning

  • Ok, let it build for Ubuntu Xenial with this kernel version:


    Code
    1. Kernel version: Linux lcy01-34 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64


    This is initial default kernel version of Xenial ... and works.


    Maybe the Raspbian Kernel does miss proper DVB API part to reduce size or so ...


    Regards
    fnu

    HowTo: APT pinning

  • Läuft bei mir auf vdr2.


    Danke an Klaus für diese Version, besonders die Verbesserung der Nummerieung von Aufzeichnungen (recordings)


    vdr-User-# 755 to_h264 chk_r

  • It could be something wrong with my Raspi 2 OS (altough i did not received any errors during update). I managed to compile vdr-2.3.4 on my raspi 3 without any errors.


    Code
    1. pi@rpi3:/opt/vdr-2.3.4$ uname -a
    2. Linux rpi3 4.4.12-v7+ #892 SMP Thu Jun 2 15:41:19 BST 2016 armv7l GNU/Linux
    3. pi@rpi3:/opt/vdr-2.3.4$ ll ./vdr
    4. -rwxr-xr-x 1 pi pi 5.5M ápr 28 11:07 ./vdr

    Server: Celeron J1800M-D3P, 6x DVB-S2 adapter, 6x Inverto quad LNB.
    Client 1: RPi 2 model B, rpihddevice, Sharp 42" LC40LE600, Client 2: RPi 1 Model B, rpihddevice, Asus Led HD monitor, Client 3: RPi 1 Model A, rpihddevice, CRT TV, Client 4: RPi 3, rpihddevice, in test.
    VDR user since: 2005-11-27 (#1199)

  • JV16Bar


    Try also to update kernel on your Raspberry 3 using "sudo rpi-update" ...


    Regards
    fnu

    HowTo: APT pinning

  • Das müsste jemand von denen sagen, die damals getestet haben. Ich hatte das Problem ja nicht, da ich die kritischen Plugins nicht benutze (osdteletext, streamdev, permashift). fnu hatte eine Test-Situation.
    Wer benutzt schon vdr-2.3.4, und auch osdteletext, streamdev, permashift, und kann dazu was sagen?