vdr September 2005

vdr@linuxtv.org

138 participants
185 discussions

Re: [linux-dvb] wake on remote
by matthieu castet 11 Sep '05

11 Sep '05

Hi, Darren Merritt wrote: > Hi, > > Seems it's possible since kernel 2.6.x but from my reading, a lot of people > have trouble with it. I believe the idea is that if you can setup a > key/combination to operate a suspend from a keyboard, then somehow you would > hope to map that command to the remote. > For keyboard, mouse, serial port it is trivial via /proc/acpi/wakeup. But for our case we should have a dvb (pci) card that allow to keep the remote device active when we shut down the computer and to send a wakeup even. So I fear it is card specific and even could need some driver code to activate this feature. Regards, Matthieu

2 1

vdr 1.3.31: Can't change DVB-T Transponder
by Dominik 10 Sep '05

10 Sep '05

Hello, Sometimes I can't change the transponder with vdr. Just 4 Channels works. When I try to switch to another channel, I just got a black screen :( With tzap and mplayer, I can switch to any transponder. I'm using Kernel 2.6.13, 2 Budget TechnoTrend DVB-T and a FF Fujitsu Siemens DVB-C Card. Just the same 4 Channels (N24, ProSieben, Sat.1, Kabel1) This are the logs: debug Sep 10 20:30:39 localhost vdr[4710]: reading EPG data from /video/epg.data Sep 10 20:30:39 localhost vdr[4710]: probing /dev/dvb/adapter0/frontend0 Sep 10 20:30:40 localhost vdr[4710]: probing /dev/dvb/adapter1/frontend0 Sep 10 20:30:40 localhost vdr[4710]: tuner on device 1 thread started (pid=4710, tid=-1211409488) Sep 10 20:30:40 localhost vdr[4710]: Section handler thread started (pid=4710, tid=-1219798096) Sep 10 20:30:40 localhost vdr[4710]: probing /dev/dvb/adapter2/frontend0 Sep 10 20:30:40 localhost vdr[4710]: tuner on device 2 thread started (pid=4710, tid=-1228186704) Sep 10 20:30:40 localhost vdr[4710]: Section handler thread started (pid=4710, tid=-1236575312) Sep 10 20:30:42 localhost vdr[4710]: tuner on device 3 thread started (pid=4710, tid=-1244963920) Sep 10 20:30:42 localhost vdr[4710]: Section handler thread started (pid=4710, tid=-1253352528) Sep 10 20:30:42 localhost vdr[4710]: probing /dev/dvb/adapter3/frontend0 Sep 10 20:30:42 localhost vdr[4710]: remote control LIRC - keys known Sep 10 20:30:42 localhost vdr[4710]: remote control KBD - keys known Sep 10 20:30:42 localhost vdr[4710]: LIRC remote control thread started (pid=4710, tid=-1261741136) Sep 10 20:30:42 localhost vdr[4710]: KBD remote control thread started (pid=4710, tid=-1270129744) Sep 10 20:30:42 localhost vdr[4710]: transfer thread started (pid=4710, tid=-1280885840) Sep 10 20:30:42 localhost vdr[4710]: receiver on device 1 thread started (pid=4710, tid=-1289274448) Sep 10 20:30:42 localhost vdr[4710]: TS buffer on device 1 thread started (pid=4710, tid=-1299764304) Sep 10 20:30:42 localhost vdr[4710]: transfer thread ended (pid=4710, tid=-1280885840) Sep 10 20:30:43 localhost vdr[4710]: TS buffer on device 1 thread ended (pid=4710, tid=-1299764304) Sep 10 20:30:43 localhost vdr[4710]: buffer stats: 0 (0%) used Sep 10 20:30:43 localhost vdr[4710]: receiver on device 1 thread ended (pid=4710, tid=-1289274448) Sep 10 20:30:43 localhost vdr[4710]: buffer stats: 0 (0%) used Sep 10 20:30:43 localhost vdr[4710]: switching device 1 to channel 8 Sep 10 20:30:43 localhost vdr[4710]: Title: 'Helden aus der zweiten Reihe' Subtitle: '(null)' Sep 10 20:30:43 localhost vdr[4710]: recording to '/video/@NEWSTIME/2005-09-10.19:59.50.99.rec/006.vdr' Sep 10 20:30:43 localhost vdr[4710]: file writer thread started (pid=4710, tid=-1289274448) Sep 10 20:30:43 localhost vdr[4710]: recording thread started (pid=4710, tid=-1299764304) Sep 10 20:30:43 localhost vdr[4710]: receiver on device 1 thread started (pid=4710, tid=-1280885840) Sep 10 20:30:43 localhost vdr[4710]: TS buffer on device 1 thread started (pid=4710, tid=-1313399888) Sep 10 20:30:43 localhost vdr[4710]: transfer thread started (pid=4710, tid=-1322054736) Sep 10 20:30:43 localhost vdr[4710]: receiver on device 2 thread started (pid=4710, tid=-1330443344) Sep 10 20:30:43 localhost vdr[4710]: TS buffer on device 2 thread started (pid=4710, tid=-1340933200) Sep 10 20:30:54 localhost vdr[4710]: transfer thread ended (pid=4710, tid=-1322054736) Sep 10 20:30:55 localhost vdr[4710]: TS buffer on device 2 thread ended (pid=4710, tid=-1340933200) Sep 10 20:30:55 localhost vdr[4710]: buffer stats: 188 (0%) used Sep 10 20:30:55 localhost vdr[4710]: receiver on device 2 thread ended (pid=4710, tid=-1330443344) Sep 10 20:30:55 localhost vdr[4710]: cTS2PES got 2 TS errors, 0 TS continuity errors Sep 10 20:30:55 localhost vdr[4710]: cTS2PES got 1 TS errors, 0 TS continuity errors Sep 10 20:30:55 localhost vdr[4710]: buffer stats: 752 (0%) used Sep 10 20:30:55 localhost vdr[4710]: transfer thread started (pid=4710, tid=-1330443344) Sep 10 20:30:55 localhost vdr[4710]: receiver on device 2 thread started (pid=4710, tid=-1340933200) Sep 10 20:30:55 localhost vdr[4710]: TS buffer on device 2 thread started (pid=4710, tid=-1322054736) Sep 10 20:31:01 localhost vdr[4710]: transfer thread ended (pid=4710, tid=-1330443344) Sep 10 20:31:01 localhost vdr[4710]: TS buffer on device 2 thread ended (pid=4710, tid=-1322054736) Sep 10 20:31:01 localhost vdr[4710]: buffer stats: 6016 (0%) used Sep 10 20:31:01 localhost vdr[4710]: receiver on device 2 thread ended (pid=4710, tid=-1340933200) Sep 10 20:31:01 localhost vdr[4710]: buffer stats: 6580 (0%) used Sep 10 20:31:01 localhost vdr[4710]: transfer thread started (pid=4710, tid=-1340933200) Sep 10 20:31:01 localhost vdr[4710]: receiver on device 2 thread started (pid=4710, tid=-1322054736) Sep 10 20:31:01 localhost vdr[4710]: TS buffer on device 2 thread started (pid=4710, tid=-1330443344) Sep 10 20:31:17 localhost vdr[4710]: recording thread ended (pid=4710, tid=-1299764304) Sep 10 20:31:17 localhost vdr[4710]: TS buffer on device 1 thread ended (pid=4710, tid=-1313399888) Sep 10 20:31:17 localhost vdr[4710]: buffer stats: 58092 (2%) used Sep 10 20:31:17 localhost vdr[4710]: receiver on device 1 thread ended (pid=4710, tid=-1280885840) Sep 10 20:31:17 localhost vdr[4710]: file writer thread ended (pid=4710, tid=-1289274448) Sep 10 20:31:17 localhost vdr[4710]: cTS2PES got 2 TS errors, 1 TS continuity errors Sep 10 20:31:17 localhost vdr[4710]: cTS2PES got 0 TS errors, 1 TS continuity errors Sep 10 20:31:17 localhost vdr[4710]: cTS2PES got 1 TS errors, 2 TS continuity errors Sep 10 20:31:17 localhost vdr[4710]: buffer stats: 58468 (1%) used Sep 10 20:31:17 localhost vdr[4710]: transfer thread ended (pid=4710, tid=-1340933200) Sep 10 20:31:17 localhost vdr[4710]: TS buffer on device 2 thread ended (pid=4710, tid=-1330443344) Sep 10 20:31:17 localhost vdr[4710]: buffer stats: 188 (0%) used Sep 10 20:31:17 localhost vdr[4710]: receiver on device 2 thread ended (pid=4710, tid=-1322054736) Sep 10 20:31:18 localhost vdr[4710]: cTS2PES got 3 TS errors, 2 TS continuity errors Sep 10 20:31:18 localhost vdr[4710]: buffer stats: 752 (0%) used Sep 10 20:31:18 localhost vdr[4710]: KBD remote control thread ended (pid=4710, tid=-1270129744) Sep 10 20:31:18 localhost vdr[4710]: tuner on device 1 thread ended (pid=4710, tid=-1211409488) Sep 10 20:31:18 localhost vdr[4710]: Section handler thread ended (pid=4710, tid=-1219798096) Sep 10 20:31:19 localhost vdr[4710]: tuner on device 2 thread ended (pid=4710, tid=-1228186704) Sep 10 20:31:19 localhost vdr[4710]: Section handler thread ended (pid=4710, tid=-1236575312) Sep 10 20:31:19 localhost vdr[4710]: tuner on device 3 thread ended (pid=4710, tid=-1244963920) Sep 10 20:31:20 localhost vdr[4710]: Section handler thread ended (pid=4710, tid=-1253352528) Sep 10 20:31:20 localhost vdr[4710]: ===================== Sep 10 20:31:20 localhost vdr[4710]: EPG bugfix statistics Sep 10 20:31:20 localhost vdr[4710]: ===================== Sep 10 20:31:20 localhost vdr[4710]: IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA FOR ONE OF THE LISTED Sep 10 20:31:20 localhost vdr[4710]: CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE FUNCTION cEvent::FixEpgBugs() Sep 10 20:31:20 localhost vdr[4710]: IN VDR/epg.c TO LEARN WHAT'S WRONG WITH YOUR DATA, AND FIX IT! Sep 10 20:31:20 localhost vdr[4710]: ===================== Sep 10 20:31:20 localhost vdr[4710]: Fix^IHits^IChannels Sep 10 20:31:20 localhost vdr[4710]: 3^I866^ISAT.1, KABEL1, ProSieben, N24 Sep 10 20:31:20 localhost vdr[4710]: 7^I6^IN24 Sep 10 20:31:20 localhost vdr[4710]: ===================== messages Sep 10 20:30:39 localhost vdr[4710]: VDR version 1.3.31 started Sep 10 20:30:39 localhost vdr[4710]: loading /video/setup.conf Sep 10 20:30:39 localhost vdr[4710]: loading /video/sources.conf Sep 10 20:30:39 localhost vdr[4710]: loading /video/diseqc.conf Sep 10 20:30:39 localhost vdr[4710]: loading /video/channels.conf Sep 10 20:30:39 localhost vdr[4710]: loading /video/timers.conf Sep 10 20:30:39 localhost vdr[4710]: loading /video/svdrphosts.conf Sep 10 20:30:39 localhost vdr[4710]: loading /video/ca.conf Sep 10 20:30:39 localhost vdr[4710]: loading /video/remote.conf Sep 10 20:30:39 localhost vdr[4710]: loading /video/keymacros.conf Sep 10 20:30:39 localhost kernel: tda1004x: found firmware revision 2c -- ok Sep 10 20:30:40 localhost kernel: tda1004x: found firmware revision 2c -- ok Sep 10 20:30:42 localhost vdr[4710]: found 3 video devices Sep 10 20:30:42 localhost vdr[4710]: setting primary device to 3 Sep 10 20:30:42 localhost vdr[4710]: SVDRP listening on port 2001 Sep 10 20:30:42 localhost vdr[4710]: loading /video/themes/classic-default.theme Sep 10 20:30:42 localhost vdr[4710]: loading /video/themes/classic-default.theme Sep 10 20:30:42 localhost vdr[4710]: switching to channel 10 Sep 10 20:30:42 localhost vdr[4710]: timer 1 (8 1959-2259 '@NEWSTIME') set to event Sam 10.09.2005 20:15-22:36 'Helden aus der zweiten Reihe' Sep 10 20:30:43 localhost vdr[4710]: timer 1 (8 1959-2259 '@NEWSTIME') start Sep 10 20:30:43 localhost vdr[4710]: record /video/@NEWSTIME/2005-09-10.19:59.50.99.rec Sep 10 20:30:43 localhost vdr[4710]: switching to channel 10 Sep 10 20:30:45 localhost vdr[4710]: channel 18 (N24) event 20:04 'Doku: World Trade Center - Anschlag auf die Frei' status 4 Sep 10 20:30:45 localhost vdr[4710]: channel 5 (KABEL1) event 20:15 'Spiel mir das Lied vom Tod' status 4 Sep 10 20:30:45 localhost vdr[4710]: channel 4 (SAT.1) event 20:15 'Doppelmord' status 4 Sep 10 20:30:46 localhost vdr[4710]: channel 8 (ProSieben) event 20:14 'Helden aus der zweiten Reihe' status 4 Sep 10 20:30:54 localhost vdr[4710]: switching to channel 11 Sep 10 20:31:01 localhost vdr[4710]: switching to channel 10 Sep 10 20:31:17 localhost vdr[4710]: caught signal 2 Sep 10 20:31:17 localhost vdr[4710]: timer 1 (8 1959-2259 '@NEWSTIME') stop Sep 10 20:31:18 localhost vdr[4710]: saved setup to /video/setup.conf Sep 10 20:31:20 localhost vdr[4710]: exiting

