vdr

vdr@linuxtv.org

2 participants
6731 discussions

VDR deleting channels it shouldn't
by Timothy D. Lenz 21 Jan '11

21 Jan '11

Using vdr-1.7.15. 3 of the local networks have duplicate transmitters. 1 is a bit too weak get right now and because of a bug in atsc, I can't rescan right now (crashes vdr, reported in another post). I pulled the entries for the secondary transmitters for two of the networks from the last scan I was able to make a few months ago. Added them back in, but vdr promptly deletes them even though they are on different real channels. Below is the revised conf followed by what vdr did to it. :Locals :@41 KVOA-DT,KVOA-DT:527028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:211:0 :@61 PBS HD,PBS HD:569028615:M10:A:0:49=2:0;52=eng@106,56=eng@106:0:0:1:0:213:0 :@62 V-Me,V-Me:569028615:M10:A:0:65=2:0;68=esl@106,72=esl@106:0:0:2:0:213:0 :@63 CREATE,CREATE:569028615:M10:A:0:81=2:0;84=eng@106,88=eng@106:0:0:3:0:213:0 :@91 KGUN-DT,KGUN-DT:189028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:215:0 :@92 MEXI ,MEXI :189028615:M10:A:0:65=2:0;68=esl@106:0:0:4:0:215:0 :@93 COOLTV ,COOLTV :189028615:M10:A:0:81=2:0;84=eng@106:0:0:5:0:215:0 :@94 KGUN2,KGUN2:485028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:215:0 :@95 Mexi2,Mexi2:485028615:M10:A:0:65=2:0;68=spa@106:0:0:4:0:215:0 :@96 COOLTV2,COOLTV2:485028615:M10:A:0:81=2:0;84=eng@106:0:0:5:0:215:0 :@111 KMSB-DT,KMSB:539028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:217:0 :@112 THIS,THIS:539028615:M10:A:0:65=2:0;68=eng@106:0:0:2:0:217:0 :@131 KOLD-DT,KOLD-DT:581028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:219:0 :@132 Weather,Weather:581028615:M10:A:0:65=2:0;68=eng@106:0:0:4:0:219:0 :@133 Tube,Tube:581028615:M10:A:0:81=2:0;84=eng@106:0:0:5:0:219:0 :@134 KOLD-DT,KOLD-DT:213028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:219:0 :@135 Weather,Weather:213028615:M10:A:0:65=2:0;68=eng@106:0:0:4:0:219:0 :@136 Tube,Tube:213028615:M10:A:0:81=2:0;84=eng@106:0:0:5:0:219:0 :@181 KTTU-DT,KTTU-DT:503028615:M10:A:0:49=2:0;53=eng@106:0:0:1:0:221:0 :@182 Estrell,Estrell:503028615:M10:A:0:65=2:0;68=esl@106:0:0:2:0:221:0 :@271 PBS HD,PBS HD:557028615:M10:A:0:49=2:0;52=eng@106,56=eng@106:0:0:1:0:223:0 :@272 KIDS,KIDS:557028615:M10:A:0:65=2:0;68=eng@106,72=fra@106:0:0:2:0:223:0 :@273 WORLD,WORLD:557028615:M10:A:0:81=2:0;84=eng@106,88=eng@106:0:0:3:0:223:0 :@401 KHRR-40, Telemundo, Tucson, AZ,KHRR-DT:629028615:M10:A:0:49=2:0;52=eng@106,54=fra@106:0:0:3:0:225:0 :@461 Univision,KUVE-DT:665028615:M10:A:0:49=2:0;52=eng@106:0:0:1:0:179:0 :@462 TeleFutura,KFTU-CA:665028615:M10:A:0:65=2:0;68=esl@106:0:0:2:0:179:0 :@581 KWBA-DT,KWBA-DT:653028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:207:0 :@582 LATV,LATV:653028615:M10:A:0:65=2:0;68=esl@106:0:0:4:0:207:0 ----------------------------------------------------------------------- :Locals :@41 KVOA-DT,KVOA-DT:527028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:211:0 :@61 PBS HD,PBS HD:569028615:M10:A:0:49=2:0;52=eng@106,56=eng@106:0:0:1:0:213:0 :@62 V-Me,V-Me:569028615:M10:A:0:65=2:0;68=esl@106,72=esl@106:0:0:2:0:213:0 :@63 CREATE,CREATE:569028615:M10:A:0:81=2:0;84=eng@106,88=eng@106:0:0:3:0:213:0 :@91 KGUN-DT,KGUN-DT:189028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:215:0 :@92 MEXI ,MEXI :189028615:M10:A:0:65=2:0;68=esl@106:0:0:4:0:215:0 :@93 COOLTV ,COOLTV :189028615:M10:A:0:81=2:0;84=eng@106:0:0:5:0:215:0 :@94 :@95 :@96 :@111 KMSB-DT,KMSB:539028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:217:0 :@112 THIS,THIS:539028615:M10:A:0:65=2:0;68=eng@106:0:0:2:0:217:0 :@131 KOLD-DT,KOLD-DT:581028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:219:0 :@132 Weather,Weather:581028615:M10:A:0:65=2:0;68=eng@106:0:0:4:0:219:0 :@133 Tube,Tube:581028615:M10:A:0:81=2:0;84=eng@106:0:0:5:0:219:0 :@134 :@135 :@136 :@181 KTTU-DT,KTTU-DT:503028615:M10:A:0:49=2:0;53=eng@106:0:0:1:0:221:0 :@182 Estrell,Estrell:503028615:M10:A:0:65=2:0;68=esl@106:0:0:2:0:221:0 :@271 PBS HD,PBS HD:557028615:M10:A:0:49=2:0;52=eng@106,56=eng@106:0:0:1:0:223:0 :@272 KIDS,KIDS:557028615:M10:A:0:65=2:0;68=eng@106,72=fra@106:0:0:2:0:223:0 :@273 WORLD,WORLD:557028615:M10:A:0:81=2:0;84=eng@106,88=eng@106:0:0:3:0:223:0 :@401 KHRR-40, Telemundo, Tucson, AZ,KHRR-DT:629028615:M10:A:0:49=2:0;52=eng@106,54=fra@106:0:0:3:0:225:0 :@461 Univision,KUVE-DT:665028615:M10:A:0:49=2:0;52=eng@106:0:0:1:0:179:0 :@462 TeleFutura,KFTU-CA:665028615:M10:A:0:65=2:0;68=esl@106:0:0:2:0:179:0 :@581 KWBA-DT,KWBA-DT:653028615:M10:A:0:49=2:0;52=eng@106:0:0:3:0:207:0 :@582 LATV,LATV:653028615:M10:A:0:65=2:0;68=esl@106:0:0:4:0:207:0

