Hi, spe@xxxxxxxxxx schrieb: > I achieved to compile the dvbs2 patched vdr1.5.13, but I can't get an > image from the S2-3200. > The S2-3200 is connected to an 19.2° oriented dish and the nexus to a 13°. > On the nexus I have an image, on the S2 a black screen. Looks like this is OK, see below. > This is what I can see in syslog regarding vdr : ... > Jan 27 09:16:44 pccave vdr: [13657] setting primary device to 1 So your primary device is the full featured nexus, isn't it? [serge pecher] yes it is. A FF device is not able to decode a H.264 stream or when it decodes the H.264 stream according to MPEG2, it won't find any pictures, respectively. So you'll get a black screen. For H.264 playback, you'll need a software device like vdr-xine as primary device. [serge pecher] Ok, but is it able to decode the stream coming from the budget card when tuned on a SD channel (dvb-s) ? I intend in a next phase to use an other machine with a vdr-xine to decode the HD streams. > Jan 27 09:16:46 pccave vdr: [13657] switching to channel 31 > Jan 27 09:16:46 pccave vdr: [13669] transfer thread started (pid=13657, tid=13669) > Jan 27 09:16:46 pccave vdr: [13670] receiver on device 2 thread started (pid=13657, tid=13670) > Jan 27 09:16:46 pccave vdr: [13665] set DVB-S2 > Jan 27 09:16:46 pccave vdr: [13671] TS buffer on device 2 thread started (pid=13657, tid=13671) > Jan 27 09:16:55 pccave vdr: [13665] frontend 1 timed out while tuning to channel 31, tp 112722 This one looks OK: DVB-S2 channels are tuned on VDR device 2 (= /dev/dvb/adapter1; frontend 1 = /dev/dvb/adapter1/frontend0). > Jan 27 09:17:15 pccave vdr: [13657] switching to channel 30 > Jan 27 09:17:15 pccave vdr: [13677] transfer thread started (pid=13657, tid=13677) > Jan 27 09:17:15 pccave vdr: [13678] receiver on device 2 thread started (pid=13657, tid=13678) > Jan 27 09:17:15 pccave vdr: [13679] TS buffer on device 2 thread started (pid=13657, tid=13679) > Jan 27 09:17:22 pccave vdr: [13665] frontend 1 timed out while tuning to channel 30, tp 112722 This one looks OK, too, tuning to the same transponder. > Jan 27 09:17:32 pccave vdr: [13657] switching to channel 1 > Jan 27 09:17:32 pccave vdr: [13662] set DVB-S > Jan 27 09:17:41 pccave vdr: [13662] frontend 0 timed out while tuning to channel 1, tp 110832 This one looks OK too. DVB-S channels shall be tuned on DVB-S capable devices only, and as a last resort, on DVB-S2 devices. But it looks like channel 1 is on ASTRA and therefore you'll get a tuning timeout on device 1 (= /dev/dvb/adapter0; frontend 0 = /dev/dvb/adapter0/frontend0) as it is connected to HOTBIRD. VDR currently assumes that all DVB-S(2) devices are able to deliver all DVB-S(2) channels (actually, it's a bit more complex). You'll need a special channel setup to bind channels to certain devices. [serge pecher] I presume that this is what I have to do, because I would like to look at the ASTRA channels with the DVB-S2 device. How can I achieve that ? > When I "scan" the Astra on device 1, I find a lot of services. What do you mean with "device 1"? VDR's "device 1" is your nexus and /dev/dvb/adapter1 is your S2-3200. [serge pecher] I mean scan -a 1 (so it scans /dev/dvb/adapter1, what I wrongly called device 1). I did modify with a patch found on the net the scan tool for dvb-s2 support. What do you mean with "scan"? Tools like szap use DiSEqC implicitly, so maybe you've to enable DiSEqC in VDR too. [serge pecher] I already tried that without succes, but I will try one more time. [serge pecher] Thanks Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@xxxxxx _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
