[vdr] VDR 1.7.0 + xine plugin 0.8.2 - several iisues
Hi I'm start to test my system - dvb-s2 card hvr4000 (with latest multiproto_plus + hvr4000 patch from Gregoire Favre) + VDR 1.7.0 + xine-plugin 0.8.2 + xine-lib-1.2 from HG + xine-ui from CVS + ffmpeg from SVN (I didn't test dvb-s2 yet, but it seems to me - the dvb-s works well) But if I disconnect from the card the antenna I will have this problem [EMAIL PROTECTED]:/usr/src/VDR$ ./vdr -c /etc/vdr -P xine -r - MakePrimaryDevice: 1 = SetVideoFormat: 0 SetVolumeDevice: 255 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetVolumeDevice: 255 SetPlayMode: 1 frame: (0, 0)-(-1, -1), zoom: (1.00, 1.00) vdr-xine: Client connecting ... vdr-xine: Client connected! frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) video: synced early [VMA]buffered 8.2 frames (v:20.1, a:8.2) buffered 9.5 frames (v:18.8, a:9.5) SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 [vVMA]buffered 8.5 frames (v:14.8, a:8.5) buffered 6.6 frames (v:15.3, a:6.6) frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) audio: synced early [AMvV]buffered 12.2 frames (v:20.9, a:12.2) SetPlayMode: 0 frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 =skipped frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 SetPlayMode: 0 SetAudioChannelDevice: 0 SetDigitalAudioDevice: 0 SetAudioChannelDevice: 0 SetPlayMode: 1 frame: (0, 0)-(720, 576), zoom: (1.00, 1.00) vdr-xine: Client disconnected! #!!1 SetPlayMode: 0 [EMAIL PROTECTED]:/usr/src/VDR$ let's see in the xine output input_cache: read calls: 0, main input read calls: 0 input_cache: seek_calls: 0, main input seek calls: 0 input_vdr: shutting down rpc thread (timeout: 1 ms) ... input_vdr: joining rpc thread ... input_vdr: rpc thread joined. xine: found input plugin : file input plugin load_plugins: probing demux 'anx' load_plugins: probing demux 'image' load_plugins: probing demux 'wve' load_plugins: probing demux 'idcin' load_plugins: probing demux 'ipmovie' load_plugins: probing demux 'vqa' load_plugins: probing demux 'wc3movie' load_plugins: probing demux 'roq' load_plugins: probing demux 'str' load_plugins: probing demux 'film' load_plugins: probing demux 'smjpeg' load_plugins: probing demux 'fourxm' load_plugins: probing demux 'vmd' load_plugins: probing demux 'aiff' load_plugins: probing demux 'flac' load_plugins: probing demux 'realaudio' load_plugins: probing demux 'snd' load_plugins: probing demux 'tta' load_plugins: probing demux 'voc' load_plugins: probing demux 'vox' load_plugins: probing demux 'mpeg-ts' load_plugins: probing demux 'avi' load_plugins: probing demux 'mpeg_block' load_plugins: probing demux 'mpeg_pes' load_plugins: probing demux 'quicktime' load_plugins: probing demux 'fli' load_plugins: probing demux 'yuv4mpeg2' load_plugins: probing demux 'real' load_plugins: probing demux 'pva' load_plugins: probing demux 'slave' load_plugins: probing demux 'nsv' load_plugins: probing demux 'matroska' ebml: invalid EBML ID size (0x0) at position 1 ebml: invalid master element load_plugins: probing demux 'iff' load_plugins: probing demux 'flashvideo' load_plugins: probing demux 'playlist' load_plugins: probing demux 'nsfdemux' load_plugins: probing demux 'ogg' load_plugins: probing demux 'asf' load_plugins: probing demux 'mpeg' load_plugins: probing demux 'dts' demux_dts: unsupported DTS stream type, or not a DTS stream load_plugins: probing demux 'ac3' load_plugins: probing demux 'wav' load_plugins: probing demux 'cdda' load_plugins: probing demux 'rawdv' load_plugins: probing demux 'mpc' load_plugins: probing demux 'mp3' load_plugins: probing demux 'shn' load_plugins: probing demux 'elem' xine: found demuxer plugin: Elementary MPEG stream demux plugin load_plugins: plugin mpeg2 will be used for video streamtype 00. av_offset=0 pts spu_offset=0 pts xine_play play_internal ...done video_out: throwing away image with pts 96108366 because it's too old (diff : 434402). video_out: throwing away image with pts 96111366 because it's too old (diff : 431402). video_out: throwing away image with pts 96114366 because it's too old (diff : 428402). video_out: throwing away image with pts 96117366 because it's too old (diff : 425402). video_out: throwing away image with pts 96120366 because it's too old (diff : 422402). video_out: throwing away image with pts
Re: [vdr] vdr-1.6.0 channel not available
Simon Baxter kirjoitti 24.4.2008 kello 10.08: Hello I have 2x DVB-C cards with Alphacrypt multi-cams. A TT-1500-C budget card and a TT-2300-C FF card and run vdr-xine. When recording one channel and attempting to watch another in the same transport stream, or trying to switch to another transport stream (and hence card) I get channel not available messages. After switching back and forth to other transport streams, usually I can overcome this problem. But occasionally I it won't play any channels in one specific transport stream or another. What's the best way to diagnose this? How do I enable debugging to see more info than is displayed in messages: Apr 24 18:53:56 callin vdr: [7375] switching to channel 8 Apr 24 18:53:56 callin vdr: [30940] transfer thread started (pid=7375, tid=30940) Apr 24 18:53:57 callin vdr: [30939] femon receiver thread ended (pid=7375, tid=30939) Apr 24 18:53:57 callin vdr: [30941] femon receiver thread started (pid=7375, tid=30941) Apr 24 18:53:58 callin vdr: [30940] setting audio track to 1 (0) Apr 24 18:54:04 callin vdr: [7375] switching to channel 9 Apr 24 18:54:04 callin vdr: [30940] transfer thread ended (pid=7375, tid=30940) Apr 24 18:54:04 callin vdr: [7375] buffer stats: 47564 (2%) used Apr 24 18:54:04 callin vdr: [7375] info: Channel not available! Apr 24 18:54:04 callin vdr: [7375] ERROR: attempt to open OSD while it is already open - using dummy OSD! Apr 24 18:54:22 callin vdr: [7375] switching to channel 1 Apr 24 18:54:22 callin vdr: [30942] transfer thread started (pid=7375, tid=30942) Apr 24 18:54:22 callin vdr: [30936] TS buffer on device 2 thread ended (pid=7375, tid=30936) Apr 24 18:54:22 callin vdr: [30935] buffer stats: 84600 (4%) used Apr 24 18:54:22 callin vdr: [30935] receiver on device 2 thread ended (pid=7375, tid=30935) Apr 24 18:54:22 callin vdr: [30943] receiver on device 2 thread started (pid=7375, tid=30943) Apr 24 18:54:22 callin vdr: [30944] TS buffer on device 2 thread started (pid=7375, tid=30944) Apr 24 18:54:23 callin vdr: [30945] femon receiver thread started (pid=7375, tid=30945) Apr 24 18:54:23 callin vdr: [30942] setting audio track to 1 (0) Apr 24 18:54:26 callin vdr: [7375] switching to channel 9 Apr 24 18:54:26 callin vdr: [30942] transfer thread ended (pid=7375, tid=30942) Apr 24 18:54:26 callin vdr: [7375] buffer stats: 194204 (9%) used Apr 24 18:54:26 callin vdr: [7375] info: Channel not available! Apr 24 18:54:26 callin vdr: [7375] ERROR: attempt to open OSD while it is already open - using dummy OSD! Apr 24 18:54:42 callin vdr: [7375] switching to channel 21 Hi, I don't know if this is same problem or not but I'm having similar symptoms with one encrypted channel. With plain VDR 1.6.0 I cannot tune to that channel, while 1.4.7 works. As can be seen from the log, the receiving starts from couple of seconds but stops right after giving this channel not available message. My system has DVB-C 2.1 FF card and Satelco Easywatch budget card. All the other encrypted channels works ok, but this one channel has problems with VDR 1.6.0. Here's the channels.conf entry: EuroNews;GlobeCast:306000:C0M128:C:6875:2221:2232=eng,2233=deu, 2231=fra,2234=ita,2235=esl,2236=por,2237=rus,2238:768:B00:214:0:10:0 and here's the syslog: Apr 27 13:31:53 localhost vdr: [10238] cTimeMs: using monotonic clock (resolution is 999848 ns) Apr 27 13:31:53 localhost vdr: [10238] VDR version 1.6.0 started Apr 27 13:31:53 localhost vdr: [10238] codeset is 'ISO-8859-1' - known Apr 27 13:31:53 localhost vdr: [10238] found 23 locales in ./locale Apr 27 13:31:53 localhost vdr: [10238] loading /video/setup.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/sources.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/channels.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/timers.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/svdrphosts.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/remote.conf Apr 27 13:31:53 localhost vdr: [10238] loading /video/keymacros.conf Apr 27 13:31:53 localhost vdr: [10238] reading EPG data from /video/ epg.data Apr 27 13:31:53 localhost vdr: [10248] video directory scanner thread started (pid=10238, tid=10248) Apr 27 13:31:53 localhost vdr: [10249] video directory scanner thread started (pid=10238, tid=10249) Apr 27 13:31:53 localhost vdr: [10249] video directory scanner thread ended (pid=10238, tid=10249) Apr 27 13:31:53 localhost vdr: [10248] video directory scanner thread ended (pid=10238, tid=10248) Apr 27 13:31:53 localhost vdr: [10238] probing /dev/dvb/adapter0/ frontend0 Apr 27 13:31:53 localhost vdr: [10251] CI adapter on device 0 thread started (pid=10238, tid=10251) Apr 27 13:31:53 localhost vdr: [10238] probing /dev/dvb/adapter1/ frontend0 Apr 27 13:31:53 localhost vdr: [10252] tuner on device 1 thread started (pid=10238, tid=10252) Apr 27 13:31:53 localhost vdr: [10253] section handler
Re: [vdr] VDR 1.7.0 + xine plugin 0.8.2 - several iisues
Hi, Igor Nikanov schrieb: But if I disconnect from the card the antenna I will have this problem [snip] Apr 27 13:37:32 localhost vdr: [5732] timer 1 (88 1318-1618 '@Das gemütliche Schlafzimmer') set to event Sun 27.04.2008 14:0 Apr 27 13:37:32 localhost vdr: [5732] switching device 1 to channel 88 Apr 27 13:37:32 localhost vdr: [5732] timer 1 (88 1318-1618 '@Das gemütliche Schlafzimmer') start Apr 27 13:37:32 localhost vdr: [5732] Title: 'Das gemütliche Schlafzimmer' Subtitle: '(null)' Apr 27 13:37:32 localhost vdr: [5732] record /video/@Das_gemütliche_Schlafzimmer/2008-04-27.13.18.50.99.rec Apr 27 13:37:32 localhost vdr: [5732] recording to'/video/@Das_gemütliche_Schlafzimmer/2008-04-27.13.18.50.99.rec/003.vdr' [snip] Apr 27 13:38:03 localhost vdr: [5746] ERROR: video data stream broken Apr 27 13:38:03 localhost vdr:[5746] initiating emergency exit Apr 27 13:38:03 localhost vdr: [5732] emergency exit requested - shuttingdown [snip] Apr 27 13:38:06 localhost vdr: [5732] exiting, exit code 1 Apr 27 13:38:06 localhost vdr: [5732] emergency exit! When there is a recording going on and no more data comes in (due to the disconnected antenna cable), then VDR assumes a buggy driver/card, requests an emergency exit which will then reload the driver. In the case where this doesn't fix the problem (i. e. it won't help if you disconnected the antenna cable), VDR will continue to record but still sees no data. The result is, it will again request an emergency exit. This scenario will go on until either the timer(s) get(s) outdated or the signal comes back (by having someone connect the antenna cable again). There has been a discussion regarding pro and cons of emergency exit and the result is that at least from VDR-1.5.18 on you can disable this feature in VDR's setup/miscellaneous menu. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 + xine plugin 0.8.2 - several iisues
Hi, Igor Nikanov schrieb: But if I disconnect from the card the antenna I will have this problem [snip] let's see in the xine output [snip] video_out: throwing away image with pts 96108366 because it's too old (diff : 434402). video_out: throwing away image with pts 96111366 because it's too old (diff : 431402). video_out: throwing away image with pts 96114366 because it's too old (diff : 428402). video_out: throwing away image with pts 96117366 because it's too old (diff : 425402). video_out: throwing away image with pts 96120366 because it's too old (diff : 422402). video_out: throwing away image with pts 96123366 because it's too old (diff : 419402). video_out: throwing away image with pts 96126366 because it's too old (diff : 416402). video_out: throwing away image with pts 96129366 because it's too old (diff : 413402). video_out: throwing away image with pts 96132366 because it's too old (diff : 410402). video_out: throwing away image with pts 96135366 because it's too old (diff : 407402). video_out: throwing away image with pts 96138366 because it's too old (diff : 404402). video_out: throwing away image with pts 96141366 because it's too old (diff : 401531). video_out: throwing away image with pts 96144366 because it's too old (diff : 398630). video_out: throwing away image with pts 96147366 because it's too old (diff : 395630). When you disconnect the antenna cable for a certain amount of time, there will be a gap in presentation time stamps (PTS). This will cause xine to jump over the gap with the result that the previously established buffer will run empty immediately. Any further received images will therefore arrive to late at xine and cause the above messages. Maybe I can find a solution for vdr-xine to detect this issue and reestablish a suitable buffer in this case. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Problem with Frontend tuning
hi, i have a vdr system with the following layout: - asus p5b-e board (3 pci slots) - reel hd-e - 2 tt s2-3200 (dvb-s2) / astra 19.2 - cam module alphacrypt classic 3.14 - vdr 1.7.0 with extension patch 59 and h.264 patch - multiproto driver of today (46df93f7bcee tip) and i have the following issue: - i cannot tune to transponder 11953 (ZDF) on frontend 1, but works on frontend 2 - i (often) cannot tune to transponder 11836 (ARD) on frontend 1, but works on frontend 2 channels.conf lines: Das Erste;ARD:11836:hC34M2O0S0:S19.2E:27500:101:102=deu,103=2ch;106=dd:104:0:28106:1:1101:0 ZDF;ZDFvision:11953:hC34M2O0S0:S19.2E:27500:110:120=deu,121=2ch;125=dd:130:0:28006:1:1079:0 what i already did: - the problem occured a while ago after updating vdr to 1.5.13 or 1.5.14 (don't know this exactly) and updating multiproto to version 7208 - i updated the following components to the current available versions: - mainboard bios to 1802 - vdr to 1.7.0, including all plugins i use - multiproto to 46df93f7bcee - alphacrypt to 3.14 - still didn't work - i switched the antenna cables - problem persists - i switched the pci slots of the cards - problem persists - i tested every card alone with both antenna connections - each card worked fine - i disconnected the ci - after that both cards worked seemless - i removed the smartcard - problem persists - i removed the cam - problem persists - i tested using one card and connected the ci to this card, removed the second card - problem persists - i did the same the with the other card - worked - i added the second card to the system - problem persists results: - the problem only occurs on the two transponders - the two budget cards work fine - no hardware problem - the antenna cables work fine - has nothing to do with the pci slot i use since i swapped them around - the problem seems to occur in conjunction with the ci interface with or without cam so my question is: is there a known issue with the tt-s2-3200 and a ci interface which prevents the tuner to tune to specific transponders? any ideas out there? suggestions would be very appreciated. frank. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.0 channell's scan
Hi how is it possible to scan dvb-s/s2 channels with vdr 1.7.0 ? Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] new parameters for channels.conf in VDR 1.7.0
Hi from readme vdr 1.7.0 = Note that the channels.conf file now supports additional parameters, so you may want to make sure you have a backup of this file in case you need to go back to the previous version of VDR! = which difference between this describing ? http://linuxtv.org/vdrwiki/index.php/Syntax_of_channels.conf Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.0 channell's scan
Hi, Igor Nikanov schrieb: how is it possible to scan dvb-s/s2 channels with vdr 1.7.0 ? Well, there is no explicit scan functionality. When VDR receives a channel (for example when it does an EPG scan for all already known transponders (generated from channels.conf)) and sees a network information table (NIT), it will analyze it and add new channels to channels.conf, when it is allowed to do so. See VDR's setup / dvb menu, update channels = add new transponders. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new parameters for channels.conf in VDR 1.7.0
Hi, Igor Nikanov schrieb: from readme vdr 1.7.0 = Note that the channels.conf file now supports additional parameters, so you may want to make sure you have a backup of this file in case you need to go back to the previous version of VDR! = which difference between this describing ? http://linuxtv.org/vdrwiki/index.php/Syntax_of_channels.conf The new parameters are documented in man 5 vdr but the parameter S is missing: S0 = DVB-S S1 = DVB-S2 For DVB-S/S2 the following parameters are new: S, M, O = system, modulation, rolloff For DVB-T the following parameters are new: A, P = alpha, priority By comparing the 1.6.0 man page against the 1.7.0 one, you'll see that a couple of parameters (for example M and C) can have much more values now. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] cvs xineliboutput
Hi, I'm using vdr-1.6 and xineliboutput from cvs. I'm using it with freevo and vdr is controlled through xine-ui/vdr-sxfe by stdin. For instance I send hitk Up to vdr-sxfe or EventUp to xine-ui. Every so often when i change between channels xine-ui/vdr-sxfe stops displaying video+osd. I have to quit it and start it again. (but commands are still sent to vdr, if i press up 2 times while xine-ui/vdr-sxfe has stopped displaying anything, I can see vdr receiving the up events) I haven't tried to reverse patches, or to reproduce it without using stdin (--stdctl/--slave). Before I do so, I'm just asking if anybody has encountered this issue already. Cheers. -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0
Hi when I want to switch on dvb-s2 channels ( Apr 28 09:18:32 localhost vdr: [4188] switching to channel 2782 Apr 28 09:18:32 localhost vdr: [4535] transfer thread ended (pid=4188, tid=4535) Apr 28 09:18:32 localhost vdr: [4188] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4756] transfer thread started (pid=4188, tid=4756) Apr 28 09:18:32 localhost vdr: [4537] TS buffer on device 1 thread ended (pid=4188, tid=4537) Apr 28 09:18:32 localhost vdr: [4536] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4536] receiver on device 1 thread ended (pid=4188, tid=4536) Apr 28 09:18:32 localhost vdr: [4757] receiver on device 1 thread started (pid=4188, tid=4757) Apr 28 09:18:32 localhost vdr: [4758] TS buffer on device 1 thread started (pid=4188, tid=4758) Apr 28 09:18:40 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 Apr 28 09:18:40 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:40 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:18:50 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:50 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:00 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:00 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:10 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:10 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:20 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:20 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:30 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:30 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:41 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0 ERROR (dvbdevice.c,302): Invalid argument
Hi when I want to switch on dvb-s2 channel ASTRA HD+;BetaDigital:11914:hC910I1M2O35S1:S19.2E:27500:1279:0;1283=deu:0:0:131:133:6:0 I receive this error Apr 28 09:18:32 localhost vdr: [4188] switching to channel 2782 Apr 28 09:18:32 localhost vdr: [4535] transfer thread ended (pid=4188, tid=4535) Apr 28 09:18:32 localhost vdr: [4188] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4756] transfer thread started (pid=4188, tid=4756) Apr 28 09:18:32 localhost vdr: [4537] TS buffer on device 1 thread ended (pid=4188, tid=4537) Apr 28 09:18:32 localhost vdr: [4536] buffer stats: 0 (0%) used Apr 28 09:18:32 localhost vdr: [4536] receiver on device 1 thread ended (pid=4188, tid=4536) Apr 28 09:18:32 localhost vdr: [4757] receiver on device 1 thread started (pid=4188, tid=4757) Apr 28 09:18:32 localhost vdr: [4758] TS buffer on device 1 thread started (pid=4188, tid=4758) Apr 28 09:18:40 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 Apr 28 09:18:40 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:40 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:18:50 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:18:50 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:00 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:00 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:10 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:10 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:20 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:20 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:30 localhost vdr: [4197] ERROR (dvbdevice.c,302): Invalid argument Apr 28 09:19:30 localhost kernel: dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2 Apr 28 09:19:41 localhost vdr: [4197] frontend 0 timed out while tuning to channel 2782, tp 111914 in attachment you can find my dvbdevice.c Igor dvbdevice.c.bz2 Description: BZip2 compressed data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
