Jump to content

Search the Community

Showing results for tags 'crash'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Deutsch
    • Ankündigungen & Neuigkeiten
    • Einsteigerfragen DVBViewer Pro/GE
    • Allgemeines DVBViewer Pro/GE
    • Vorschläge & Ideen
    • Fehlermeldungen DVBViewer Pro/GE
    • Plugins und AddOns
    • DVB Hardware (Digital TV Karten)
    • DVBViewer Recording Service 1.x
    • DVBViewer Media Server
    • Sat>IP Viewer & Co (Android,iOS,Mac)
    • Verschiedenes
    • DVBViewer Video Editor
  • English
    • News & Announcements
    • Newbies DVBViewer Pro/GE
    • General DVBViewer Pro/GE
    • Suggestions & Ideas
    • Bug Reports DVBViewer Pro/GE
    • Plugins and AddOns
    • DVB Hardware (Digital TV cards)
    • DVBViewer Recording Service 1.x
    • DVBViewer Media Server
    • Sat>IP Viewer & Co (Android,iOS,Mac)
    • Off-Topic
    • DVBViewer Video Editor
  • Miscellaneous
    • Scripting Lounge / API (de/en)
    • Area HTPC
    • HDTV / UHDTV (de/en)
    • DVB - The technique behind
    • Conversion & Encoding
    • OEM Edition - User Helping Users (de/en)
    • Forum / Wiki / Website (de/en)
  • Survey ● Umfragen
    • DVBViewer Pro Cleanup (en/de)

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 6 results

  1. Hallo, die Vorgeschichte zu meiner unten folgenden Anfrage: Leider habe ich folgende drei Probleme In unregelmäßigen Abständen stürzt Kodi beim Starten ab, d.h. direkt nachdem das EPG vom DVBViewer PVR Client geladen wurde. Das EPG hat sporadisch bei manchen Sendern Lücken für z.B. 1ne Stunde, obwohl vorher und nachher die Daten da sind. Die vom DVBViewer PVR Client geladenen Aufnahme-Timer (erstellt mit dem 'Medi Server Web Interface') sind alle "schreibgeschützt", d.h. ich kann sie in Kodi nicht einmal aktivieren oder deaktivieren. Fehlermeldung "Timer konnte nicht aktualisiert werden. Für mehr Informationen Protokoll einsehen." (Could not update the timer. Check log for more information about this error.) Im Kodi.log konnte ich nichts erkennen. mit meinem HTPC und muss nun versuchen das Ganze aus der Welt zu bringen. Der HTPC mit aller SW ist neu, bei meinem alten PC lief alles einwandfrei nur dort war der gesamte SW Stand Jahre alt ... Zu 3. gibt es nach Google suche nur diesen <<Kodi errors our when trying to update timer rule (nextpvr.com)>> nicht ganz passenden Treffer. Dort wurde das backend geändert und deshalb lief der NextPVR Client nicht mehr richtig. Der Media Server 3.2.1.0 ist z.Zt. installiert. Was passiert, wenn ich den Installer des Media Server 2.1.5.2 ausführe? Anders gefragt: Ist ein Downgrade möglich ohne alles neu einstellen zu müssen? P.S. Im forum.kodi.tv habe ich auch schon versucht weiter zu kommen, entweder man bekommt gar keine Antwort oder keine die tatsächlich weiter hilft. Jetzt gerade habe ich nach dem Crash evtl. doch etwas nützliches im Kodi.log gefunden: 2022-04-08 20:31:27.477 T:9256 ERROR <general>: GetRecordingLastPlayedPosition: Add-on 'DVBViewer Media Server 3.2.1.0 (HTPC):127.0.0.1' returned an error: server error 2022-04-08 20:31:33.506 T:9256 INFO <general>: Skipped 2 duplicate messages.. 2022-04-08 20:31:33.506 T:9256 INFO <general>: Loading skin file: Settings.xml, load type: KEEP_IN_MEMORY 2022-04-08 20:31:40.846 T:9256 INFO <general>: Loading skin file: SettingsCategory.xml, load type: KEEP_IN_MEMORY 2022-04-08 20:31:50.610 T:9256 INFO <general>: Loading skin file: DialogSelect.xml, load type: KEEP_IN_MEMORY 2022-04-08 20:32:12.618 T:10476 INFO <general>: AddOnLog: pvr.DVBViewer: Running timer + recording updates! 2022-04-08 20:32:12.633 T:10504 WARNING <general>: Unable to determine channel type. Defaulting to TV. 2022-04-08 20:32:12.634 T:10504 INFO <general>: Skipped 15 duplicate messages.. 2022-04-08 20:32:12.634 T:10504 INFO <general>: AddOnLog: pvr.DVBViewer: Loaded 21 recording entries 2022-04-08 20:32:16.428 T:9256 ERROR <general>: GetRecordingLastPlayedPosition: Add-on 'DVBViewer Media Server 3.2.1.0 (HTPC):127.0.0.1' returned an error: server error 2022-04-08 20:32:17.926 T:9256 INFO <general>: Skipped 2 duplicate messages.. Die zwei ERRORs könnten der Auslöser der Abstürze sein ... System: DVBViewer Media Server 3.2.1.0 / Kodi 19.4 / DVBViewer Client 19.02 / Win10 21H2, 64 Bit
  2. When I play this stream: https://www91.zippyshare.com/v/HpXZhE2M/file.html and try to run Teletext/Subtitle Analyzer on PID 8125 (Teletext subtitles for channel WP) - TransEdit will freeze, need to kill it. I think this is something new, started to happen on 4.2.4, might be related to this fix, but not sure...
  3. Summary: 100% Crash (multiple devices) tuning 28.8E Satellite in UK *Bug Reduction:* Tested on iPhone 8 Plus & iPad Pro 10.5" with similar results. iPhone 8 Plus -> iOS 11.2.2 - wifi (no internet available). iPad Pro 10.5 -> iOS 11.0 - wifi (no internet available). SELFSAT IP21-> Satellite tuner used. Free Windows Sat>IP application found on satip.info website runs tuning without crashing *Steps to reproduce:* Open Sat>IP Viewer Select Settings -> Search Channels Select Astra 28.8E and start the scan The scan will run between 1 and 5 minutes and progress between ~30% and ~90% of the progress bar. The app will then crash back to Springboard No channels are saved and you need to restart the scan again. *Reproduction Rate:* Attempted 4/4 crash on iPad and 10/10 crash on iPhone 8. Total of 14/14 crashes attempting tuning. *Estimate on time to reproduce:* Initial test takes about 5 minutes including installation. Repeated tests can take a minute if it crashes early. While doing these tests I also encountered a few crash on launch issues but these seem to be unrelated to the main problem. (/) *Expected Result:* I can complete a tune of the satellite on 28.8E without it crashing (x) *Actual Result:* Cannot tune Sat>IP on 28.8E (!) *Regression:* New purchase of the app so no regression possible. (i) *Workaround:* No workaround found. I am a developer so I can test a TestFlight build or provide logs on request to help debug this issue.
  4. Hello, I had a problem yesterday with the recording service, it was not responding. On the tray, icon was orange. I clicked "stop recording service", then impossible to restart it. On the windows services the state was "stopped" and impossible to start it. The only way was to restart computer. Is there any log file i can send? The checkbox "write log file" is checked but can't find the log file. Thanks support.zip
  5. Hello everybody. I have already posted this topic on the forum some months ago, in the "Hardware" section. But I did not receive any satisfactory answer. I was expecting version 5.3 of DVBViewer before posting again. Unfortunately, the current version did not fix the problem below. I am using DVBViewer Pro (as a registered user) with a TBS USB device for DVB-C and DVB-T. It works fine, there is no problem. There is none of the issues mentioned below. But I use it too for DVB-S with the new Terratec Cinergy S2 Stick HD. And, even though I can watch and record satellite TV and radio programmes, there are serious issues with this device. First, when I close DVBViewer (with the Cinergy stick plugged), something remains active in the task manager and I cannot relaunch it unless I restart the computer. Second, when DVBViewer Pro is programmed so as to shut down the PC at the end of a recording, it crashes instead. Third, when I try to make a scan for new channels, it crashes (so there are some satellites I cannot tune). I think something is wrong between hardware and software. Can you please help me to solve this issue? I am unsure it is a Codec problem. Maybe a software or driver update would be necessary to make the Cinergy S2 Stick HD fully compatible? I am very happy with the functionalities of DVBViewer Pro and I want to keep using it for DVB-C and DVB-T as well as for DVB-S. Thank you for your help.
  6. My objective is to stream a certain channel for a few days, and I've set up DVBViewer to do so using the NetStream plugin. The streaming type is set to unicast and ffmpeg is being run on a different computer to restream this channel via rtmp. The problem I'm having is a day or so later I find that DVBViewer has crashed and the Windows 7 crash message box is displayed. I'm running DVBViewer v5.2.7.0 on Windows 7 with NetStream plugin v1.4.6.0. Is there a crash log I can check or share here to help identify why this is happening? Thanks, Sebouh
×
×
  • Create New...