vdr November 2005

vdr@linuxtv.org

144 participants
178 discussions

StartHWFilterError
by Christoph Gohle 08 Nov '05

08 Nov '05

Dear List, since some time I am experiencing a strange error during the boot of my vdr. After the driver was loaded and vdr starts, the live picture briefly appears, and then diappears with the funny pattern from driver loading reappearing. After a while the screen goes black. The OSD is fully functional and after a reload of the drivers and restart of vdr everything works fine. When i look into the syslog, I find the following: Nov 8 03:33:12 glotze vdr[570]: starting plugin: vdrcd Nov 8 03:33:12 glotze vdr[570]: starting plugin: games Nov 8 03:33:12 glotze vdr[570]: loading /vdrconf/vdr-1.3.x-skin-conf/themes/stt ng-default.theme Nov 8 03:33:12 glotze vdr[963]: LIRC remote control thread started (pid=963, ti d=6151) Nov 8 03:33:12 glotze vdr[964]: KBD remote control thread started (pid=964, tid =7176) Nov 8 03:33:12 glotze vdr[570]: remote control LIRC - keys known Nov 8 03:33:12 glotze vdr[570]: remote control KBD - keys known Nov 8 03:33:12 glotze vdr[570]: switching to channel 1 Nov 8 03:33:12 glotze vdr[570]: creating directory /vtx/S19.2E-1-1101-28106 Nov 8 03:33:12 glotze vdr[966]: receiver on device 1 thread started (pid=966, t id=9226) Nov 8 03:33:12 glotze vdr[967]: TS buffer on device 1 thread started (pid=967, tid=10251) Nov 8 03:33:12 glotze vdr[961]: TVTV Receive 260 Bytes Nov 8 03:33:12 glotze vdr[961]: TVTV Timer File processed Nov 8 03:33:13 glotze kernel: lirc_serial: port 02f8 already in use, proceeding anyway Nov 8 03:33:13 glotze kernel: lirc_serial: compile the serial port driver as mo dule and Nov 8 03:33:13 glotze kernel: lirc_serial: make sure this module is loaded firs t Nov 8 03:33:14 glotze kernel: lirc_serial: auto-detected active low receiver Nov 8 03:33:14 glotze vdr[570]: setting watchdog timer to 30 seconds Nov 8 03:33:15 glotze kernel: CommandRequest: timeout waiting for COMMAND to co mplete Nov 8 03:33:15 glotze kernel: StartHWFilter error Nov 8 03:33:16 glotze kernel: OutCommand: timeout waiting for COMMAND idle Nov 8 03:33:16 glotze kernel: CommandRequest error Nov 8 03:33:16 glotze kernel: StopHWFilter error Nov 8 03:33:17 glotze kernel: OutCommand: timeout waiting for COMMAND idle . . . Nov 8 03:33:26 glotze kernel: SOutCommand error Nov 8 03:33:26 glotze kernel: outcom error Nov 8 03:33:27 glotze kernel: OutCommand: timeout waiting for COMMAND idle Nov 8 03:33:27 glotze kernel: CommandRequest error Nov 8 03:33:27 glotze kernel: StartHWFilter error Nov 8 03:33:28 glotze kernel: OutCommand: timeout waiting for COMMAND idle Nov 8 03:33:12 glotze vdr[961]: TVTV Receive 260 Bytes Nov 8 03:33:12 glotze vdr[961]: TVTV Timer File processed Nov 8 03:33:13 glotze kernel: lirc_serial: port 02f8 already in use, proceeding anyway Nov 8 03:33:13 glotze kernel: lirc_serial: compile the serial port driver as module and Nov 8 03:33:13 glotze kernel: lirc_serial: make sure this module is loaded first Nov 8 03:33:14 glotze kernel: lirc_serial: auto-detected active low receiver Nov 8 03:33:14 glotze vdr[570]: setting watchdog timer to 30 seconds Nov 8 03:33:15 glotze kernel: CommandRequest: timeout waiting for COMMAND to complete Nov 8 03:33:15 glotze kernel: StartHWFilter error Nov 8 03:33:16 glotze kernel: OutCommand: timeout waiting for COMMAND idle . . . Nov 8 03:33:26 glotze kernel: outcom error Nov 8 03:33:27 glotze kernel: OutCommand: timeout waiting for COMMAND idle Nov 8 03:33:27 glotze kernel: CommandRequest error Nov 8 03:33:27 glotze kernel: StartHWFilter error Nov 8 03:33:28 glotze kernel: OutCommand: timeout waiting for COMMAND idle Nov 8 03:33:28 glotze kernel: SOutCommand error Nov 8 03:33:28 glotze kernel: outcom error Nov 8 03:33:29 glotze kernel: OutCommand: timeout waiting for COMMAND idle Nov 8 03:33:29 glotze kernel: SOutCommand error Nov 8 03:33:29 glotze kernel: outcom error Nov 8 03:33:29 glotze vdr[570]: max. latency time 15 seconds Nov 8 03:33:30 glotze kernel: OutCommand: timeout waiting for COMMAND idle Nov 8 03:33:30 glotze kernel: CommandRequest error Nov 8 03:33:30 glotze kernel: StartHWFilter error Nov 8 03:33:30 glotze kernel: av71100: ARM crashed! Nov 8 03:33:30 glotze kernel: StartHWFilter error Nov 8 03:33:31 glotze kernel: outcom error Nov 8 03:34:08 glotze sshd[970]: Accepted password for ctg from ::ffff:192.168.0.1 port 3914 Nov 8 03:34:10 glotze vdr[570]: PANIC: watchdog timer expired - exiting! Nov 8 03:34:11 glotze vdr[964]: KBD remote control thread ended (pid=964, tid=7176) Nov 8 03:34:11 glotze vdr[967]: TS buffer on device 1 thread ended (pid=967, tid=10251) Nov 8 03:34:11 glotze vdr[966]: buffer stats: 3948 (0%) used Nov 8 03:34:11 glotze vdr[966]: receiver on device 1 thread ended (pid=966, tid=9226) I am running vdr 1.3.32 (although this phenomenon was observed with 1.3.15 too) with linux-dvb.2004-12-26 on a siemens 1.3 card. The kernel is 2.4.18 in a suse system (8.0) Anyone seen this before (I have seen a few posts in google, but no ideas) Best Regards, Christoph-

