vdr November 2015

vdr@linuxtv.org

6 participants
6 discussions

VDR ISDB-T support
by Christian Rodriguez 14 Sep '18

14 Sep '18

Hello everyone! I'm from Argentina, and up to last month I've been using VDR 1.7.262 with an ISDB-T USB adapter. It works really good, but the last week I've been trying to upgrade to VDR 2.2 and I've found a problem with ISDB-T cards: they are not supported. As I'm really interested in using VDR, I was digging inside the code and found a partial solution for this problem: as ISDBT is the same as DVBT, I've changed the way delivery system is queried. My changes are applied in a cloned repo at github: https://github.com/chrodriguez/vdr/commit/dadbca57c2dc55c1c53b4fa8f68b56728… That's the only change I've made. Now I can enjoy my fresh upgraded VDR installation!! I think a better refactor should be made, but for now it's working perfectly deployed as a docker container: https://registry.hub.docker.com/u/chrodriguez/vdr Thanks for this wonderfull project! -- Lic. Christian A. Rodriguez @car_unlp

4 7

Using a rasberry pi as vdr client
by Damien Bally 01 Feb '16

01 Feb '16

Hi I want to use raspberry pi as if it were a graphic card : I mean the dvb devices on a PC style server, IR receiver preferably on the server too (rpi and server in the same room) I don't know how to configure it, there is apparently 2 ways of doing it (from what I understood) + xineliboutput with vdr-fbfe (rpi plugin is closed source ? the one here : http://www.vdr-portal.de/board18-vdr-hardware/board98-arm-co/118588-rasperr…) + streamdev and rpihddevice (which additional plugins ?) The second way seems to be more complicated to configure, and I'm not sure it suits my project, but the rpihddevice is well maintained though. The first solution is perhaps much straightforward and includes a media player (?) Could you tell me more please ? Damien

6 6

bad characters in epg.data
by Peter Münster 07 Dec '15

07 Dec '15

Hi, It seems, that the encoding of the epg.data file is utf-8, but sometimes, there are lines like this: C S19.2E-133-3-263 18:00 GRÖD - RBS The "Ö" is one byte (0xD6) that seems not conform to utf-8 encoding. How could I avoid such characters in the epg.data file please? TIA for any hints, -- Peter

2 5

linuxtv.org downtime around Mon Nov 30 12:00 UTC
by Johannes Stezenbach 30 Nov '15

30 Nov '15

Hi, the linuxtv.org server will move to a new, freshly installed machine tomorrow. Expect some downtime while we do the final rsync and database export+import. I'm planning to start disabling services on the old server about 30min before 12:00 UTC (13:00 CET) on Mon Nov 30. If all goes well the new server will be available soon after 12:00 UTC. The IP address will not change. Johannes

1 1

TT S2 6400 card vdr and no video/recording on one particular channel
by Richard Scobie 29 Nov '15

29 Nov '15

I am using vdr and a TT S2 6400 card, along with the latest versions of vdr, all related drivers, firmware and plugin, very sucessfully for some time now, except for one channel, which will not decode the video - audio is fine. I have spent some time with dvbsnoop and DVBInspector, trying to find out what is wrong, but am now out of ideas and wondered if you could offer some suggestions. If I get vdr to record this channel, nothing is recorded and likewise if I try to stream the channel to MPlayer on another machine using streamdev-server, I get nothing and this is the output: Cache size set to 2048 KBytes Cache fill: 15.41% (323172 bytes) libavformat version 55.8.102 (internal) TS file format detected. Cache empty, consider increasing -cache and/or -cache-min. [performance issue] VIDEO MPEG2(pid=308) AUDIO MPA(pid=256) NO SUBS (yet)! PROGRAM N. 0 Cache empty, consider increasing -cache and/or -cache-min. [performance issue] Cache empty, consider increasing -cache and/or -cache-min. [performance issue] Cache empty, consider increasing -cache and/or -cache-min. [performance issue] If however, if I use dvbsnoop to dump the raw ts to a file: dvbsnoop -b -n 10000 -s ts -tsraw > ch9raw.ts I can play this in Mplayer fine - audio and video are perfect: Playing /tmp/ch9raw.ts. libavformat version 55.8.102 (internal) TS file format detected. TS_PARSE: COULDN'T SYNC VIDEO H264(pid=308) AUDIO MPA(pid=256) SUB Teletext(pid=583) PROGRAM N. 1185 FPS seems to be: 25.000000 Load subtitles in /tmp/ ========================================================================== Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family libavcodec version 55.16.100 (internal) Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264) ========================================================================== ========================================================================== Opening audio decoder: [mpg123] MPEG 1.0/2.0/2.5 layers I, II, III AUDIO: 48000 Hz, 2 ch, s16le, 192.0 kbit/12.50% (ratio: 24000->192000) Selected audio codec: [mpg123] afm: mpg123 (MPEG 1.0/2.0/2.5 layers I, II, III) ========================================================================== AO: [oss] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... Movie-Aspect is 1.82:1 - prescaling to correct movie aspect. VO: [vdpau] 720x576 => 1048x576 Planar YV12 A:36436.9 V:36437.0 A-V: -0.154 ct: -0.012 14/ 14 ??% ??% ??,?% 12 0 Note the first Mplayer example thinks the video PID (308) is MPEG2 and the second is H264. DVBInspector confirms the video stream is H264. What is it that I should be looking for wrong in the stream, that vdr will not record this channel or pass the video stream through the system? Thank you for anything you can offer. Kind regards, Richard Scobie

