vdr October 2008

vdr@linuxtv.org

81 participants
84 discussions

Two different types of DVB card
by Tony Houghton 17 Nov '08

17 Nov '08

Can VDR handle two different types of DVB card at once? I've got two different makes of DVB-T card at the moment, which is fine because they share one channels.conf, but I'm thinking of replacing one with DVB-S for HD. Can VDR assign a different channels.conf to each card and merge the channels list for the EPG? -- TH * http://www.realh.co.uk

4 8

fedora 9 vdr-1.6.0 - int no audio on channel change
by Simon Baxter 15 Nov '08

15 Nov '08

Hi I've built a new fedora 9 x86_64 system (twice!) and get an intermittant problem when changing channels - no audio!! I've tried it with pvrinput analog channels, as well as digital channels via my TT-1501, TT-2300 (both with CAMs). When I change to a neighbouring channel and back again, I often get audio. Weird huh? Here's the /var/log/messages from the experience. Any ideas?? What can I try - seems like something is resetting and the audio starting with pvrinput, and nothing resetting with the TT-1501 card. HELP!!! This has been going on for months..... pvrinput. 2 audio works. Change to 3, audio doesn't work. Then after 4 seconds works on it's own.... Sep 8 19:11:53 freddy vdr: [3108] switching to channel 2 Sep 8 19:11:53 freddy vdr: [3406] transfer thread ended (pid=3108, tid=3406) Sep 8 19:11:53 freddy vdr: [3108] buffer stats: 141000 (6%) used Sep 8 19:11:53 freddy vdr: [3407] receiver on device 10 thread ended (pid=3108, tid=3407) Sep 8 19:11:53 freddy kernel: saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer Sep 8 19:11:54 freddy vdr: [3410] transfer thread started (pid=3108, tid=3410) Sep 8 19:11:54 freddy vdr: [3411] receiver on device 10 thread started (pid=3108, tid=3411) Sep 8 19:11:55 freddy vdr: [3410] setting audio track to 1 (0) Sep 8 19:11:55 freddy kernel: saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer Sep 8 19:11:57 freddy kernel: saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer Sep 8 19:11:57 freddy vdr: [3108] switching to channel 3 Sep 8 19:11:57 freddy vdr: [3410] transfer thread ended (pid=3108, tid=3410) Sep 8 19:11:57 freddy vdr: [3108] buffer stats: 141752 (6%) used Sep 8 19:11:57 freddy vdr: [3411] receiver on device 10 thread ended (pid=3108, tid=3411) Sep 8 19:11:58 freddy vdr: [3414] transfer thread started (pid=3108, tid=3414) Sep 8 19:11:58 freddy vdr: [3415] receiver on device 10 thread started (pid=3108, tid=3415) Sep 8 19:11:58 freddy kernel: saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer Sep 8 19:11:58 freddy vdr: [3414] setting audio track to 1 (0) Sep 8 19:12:01 freddy kernel: saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer Sep 8 19:12:03 freddy kernel: saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer Digital. 9 audio working. Change to 8, working. Change to 9 audio not working Sep 8 19:06:35 freddy vdr: [3108] switching to channel 9 Sep 8 19:06:35 freddy vdr: [3108] cTS2PES got 0 TS errors, 2 TS continuity errors Sep 8 19:06:35 freddy vdr: [3108] cTS2PES got 0 TS errors, 1 TS continuity errors Sep 8 19:06:35 freddy vdr: [3108] buffer stats: 58280 (2%) used Sep 8 19:06:35 freddy vdr: [3336] transfer thread started (pid=3108, tid=3336) Sep 8 19:06:35 freddy vdr: [3334] TS buffer on device 1 thread ended (pid=3108, tid=3334) Sep 8 19:06:35 freddy vdr: [3333] buffer stats: 58656 (2%) used Sep 8 19:06:35 freddy vdr: [3333] receiver on device 1 thread ended (pid=3108, tid=3333) Sep 8 19:06:35 freddy vdr: [3337] receiver on device 1 thread started (pid=3108, tid=3337) Sep 8 19:06:35 freddy vdr: [3338] TS buffer on device 1 thread started (pid=3108, tid=3338) Sep 8 19:06:37 freddy vdr: [3336] setting audio track to 1 (0) Sep 8 19:07:57 freddy vdr: [3336] transfer thread ended (pid=3108, tid=3336) Sep 8 19:07:57 freddy vdr: [3108] switching to channel 8 Sep 8 19:07:57 freddy vdr: [3108] buffer stats: 95692 (4%) used Sep 8 19:07:57 freddy vdr: [3344] transfer thread started (pid=3108, tid=3344) Sep 8 19:07:57 freddy vdr: [3338] TS buffer on device 1 thread ended (pid=3108, tid=3338) Sep 8 19:07:57 freddy vdr: [3337] buffer stats: 95316 (4%) used Sep 8 19:07:57 freddy vdr: [3337] receiver on device 1 thread ended (pid=3108, tid=3337) Sep 8 19:07:57 freddy vdr: [3345] receiver on device 1 thread started (pid=3108, tid=3345) Sep 8 19:07:57 freddy vdr: [3346] TS buffer on device 1 thread started (pid=3108, tid=3346) Sep 8 19:07:58 freddy vdr: [3344] setting audio track to 1 (0) Sep 8 19:08:02 freddy vdr: [3344] transfer thread ended (pid=3108, tid=3344) Sep 8 19:08:03 freddy vdr: [3108] switching to channel 9 Sep 8 19:08:03 freddy vdr: [3108] buffer stats: 62792 (2%) used Sep 8 19:08:03 freddy vdr: [3349] transfer thread started (pid=3108, tid=3349) Sep 8 19:08:03 freddy vdr: [3346] TS buffer on device 1 thread ended (pid=3108, tid=3346) Sep 8 19:08:03 freddy vdr: [3345] buffer stats: 62416 (2%) used Sep 8 19:08:03 freddy vdr: [3345] receiver on device 1 thread ended (pid=3108, tid=3345) Sep 8 19:08:03 freddy vdr: [3350] receiver on device 1 thread started (pid=3108, tid=3350) Sep 8 19:08:03 freddy vdr: [3351] TS buffer on device 1 thread started (pid=3108, tid=3351) Sep 8 19:08:04 freddy vdr: [3349] setting audio track to 1 (0)

