Danke JoeBar Ich hatte das schon im vdr Wiki gelesen und so ausprobiert aber hat nichts gebracht. Trotzdem hilfreich zu wissen an der Schraube nicht weiter drehen zu müssen. Ich werde das in den nächsten Tagen so einstellen und nochmal probieren und ggfs. mit den channels.conf rumspielen.
Beiträge von EricAmir
-
-
Die channels.conf (im Anhang) benutzte ich schon ewig bei mir zu Hause. Der jultec multiswitch ist im ein anderem Haus. Könnte es daran liegen?
Die LNB Kabel am jultec Eingänge sind beschriftet
1 28.2 LV
2 28.2 LH
3 28.2 HB
4 28.2 HH
5 19.2 LV
6 19.2 LH
7 19.2 HB
8 19.2 HH
Ich habe jegliche diseqc.conf Konfigurationen (im Anhang) - full diseqc, mini diseqc, optimized for full diseqc - ohne Erfolg ausprobiert.
Bekomme nur wenige ITV Programme von 10861 Transponder sonst nix. Wäre dankbar für Vorschläge.
-
Ein Sat fähiges Fernsehen kann deutsche, englische Programme empfangen aber nicht mein VDR. Verschiedene diseqc Varianten - toneburst, full diseqc, optimized diseqc - ohne Erfolg ausprobiert. Mit eingeschalteter o. ausgeschalteter diseqc im LNB Menü werden nur vereinzelte englische Programme empfangen obwohl der grüne Balken Empfang für deutsche Programme anzeigt wird. Foto im Anhang.
-
Ich habe den tt-4600s im Einsatz aber nur als satip Server (tvheadend) mit raspbian buster und musste lediglich die Firmware kopieren von http://palosaari.fi/linux/v4l-….B/dvb-demod-m88ds3103.fw nach /lib/firmware
pi@satip:~ $ grep dvb /var/log/syslog
Apr 14 03:31:32 satip kernel: [ 4.416494] dvb-usb: found a 'TechnoTrend TT-connect S2-4600' in warm state.
Apr 14 03:31:32 satip kernel: [ 4.422143] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
Apr 14 03:31:32 satip kernel: [ 4.436356] dvbdev: DVB: registering new adapter (TechnoTrend TT-connect S2-4600)
Apr 14 03:31:32 satip kernel: [ 4.448010] dvb-usb: MAC address: bc:ea:2b:46:0e:f1
Apr 14 03:31:32 satip kernel: [ 4.869666] dvb-usb: schedule remote query interval to 250 msecs.
Apr 14 03:31:32 satip kernel: [ 4.869691] dvb-usb: TechnoTrend TT-connect S2-4600 successfully initialized and connected.
Apr 14 03:31:34 satip kernel: [ 8.507917] m88ds3103 7-0068: downloading firmware from file 'dvb-demod-m88ds3103.fw'
Apr 14 03:31:35 satip tvheadend[461]: linuxdvb: adapter added /dev/dvb/adapter0
-
Hi Seahawk
Nachdem ich die drop-in Sachen im post in /etc/systemd/system/multi-user.target.wants/Vdr.service konsolidiert habe lief Vdr nicht nachdem reboot. Ist das die richtige Vorgehensweise?
Gruß
-
Hallo Seahawk
Mein Ziel ist ein vdr für ein RP B+ mit selbst kompilierten rpihddevice mit Stretch. Bei start wird kurz ein grünes Kästchen mit no Channel Meldung gezeigt, gefolgt von ein rosa Kästchen mit Tag und Datum, und im Hintergrund werden immer noch log Einträge gezeigt obwohl auf tty10 in cmdline.txt angepasst. Aber Tastatur mit Remote.conf von ein anderen Rechner (x86) funktioniert nicht ☹️.
Code
Alles anzeigenOct 6 15:02:10 raspberrypi systemd[1]: Starting Video Disk Recorder... Oct 6 15:02:11 raspberrypi vdr: [724] VDR version 2.2.0 started Oct 6 15:02:11 raspberrypi vdr: [724] switched to user 'vdr' Oct 6 15:02:11 raspberrypi vdr: [724] codeset is 'UTF-8' - known Oct 6 15:02:11 raspberrypi vdr: [724] found 28 locales in /usr/share/locale Oct 6 15:02:11 raspberrypi vdr: [724] loading plugin: /usr/lib/vdr/plugins/libvdr-satip.so.2.2.0 Oct 6 15:02:11 raspberrypi vdr: [724] loading plugin: /usr/lib/vdr/plugins/libvdr-rpihddevice.so.2.2.0 Oct 6 15:02:12 raspberrypi vdr: [724] loading /var/lib/vdr/setup.conf Oct 6 15:02:12 raspberrypi vdr: [724] loading /var/lib/vdr/sources.conf Oct 6 15:02:12 raspberrypi vdr: [724] loading /var/lib/vdr/diseqc.conf Oct 6 15:02:12 raspberrypi vdr: [724] loading /var/lib/vdr/scr.conf Oct 6 15:02:12 raspberrypi vdr: [724] loading /var/lib/vdr/channels.conf Oct 6 15:02:13 raspberrypi vdr: [724] loading /var/lib/vdr/commands.conf Oct 6 15:02:13 raspberrypi vdr: [724] loading /var/lib/vdr/reccmds.conf Oct 6 15:02:13 raspberrypi vdr: [724] loading /var/lib/vdr/svdrphosts.conf Oct 6 15:02:13 raspberrypi vdr: [724] loading /var/lib/vdr/remote.conf Oct 6 15:02:13 raspberrypi vdr: [724] loading /var/lib/vdr/keymacros.conf Oct 6 15:02:13 raspberrypi vdr: [724] loading /var/lib/vdr/remote.conf Oct 6 15:02:13 raspberrypi vdr: [724] loading /var/lib/vdr/keymacros.conf Oct 6 15:02:13 raspberrypi vdr: [724] registered source parameters for 'A - ATSC' Oct 6 15:02:13 raspberrypi vdr: [724] registered source parameters for 'C - DVB-C' Oct 6 15:02:13 raspberrypi vdr: [724] registered source parameters for 'S - DVB-S' Oct 6 15:02:13 raspberrypi vdr: [724] registered source parameters for 'T - DVB-T' Oct 6 15:02:13 raspberrypi vdr: [724] no DVB device found Oct 6 15:02:13 raspberrypi vdr: [724] initializing plugin: satip (2.2.4): SAT>IP Devices Oct 6 15:02:13 raspberrypi vdr: [728] epg data reader thread started (pid=724, tid=728, prio=high) Oct 6 15:02:13 raspberrypi vdr: [728] reading EPG data from /var/cache/vdr/epg.data Oct 6 15:02:13 raspberrypi vdr: [728] epg data reader thread ended (pid=724, tid=728) Oct 6 15:02:13 raspberrypi vdr: [727] video directory scanner thread started (pid=724, tid=727, prio=high) Oct 6 15:02:13 raspberrypi vdr: [727] video directory scanner thread ended (pid=724, tid=727) Oct 6 15:02:13 raspberrypi vdr: [726] video directory scanner thread started (pid=724, tid=726, prio=high) Oct 6 15:02:13 raspberrypi vdr: [726] video directory scanner thread ended (pid=724, tid=726) Oct 6 15:02:13 raspberrypi vdr: [724] cTimeMs: using monotonic clock (resolution is 1 ns) Oct 6 15:02:13 raspberrypi vdr: [724] new device number 1 Oct 6 15:02:13 raspberrypi vdr: [724] SATIP: Creating device CardIndex=0 DeviceNumber=0 [device 0] Oct 6 15:02:13 raspberrypi vdr: [724] new device number 2 Oct 6 15:02:13 raspberrypi vdr: [724] SATIP: Creating device CardIndex=1 DeviceNumber=1 [device 1] Oct 6 15:02:13 raspberrypi vdr: [724] initializing plugin: rpihddevice (1.0.4): HD output device for Raspberry Pi Oct 6 15:02:13 raspberrypi vdr: [729] SATIP poller thread started (pid=724, tid=729, prio=high) Oct 6 15:02:13 raspberrypi vdr: [730] SATIP discover thread started (pid=724, tid=730, prio=high) Oct 6 15:02:13 raspberrypi vdr: [731] SATIP#0 tuner thread started (pid=724,tid=731, prio=high) Oct 6 15:02:13 raspberrypi vdr: [732] SATIP#0 section handler thread started (pid=724, tid=732, prio=high) Oct 6 15:02:13 raspberrypi vdr: [733] device 1 section handler thread started (pid=724, tid=733, prio=low) Oct 6 15:02:13 raspberrypi vdr: [734] SATIP#1 tuner thread started (pid=724, tid=734, prio=high) Oct 6 15:02:13 raspberrypi vdr: [735] SATIP#1 section handler thread started (pid=724, tid=735, prio=high) Oct 6 15:02:13 raspberrypi vdr: [736] device 2 section handler thread started (pid=724, tid=736, prio=low) Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: supported HDMI modes: Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[01]: 640x 480@60p | 4:3 | 25.200MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[02]: 720x 480@60p | 4:3 | 27.027MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[03]: 720x 480@60p | 16:9 | 27.027MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[04]: 1280x 720@60p | 16:9 | 74.250MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[05]: 1920x1080@60i | 16:9 | 74.250MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[16]: 1920x1080@60p | 16:9 | 148.500MHz (native) (current) Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[17]: 720x 576@50p | 4:3 | 27.000MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[18]: 720x 576@50p | 16:9 | 27.000MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[19]: 1280x 720@50p | 16:9 | 74.250MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[20]: 1920x1080@50i | 16:9 | 74.250MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[21]: 720x 576@50i | 4:3 | 27.000MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[31]: 1920x1080@50p | 16:9 | 148.500MHz (native) Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[32]: 1920x1080@24p | 16:9 | 74.250MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[33]: 1920x1080@25p | 16:9 | 74.250MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: CEA[34]: 1920x1080@30p | 16:9 | 74.250MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: DMT[04]: 640x 480@60p | 4:3 | 25.200MHz 6 15:02:13 raspberrypi vdr: [724] rpihddevice: DMT[09]: 800x 600@60p | 4:3 | 40.000MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: DMT[16]: 1024x 768@60p | 4:3 | 65.000MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: DMT[35]: 1280x1024@60p | 5:4 | 108.000MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: DMT[39]: 1360x 768@60p | 16:9 | 85.500MHz Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: HwInit() done, display size is 1920x1080 Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: MPEG2 video decoder not enabled! Oct 6 15:02:13 raspberrypi vdr: [724] new device number 3 Oct 6 15:02:13 raspberrypi vdr: [724] setting primary device to 3 Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: new cOsdProvider() Oct 6 15:02:13 raspberrypi vdr: [724] assuming manual start of VDR Oct 6 15:02:13 raspberrypi vdr: [724] SVDRP listening on port 6419 Oct 6 15:02:13 raspberrypi vdr: [724] setting current skin to "lcars" Oct 6 15:02:13 raspberrypi vdr: [724] loading /var/lib/vdr/themes/lcars-default.theme Oct 6 15:02:13 raspberrypi vdr: [744] audio decoder thread started (pid=724, tid=744, prio=high) Oct 6 15:02:13 raspberrypi vdr: [745] ovgthread thread started (pid=724, tid=745, prio=high) Oct 6 15:02:13 raspberrypi vdr: [745] rpihddevice: cOvgThread() thread started Oct 6 15:02:13 raspberrypi vdr: [744] rpihddevice: cAudioDecoder() thread started Oct 6 15:02:13 raspberrypi vdr: [724] starting plugin: satip Oct 6 15:02:13 raspberrypi vdr: [724] SATIP: Using CURL 7.52.1 rtsp Oct 6 15:02:13 raspberrypi vdr: [724] starting plugin: rpihddevice Oct 6 15:02:13 raspberrypi vdr: [724] rpihddevice: display PAR=1.000, setting video render PAR=1/1 Oct 6 15:02:15 raspberrypi vdr: [724] switching to channel 1 (RTL Television)Oct 6 15:02:15 raspberrypi vdr: [724] info: Channel not available! Oct 6 15:02:15 raspberrypi vdr: [745] rpihddevice: loading /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf ... Oct 6 15:02:17 raspberrypi vdr: [724] setting watchdog timer to 60 seconds Oct 6 15:02:17 raspberrypi systemd[1]: Started Video Disk Recorder. Oct 6 15:02:17 raspberrypi vdr: [724] OSD size changed to 1920x1080 @ 1 15:02:17 raspberrypi systemd[1]: Started Video Disk Recorder. Oct 6 15:02:17 raspberrypi vdr: [724] OSD size changed to 1920x1080 @ 1 Oct 6 15:02:17 raspberrypi vdr: [745] rpihddevice: loading /usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf ... Oct 6 15:02:18 raspberrypi vdr: [724] max. latency time 1 seconds
Schöne Grüße
Eric
-
Was ist da passiert, dass die Dateien leer waren?
Keine Ahnung. Hab Fehlermeldung gegoogelt und irgendwo gelesen leere Dateien zu löschen.
-
Hallo Seahawk
Nachdem ich /var/lib/vdr/.kodi/userdata/Profile.xml gelöscht habe kann ich kodi starten.
Gruß
Eric
-
Im wesentlichen
Code------------------------------------------- 2019-08-26 17:34:12.545 T:140310356510912 INFO: loading settings 2019-08-26 17:34:12.545 T:140310356510912 ERROR: CProfileManager: error loading special://masterprofile/profiles.xml, Line 0 Failed to open file 2019-08-26 17:34:12.545 T:140310356510912 NOTICE: special://profile/ is mapped to: special://masterprofile/ 2019-08-26 17:34:12.545 T:140310356510912 FATAL: unable to load profile
-
Der nach dem reboot Versuch Scheitert auch und sehe Logo aber kein set -kodi-Display fehler
Code
Alles anzeigenAug 26 16:00:41 monsta2 systemd[1525]: Starting Start kodi in user session... Aug 26 16:00:41 monsta2 set-kodi-display[2377]: DEBUG:no changes necessary, exiting Aug 26 16:00:41 monsta2 systemd[1525]: Started Start kodi in user session. Aug 26 16:00:41 monsta2 yavdr-frontend[1728]: DEBUG:SystemdUnitFrontend:unit is running Aug 26 16:00:41 monsta2 kodi[2379]: ERROR: Unable to create application. Exiting Aug 26 16:00:41 monsta2 systemd[1525]: kodi.service: Main process exited, code=exited, status=255/n/a Aug 26 16:00:41 monsta2 systemd[1525]: kodi.service: Failed with result 'exit-code'. Aug 26 16:00:41 monsta2 systemd[1525]: kodi.service: Service hold-off time over, scheduling restart. Aug 26 16:00:41 monsta2 systemd[1525]: kodi.service: Scheduled restart job, restart counter is at 4. Aug 26 16:00:41 monsta2 systemd[1525]: Stopped Start kodi in user session. Aug 26 16:00:41 monsta2 systemd[1525]: Starting Start kodi in user session... Aug 26 16:00:41 monsta2 set-kodi-display[2397]: DEBUG:no changes necessary, exiting Aug 26 16:00:41 monsta2 systemd[1525]: Started Start kodi in user session. Aug 26 16:00:41 monsta2 yavdr-frontend[1728]: DEBUG:SystemdUnitFrontend:unit is running Aug 26 16:00:42 monsta2 kodi[2399]: ERROR: Unable to create application. Exiting Aug 26 16:00:42 monsta2 systemd[1525]: kodi.service: Main process exited, code=exited, status=255/n/a Aug 26 16:00:42 monsta2 systemd[1525]: kodi.service: Failed with result 'exit-code'. Aug 26 16:00:42 monsta2 systemd[1525]: kodi.service: Service hold-off time over, scheduling restart. Aug 26 16:00:42 monsta2 systemd[1525]: kodi.service: Scheduled restart job, restart counter is at 5. Aug 26 16:00:42 monsta2 systemd[1525]: Stopped Start kodi in user session. Aug 26 16:00:42 monsta2 systemd[1525]: kodi.service: Start request repeated too quickly. Aug 26 16:00:42 monsta2 systemd[1525]: kodi.service: Failed with result 'exit-code'. Aug 26 16:00:42 monsta2 systemd[1525]: Failed to start Start kodi in user session.
-
Hi seahawk
Ja die
Hier das ergebnis
Codeyavdr-frontend.service - manage VDR frontends Loaded: loaded (/usr/lib/systemd/user/yavdr-frontend.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-08-26 07:31:33 CEST; 6h ago Main PID: 2238 (yavdr-frontend) CGroup: /user.slice/user-666.slice/user@666.service/yavdr-frontend.service └─2238 /usr/bin/python3 /usr/bin/yavdr-frontend
-
Hi Seahawk
Obwohl jetzt set-kodi-Display durchläuft und yavdr-Xorg restart bekomme ich dieselbe Fehlermeldung wie vorher (3 std) mit frontend Switch to kodi
Gruß
Eric
-
Leider nicht
Code
Alles anzeigensudo -u vdr DISPLAY=:0 set-kodi-display DEBUG:/var/lib/vdr/.kodi/userdata/guisettings.xml not found, creating stub file DEBUG:written backup for Default to /var/lib/vdr/.kodi/.display_cache/Default-videoscreen.xml ERROR:Could not change videoscreen.* settings Traceback (most recent call last): File "/usr/bin/set-kodi-display", line 67, in parse_template xml_tree = ET.parse(template_path) File "src/lxml/etree.pyx", line 3426, in lxml.etree.parse File "src/lxml/parser.pxi", line 1839, in lxml.etree._parseDocument File "src/lxml/parser.pxi", line 1865, in lxml.etree._parseDocumentFromURL File "src/lxml/parser.pxi", line 1769, in lxml.etree._parseDocFromFile File "src/lxml/parser.pxi", line 1162, in lxml.etree._BaseParser._parseDocFromFile File "src/lxml/parser.pxi", line 600, in lxml.etree._ParserContext._handleParseResultDoc File "src/lxml/parser.pxi", line 710, in lxml.etree._handleParseResult File "src/lxml/parser.pxi", line 639, in lxml.etree._raiseParseError File "/var/lib/vdr/.kodi/.display_cache/HDMI-0-videoscreen.xml", line 1 lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/set-kodi-display", line 120, in <module> main(output) File "/usr/bin/set-kodi-display", line 104, in main videodir_xml = parse_template(xml_path, VIDEOSCREEN_TEMPLATE, output) File "/usr/bin/set-kodi-display", line 73, in parse_template xml_tree.write(template_path) UnboundLocalError: local variable 'xml_tree' referenced before assignment
-
Code
sudo frontend-dbus-send switchto kodi Traceback (most recent call last): File "/usr/bin/frontend-dbus-send", line 11, in <module> load_entry_point('yavdr-frontend==0.0.24', 'console_scripts', 'frontend-dbus-send')() File "/usr/lib/python3/dist-packages/yavdr_frontend/frontend_dbus_send.py", line 10, in main fe = bus.get('de.yavdr.frontend') File "/usr/lib/python3/dist-packages/pydbus/proxy.py", line 47, in get 0, timeout_to_glib(timeout), None) GLib.Error: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name de.yavdr.frontend was not provided by any .service files (2)
-
Hi Seahawk
Ergebnis von dein set-kodi-display
Code
Alles anzeigenERROR:Could not change videoscreen.* settings Traceback (most recent call last): File "/usr/bin/set-kodi-display", line 67, in parse_template xml_tree = ET.parse(template_path) File "src/lxml/etree.pyx", line 3426, in lxml.etree.parse File "src/lxml/parser.pxi", line 1839, in lxml.etree._parseDocument File "src/lxml/parser.pxi", line 1865, in lxml.etree._parseDocumentFromURL File "src/lxml/parser.pxi", line 1769, in lxml.etree._parseDocFromFile File "src/lxml/parser.pxi", line 1162, in lxml.etree._BaseParser._parseDocFromFile File "src/lxml/parser.pxi", line 600, in lxml.etree._ParserContext._handleParseResultDoc File "src/lxml/parser.pxi", line 710, in lxml.etree._handleParseResult File "src/lxml/parser.pxi", line 639, in lxml.etree._raiseParseError File "/var/lib/vdr/.kodi/userdata/guisettings.xml", line 1 lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/set-kodi-display", line 120, in <module> main(output) File "/usr/bin/set-kodi-display", line 78, in main guisettings = parse_template(GUISETTINGS, VIDEOSCREEN_TEMPLATE, "Default") File "/usr/bin/set-kodi-display", line 73, in parse_template xml_tree.write(template_path) UnboundLocalError: local variable 'xml_tree' referenced before assignment
-
Hallo Seahawk
Welche KODI-Version ist denn bei dir installiert? apt policy kodi
Installiert: 2:18.3+git20190621.1610-final-0bionic
Installationskandidat: 2:18.3+git20190621.1610-final-0bionic
Versionstabelle:
*** 2:18.3+git20190621.1610-final-0bionic 500
500 http://ppa.launchpad.net/yavdr/experimental-kodi/ubuntu bionic/main amd64 Packages
500 http://ppa.launchpad.net/yavdr/experimental-kodi/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
2:17.6+dfsg1-1ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
Komisch dachte wäre 17 .. apt cache show kodi zeigt
Package: kodi
Architecture: amd64
Version: 2:17.6+dfsg1-1ubuntu1
Wie sehen die Rechte für das Verzeichnis /var/lib/vdr/.kodi/.display_cache und die Datei /var/lib/vdr/.kodi/userdata/guisettings.xmlaus?
drwxr-xr-x 2 vdr vdr 4096 Mai 5 22:07 .
drwxrwxr-x 8 vdr vdr 4096 Mai 5 22:07 ..
-rw-r--r-- 1 vdr vdr 0 Mai 5 22:07 Default-videoscreen.xml
-rw-r--r-- 1 vdr vdr 0 Mai 5 22:07 HDMI-0-videoscreen.xml
-rw-r--r-- 1 vdr vdr 0 Mai 5 22:07 /var/lib/vdr/.kodi/userdata/guisettings.xml
Nach der Installation hat es ja geklappt mit
sudo frontend-dbus-send switchto kodi
aber irgendwann danach nicht mehr.
Gruß
Eric
-
Guten Abend
Kodi startet nicht
Einzige Fehlermeldung
set-kodi-display[3540]: Could not change videoscreen.* settings: local variable 'xml_tree' referenced before assignment
Danach
ERROR: Unable to create application. Exiting
kodi.service:
Main process exited, code=exited, status=255/n/a
Habe Kodi gelöscht (apt-get remove kodi*) und yavdr ansible wieder runter geladen und Installation durchgeführt aber nicht geholfen.
kann mir jemand sagen wie ich den Fehler beheben das kodi (wieder) läuft..
Gruß
Eric
-
Thanks with vdr-plugin-softhddevice (so with ffmpeg 3.2) bbc one HD works like a charm.
Schätze mal der NVIDIA 8200 (mit zehn Jahre) an seine Grenzen mit ffmpeg 3.4 stößt.
Schönen Sonntag
-
Guten Tag
Bis auf bbc one hd funktioniert alles, auch bbc two hd und bbc Four hd. Wenn auf bbc one hd schalte startet Vdr und im syslog sehe ich
softhddev video[4528]: segfault at 18 ip 00007f9f4756fa62 sp 00007f9ecba33860 error 4 in libavcodec.so.57.107.100[7f9f47266000+ca6000]
Auch nach einer Aktualisierung besteht das Problem. Was könnte die Ursache sein?
Gruß
Eric
-
Das es mit hyper-v (VM)unter Windows klappt hab ich folgende Änderung gemacht in
roles/autoinstall-virtualbox-guest/tasks/main.yml
when:
- ansible_virtualization_type == "virtualbox" or ansible_virtualization_type == "VMware" or ansible_virtualization_type =="VirtualPC"