1 0

simulate recordings?
by Christian Wieninger 10 Sep '05

10 Sep '05

Hi, is there a simple way to simulate recordings when I have no dvb hardware? The reason is, that I need to test some new features in my plugin on my development system (no dvb hardware + xine) and therefore have to do many recordings (also more that one concurrently). It would be sufficient, if the recordings only contain black screens. Can I add any plugin, that simulates a recording device or patch parts of VDR in a way, that it doesn't mind if there's no device? streamdev is no real solution, since I do not want to depend on my real VDR system. Thanks, Christian

3 2

Rotor Plugin fix for circular polarity
by M Racine 10 Sep '05

10 Sep '05

Great plugin! But it was not reading all my rotor positions in my diseqc.conf. I use a circular LNB, the polarities are 'L' or 'R' instead of 'H' or 'V' So a little patch was needed for the plugin to read both Linear and Circular sources found in diseqc.conf.

2 1

video data stream broken - again - (Privat)
by christian jacobsen 09 Sep '05

09 Sep '05

Hallo, On seldom occations I still (again) get the VDSB error :( This time I saw some cVideoRepacker infos in the Syslog that might help clear up some things !? See attached logfile. Unfortunatly I first saw this error yesterday evening and already had deleted the recording (if that would be of any use). System : Suse 9.1 Vanilla Kernel 2.6.11.7 2 x DVB-s (rev. 1.6-4mb + 1.3) vdr-1.3.29 with several patches and several plugins. dvb-kernel-20050826 dvb-kernel-20050324 fw-261e to 2620 Here a grep "video data stream broken" on all syslogs of this year - you see it did not happen between February and June (added the vdr version used at that time) : Jan 27 06:58:55 vdr vdr[12622]: ERROR: video data stream broken vdr-1.3.17 or 18 Jan 27 06:59:42 vdr vdr[14387]: ERROR: video data stream broken Jan 29 00:13:42 vdr vdr[22619]: ERROR: video data stream broken Feb 26 21:55:44 vdr vdr[27103]: ERROR: video data stream broken vdr-1.3.20 or 21 Jun 3 22:02:13 vdr vdr[20782]: ERROR: video data stream broken vdr-1.3.25 (since 2. jun) Jul 11 18:54:14 vdr vdr[8022]: ERROR: video data stream broken Jul 22 10:28:31 vdr vdr[27589]: ERROR: video data stream broken vdr-1.3.27 Jul 29 19:43:57 vdr vdr[25319]: ERROR: video data stream broken Jul 29 19:51:36 vdr vdr[5760]: ERROR: video data stream broken Aug 4 18:43:32 vdr vdr[16205]: ERROR: video data stream broken Aug 8 22:30:23 vdr vdr[27564]: ERROR: video data stream broken Aug 8 22:30:54 vdr vdr[27564]: ERROR: video data stream broken Aug 8 22:31:25 vdr vdr[27564]: ERROR: video data stream broken Aug 10 00:31:38 vdr vdr[31800]: ERROR: video data stream broken Aug 10 00:32:09 vdr vdr[31800]: ERROR: video data stream broken Aug 21 20:17:09 vdr vdr[9679]: ERROR: video data stream broken vdr-1.3.29 Aug 28 00:44:23 vdr vdr[31163]: ERROR: video data stream broken vdr-1.3.30 Sep 7 18:43:36 vdr vdr[18036]: ERROR: video data stream broken vdr-1.3.29 And I did some research ;) Kernel used : 2.6.10-rc1 since 15. Dec. 2004 2.6.10 (final) since 2. feb 2.6.11.8 since 8. May. Firmware used : 261c(+261d shortly) - used since vdr-1.3.17 261d - used since vdr-1.3.19 261e-1.4 - Around 31. may I (togehter with vdr-1.3.24) started using the New Firmware (1.4 !? IIRC the first of the 261e - from 26. may) that no longer needed FW_NEEDS_BUFFER_RESERVE_FOR_AC3. 261f - might be that I tried that since 22. august - can't say for sure. 2620 - since 29. Aug. - with vdr-1.3.30 + 29 Here a list of the DVD drivers I used, I allways started using them on the Day that I downloaded them : Up till vdr-1.3.17 - dvb-kernel-20041221 vdr-1.3.19 - dvb-kernel-20050118 vdr-1.3.23 - dvb-cvs-kernel-20050324) vdr-1.3.25 - dvb-kernel-20050617 vdr-1.3.27 (20. June) - back to dvb-kernel-20050324 (more stable) vdr-1.3.29 - dvb-kernel-20050826 (together with FW 2620) So if I see this right it comes down to that it probably is caused by the New Firmware or maybe something that was changed in VDR >= 1.3.25 ? Greetings Christian Jacobsen