3 5

XBMC vnsi dts/pts errors on ATSC Channel through VDR
by Rob Davis 21 Jan '11

21 Jan '11

Using VDR 1.7.16 and the vnsi plugin, xbmc seems to be struggling to play one particular channel. Unfortunetly, it's the channel I'm doing a temporary admin contract for, so I kind of need to see it. vdr-sxfe plays it OK, but I get too much video stuttering on it, and all other channels play ok on xbmc/vdr. Working at the station, if the problem is there, I have a hope of getting it fixed. Their sister station using the same equipment but on a different frequency and antenna (transmitter) is fine. I get the same symptoms using both OTA (8vsb) and via Comcast QAM256, so am fairly sure the problem is specific to something at the station. The code from demuxer.c (in vnsi plugin) that's being triggered is this: else if(checkTimestamp) { int d = dts + m_epochDTS - m_LastDTS; if (d < 0 || d > 90000) { if (d < -PTS_MASK || d > -PTS_MASK + 180000) { m_badDTS++; if (m_badDTS < 5) { dsyslog("VNSI-Error: DTS discontinuity. DTS = %10lu, last = %10lu", dts, m_LastDTS); } } else { /* DTS wrapped, increase upper bits */ m_epochDTS += PTS_MASK + 1; m_badDTS = 0; } } I get my logs filled with the VNSI-Error, DTS discontinuity. The audio stutters. It appears to be AC-3 Stereo, but may be labelled 5.1? I have audio passthrough to my amp. On another laptop with analog output it seems to stutter in a different way.. I'm fairly happy putting some kind of checking in VDR or VNSI and recompiling if it'll help. I have two ATSC tuners, it happens to both tuners. Thanks Rob

2 3

Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)
by Stuart Morris 19 Jan '11

19 Jan '11