1 0

vdr-xine build error
by tony 07 Nov '05

07 Nov '05

Tried building xine plugin yesterday - ideas? Tony xineLib.h:31: attention : ‘class PluginXine::cXineLibEvents’ has virtual functions but non-virtual destructor xineDevice.h:39: erreur: expected class-name before ‘,’ token xineDevice.h:49: erreur: ‘ePlayMode’ has not been declared make[1]: *** [xine.o] Erreur 1

2 1

cReceiver vs cFilter and PTS questions
by Patrick Fischer 07 Nov '05

07 Nov '05

Hello I have a couple of questions. 1. whats the differents between cReceiver and cFilter? I was first exposed the cFilter is set for only one PID and the cReceiver can get all Pakets from the whole stream. But now I think the cReceiver can't get all the Pakets because the bandwidth of the pci/usb/.. can't be enough. So what is the differents? Im not so long in this list but I think this question sould picked up in the PLUGINS.html 2. I want to get the PTS from the current V-PID. I have looked at the femon Plugin. This use a cReceiver which gives me an repacked TS with 188byts. I have surched for a Spec. which gives me more informations about the 188Byts. The first 16bit (12bit used) are the PID 8bit are the (PAYLOAD/ADAPT_FIELD)(don't know what it is) 8bit some kind of offset ...... then femon sets a pointer to the receved paket+offset (named sb) next femon sets a new pointer to sb + sb[8] + 9 (named pay) after all pay shows to the video, audio or AC3 data. But how to get the PTS? 3. I want to get all PTS from all V-PID's on the transponder. Is it possible? Yours sincerely Patrick

4 8

readline patches for broken plugins (vdr-1.3.36)
by C.Y.M 07 Nov '05

07 Nov '05

I noticed that several plugins that were using the MAXPARSEBUFFER macros have broke for vdr-1.3.36. The following plugins have been affected: autotimer-0.1.7 mplayercluster-0.0.1a (with Udo's latest patchset) playlist-0.0.2 streamplayer-0.1.1 text2skin.cvs undelete-0.0.3 Here is my attempt at fixing the compile. I'm not much of a programmer, so please be gentle. :) I would appreciate any criticism. BTW, these patches are not backwards compatible with older versions of vdr, so you have been warned. :) Thanks.