2 1

1.3.30 Bug: SVDRP timer installation
by Patrick Rother 09 Sep '05

09 Sep '05

Hello. There seems to be a bug in timer handling. Please see this SVDRP snapshot: 220 vdr SVDRP VideoDiskRecorder 1.3.30; Tue Sep 6 10:50:38 2005 newt 1:S19.2E-133-33-46:----F--:2213:2250:90:30:Sechserpack: 550 Timer already defined: 12 1:5:-D-----:2213:2250:40:10:Mensch_Markus: lstt 12 250 12 1:5:-D-----:2213:2250:40:10:Mensch_Markus: newt 1:S19.2E-133-33-46:----F--:2213:2250:90:30:Sechserpack: 550 Timer already defined: 12 1:5:-D-----:2213:2250:40:10:Mensch_Markus: vdr 1.3.30 refuses to install a weekly timer with same start/stop time for a different day of week. I get the new timer in by modifying start to by one minute, so this has no actual service impact, but this shall be fixed anyway. Thank you.

2 1

two recordings at same time
by Leo Márquez 09 Sep '05

09 Sep '05

Hi, I have problems when record two programs at same time with two differents cards: Cinergy 1200 dvd-t (budget) haupaugge nexus-s dvb-s (ff) I use dvb kernel driver (2.6.11) with external firmware compiled, vdr 1.3.22 and one of the channels I record is an encrypted channel. I don't see any clearly message in syslog. Some 'emergency exit' Any ideas? Leo