1 0

Raspberry Pi, satip, MLD
by Nicolas Huillard 15 Nov '15

15 Nov '15

Hi all, I still have a problem with my new setup: * Raspberry Pi B (256MB system + 256MB video) * MLD 5.0.0 testing distribution (http://www.minidvblinux.de/) on a 4GB class 6 SD card, using VDR 2.2.0.203-207 * vdr-plugin-rpihddevice (from MLD 1:2015.08.24-37+2.2.0.203) * Octopus Net (firmware 1.0.55) : Linux VLC shows TV channels without problems * vdr-plugin-satip (from MLD 2015.09.19-20+2.2.0.203) * recordings on an NFS share (works for playing, didn't test recording) * the Raspberry is powered from one of the 5V output from the Octopus, which provides enough power for the CI interface, which seems Playing live TV works great, until some point a few dozen minutes later, where some errors start to appear in /var/log/messages: Oct 25 10:51:59 vdrpi user.err vdr: [17414] ERROR: 1 ring buffer overflow (940 bytes dropped) Oct 25 10:52:01 vdrpi user.info vdr: [17414] SATIP: Detected 1 RTP packet errors [device 0] Oct 25 10:52:05 vdrpi user.err vdr: [17414] ERROR: 496 ring buffer overflows (652736 bytes dropped) Oct 25 10:52:11 vdrpi user.err vdr: [17414] ERROR: 584 ring buffer overflows (768544 bytes dropped) Oct 25 10:52:17 vdrpi user.err vdr: [17414] ERROR: 584 ring buffer overflows (768544 bytes dropped) Oct 25 10:52:23 vdrpi user.err vdr: [17414] ERROR: 580 ring buffer overflows (763280 bytes dropped) Oct 25 10:52:28 vdrpi user.err vdr: [17413] rpihddevice: [libav] Header missing Oct 25 10:52:28 vdrpi user.err vdr: [17413] rpihddevice: failed to decode audio frame! Oct 25 10:52:31 vdrpi user.err vdr: [17426] ERROR: TS packet not accepted in Transfer Mode Oct 25 10:52:31 vdrpi user.debug vdr: [17413] rpihddevice: set HDMI audio output format to 2ch PCM, 48.0kHz Oct 25 10:52:38 vdrpi user.err vdr: [17426] ERROR: TS packet not accepted in Transfer Mode Oct 25 10:52:38 vdrpi user.debug vdr: [17413] rpihddevice: set HDMI audio output format to 2ch PCM, 48.0kHz Some earlier errors were: Oct 24 18:02:59 (none) user.err vdr: [11447] SATIP-ERROR: Connection timeout - retuning [device 1] Oct 24 18:03:00 (none) user.err vdr: [11442] ERROR: 584 ring buffer overflows (768544 bytes dropped) Oct 24 18:03:04 (none) user.err vdr: [11447] SATIP-ERROR: Connection timeout - retuning [device 1] Oct 24 18:03:06 (none) user.err vdr: [11442] ERROR: 584 ring buffer overflows (768544 bytes dropped) Those errors lasted for hours, until I stopped VDR. It's usually not fixed until I power cycle the pi. I don't know were to look from here. Options are: * the satip plugin may not be the latest one (but the version number is unclear and the MLD forum is all german-speaking, which is a problem for me) * the ethernet interface may miss packets even though it does not report any packet loss (I changed the cable -quality and length- without success) * the power provided to the rpi may be enough, but I don't know about temperatures (the video core reports 54°C, but the ethernet chip may be too hot) * maybe the Octopus does not provide a proper stream, or the problem comes from the VDR core or the rpihddevice output... Since I'm new to rpihddevice, satip and MLD, and didn't stress previous Raspberry Pïs before, even though I use VDR since a dozen years at least, I'm really lost here. Latest test: a few second after switching some channel, the image froze, sound looped, and the pi was not reachable anymore through SSH, even though the octopus still reported the live stream and the network LEDs on the pi was still blinking. Hardware problem, network driver problem ? TIA, -- NH

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr November 2015