1 4

OT: VDR for grandparents
by Paul Menzel 14 Nov '08

14 Nov '08

Dear list, has anyone on this list any experience in setting up VDR for older people like grandparents? It would be nice, if she/he could share her/his experience or point me to information on the WWW. Thanks, Paul

7 8

xineliboutput not working
by Artem Makhutov 05 Nov '08

05 Nov '08

Hi, the xineliboutput plugin does not work for me. I can see the OSD in xineliboutput, but not the movie. Switching to other channes does not work. I am using vdr 1.7.1 and xineliboutput 1.0.2. I see a lot of error messages in my syslog: ... Oct 6 18:44:40 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:40 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:41 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:41 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:41 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:42 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:43 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:43 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:44 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:44 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:44 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:45 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:45 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:46 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! Oct 6 18:44:46 gandalf vdr: [23324] [xine..put] cXinelibDevice::PlayAny: invalid data ! ... Any ideas how to fix this problem? Thanks, Artem

10 20

[ANNOUNCE] fEPG 0.4.1
by Alex Lasnier 02 Nov '08

02 Nov '08

Hi, A new version of fEPG is now available at http://www.fepg.org Description ----------- fEPG is a plugin for VDR that provides a graphical way of viewing and navigating through EPG data. Almost all aspects of the user interface are configurable. Changes ------- 2008-10-29: Version 0.4.1 - Fixed error in grid drawing code; 'No Info' entries were not always properly determined. - Key names are now being translated. - Added Italian translations (thanks to Diego Pierotto). - Added Spanish translations (thanks to Manuel Gomez). - Now only drawing the first line of an event name if row height is insufficient for two. - Selected event is now properly updated when the time changes. - Several minor cosmetic fixes. - Fixed prototype of function 'Darken'. - Cleaned up '#include's - Updated license information. Regards, Alex Lasnier

2 2

[ANNOUNCE] remotetimers-0.1.0
by Frank Schmirler 30 Oct '08

30 Oct '08

Hi there, I just released remotetimers-0.1.0 on http://vdr.schmirler.de. Changelog: - Plugin now has its own Recordings menu. Features: * filtering by user * editing of recordings (name, priority, lifetime, user) * starting local/remote cutter * replacement for VDR's Recordings menu (requires MainMenuHooks patch) - Multiuser support for Timers and Recordings (check README for details) - Dedicated setup options for user filter in Schedule, Timers and Recordings menus, either backed by VDR's "Resume ID" or set to a static value - Progress bars for "What's on now?" menu (thanks to HolgerR@vdrportal) - Patch for server-side instant recordings and paused live view - Keep recordings list up-to-date if server's video directory is mounted in a subdirectory of the local video directory - Updated Italian translations (thanks to Diego Pierotto) Version 0.1.0 is a development release. The core functionality should be fine, but some of the new features are either incomplete or not very well tested. In particular: - Renaming recordings on VDR's with multiple video directories has not been tested at all. BEWARE! You might loose your data! - Renaming recordings across filesystems not implemented yet - I added support for the timersync-plugin to the remote_instant_recordings patch as the patch might work with it, too. Maybe someone using timersync could give it a try and report back. Have fun, Frank