4 5

Re: Fwd: Softdevice not working properly...
by Eric GRAMMATICO 07 Nov '05

07 Nov '05

Thanks a lot for your reply! See my answers in line. BTW, VDR Wiki states xvmc is supported by Softdevice. http://www.linuxtv.org/vdrwiki/index.php/Softdevice-plugin So what is the best option to minimize CPU usage with Softdevice ? Thanks again Regards, Eric. 2005/11/2, Stefan Lucke <stefan(a)lucke.in-berlin.de>: > Quoting Eric GRAMMATICO <e.grammatico(a)gmail.com>: > > > Hi Luke, Hi Martin, > > > > Please could you have a look on the following mail I sent to vdr > > mailing list ? My graphic card is a NV gfx5200 with tv-out. > > > > Thanks and regards. > > I've seen your post on vdr list, and I still don't know what to ask > or check. So lets do the usual Qs. > > Is it X11 from Xfree or Xorg ? > What is the exact version ? (written in /var/log/X.log.???) xorg-x11-6.8.2 > Does video appear when you are moving the window ? No window, bcs no windows/desktop manager. VDR is launch alone from the .Xclients file. > Whats the output of command xvinfo ? Cant reply now as I am at work... > > All I know is that there are reports from some people that > softdevice works with nvidia cards, so it is not hopeless to > get your card work too. > > Have to look at private mail exchange with Olaf, who > had some nvidia troubles too. > > > > > Eric. > > > > ---------- Forwarded message ---------- > > From: Eric GRAMMATICO <e.grammatico(a)gmail.com> > > Date: 1 nov. 2005 22:32 > > Subject: Softdevice not working properly... > > To: Klaus Schmidinger's VDR <vdr(a)linuxtv.org> > > > > > > Hi All, > > > > I am trying desperately to have softdevice plugin working on my vdr box. > > > > My config: > > FC4 > > nvidia drivers 7174 > > ffmpeg-0.4.8 > > vdr-1.3.34 > > softdevice-0.2.0 or cvs > > > > > > When vdr starts, the video is displayed but freezed, osd is running > > correctly, I can open the menu and do what I want. the same for > > recorded videos. What is strange, if I fast forward my records, it > > works... > > > > Nothing interesting in /var/log/messages, and console says: > > > CMD[1626]:TrickSpeed 1 > > CMD[1626]:Play > > CMD[1626]:Neuer Thread gestartet: Mpeg2Decoder pid 2856 > > CMD[1630]:new Video stream index.. old -1 new 0 > > CMD[1631]:Neuer StreamDecoder Pid: 2856 context 0x9ec17f8 type 0 > > CMD[1631]:Neuer Thread gestartet: pid:2857 type 0 > > ++++++++++CMD[2307]:Clear > > ... > > I am not sure how to configure X to use xvmc, didnt find any > > documentation on that someone to guide me ? > > Softdevice has no support for xvmc :-( . > > > Stefan Lucke >

2 9

Suggestions for VDR setup with output over GeForce 3 Ti500
by Anders Gunnarsson 07 Nov '05