--- On Wed, 19/1/11, Niko Mikkilä <nm(a)phnet.fi> wrote: > From: Niko Mikkilä <nm(a)phnet.fi> > Subject: Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2) > To: "VDR Mailing List" <vdr(a)linuxtv.org> > Date: Wednesday, 19 January, 2011, 10:48 > ke, 2011-01-19 kello 10:18 +0000, > Stuart Morris kirjoitti: > > My experience with an nVidia GT220 has been less than > perfect. It can > > perform temporal+spatial+inverse_telecine on HD video > fast enough, but > > my PC gets hot and it truly sucks at 2:2 pulldown > detection. The > > result of this is when viewing progressive video > encoded as interlaced > > field pairs (2:2 pulldown), deinterlacing keeps > cutting in and out > > every second or so, ruining the picture quality. > > I think VDPAU's inverse telecine is only meant for non-even > cadences > like 3:2. Motion-adaptive deinterlacing handles 2:2 pullup > perfectly > well, so try without IVTC. > > > > IMHO the best way to go for a low power HTPC is to > decode in hardware > > e.g. VDPAU, VAAPI, but output interlaced video to your > TV and let the > > TV sort out deinterlacing and inverse telecine. > > Well, flat panel TVs have similar deinterlacing algorithms > as what VDPAU > provides, but it would certainly be a nice alternative. > > > These are the key requirements to achieve interlaced > output: > > > > Get the right modelines for your video card and TV. > Draw interlaced > > fields to your frame buffer at field rate and in the > correct order > > (top field first or bottom field first). When drawing > the field to the > > frame buffer, do not overwrite the previous field > still in the frame > > buffer. Maintain 1:1 vertical scaling (no vertical > scaling), so you > > will need to switch video output to match the source > video height > > (480i, 576i or 1080i). Display the frame buffer at > field rate and > > synchronised to the graphics card vertical sync. > Finally, there is NO > > requirement to synchronise fields, fields are always > displayed in the > > same order they are written to the frame buffer, even > if occasionally > > fields are dropped. > > Interesting. Could you perhaps write full instructions to > some suitable > wiki and post the code that you used to do this? I'm sure > others would > like to try it too. I can provide the simple bit of source code I have used to demonstrate the basic principle. Please see attached.

1 0

Re: [vdr] vdr segfaults with glibc 2.12.2
by gimli 18 Jan '11

18 Jan '11

I'm on Archlinux 32bit and there it works fine. Am 06.01.2011 um 22:19 schrieb scott(a)waye.co.uk: > Funny, I tried to change my system to Archlinux last weekend and had the same problem. I gave up in the end and will try Opensuse 11.3 now. I also tried recompiling glibc from source but it gave the same error. Would be to have a test suite for pthread. Could be a 64bit problem... if I was going to pursue it I would create a test program that made the same call as vdr to submit to the Archlinux guys. > > Sent from my HTC > > ----- Reply message ----- > From: "David Spicer" <azleifel(a)googlemail.com> > Date: Thu, Jan 6, 2011 20:53 > Subject: [vdr] vdr segfaults with glibc 2.12.2 > To: <vdr(a)linuxtv.org> > > Hi, > > I'm not a programmer and I'm not sure where to go with this but I > thought that I'd try here first. I'm running vdr 1.6.0-2 on Arch Linux > x86_64. The Arch glibc package was upgraded from 2.12.1 to 2.12.2 > recently, with associated toolchain package updates. After the upgrade, > vdr started segfaulting when it was run so I recompiled it with > debugging symbols and got the following backtrace from gdb: > > (gdb) bt > #0 0x0000000000000001 in ?? () > #1 0x00000000004f2d06 in ?? () > #2 0x00007fff1bb0269f in ?? () > #3 0x00000000004c2775 in cRwLock::Lock (this=0x72bb40, Write=true, > TimeoutMs=<value optimized out>) at thread.c:163 > #4 0x000000000047d382 in cSchedulesLock::cSchedulesLock > (this=0x7fff1bb0269f, WriteLock=<value optimized out>, TimeoutMs=<value > optimized out>) at epg.c:911 > #5 0x000000000047dd06 in cSchedules::Read (f=0x0) at epg.c:1014 > #6 0x00000000004cc304 in main (argc=<value optimized out>, argv=<value > optimized out>) at vdr.c:604 > > If I've done this properly then problem seems to be with the glibc, > specifically pthread, functions that vdr uses to lock the epg data file > for reading and writing but I have no idea whether the problem is with > the vdr code or with glibc. The only workaround I have at the moment is > to downgrade to glibc 2.12.1, after which vdr works again. > > Can anybody help please? > > TIA, > > David Spicer > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

3 2

Re: [vdr] vdr Digest, Vol 72, Issue 30
by master.of.brainless.things＠gmx.net 18 Jan '11

18 Jan '11