1 0

Re: [vdr] Tuning failures for transponder-locked tuners (VDR 1.4.7)
by Richard F 29 Oct '08

29 Oct '08

Teemu, I had a similar problem with budget Freecom / WT-220U USB stick tuners. I usually had to swap multiplex/transponder to get them to re-tune reliably. I observed that if they lost tuning, vdr made them re-try (which I saw in the log) but eventually would bomb out if it couldn't tune, which is maybe what you're seeing? Originally I logged it as a DVB driver bug, but the maintainer said it was an application bug. I found the following, which requires you to patch/rebuild vdr from source. Basically it just adds a small delay to the tuning process, and it works 100% for me. I had to do this on 1.4.7 and carried it over in 1.6.0 also - so no, vanilla 1.6 won't help you. It would be good if something equivalent was in vanilla VDR but I suppose it slows some systems by a fraction of a second when tuning. Perhaps a "budget card" option? http://www.vdr-portal.de/board/thread.php?postid=639048 The actual patch is at http://tafe.unkelhaeusser.de/vdr/dvbdevice.c.patch HTH

3 2

Tuning failures for transponder-locked tuners (VDR 1.4.7)
by Teemu Suikki 29 Oct '08

29 Oct '08

I have a VDR box with three DVB-T tuners.. All cards are saa7146+tda10045 -based budget cards. I have forced the cards to specific transponders in channels.conf. Basicly VDR never has to switch transponders, all channels are always tuned. However, sometimes one of the cards looses sync and doesn't re-tune.. It's not always the same card, can be any of the three. The problem is that VDR doesn't recover from this. If there is a timed recording going on that "jammed" tuner, VDR keeps on restarting over and over again, which effectively ruins recordings on all other channels as well. VDR restarting doesn't solve the problem, the card still doesn't tune. I have tried killing VDR when the tuner is jammed, and then try tuning with tzap.. Tuning fails for the "already tuned" channel, but if I simply tune to another transponder and then back, it tunes fine. So apparently the problem is that VDR doesn't even try re-tuning because the tuners are "locked" to specific transponders in channels.conf.. I'm actually using VDR 1.4.7, I know it's old but otherwise it's working fine. Has there been any changes in this area in recent versions? So is it likely to fix my problem if I upgrade to latest developer version for example? -- Teemu Suikki http://www.z-power.fi/

2 1

What ever happened to...
by jean-paul＠goedee.nl 28 Oct '08

28 Oct '08

I running vdr & streamdev for years now. First with 2* t\t 1500 ci (default dvb) and now with 2* tt 3200ci (multiproto). Only some judder and I think it?s a remux problem. For the Windows clients (my self and the children) you can use vdr zapper (choose TS transport in application settings) and for example media player classic or vlc. Personal like media player classic (older version) with powerdvd video decoder and for HDTV CoreAVC (is 42? screen and gives me a very good picture. Why windows? Laptop/desktop for playing games(windows), listen music, internet, and watching tv. So what is the problem? Regards Jean-Paul

2 1

Re: [vdr] Problems building xine-lib on openSUSE 11.0 w/ gcc 4.3.1
by Niels Wagenaar 28 Oct '08

28 Oct '08

-----Original message----- From: Goga777 <goga777(a)bk.ru> Sent: Tue 28-10-2008 10:06 To: vdr(a)linuxtv.org; Subject: Re: [vdr] Problems building xine-lib on openSUSE 11.0 w/ gcc 4.3.1 > > -- SNIP -- > > How did you deduce that, when Darren said that you should upgrade your > > xine-lib? You might even jump to xine-lib 1.2 which already includes > > vdr-xine plugin. > > does xine-lib 1.2 include vdr-pligin from Reinchard Nissl ? are you sure ? > Last time I check, xine-lib 1.2 doesn't include the vdr-xine plugin. But, if you use 1.2, you don't have to patch xine-lib anymore. Xine-lib 1.2 now includes the patches for Xine-Lib so that you connect to a VDR system which is using the vdr-xine plugin. > Goga > Regards, Niels Wagenaar

2 1

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr October 2008