Re: [vdr] vdr-xine 0.8.0 to 0.8.2 audio sync problems
Hi, Simon Baxter schrieb: I also have consistent audio sync problems on playback. The audio is about 1/4 of a second behind the video. Can this be adjusted out? Try to adjust the A/V offset in xine-ui by pressing the keys M, N or HOME. I'm not sure whether the set offset is persistent. 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] error decompressing frame for Astra HD+
Hi, Igor schrieb: during watching of Astra HD+ from Astra 19,2E I always have this errors We'll need to clarify what during watching means. See below for details. [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame 200 frames delivered, 31 frames skipped, 52 frames discarded video_out: throwing away image with pts 120676128 because it's too old (diff : 25806). video_out: throwing away image with pts 120690172 because it's too old (diff : 43300). video_out: throwing away image with pts 120711478 because it's too old (diff : 73586). vdr: osdflush: n: 4, 76.7, timeout: 0, result: 0 video_out: throwing away image with pts 120732839 because it's too old (diff : 104127). I think it's ffmpeg's problem, but I don't know how can I solve it. It seems to me, nobody from ffmpeg-devel list doesn't want to fix it. Has somebody experience with this problem ? The above messages are OK when you switch to this channel because we jump right into the middle of the video stream. So we will see B pictures, which cannot be decoded without it's reference pictures (I or P pictures respectively). Moreover some pictures reference Picture Parameter Sets (PPS) which have been broadcast just before you switched to the channel, so these pictures cannot be decoded too. All those errors should go away from the time on, where an IDR picture is seen in the video stream, as all data up to the next IDR picture will not reference any data structures broadcast before the IDR picture. Let's now come back to the term during watching: As written above, those messages are OK when switching to a channel. When they appear during watching the channel, I could think of VDR having issued a CLEAR as it's buffers ran full for any reason, but your excerpt doesn't show such messages. Last but not least, the broadcast stream could have been buggy. 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] error decompressing frame for Astra HD+
Guten Tag, Reinhard I'm glad to see you :) during watching of Astra HD+ from Astra 19,2E I always have this errors We'll need to clarify what during watching means. See below for details. [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame 200 frames delivered, 31 frames skipped, 52 frames discarded video_out: throwing away image with pts 120676128 because it's too old (diff : 25806). video_out: throwing away image with pts 120690172 because it's too old (diff : 43300). video_out: throwing away image with pts 120711478 because it's too old (diff : 73586). vdr: osdflush: n: 4, 76.7, timeout: 0, result: 0 video_out: throwing away image with pts 120732839 because it's too old (diff : 104127). I think it's ffmpeg's problem, but I don't know how can I solve it. It seems to me, nobody from ffmpeg-devel list doesn't want to fix it. Has somebody experience with this problem ? The above messages are OK when you switch to this channel because we jump right into the middle of the video stream. So we will see B pictures, which cannot be decoded without it's reference pictures (I or P pictures respectively). ok, but I see this errors everytime :( Moreover some pictures reference Picture Parameter Sets (PPS) which have been broadcast just before you switched to the channel, so these pictures cannot be decoded too. All those errors should go away from the time on, ah, it would be fine, but really I have this errors always during the watching AstraHD where an IDR picture is seen in the video stream, as all data up to the next IDR picture will not reference any data structures broadcast before the IDR picture. Let's now come back to the term during watching: As written above, those messages are OK when switching to a channel. When they appear during watching the channel, I could think of VDR having issued a CLEAR as it's buffers ran full for any reason, but your excerpt doesn't show such messages. Last but not least, the broadcast stream could have been buggy. what about your VDR system ? Have you the same errors ? btw , I have uploaded one sample from AstraHD with the size 10 MB Astra.pes http://www.zshare.net/download/1179707004348a83/ you can try it Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] error decompressing frame for Astra HD+
Hi, Igor schrieb: I'm glad to see you :) Well, I was quite busy at work this week. what about your VDR system ? Have you the same errors ? Well, my P4 2.8 GHz HT system is not powerful enough to play this stream in real time. Hence, I regularly see VDR issue CLEARs after which such messages are normal. btw , I have uploaded one sample from AstraHD with the size 10 MB Astra.pes http://www.zshare.net/download/1179707004348a83/ you can try it As written above, I had to slow down replaying: xine -S slow2 astra.pes#demux:mpeg_pes This only gives me messages for two B pictures, i. e. you're cut VDR recording shows a picture structure like that: IBBP In MPEG2, one (VDR) would have set the broken link flag for such a group of pictures as the B pictures cannot be decoded without a reference picture from the previous GOP. But H.264 doesn't have a broken link flag, so that's why FFmpeg gives messages like the following: [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]no frame! [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]no frame! 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] Can not view DVB-S2 channels
Vangelis Nonas wrote: I dont think that this is the case because with encrypted DVB-S channels I get a blank screen but NOT the message channel not available. I get this message ONLY on DVB-S2 channels. I can perfectly watch HD Suisse which is DVB-S. with vdr 1.7 and the patch it´s possible to say that there is something if you remove the encrypted flag, and vpid, ppid and dpid they will reappear when you switch to that channel - its there, maybe they are not broadcasting at that moment ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] error decompressing frame for Astra HD+
what about your VDR system ? Have you the same errors ? Well, my P4 2.8 GHz HT system is not powerful enough to play this stream in real time. yes, I have the same CPU CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (Family: 15, Model: 3, Stepping: 4) Hence, I regularly see VDR issue CLEARs after which such messages are normal. sorry, what do you mean VDR issue CLEARs ? btw , I have uploaded one sample from AstraHD with the size 10 MB Astra.pes http://www.zshare.net/download/1179707004348a83/ you can try it As written above, I had to slow down replaying: xine -S slow2 astra.pes#demux:mpeg_pes This only gives me messages for two B pictures, i. e. you're cut VDR recording shows a picture structure like that: IBBP In MPEG2, one (VDR) would have set the broken link flag for such a group of pictures as the B pictures cannot be decoded without a reference picture from the previous GOP. But H.264 doesn't have a broken link flag, so that's why FFmpeg gives messages like the following: [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error so, could you give some resume about this errors ? is it ffmpeg/provider/vdr/driver problem ? or no any problem ? Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can not view DVB-S2 channels
Vangelis Nonas wrote: I dont think that this is the case because with encrypted DVB-S channels I get a blank screen but NOT the message channel not available. I get this message ONLY on DVB-S2 channels. I can perfectly watch HD Suisse which is DVB-S. with vdr 1.7 and the patch it s possible to say that there is something if you remove the encrypted flag, and vpid, ppid and dpid they will reappear when you switch to that channel - its there, maybe they are not broadcasting at that moment I suppose Vangelis Nonas didn't remove any encrypted flags and pids. For you information - what's new in VDR 1.6.0 The changes since version 1.5.13: - Removed switching to the next higher or lower channel if the current channel is not available, in order to allow staying on an encrypted channel that takes a while for the CAM to start decrypting. = may be in 1.7.0 it was broken for dvb-s2 encrypted channels Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.6.0 channel not available
On 05/08/08 12:12, Simon Baxter wrote: OK - I'm getting this: SetPlayMode: 0 frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) GetDevice 20 0 1 -1 no device found any ideas? If it makes any difference, I'm running vdr-1.6.0 with a budget TT-1500-C (with Alpha Multicrypt) and a FF TT-2300-C (also with Alpha Multicrypt). The card failing on this channel is the FF one (other card is tied up recording on another transponder) only seems to be failing with a single channel - other encrypted channels within the same boquet work fine works: UKTV;T:674000:C0M64:C:6900:1310+1210:1410=eng:0:606:810:182:8:0 doesn't work: Sky Movies;T:674000:C0M64:C:6900:1301+8190:1401=eng,1501=enm:0:606:801:182:8:0 Have tried the 1.6.0-1 patch, still get: SetPlayMode: 0 frame: (0, 0)-(720, 576), zoom: (1.05, 1.01) GetDevice 20 0 1 -1 no device found with this channel Here what you could try: - swap the CAMs - use only one CAM at a time - try the CAMs with either of the DVB cards Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR constantly adding and deleting filters
On 05/06/08 04:27, Anssi Hannula wrote: Hi all! While debugging another issue, I noticed (ADDF/DELF streamdev traffic) that VDR is constantly adding and deleting filters in cPatFilter::Process(). As I don't know of this filter stuff, I ask here: Is this correct behaviour? That's normal behavior - VDR is scaning for the PMT data of the various channels. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can not view DVB-S2 channels
As far as trying vdr with clear DVB-S2 channels, unfortunately it is not possible in my case since I only have access to Hotbird, which I think has no clear DVB-S2 channels. yes, you are right - on Hotbird the open dvb-s2 channels absent http://www.lyngsat.com/hd/hotbird.html As fas as changing encrypted flag, vpid, ppid and dpid, can you please give me an example, what I have to change in the following line: Next HD;SkyItalia:11996:vC23M5S1Z35:S13.0E:27500:10160+160:0;400=ita,401=eng:0:919,93B:11030:64511:6400:0 Finally, I have to mention that using multiproto (not multiproto plus) and modified szap, I can tune to Next HD and get a lock (of course I can not watch the channel, I just get the message from modified szap that it has lock). which multipro's version and szap do you use ? where from did you get szap ? Modified szap does not work at all with multiproto plus. it's strange. May be the version of multiproto_plus and multiproto is different ? Moreover, using multiproto (not multiproto plus) and vdr-1.5.14 (with h264 patch) or vdr-1.5.12 (with dvb-s2 + h264 patch) I have exactly the same behaviour with vdr-1.7.0 and multiproto plus : channel not avaialble for all DVB-S2 channels. what about the logs ? could you see un /var/syslog Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can not view DVB-S2 channels
This is my log from vdr-1.7.0 changing to HD Suisse (1853) then to Sky Sport HD 1 (1854) and then back to HD Suisse: May 10 18:49:12 vagoshome vdr: [4815] receiver on device 1 thread started (pid=4774, tid=4815) May 10 18:49:12 vagoshome vdr: [4816] TS buffer on device 1 thread started (pid=4774, tid=4816) May 10 18:49:13 vagoshome vdr: [4814] cVideoRepacker: operating in H.264 mode May 10 18:49:13 vagoshome vdr: [4774] retuning due to modification of channel 1853 May 10 18:49:13 vagoshome vdr: [4774] switching to channel 1853 May 10 18:49:13 vagoshome vdr: [4814] transfer thread ended (pid=4774, tid=4814) May 10 18:49:13 vagoshome vdr: [4774] buffer stats: 253048 (12%) used May 10 18:49:13 vagoshome vdr: [4774] PMT-SWITCH Device: '0' Channel: '1853' SID '990' May 10 18:49:13 vagoshome vdr: [4774] /dev/dvb/adapter0/demux0 May 10 18:49:13 vagoshome vdr: [4816] TS buffer on device 1 thread ended (pid=4774, tid=4816) May 10 18:49:13 vagoshome vdr: [4815] buffer stats: 178412 (8%) used May 10 18:49:13 vagoshome vdr: [4815] receiver on device 1 thread ended (pid=4774, tid=4815) May 10 18:49:13 vagoshome vdr: [4819] transfer thread started (pid=4774, tid=4819) May 10 18:49:13 vagoshome vdr: [4820] receiver on device 1 thread started (pid=4774, tid=4820) May 10 18:49:13 vagoshome vdr: [4821] TS buffer on device 1 thread started (pid=4774, tid=4821) May 10 18:49:14 vagoshome vdr: [4819] cVideoRepacker: operating in H.264 mode May 10 18:49:23 vagoshome vdr: [4774] switching to channel 1854 May 10 18:49:23 vagoshome vdr: [4819] transfer thread ended (pid=4774, tid=4819) May 10 18:49:23 vagoshome vdr: [4774] buffer stats: 331256 (15%) used May 10 18:49:23 vagoshome vdr: [4774] info: Channel not available! May 10 18:49:23 vagoshome vdr: [4821] TS buffer on device 1 thread ended (pid=4774, tid=4821) May 10 18:49:23 vagoshome vdr: [4820] buffer stats: 254552 (12%) used May 10 18:49:23 vagoshome vdr: [4820] receiver on device 1 thread ended (pid=4774, tid=4820) May 10 18:49:27 vagoshome vdr: [4774] switching to channel 1853 May 10 18:49:27 vagoshome vdr: [4774] PMT-SWITCH Device: '0' Channel: '1853' SID '990' May 10 18:49:27 vagoshome vdr: [4774] /dev/dvb/adapter0/demux0 May 10 18:49:27 vagoshome vdr: [4824] transfer thread started (pid=4774, tid=4824) May 10 18:49:27 vagoshome vdr: [4825] receiver on device 1 thread started (pid=4774, tid=4825) May 10 18:49:27 vagoshome vdr: [4826] TS buffer on device 1 thread started (pid=4774, tid=4826) May 10 18:49:27 vagoshome vdr: [4824] cVideoRepacker: operating in H.264 mode Vangelis Nonas wrote: My multiproto version is not the latest, it is changeset 7205 dated a couple of months ago. My modified szap is dated from that date also, but it does not compile with multiproto plus. I cant find the exact links I downloaded multiproto and modified szap but they were mentioned on the linux-dvb mailing list. As fas as changing encrypted flag, vpid, ppid and dpid, can you please give me an example, what I have to change in the following line: Next HD;SkyItalia:11996:vC23M5S1Z35:S13.0E:27500:10160+160:0;400=ita,401=eng:0:919,93B:11030:64511:6400:0 Following is the log from vdr-1.5.14 with h264 patch and multiproto. If you want log from vdr-1.7.0 I'll send. Channel 1854 is HD Suisse and channel 1855 is Sky Sport HD 1. May 10 18:18:03 vagoshome vdr: [5996] cVideoRepacker: operating in H.264 mode May 10 18:18:13 vagoshome vdr: [5957] switching to channel 1854 May 10 18:18:13 vagoshome vdr: [5996] transfer thread ended (pid=5957, tid=5996) May 10 18:18:13 vagoshome vdr: [5957] buffer stats: 228984 (10%) used May 10 18:18:13 vagoshome vdr: [5957] info: Channel not available! May 10 18:18:13 vagoshome vdr: [5999] TS buffer on device 1 thread ended (pid=5957, tid=5999) May 10 18:18:13 vagoshome vdr: [5998] buffer stats: 203040 (9%) used May 10 18:18:13 vagoshome vdr: [5998] receiver on device 1 thread ended (pid=5957, tid=5998) May 10 18:18:15 vagoshome vdr: [5957] switching to channel 1853 May 10 18:18:15 vagoshome vdr: [5957] PMT-SWITCH Device: '0' Channel: '1853' SID '990' May 10 18:18:15 vagoshome vdr: [5957] /dev/dvb/adapter0/demux0 May 10 18:18:16 vagoshome vdr: [6002] transfer thread started (pid=5957, tid=6002) May 10 18:18:16 vagoshome vdr: [6003] receiver on device 1 thread started (pid=5957, tid=6003) May 10 18:18:16 vagoshome vdr: [6004] TS buffer on device 1 thread started (pid=5957, tid=6004) Igor wrote: As far as trying vdr with clear DVB-S2 channels, unfortunately it is not possible in my case since I only have access to Hotbird, which I think has no clear DVB-S2 channels. yes, you are right - on Hotbird the open dvb-s2 channels absent http://www.lyngsat.com/hd/hotbird.html As fas as changing encrypted flag, vpid, ppid and dpid, can you please give me an example, what I have to change in the following line: Next
Re: [vdr] error decompressing frame for Astra HD+
Hi, Igor schrieb: Hence, I regularly see VDR issue CLEARs after which such messages are normal. sorry, what do you mean VDR issue CLEARs ? vdr-xine's console output: video: synced early [vVMA]buffered 8,8 frames (v:25,2, a:8,8) frame: (0, 0)-(1920, 1088), zoom: (1,00, 1,00) buffered 9,3 frames (v:20,4, a:9,3) buffered 10,5 frames (v:25,9, a:10,5) buffered 10,2 frames (v:30,8, a:10,2) Clear(0)DiscontinuityDetected: triggering soft start ! video: synced early [vAV]buffered 8,7 frames (v:28,7, a:8,7) buffered 9,3 frames (v:30,1, a:9,3) buffered 10,5 frames (v:30,5, a:10,5) buffered 7,2 frames (v:28,5, a:7,2) Clear(1)DiscontinuityDetected: triggering soft start ! video: synced early [VA]buffered 8,5 frames (v:21,5, a:8,5) VDR's syslog: May 10 17:31:49 video vdr: [5227] cVideoRepacker: operating in H.264 mode May 10 17:32:01 video vdr: [5228] buffer usage: 70% (tid=5227) May 10 17:32:01 video vdr: [5228] buffer usage: 80% (tid=5227) May 10 17:32:01 video vdr: [5228] buffer usage: 90% (tid=5227) May 10 17:32:01 video vdr: [5228] buffer usage: 100% (tid=5227) May 10 17:32:01 video vdr: [5228] ERROR: 3607 ring buffer overflows (678105 bytes dropped) May 10 17:32:01 video vdr: [5227] clearing transfer buffer to avoid overflows May 10 17:32:02 video vdr: [5228] buffer usage: 0% (tid=5227) xine's output: +++ CLEAR(17a): sync point: 1d ao_flush (loop running: 1) === CLEAR(17.1) === CLEAR(17.2) === CLEAR(17.3) === CLEAR(17.4) === CLEAR(17.5) --- CLEAR(17a) ao_close audio_out: no streams left, closing driver audio discontinuity #80, type is 0, disc_off 0 waiting for in_discontinuity update #80 video discontinuity #80, type is 0, disc_off 0 vpts adjusted with prebuffer to 58459551 +++ CLEAR(17b): sync point: 1d ao_flush (loop running: 1) === CLEAR(17.1) === CLEAR(17.2) === CLEAR(17.3) === CLEAR(17.4) === CLEAR(17.5) --- CLEAR(17b) But H.264 doesn't have a broken link flag, so that's why FFmpeg gives messages like the following: [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error [h264 @ 0xac236490]B picture before any references, skipping [h264 @ 0xac236490]decode_slice_header error so, could you give some resume about this errors ? is it ffmpeg/provider/vdr/driver problem ? or no any problem ? Well, one might consider this an error, but it has no influence on the output. VDR was written for MPEG1/2 and it properly calls cRemux::SetBrokenLink() when necessary, to indicate that the first few B frames shall not be decoded until two reference frames are available. As there is no such flag in H.264, the function doesn't do anything than logging, that it didn't find a MPEG1/2 GOP header where this flag is located. May 10 17:38:16 video vdr: [5430] SetBrokenLink: no GOP header found in video packet Supporting this issue properly in H.264 would mean to not send the first B frames to the output device which is more complex than just setting a single bit. And with the upcoming recording format changes I don't want to address this issue at the moment. 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] Can not view DVB-S2 channels
Hi, can you try this FTA channel, which broadcasts MPEG2 via DVB-S2 at Hotbird 13.0 E: Initial;ITI:11449:hC23M5O35S1:S13.0E:27500:519:0:0:0:15100:318:1300:0 BTW: your syslog excerpt didn't show messages like May 10 18:04:03 video vdr: [6165] cVideoRepacker: switching to MPEG1/2 mode just May 10 18:04:03 video vdr: [6165] cVideoRepacker: operating in MPEG1/2 mode so I assume you didn't specify -l 3 on VDR's command line, or debug messages are logged into a different file by syslog. Please try to provide those log lines too. 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] Can not view DVB-S2 channels
When I switch to Initial channel I dont get the channel not available message, however I dont get a picture as well. I believe that this channel is not receivable, at least not at my location. Following is my log when starting vdr with BBC World, then switching to Initial, then back to BBC World (using -l 3): May 10 19:42:07 vagoshome vdr: [5296] cTimeMs: not using monotonic clock - resolution is too bad (0 s 1 000 ns) May 10 19:42:07 vagoshome vdr: [5296] VDR version 1.7.0 started May 10 19:42:07 vagoshome vdr: [5296] codeset is 'ANSI_X3.4-1968' - unknown May 10 19:42:07 vagoshome vdr: [5296] found 0 locales in ./locale May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'deu,ger' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'slv,slo' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'ita' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'dut,nla,nld' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'por' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'fra,fre' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'nor' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'fin,smi' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'pol' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'esl,spa' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'ell,gre' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'sve,swe' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'rom,rum' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'hun' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'cat,cln' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'rus' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'hrv' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'est' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'dan' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'cze,ces' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'tur' May 10 19:42:07 vagoshome vdr: [5296] no locale for language code 'ukr' May 10 19:42:07 vagoshome vdr: [5296] loading plugin: ./PLUGINS/lib/libvdr-xine.so.1.7.0 May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/setup.conf May 10 19:42:07 vagoshome vdr: [5296] ERROR: unknown config parameter: MenuButtonCloses = 0 May 10 19:42:07 vagoshome vdr: [5296] unknown locale: '0' May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/sources.conf May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/diseqc.conf May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/channels.conf May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/timers.conf May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/svdrphosts.conf May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/remote.conf May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/keymacros.conf May 10 19:42:07 vagoshome vdr: [5296] reading EPG data from /video/epg.data May 10 19:42:07 vagoshome vdr: [5298] video directory scanner thread started (pid=5296, tid=5298) May 10 19:42:07 vagoshome vdr: [5296] probing /dev/dvb/adapter0/frontend0 May 10 19:42:07 vagoshome vdr: [5298] video directory scanner thread ended (pid=5296, tid=5298) May 10 19:42:07 vagoshome vdr: [5296] device 1 provides: DVBS DSS DVBS2 May 10 19:42:07 vagoshome vdr: [5297] video directory scanner thread started (pid=5296, tid=5297) May 10 19:42:07 vagoshome vdr: [5296] found 1 video device May 10 19:42:07 vagoshome vdr: [5297] video directory scanner thread ended (pid=5296, tid=5297) May 10 19:42:07 vagoshome vdr: [5296] initializing plugin: xine (0.8.2): Software based playback using xine May 10 19:42:07 vagoshome vdr: [5296] setting primary device to 2 May 10 19:42:07 vagoshome vdr: [5296] assuming manual start of VDR May 10 19:42:07 vagoshome vdr: [5296] SVDRP listening on port 2001 May 10 19:42:07 vagoshome vdr: [5296] setting current skin to sttng May 10 19:42:07 vagoshome vdr: [5296] loading /home/vagos/vdr-1.4.7/video/themes/sttng-default.theme May 10 19:42:07 vagoshome vdr: [5296] starting plugin: xine May 10 19:42:07 vagoshome vdr: [5299] tuner on device 1 thread started (pid=5296, tid=5299) May 10 19:42:07 vagoshome vdr: [5300] section handler thread started (pid=5296, tid=5300) May 10 19:42:07 vagoshome vdr: [5301] XineRemote control thread started (pid=5296, tid=5301) May 10 19:42:07 vagoshome vdr: [5301] Entering cXineRemote thread May 10 19:42:07 vagoshome vdr: [5296] ERROR: remote control XineRemote not ready! May 10 19:42:07 vagoshome vdr: [5296] remote control KBD - keys known May 10 19:42:07 vagoshome vdr: [5296] switching to channel 299 May 10
Re: [vdr] Can not view DVB-S2 channels
Hi, Vangelis Nonas schrieb: When I switch to Initial channel I dont get the channel not available message, however I dont get a picture as well. I believe that this channel is not receivable, at least not at my location. Following is my log when starting vdr with BBC World, then switching to Initial, then back to BBC World (using -l 3): Well, I forgot to mention that the SkyStar HD (TT3200) driver still has an issue regarding tuning this channel. It may take up to several minutes until it successfully tunes to this channel (you'll see several messages like 'frontend 0 timed out while tuning to channel 1860, tp 111449'). BTW: Where do these PMT-SWITCH messages come from? OT: check your LANG and LC_... environment variables. Set LANG to one entry among the list which locale -a outputs and check the values of the other variables by typing locale In case an LC_... variable is not set explicitly, the locale command will print it's default value derived from other variables like LANG, so there is no need to set them unless you want some of them to be different from their default values. 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] Can not view DVB-S2 channels
So, I have checked on my VDR 170 your issue. I can confirm that on encrypted dvb/s dvb/s2 channels I receive the message Channal not available But you can fix it easy :) Go to Menu - Setup - Update channels - NO after that go to the channels edit (red button) - change CA field from encrypted to Free to Air Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] coreavc for Linux (coreavc 1.7.0 + x ine patches)
Hi can someone to run the coreavc for linux 170 with vdr 170 ? I couldn't :( Igor -Original Message- From: Darren Salt [EMAIL PROTECTED] To: vdr@linuxtv.org Date: Wed, 07 May 2008 21:58:55 +0100 Subject: Re: [vdr] coreavc for Linux (coreavc 1.7.0 + xine patches) I demand that Igor may or may not have written... [snip] http://groups.google.com/group/coreavc-for-linux?hl=en here you can find a new patches for xine 1.1.12 h264_pes.patch demux_ts_fixes.patch coreavc-xine-1.1.12_more.patch coreavc-xine-1.1.11.patch NAK. Unattributed, no summary lines, no descriptions, insufficiently and unsuitably split up, C++ comments, strange comments such as My Hack. There is at least one ABI change: a struct in a public header file is changed, which automatically makes this 1.2 material. Bug fixes then the h264 PES patch (without any ABI changes which are not simple additions) sent to xine-devel if you want any of this added to xine-lib. After that, the CoreAVC patches; one patch series against hg tip is STRONGLY preferred. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | Kill all extremists! Bother, said Pooh, as he saw the mushroom cloud. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
