Ingo Bressler wrote: >Hello, >in conjunction with my Hauppauge Nexus v2.3 I get unexpected results with scan and szap (at least I think so) and because I'm using DiSEqc it could be a driver issue. (I've read its not tested so far) > >When using 'szap -c <file_A> <channel> -r' where file_A was generated by 'scan -s 0 /usr/share/doc/dvb-utils/examples/scan/dvb-s/Hotbird-13.0E' (debian unstable package) I get a lot of data at /dev/dvb/adapter0/dvr0 (as expected). >szap output like: "status 1f | signal b3fe | snr dd37 | ber 00000000 | unc 00000000 | FE_HAS_LOCK" > >But when using 'szap -c <file_B> <channel> -r' where file_B was successfully generated by 'scan -s 1 /usr/share/doc/dvb-utils/examples/scan/dvb-s/Sirius-5.0E' I get _zero_ data at /dev/dvb/adapter0/dvr0 (not expected). >szap output like: "status 1f | signal a23c | snr ce76 | ber 00000000 | unc 00000000 | FE_HAS_LOCK" > > 0x1f means both HAS_LOCK |HAS_SYNC, so the driver is receiving data, unless the driver is reporting false statuses. I had the same problem with early revision of mt352.c >First I thought that szap doesnt support DiSEqc but why does it get a lock ? And why is there no data with FE_HAS_LOCK ? > >I tried dvbstream with tuning settings from file_B of the particular channel: it ends up with the same results: FE_HAS_LOCK + "Streaming 2 streams" but no data (empty file/stdout) > >At last I tried dvbtune which supports explicitly some DiSEqc switches but it's not reliable in getting a lock (with -D 0): Sometimes it gets a FE_HAS_LOCK very fast but later I get only a lot of "polling....". I didnt manage to get a lock with 'dvbtune -D [1-4] ...' so far. When dvbtune gets a lock without DiSEqc (the '-D' option) there is some (uncompressed video ?) data at /dev/video0 but nothing at /dev/dvb/adapter0/dvr0. (I dont know exactly where to get my data from after using dvbtune ..) > > dvbstream and dvbtune have exactly the same tuning code, unless you have two very versions of each