1 1

vlc-0.8.2 : compilaiton problem
by kafifi 09 Sep '05

09 Sep '05

Hello, I've encountered some problem to install vlc-0.8.2-8mdk.src.rpm. MDK 10.2 asks me for somes dependencies, theses dependencies asks me some others etc.. etc.. Then I decided to install "vlc-0.8.2.tar.tar", but compilation stops after a while, with this message : ..... checking for ffmpeg-config... no checking ffmpeg/avcodec.h usability... yes checking ffmpeg/avcodec.h presence... yes checking for ffmpeg/avcodec.h... yes checking postproc/postprocess.h usability... no checking postproc/postprocess.h presence... no checking for postproc/postprocess.h... no configure: error: Missing header file postproc/postprocess.h. Mandrake 10.2 - kernel 2.6.13 I tried with gcc 3.3.2 and 3.4.1 => samed problem. Could you please help to find what's wrong ? Regards Karim.

2 1

SourceCaps patch for VDR 1.3.31.
by Carsten Koch 08 Sep '05

08 Sep '05

The attached patch allows a VDR system with multiple cards to attach each card to an individual dish pointing at a different satellite. I have 3 DVB cards in my VDR system: 1) FF card connected to one output of LNB at a dish pointed at Astra 19.2E. 2) budget card connected to another output of LNB at a dish pointed at Astra 19.2E. 3) budget card connected to output of LNB at a dish pointed at Eutelsat 13.0E. I am using the following entries for that in my setup.conf: SourceCaps = 1 S19.2E SourceCaps = 2 S19.2E SourceCaps = 3 S13.0E

3 4

VDR+DXR3 and MP3 -plugin problem
by Tommi Lundell 08 Sep '05

08 Sep '05

Hello all :-) I haven't find MP3-plugins mailing list so i need to ask questions here. That system plays music and net radios fine but problem is in osd and response times whit remote control. When i start to play some mp3 file sound start to coming almost instantly. But when i want to see artist and filename i press 1 from remote and after 5-30 (variable) i see that information on OSD. Second OSD refresh happening after about 30s. After that OSD disappears and i hear some cap (below 0.5s) in music. It's probably a same problem but still. In MP3 playback mode any remote keys processing takes 5-30sec. I add DBG=1 variable to MP3 plugins makefile but it's not tell anything new. Ouh yeah. And beginning (music on but nothing on OSD) when i press that 1 key i got message (below 1 sec lag) to syslog: Sep 7 23:35:13 localhost vdr[21270]: dxr3: cSPUEncoder::Flush: OSD data size: 4676 Aim not a capable to coding but i can to debug it if someone say what to do :-) Regards: Tommi

4 4

← Newer
1
...
11
12
13
14
15
16
17
18
19
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr September 2005