07 Nov '05

Hi all, I'm going to set up a VDR-box with output over an ordinary graphics card for the first time. The box is to be a dedicated tv and mediaplayer. As I understood the choise is between xine and softdevice plugins, and then if X or frame buffer is to be used. It would be nice to make use of hardware acceleration if that is possible. I would be glad if someone with experience from such setups could be kind enough to give me some hints to what would be suitable setup for my needs, when it comes to plugins to use for output and media playing, and output method (X, FB, ...). Hardware to be used is: P4 1.8, 512MB Geforce 3 Ti 500 SB Live 5.1 with S/P-dif

2 1

testing vdradmin-0.97-am3.4.2rc3
by C.Y.M 07 Nov '05

07 Nov '05

I have been testing vdradmin-0.97-am3.4.2rc3 from vdrportal.de and have come across a bug that I can not explain. When I check the "Timers" page, it shows the recording light on several timers scheduled throughout the week. For example, today is Sunday, but the timer page says that the timers scheduled on Wednesday and Friday are currently running. Has anyone else noticed this problem? Best Regards,

4 4

get informations about current running recording or timeshifting
by Patrick Fischer 07 Nov '05

07 Nov '05

Hello I would like to get some informations from the current cPlayer. Just like the PTS of the current running recording or of the current timeshift. Maybe also "time to run of current running recording" or "total Time of current running recording" At the moment I don't have a overview over all functions of vdr. I think there are two ways to get this informations. 1) create an own cPlayer with the same function the the dvbplayer but with one more function to get the informations. Drawback is that I need to copy much functions. 2) patch vdr to include my function into the dvbplayer. I'm not sure which is the best(and maybe fastest) way to implement this function. I prefer a plugin. Maybe there is a way for SVDRP or Custom services that I don't know. Patrick

1 0

RE: [vdr] CAMS and DVB-C card recommendations
by jori.hamalainen＠teliasonera.com 07 Nov '05

07 Nov '05

> Dumb question - what happens if you plug a Cable-TV service into a DVB-T > card? > > Will it find any channels? No it will not, because modulation if different. So DVB-T card seeing DVB-C modulation is like me (and probably you) seeing Hebrew.. >From DVB wiki: These distribution systems differ mainly in the modulation schemes used, due to the different technical constraints: * DVB-S (SHF) uses QPSK; * DVB-C (VHF/UHF) uses QAM (64-QAM in general); * DVB-T (VHF/UHF) uses COFDM. Best regards, Jori

2 1

CAMS and DVB-C card recommendations
by Simon Baxter 07 Nov '05

07 Nov '05

Hi. TelstraClear New Zealand has just launched it's digital cable service using the set-top-box from 'Advanced Digital Broadcast'. It's the 3000 series which the datasheet says supports : Cable Tuner Input frequency: 47MHz 862 MHz QAM Modes: 64, 128, 256 Symbol Rate 4 - 6.9 MS/s Middleware compliant with MHP, DVB-MHP compliant MHEG-5 ADB proprietary NDS Core OpenTV CA System Support up to 2 smartcards Compliant with all main CAS systems System Main Processor: STi5514/5516 Memory: Up to 48MB RAM, up to 8MB Flash Cable: DVB C compliance: ETS 300 - 429; ITU-T J.83 Annex A and C Terrestrial: DVB T compliance: ETS 300 -744 Satellite: DVB S compliance: ETS 300 - 421 Output signal: PAL B, G, D, K, I, M, N, NTSC; SECAM I'm currently using a single budget DVB-T card with VDR, but would like to add a DVB-C card which will work with the New Zealand cable service. Based on the information above, what model DVB-C card should I buy? Also, if I want to add a CAM for the encrypted channels, what CAM should I buy? Is the above box likely to license the decryption against just the smartcard, or a combination of smartcard and box serial number? any help appreciated - thanks!!

1 1

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr November 2005