Bin noch nicht ganz soweit meine Wohnzimmer VDR 2.2.0, oder zumindest einen davon komplett mit VDR 2.3.4 zu ersetzen. Auf den Geräten habe ich aber jrie's Patch für VDR 2.2.0 am Start, aber auch mit Verlagerungen von Timern dafür gesorgt, dass die Situation vmtl. nicht mehr auftritt.
Habe aber sehr interessiert die Changes zu VDR 2.3.3/4 gelesen und hatte mir schon gedacht, das könnten Verbesserungen sein.
Regards
fnu
Besten Dank!
Hab das eben mal zusammengabut (auf einem virtuellen Fedora 25 System - benutze satip als input). Sieht soweit mal gut aus.
Allerdings läuft das epgsearch-plugin nicht. Dort wird die Funktion "HandleRemoteModifications" aufgerufen, die in menu.c als "static" deklariert ist. D.h. die ist nicht sichtbar. Wenn ich in menu.c das "static" für HandleRemoteModifications entferne, dann funktioniert alles. Aber das war ja wohl nicht im Sinne des Erfinders ...
Gruß
HISTORY:
2017-04-27: Version 2.3.4
- The functionality of HandleRemoteModifications(), which synchronizes changes to
timers between peer VDR machines, has been moved to timers.[ch] and renamed to
HandleRemoteTimerModifications(). It now also handles deleting remote timers.
Klaus
Zitat
- Added some guidelines and recommendations to the 'Logging' section of PLUGINS.html.
The most important being: implement a command line option to control the level
of logging (in particular allow turning off logging completely!) and never print
anything to stdout or stderr (unless one of the listed exceptions applies).
Ob das wohl zu Verbesserungen in softhddevice führt?
- Markus
softhddevice verhält sich inzwischen bereits so ;-).
Klaus
Irgendwie kann ich mit 2.3.4 keine Timer mehr setzten, mit 2.3.3 hatte das glaube ich noch funktioniert (bin mir aber nicht 100%ig sicher). Das Timer-Menü bleibt offen, ich kann über die Fernbedienung nichts mehr steuern (Bild und Ton läuft im Hintergrund weiter). Nach kurzer Zeit schlägt dann der Watchdog zu und startet den VDR neu, der gewählte Timer ist aber nicht aktiv. Das Problem tritt mit VDR 2.3.4 im Zusammenhang mit Graphtft-ng auf. Ohne Graphtft-ng funktioniert das.
May 07 12:00:59 vdr vdr[838]: [90B blob data]
May 07 12:00:59 vdr vdr[838]: [graphTFT] OsdClear
May 07 12:00:59 vdr vdr[838]: [graphTFT] OsdMenuDisplay - set category (2) to 'MenuSchedule'
May 07 12:00:59 vdr vdr[838]: [838] timer 0 (17 1200-1325 VPS 'Des Kaisers neue Kleider') set to event So. 07.05.2017 12:00-13:25 (VPS: 07.05. 12:00)
'Des Kaisers neue Kleider'
May 07 12:00:59 vdr vdr[838]: [graphTFT] trylock for finalizeItemList(CHANNELS)
May 07 12:00:59 vdr vdr[838]: [graphTFT] trylock for finalizeItemList(REGORDINGS)
May 07 12:00:59 vdr vdr[838]: [graphTFT] Force draw of all items now
May 07 12:01:49 vdr vdr[838]: video: slow down video, duping frame
May 07 12:01:49 vdr vdr[838]: video: 20:29:32.997 +19 436 0/\ms 38+1+4 v-buf
May 07 12:01:59 vdr vdr[838]: [838] PANIC: watchdog timer expired - exiting!
#0 0x00007fefd8f468d7 in raise () at /lib64/libc.so.6
#1 0x00007fefd8f47caa in abort () at /lib64/libc.so.6
#2 0x00007fefd8f841b4 in () at /lib64/libc.so.6
#3 0x00007fefd8f899d6 in malloc_printerr () at /lib64/libc.so.6
#4 0x00007fefd8f89ca2 in malloc_consolidate () at /lib64/libc.so.6
#5 0x00007fefd8f8a6cb in _int_free () at /lib64/libc.so.6
#6 0x00007fefcbdc6efe in cDisplayImage::~cDisplayImage() (this=0x12e0de0, __in_chrg=<optimized out>) at ./theme.h:721
#7 0x0000000000522401 in cListBase::Clear() (this=0x112a3d0) at tools.c:2210
#8 0x00007fefcbde54fe in cGraphTFTTheme::exit() (this=this@entry=0x10e3ce0) at theme.c:1841
#9 0x00007fefcbdeb6ef in cGraphTFTTheme::~cGraphTFTTheme() (this=0x10e3ce0, __in_chrg=<optimized out>) at ./theme.h:1116
#10 0x00007fefcbdeb6ef in cGraphTFTTheme::~cGraphTFTTheme() (this=0x10e3ce0, __in_chrg=<optimized out>) at ./theme.h:1116
#11 0x0000000000522401 in cListBase::Clear() (this=this@entry=0x7fefcc00c6a0 <themes>) at tools.c:2210
#12 0x00000000005224e2 in cListBase::~cListBase() (this=0x7fefcc00c6a0 <themes>, __in_chrg=<optimized out>) at tools.c:2117
#13 0x00007fefcbdea1db in cGraphTFTThemes::~cGraphTFTThemes() (this=<optimized out>, __in_chrg=<optimized out>)
at /video/src/vdr/include/vdr/tools.h:572
#14 0x00007fefcbdea1db in cGraphTFTThemes::~cGraphTFTThemes() (this=<optimized out>, __in_chrg=<optimized out>) at ./theme.h:1243
#15 0x00007fefd8f49139 in __run_exit_handlers () at /lib64/libc.so.6
#16 0x00007fefd8f49185 in () at /lib64/libc.so.6
#17 0x0000000000527c0f in Watchdog(int) (signum=<optimized out>) at vdr.c:177
#18 0x00007fefd8f46950 in <signal handler called> () at /lib64/libc.so.6
#19 0x00007fefda8d4a7a in __lll_lock_wait () at /lib64/libpthread.so.0
#20 0x00007fefda8cf793 in pthread_mutex_lock () at /lib64/libpthread.so.0
#21 0x000000000051cc65 in cMutex::Lock() (this=0xfe53e0) at thread.c:219
#22 0x000000000051d259 in cMutexLock::Lock(cMutex*) (this=0x7fff38dd7a70, Mutex=<optimized out>) at thread.c:399
#23 0x000000000051d280 in cMutexLock::cMutexLock(cMutex*) (this=<optimized out>, Mutex=<optimized out>) at thread.c:386
#24 0x00007fefcbdcc988 in cGraphTFTDisplay::OsdCurrentItem(char const*) (this=0xfe4f90, Text=0x1fc3910 "Aktiv:\tnein") at status.c:486
#25 0x0000000000511646 in cStatus::MsgOsdCurrentItem(char const*) (Text=0x1fc3910 "Aktiv:\tnein") at status.c:113
#26 0x00000000004ceedf in cMenuEditItem::SetValue(char const*) (this=this@entry=0x1fc37e0, Value=Value@entry=0x7fff38dd7b10 "nein")
at menuitems.c:41
#27 0x00000000004cf039 in cMenuEditBoolItem::Set() (this=this@entry=0x1fc37e0) at menuitems.c:152
#28 0x00000000004cf0c2 in cMenuEditBoolItem::cMenuEditBoolItem(char const*, int*, char const*, char const*) (this=this@entry=0x1fc37e0, Name=<optimized out>, Value=Value@entry=0x1fc3874, FalseString=0x0, TrueString=0x0) at menuitems.c:145
#29 0x00000000004cf148 in cMenuEditBitItem::cMenuEditBitItem(char const*, unsigned int*, unsigned int, char const*, char const*) (this=0x1fc37e0, Name=<optimized out>, Value=0x1fc333c, Mask=1, FalseString=<optimized out>, TrueString=<optimized out>) at menuitems.c:158
#30 0x00000000004c905b in cMenuEditTimer::cMenuEditTimer(cTimer*, bool) (this=0x1fc31e0, Timer=<optimized out>, New=<optimized out>) at menu.c:994
#31 0x00000000004c9fe0 in cMenuSchedule::Record() (this=this@entry=0x1ee7000) at menu.c:1983
#32 0x00000000004ca239 in cMenuSchedule::ProcessKey(eKeys) (this=0x1ee7000, Key=kRed) at menu.c:2029
#33 0x00000000004d6211 in cOsdMenu::ProcessKey(eKeys) (this=this@entry=0x1eca560, Key=Key@entry=kRed) at osdbase.c:535
#34 0x00000000004c8701 in cMenuMain::ProcessKey(eKeys) (this=0x1eca560, Key=kRed) at menu.c:4397
#35 0x000000000052b702 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at vdr.c:1388Das Problem ist bekannt.
Danke für die Info, ich habe das in dem Thread auch noch mal gepostet.
Klaus hatte mir schon den Tip gegeben, das mal testweise zu ändern, vielen Dank dafür:
Index: b/epg.h
===================================================================
--- a/epg.h
+++ b/epg.h
@@ -284,7 +284,7 @@
virtual bool DropOutdated(cSchedule *Schedule, time_t SegmentStart, time_t SegmentEnd, uchar TableID, uchar Version) { return false; }
///< Takes a look at all EPG events between SegmentStart and SegmentEnd and
///< drops outdated events.
- virtual bool BeginSegmentTransfer(const cChannel *Channel, bool Dummy) { return false; } // TODO remove obsolete Dummy
+ virtual bool BeginSegmentTransfer(const cChannel *Channel, bool Dummy) { return true; } // TODO remove obsolete Dummy
///< Called directly after IgnoreChannel() before any other handler method is called.
///< Designed to give handlers the possibility to prepare a database transaction.
///< If any EPG handler returns false in this function, it is assumed that
Nun blockiert xmltv2vdr und vmtl. auch noepg nicht mehr den Eingang von DVB EPG.
Regards
fnu
ZitatKlaus hatte mir schon den Tip gegeben, das mal testweise zu ändern, vielen Dank dafür:
ja das ist die Richtige Lösung, ich habe in dem Patch, welcher in 2.3.4 eingeflossen ist, vergessen den Rückgabewert anzupassen, der Fehler fällt ohne Handler Plugin nicht auf und auch nicht mit epg2vdr da dieses die Methode überschreibt. daher ist er leider beim testen untergegangen.
Sorry dafür!
Grüße Jörg
Hi,
so wie ich Klaus verstehe bleibt es bei beiEndSegmentTransfer beim alten da hierüber nichts gesteuert werden soll/muss. Ohne weitere Code Änderung wäre dort jedenfalls 'true' als default falsch!
Grüße Jörg
Hi Guys,
Sorry to disturb with english in a german thread..
I get the same error
dvbdevice.c: In member function 'bool cDvbTuner::GetSignalStats(int&, double*, double*, double*, double*, double*) const':
dvbdevice.c:585:19: error: 'DTV_STAT_SIGNAL_STRENGTH' was not declared in this scope
dvbdevice.c:586:19: error: 'DTV_STAT_CNR' was not declared in this scope
dvbdevice.c:587:19: error: 'DTV_STAT_PRE_ERROR_BIT_COUNT' was not declared in this scope
dvbdevice.c:588:19: error: 'DTV_STAT_PRE_TOTAL_BIT_COUNT' was not declared in this scope
dvbdevice.c:589:19: error: 'DTV_STAT_POST_ERROR_BIT_COUNT' was not declared in this scope
dvbdevice.c:590:19: error: 'DTV_STAT_POST_TOTAL_BIT_COUNT' was not declared in this scope
dvbdevice.c:591:19: error: 'DTV_STAT_ERROR_BLOCK_COUNT' was not declared in this scope
dvbdevice.c:592:19: error: 'DTV_STAT_TOTAL_BLOCK_COUNT' was not declared in this scope
dvbdevice.c:600:21: error: 'union dtv_property::<anonymous>' has no member named 'st'
dvbdevice.c:601:28: error: 'union dtv_property::<anonymous>' has no member named 'st'
dvbdevice.c:602:16: error: 'FE_SCALE_DECIBEL' was not declared in this scopeas 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.
uname -a
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/LinuxIn the releasenote is mentioned about DVB API 5
Zitat- 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 
You need to test with a newer kernel version. Either using a mainline kernel or updating to Ubuntu Trusty, an easy task with "do-release-upgrade", there you get kernel 4.4 as latest. Precise is out of support since April 2017.
So, maybe in theory DVB-API5 is part since these early kernel versions, but due to it's ongoing development things have been improved and functions have been added over the time.
Cheers
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
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!