[linux-dvb] [linux-dvb]-Not able to lock...
Hi list, I have again a bad problem: polling Getting frontend event FE_STATUS: polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL FE_HAS_CARRIER polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL FE_TIMEDOUT FE_HAS_CARRIER Not able to lock to the signal on the given frequency. There are any patches to apply or code to modify or something else? Thanks _ MSN Foto: condividi, ritocca e stampa le tue foto online http://photos.msn.it -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] mplayer dvb input and TS-demuxer combo patch
Hello,
this is a combo patch that:
1) adds an experimental TS demuxer to mplayer
2) adds an input (streaming) interface from DVB cards.
It compiles and runs with the following versions of the drivers:
dvb-kernel (HEAD) (with stock kernel 2.4.20) and 0.9.4 (with kernel
2.4.18)
It was reported to work with Metzlerbros' drivers, but I didn't test them.
A note about the TS demuxer: it's based on Xine's and FFmpeg's ones, it's
very experimental,
and some functions such as seeking are a little more than a joke, so it
needs serious improvement; any volunteer?
In particular I want to add support for teletext and subtitles. Actually
it should be enough for streaming from DVB;
It can accept an option:
-tsfastparse 1
which disables accurate searching of the streams, and in some rare case
(such as small files piped to mplayer) might be necessary;
furthermore -vid and -aid have been raised to 8192.
I couldn't test this demuxer with a stream containing A52 audio, so if you
have some sample, please send me a link.
About the DVB interface:
I made a major cleanup and added the option to record directly in a
compressed format (such as mpeg1 / 4);
e.g.:
# mencoder -dvbin on=1:prog=C5 -oac copy -vop pp=ci:c -ovc lavc -lavcopts
vcodec=mpeg1video:vhq:vbitrate=1150:aspect=4/3 -o x.avi -
notice that you still need to add - at the end, or mencoder will quit
immediately.
You can use any codec and filter you want.
For watching TV you can use the same syntax:
mplayer -dvbin on=1:prog=R2
where R2 is a program defined in your ~/.mplayer/channels.conf, which has
the same syntax as szap and VDR for DVB-S
and the same for tzap in the case of DVB-T.
You can specify with card type you have with the option type (SAT or
TER), and which card number with card (from 1 to 4).
Default is type=SAT:card01.
Support for DVB-T is analogous, but totally untested: I used dvbstream's
code that usually works well, so where dvbstream works
this patch should run too.
The command-line syntax for DVB-T parameters is a shortened version of the
same parameters in channels.conf,
e.g.: :gi=32 stands for GUARD_INTERVAL_1_32 and so on.
Read libmpdemux/dvbin.c and cfg-common.h for a complete list.
I also removed some previous dependency from ts2ps and streaming_ctrl. The
system-load should be lower and the visualization more reliable.
The rest remains the same: h= channel up, k=channel down.
The lock-up in the case of a scrambled channel still remains, too. I'd
like to know what to do in this case
(tight loop when reading from the stream when filling the buffer).
This demuxer as a strange feature: the first few seconds (3 or 4) usually
are out of sync, but short after the synchrony fixes.
All the other parameters remain the same.
Last minute update: in mencoder.c at line 209 you should add:
#ifdef HAS_DVBIN_SUPPORT
#include libmpdemux/dvbin.h
extern dvb_history_t dvb_prev_next = {-1, -1};
#endif
(before
m_config_t* mconfig;
)
otherwise it records only from the first channel it finds in the
conf-file.
Have fun, and please report if it works or not (remember to run mplayer
with -v and send me the log).
Thanks to all the authors from whom I took the code (xine, dvbstream,
ffmpeg).
Nico
dvbin_ts_v5.gz
Description: Binary data
[linux-dvb] linux 2.5.63xx - CVS: dvb-linux and devfs ...
Hello ... It seems that the dvb-linux-driver for linux-2.5.x dont create the dev-devfs entries ... #ls -l /dev/dvb/ /dev/dvb/: total 0 #lsmod Module Size Used by stv0299 7616 0 dvb_ttpci 283336 0 dvb_core 42212 2 stv0299,dvb_ttpci crc32 2976 1 dvb_core saa7146_vv 34272 1 dvb_ttpci video_buf 10688 1 saa7146_vv saa7146 8764 2 dvb_ttpci,saa7146_vv v4l1_compat11968 1 saa7146_vv v4l2_common 2784 1 saa7146_vv videodev5696 1 saa7146_vv [cut] #dpkg -l |grep -i devfsd ii devfsd 1.3.25-12 Daemon for the device filesystem #uname -a Linux macbeth 2.5.63bk5 #2 SMP Sun Mar 2 11:57:15 CET 2003 i686 unknown unknown GNU/Linux mfg boris -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] redhat8 and skystar1 problems
today I got a skystar1 and am trying to install it on my redhat8 new pc. i am using the siemens dvb driver 0.9.4. I am stuck in first page when I do make :( [EMAIL PROTECTED] driver]# make /usr/src/linux/scripts/pathdown.sh: line 4: TOPDIR: parameter null or not set DIR=`pwd`; (cd /usr/src/linux; make SUBDIRS=$DIR modules) make[1]: Entering directory `/usr/src/linux-2.4.18-26.8.0' scripts/split-include include/linux/autoconf.h include/config find: *: No such file or directory scripts/split-include: find: Success make[1]: *** [include/config/MARKER] Error 1 make[1]: Leaving directory `/usr/src/linux-2.4.18-26.8.0' make: *** [here] Error 2 [EMAIL PROTECTED] driver]# any help please ? is this driver OK for my card or are there any new drivers I might use ? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: [vdr] Re: dxr3/vdr problem
On Wed, Mar 05, 2003 at 08:47:26AM +0100, Marcus Metzler wrote: Malcolm Caldwell writes: Kai argues that the dvb drivers should not be passing frames with errors through to applications. Given that there is FEC etc in the dvb spec this may be so - I don't know. I also don't know if a budget card is capable of doing this. All the error correction required and possible for the DVB signal is already done by the frontend. Any remaining errors cannot be fixed on the transport stream level. It would not make sense to check the MPEG stream on the ES level inside the driver. It is the task of the MPEG decoder to fix or ignore these problems. E.g. the hardware MPEG decoder of the av7110 already does these things which are often necessary for MPEG streams received from a error prone source. The dxr3 decoder is probably a little more picky because it was not developed for decoding a broken stream. If a TS packet has errors that cannot be corrected by FEC the frontends (depending on configuration) force the transport_error_indicator bit in the TS header to 1. VDR could use this information to do error processing, i.e. try to fix the PES packet that the TS packet belongs to (provided the PID field in the TS is still intact or can be guessed), at least by ensuring consistent length fields. I don't know if t is practical in software, but hardware specs always talk about error concealment in their feature lists. E.g. the video MPEG decoder can use data from the previous frame to fill in the gaps. So it would be better to drop erronous data than to feed crap to the decoder, but you can't just drop the TS (or even the PES) packet, you would have to unpack the ES to the slice level and repack it with filled-in data. The dxr3 never sees the transport_error_indicator, so it can't do it. It shouldn't crash, though. Regards, Johannes -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: C/A routing Question
Hi, On Tue, Feb 25, 2003 at 07:31:30PM +0100, I wrote: Ralph Metzler wrote: - Move the memory frontends to separate devices. Either also call them frontend with type memory frontend or call them memfrontend, mfrontend, dvrin, ... whatever They should offer mmap, write, etc. maybe even a software controlled rate control (some chips have it in hardware) to allow for decent non-blocking writing. Each demuxN can select which frontend (no matter if real or memory) to use as input. I seen that you've already defined FE_MEMORY and FE_NET in your version of the API header files. I for one would be happy with a /dev/.../frontend of type FE_MEMORY. How do we handle capabilites, i.e. if we can feed TS, PS and/or AVPES into the frontend? Is this handled by the demux that we connect to the frontend? I've thought about this, and now I think that it's no a good idea, because none of the ioctls for normal frontend devices apply to memory frontends, ecept FE_GET_INFO. I think it would be better to have a dedicated input device for the demux, which would then support write() and possbly mmap(). Regards, Johannes -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: [linux-dvb]-Not able to lock...
At 11:07 05/03/2003, you wrote: Hi list, I have again a bad problem: polling Getting frontend event FE_STATUS: polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL FE_HAS_CARRIER polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL FE_TIMEDOUT FE_HAS_CARRIER Not able to lock to the signal on the given frequency. There are any patches to apply or code to modify or something else? Thanks Looks like a signal strength problem to me. What does dvbtune -c cardnumber -f frequency -m say for the transponder in question? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] DVB driver release 1.0.0-pre2
Hi all, I've uploaded a new DVB driver release tarball on http://linuxtv.org/. Many thanks to all who contributed! Changes for linuxtv-dvb-1.0.0-pre2 o AV7110 firmware update; fixes OSD problems with VDR o fixes to poll() handling for audio and video device o stop video DMA (overlay) when v4l device is closed o fixes to ring buffer handling for CI link layer interface o added PCI ids for Technotrend/Hauppauge Nexus PCI DVB-S Regards, Johannes -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] filter and mask
I have read the API version 3, the HOW-TO-USE-THE-DEMUX-API , and some examples and I don't understand the meaning of the fields filter and mask in the struct dmx_filter. Can you help me? Bye. ___ Yahoo! Móviles Personaliza tu móvil con tu logo y melodía favorito en http://moviles.yahoo.es -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] MPEG Section CRC-32 error checking
Hi, Can someone give me an update on the current state of MPEG Section CRC-32 error checking. Is it done correctly in the DVB card hardware or the driver software and, if so, what is seen by client software using the Section Filter API when the CRC-32 check fails? Thanks, Chris -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: MPEG Section CRC-32 error checking
Chris Newell wrote: Hi, Can someone give me an update on the current state of MPEG Section CRC-32 error checking. Is it done correctly in the DVB card hardware or the driver software and, if so, what is seen by client software using the Section Filter API when the CRC-32 check fails? If you use a Nova or Budget card this works as expected, for av7110 based cards this is not implemented right now. Patches are welcome. Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: MPEG Section CRC-32 error checking
Hi, Can someone give me an update on the current state of MPEG Section CRC-32 error checking. Is it done correctly in the DVB card hardware or the driver software and, if so, what is seen by client software using the Section Filter API when the CRC-32 check fails? The DVB layer provides software CRC checking. But it's up to the drivers to provide hw accelerated CRC checking. AFAIK only the AViA GTX/eNX driver (used on the D-BOX2 stb) provides such functions. Bad sections will be silently dropped. Bye, Florian -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: filter and mask
Antonio Mosquera Quindimil wrote: I have read the API version 3, the HOW-TO-USE-THE-DEMUX-API , and some examples and I don't understand the meaning of the fields filter and mask in the struct dmx_filter. Can you help me? The filter field defines a bitfield which is compared to the section bits, mask specifies which bits are actually used for comparision. If you set mode bits to '1' you get a not-equal-filter, this means that the bits get actually XOR'd before comparision. Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] SKYSTAR1 and VDR
been trying whole day ...someone can please tell me what I need to get and what to do to make this working ? am using redhat8 with kernel 2.4.18-26.80 -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] LinVDR displays recurring timers multiple times
Hello, I'm using VDR 1.1.25 with driver linuxtv-dvb-1.0.0-pre2 and LinVDR 0.23 (vdradmin-0.23). Timers, which are scheduled for specific weekdays are displayed multiple times in LinVDR. (I cannot find out, which algorithm it follows...) I'm not sure where the problem is. It may be in the SVDR protocol handled by VDR or LinVDR, which interprets the data wrong. Does anybody else have this behaviour? Regards, Anton Schegg -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] The drivers and HTV
Hi everyone, Do I still need to use Jaakkos patch for HTV (Helsinki cable) with the drivers at: http://linuxtv.org/ or www.metzlerbros.org regards, Josce __ The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: The drivers and HTV
On Wed, Mar 05, 2003 at 03:53:15PM -0500, [EMAIL PROTECTED] wrote: Hi everyone, Do I still need to use Jaakkos patch for HTV (Helsinki cable) with the drivers at: http://linuxtv.org/ or www.metzlerbros.org regards, Josce I think so. I'm using them with a driver from 18th Feb. Try it first without the patches and then with the patches if it doesn't work. -- Lauri -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: DVB driver release 1.0.0-pre2
Johannes Stezenbach wrote: Hi all, I've uploaded a new DVB driver release tarball on http://linuxtv.org/. Hi, with the new drivers 1.0.0-rc1 and -rc2 I experience desync of a/v in VDR after viewing a recording. This does not happen with a driver from CVS as of 13. January. This is very reproducable. It affects all programs on the same frequency (I use DVB-T) but vanishes, if I switch to a channel on another frequency. This happens also, if I use the old firmware (from the 13-01 driver) with the new driver, so it seems to be not a problem of the new firmware. Anyone else seeing this? Cheers, Juri -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Hauppauge
Dear list, I have bought a Hauppauge DVB-C-card, in the hope it would be usefull for me. My goal was, to watch and record digital tv on my pc. The hardware does kind of work, but it is not very comfortable. Sometime in december I fetched the current cvs-version on linuxtv.org and I can use this software to bring pictures on my monitor. I have to issue make insmod in DVB/driver, then I can start apps/szap/czap channel and if I then start apps/test/video, I get a picture, which I can only recognize, if I am using my text-console, which is on a framebuffer. Under X the picture is distorted. If I want to tune to a different channel, I have to remove the modules and re-insert them, otherwise the tuning is not successfull (no FE_HAS_LOCK) My questions are: Am I with the right mailing list for this kind of problems? What is a frontend in this environment? Which is the right driver to use? I found the cvs at linuxtv.org, I have seen, that linux 2.5 contains something very similar and I have seen various other drivers, which seem to differ not too much, so that I am a bit confused. Unfortunately it does not work as I wish and I am confused, so I guess I need some help to get this to work. Thank you very much in advance Karl lspci -v reports the following for this card 00:0c.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH: Unknown device 0002 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at dffeee00 (32-bit, non-prefetchable) [size=512] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: [vdr] Re: dxr3/vdr problem
I have a few questions about the dvb drivers/devices that perhaps someone can answer. When receiving from one of the transponders on asiasat2 I have no problems at at all. While running vdr and also running dvbtune -m I see: ... Signal=53116, Verror=0, SNR=43860dB, BlockErrors=0, (S|L|C|V|SY|) Signal=53427, Verror=0, SNR=43815dB, BlockErrors=0, (S|L|C|V|SY|) Signal=52821, Verror=0, SNR=43836dB, BlockErrors=0, (S|L|C|V|SY|) Signal=53090, Verror=0, SNR=43758dB, BlockErrors=0, (S|L|C|V|SY|) On another transponder I see: Signal=41268, Verror=65357, SNR=37605dB, BlockErrors=0, (S|L|C|V|SY|) Signal=41267, Verror=65291, SNR=37608dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40916, Verror=65494, SNR=37554dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40953, Verror=65381, SNR=37479dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40660, Verror=65349, SNR=37548dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40977, Verror=65315, SNR=37539dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40976, Verror=65434, SNR=37560dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40665, Verror=65419, SNR=37575dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40946, Verror=65478, SNR=37641dB, BlockErrors=0, (S|L|C|V|SY|) This second transponder always gives high levels of Verror. For parts of the day the Verror will be around 2 and the service seems to work and my dxr3 won't freeze. At other times it is up around 65000 and things don't work and the dxr3 will eventually freeze (requiring either a vdr restart or sometimes a machine restart) My questions: 1. Whis is this Verror? What is its units? It understand it is related to BER but how? I understand it is a 16bit number so it would seem my values are high. 2. Why the difference between these two services? I thought it may be symbol rate (the first is 20400 while the second is 28125). I have been assuming that my problems are RF related but is this perhaps some kind of problem due to a high load on a low end machine? On Wed, 2003-03-05 at 22:48, Johannes Stezenbach wrote: On Wed, Mar 05, 2003 at 08:47:26AM +0100, Marcus Metzler wrote: Malcolm Caldwell writes: Kai argues that the dvb drivers should not be passing frames with errors through to applications. Given that there is FEC etc in the dvb spec this may be so - I don't know. I also don't know if a budget card is capable of doing this. All the error correction required and possible for the DVB signal is already done by the frontend. Any remaining errors cannot be fixed on the transport stream level. It would not make sense to check the MPEG stream on the ES level inside the driver. It is the task of the MPEG decoder to fix or ignore these problems. E.g. the hardware MPEG decoder of the av7110 already does these things which are often necessary for MPEG streams received from a error prone source. The dxr3 decoder is probably a little more picky because it was not developed for decoding a broken stream. If a TS packet has errors that cannot be corrected by FEC the frontends (depending on configuration) force the transport_error_indicator bit in the TS header to 1. VDR could use this information to do error processing, i.e. try to fix the PES packet that the TS packet belongs to (provided the PID field in the TS is still intact or can be guessed), at least by ensuring consistent length fields. I don't know if t is practical in software, but hardware specs always talk about error concealment in their feature lists. E.g. the video MPEG decoder can use data from the previous frame to fill in the gaps. So it would be better to drop erronous data than to feed crap to the decoder, but you can't just drop the TS (or even the PES) packet, you would have to unpack the ES to the slice level and repack it with filled-in data. The dxr3 never sees the transport_error_indicator, so it can't do it. It shouldn't crash, though. Regards, Johannes -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] MHP running on Linux-TV
Hi, A while back there was a proposal from LinuxTV on an open source MHP implementation running on top of the Kaffe JVM and using GGI, LinuxTV, etc as the framework. Has anyone got MHP running on their LinuxTV platform? Thanks in advance and regards, RajeshDo you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, and more
[linux-dvb] HW for running LinuxTV DVB / Linux TV on MIPS/Linux
Hi, I live in the US. I found that the Siemens and other PCIMPEGcards for the Linux TV - DVB receiver are available easily in Europe. Has anyone here in the US got these cards or similar cards locally or via other sources? I would appreciate some info. on this. I would also like to know experiences of folks who have tried running Linux TV on Linux/MIPS platforms. Thanks in advance and regards, RajeshDo you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, and more