hello, sorry for just jumpin in. haven't read the whole thread, and i don't know all details, i just want to say: my current (ya)vdr: - asus at3iont-t (deluxe, for extern 19V) attached to my flat, sound over hdmi - it has serial port, and one pci-e. - mc-1200 case (but built-in remote not really working yet) the only noise is now coming from my harddrives, as this machine currently is more than a video player. so an ssd would make this machine completly silent. sometimes the cpu heat is nearly 60C°, but as i said, i do more than just watching tv and hd movies. in this case, the machine gets instable. xbmc can play 1080p, but more details i can't say, for i have not that knowledge... -- Brain fried - core dumped.

1 0

Collecting patches for vdr-xine-0.9.4
by Reinhard Nissl 17 Jan '11

17 Jan '11

Hi, it looks like I can find more time this week to work on vdr-xine. I've seen some patches for vdr-xine-0.9.3 (and xine-lib) in the mailing list which address so far unsupported audio formats if I recall correctly, as vdr-xine still uses PES and my c*Repackers. I'd like to invite you to send them again to me (privately). A sample recording would be appreciated too. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

2 1

new OSD system
by Gero 16 Jan '11

16 Jan '11

Hello, I read about the ongoing work at the OSD system. I have to confess, that I don't really miss a truecolor OSD, but what I miss is the possibility to configure the OSD for each output-device separately. Currently I use a "backend"-vdr with budget-cards and an old fashioned FF. My TV is plugged to the old FF and I watch HD through a frontend-client with xineliboutput. That's not bad at all, but one shortcoming I noticed is, that configuration works for all output-devices. I tried the cool anthra-skin for HD - but then I don't get any OSD on FF. Same happens with keyboard. Currently its easy to distinguish the keys, as they are created from different systems and for so have different keycodes. But when I update my TV to a HD system and use xineliboutput on the backend as well as the frontend, than there's no way to have separate keyboard configurations. Why I want different setups? At the vdr I use a standard keyboard and the frontend is my desktop, where I use a Natural keyboard from M$ - which has a completely different layout of function-keys and additional keys. So it would be nice, to have sections in remote.conf that could be separated by output-device. Really great would be, if that sections could be created based on the IP of the client :) kind regards Gero

6 17

epgload for Digital+ (spain)
by Josu Lazkano 14 Jan '11

14 Jan '11

Hello list! This is my first post on this list. I want to get my satellite provider (Digital+ spain) EPG data. With tv_grab_dvb I just get the current and next program. Is possible to get more days data? I read that that there is "epgload" software to do that. But I don't know where to download and how to install/config. Can someone help with this? Thanks and best regards. -- Josu Lazkano

1 0

Developer versions
by Tony Houghton 14 Jan '11

14 Jan '11

I don't find VDR 1.6.0 very reliable and I'm wondering whether 1.7 is mature enough now to be worth setting up. At the moment I use Debian packages and although I have to recompile it to add the Freesat patch it's still a lot easier than gathering the bits and pieces and getting it to live nicely on my system. Any chance of a 1.8 release soon? I'd also be interested in the developer version of xine with VDPAU support. The trouble is there's a bewildering set of mercurial branches. There are some libxine2 packages in Debian experimental, but there don't seem to be any packages for "version 2" players, nor libxine2-dev packages (not to mention vdpau support) so I don't see what use they are.

19 66

Meridian
by Tony Houghton 14 Jan '11

14 Jan '11

Since my upgrade from VDR 1.6.0 to 1.7.16 I can't view my local ITV1 region (ITV1 Mer South) on Freesat. The EPG appears normal, but there's no picture or sound. ITV1 is OK on Freeview, as is the London version on Freesat. The log says: Jan 11 18:07:57 htpc vdr: [10023] switching to channel 103 Jan 11 18:07:57 htpc vdr: [10023] setstatus 0 Jan 11 18:08:06 htpc vdr: [10027] frontend 0/0 timed out while tuning to channel+ 103, tp 110891 The channels.conf entry (which I've checked is up-to-date) is: ITV1 Mer South;BSkyB:10891:hC56:S28.2E:22000:3336=2:3337=eng@4:2344:0:10140:2:20+53:0 I've written my scan script to substitute BSkyB as the provider instead of Freesat because VDR was picking up the BSkyB SDT instead of Freesat's when I was using the Freesat patch, but I'm not sure whether that's the case with the EEPG plugin. My VDR versions are now: * vdr 1.7.16-1devel2 from Tobias Grimm's Debian sid repository. * vdr-plugin-eepg 0.0.3-28yavdr1 built from yavdr's vdr-unstable deb source -- TH * http://www.realh.co.uk

2 5

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr