Talk:Main Page

From LinuxTVWiki
Revision as of 11:41, 12 October 2006 by Js (Talk | contribs)

Jump to: navigation, search

KaxTV

Should the entry of KaxTV not be removed in the main listing if it is discontinued and now part of Kaffeine?

Use case page for linux tv

Hello

I was thinking about creating a page that would list working solutions for various encrypted operators across the world. This would be structured something like:

  • Section Country
  • sub-section: Operator
  • A table for budget card that would contain: software, card, CAM type, CAM brand, comments
  • A likewise table for FF cards.

What do you think about such a page ?

Cheers

-- would be very helpful I find. BTW, I think we should have the wiki-typical "just do it" approach here, i.e. don't ask - if you think it'd be useful and help others, yes, write it up! --LAk loho 23:42, 24 April 2006 (CEST)

-- Done in Use_cases. Now I hope that other people will complete this page. --Ddumont 10:19, 28 July 2006 (CEST)

Long software list on it's own page?

Hi! I was thinking the software list on the main page gets too long. At the same time, not all software is helpful for all users (analogue, FF or budget cards). So does anyone mind if I move all links to a separate page, where there'd be comments on each program? --LAk loho 23:42, 24 April 2006 (CEST)

-- By comments, do you mean a one line description for the software or longer comments ? --Ddumont 14:23, 25 April 2006 (CEST)

I thought of something like one line for each program or maybe a table. Longer descriptions are/should be available on the individual program's page so there's no real need. --LAk loho 21:18, 29 April 2006 (CEST)

Okay, I did it now. See the software page if you wonder where all the programs went to. Of course it's a bit subjective which programs to list on the front page but I think those are the most commonly used. If you think a prominent program is now missing, just put it back up again. Lak loho


Leadtek DTV1000 Remote Control

Hi,

I have been working for a while in developing the code for the Leadtek DTV1000 remore control. I think is almost ready (it works for me), maybe someone can double check it for me. How do I do I contribute to the project?

Thanks


probleme with

dvb: Leadtek Winfast DTV dongle driver: v4l-dvb-stk3000p-e5798f307b00 firmware: dvb-usb-dibusb-6.0.0.8.fw distrib: ubuntu 6.6 5.10 fc5

good aerial (very good reception with other dvb and analog) try anyway with ampli and atenuation

i can scan only 2 freq on 5 (freq under 500 mega) the tzap on a good or no good channel is very unstable:

claude@ch:~$ tzap TF1 (this channel do not work) using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 562000000 Hz video pid 0x0078, audio pid 0x0082 status 02 | signal b237 | snr 0000 | ber 001fffff | unc 0000ffff | status 1e | signal b231 | snr 0000 | ber 001fffff | unc 0000ffff | FE_HAS_LOCK status 1e | signal ff3f | snr 0001 | ber 00000000 | unc 00000ef5 | FE_HAS_LOCK status 1e | signal 0000 | snr ffff | ber 00000000 | unc 00000ef6 | FE_HAS_LOCK status 1e | signal 0000 | snr ffff | ber 00000000 | unc 00000ef6 | FE_HAS_LOCK status 1e | signal 0000 | snr ffff | ber 000001d0 | unc 00000ef5 | FE_HAS_LOCK status 1e | signal 0710 | snr 0000 | ber 00000000 | unc 00000ef6 | FE_HAS_LOCK status 1e | signal 0000 | snr ffff | ber 00000240 | unc 00000ef5 | FE_HAS_LOCK status 1e | signal 0900 | snr 0000 | ber 00000000 | unc 00000ef6 | FE_HAS_LOCK status 1e | signal 0000 | snr ffff | ber 00000000 | unc 00000ef5 | FE_HAS_LOCK

claude@ch:~$ tzap "Direct 8" (this channel work) using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 474000000 Hz video pid 0x00a0, audio pid 0x0050 status 03 | signal dc0d | snr 0001 | ber 001fffff | unc 0000ffff | status 1f | signal dc11 | snr 0001 | ber 00057010 | unc 00000046 | FE_HAS_LOCK status 1f | signal c010 | snr 00c0 | ber 00029230 | unc 00000018 | FE_HAS_LOCK status 1f | signal 4830 | snr 0002 | ber 0000dab0 | unc 00000000 | FE_HAS_LOCK status 1f | signal 6a30 | snr 0000 | ber 00011d90 | unc 00000000 | FE_HAS_LOCK status 1f | signal 7610 | snr 0000 | ber 00014130 | unc 00000000 | FE_HAS_LOCK status 1f | signal 0430 | snr 0000 | ber 00005840 | unc 00000000 | FE_HAS_LOCK status 1f | signal 6100 | snr 0000 | ber 000074c0 | unc 00000000 | FE_HAS_LOCK status 1f | signal d300 | snr 0002 | ber 0000af80 | unc 00000000 | FE_HAS_LOCK status 1f | signal be00 | snr 0000 | ber 00009640 | unc 00000000 | FE_HAS_LOCK status 1f | signal 5900 | snr 0000 | ber 0000e730 | unc 00000000 | FE_HAS_LOCK status 1f | signal 9c30 | snr 0001 | ber 00015770 | unc 00000000 | FE_HAS_LOCK status 1f | signal 5d30 | snr 0000 | ber 0000bbf0 | unc 00000000 | FE_HAS_LOCK


i think, this look like a wrong initilisation ????


Hi, guy's I see here is a lot good tester,, If some one is intereted, I have soruce code complete form a SetTopBox , CPU IBMpower PC 405 stb002500,flash 2mb, ram 16mb,, the stb is very fast and video and audios is same as dreambox, because have same CPU, but difrent Model DB is a stb004400 PPC. This unit on U* market is working very good on N2 , but becuase charlie make a change over 1 month now, stb can't view video and audio from charlie, what they make is a new update REVISION.

At same time few others brand stb have been release a temporary soltution, but using conditional access card , on they unit they make some new modification on the STB firmware , what it does is comunicate with the smartcard, also they implement on they firmware a Boxkey #, becuase the smartcard have a Box key and a CAM ID, so , for these reason card get comunicate with the unit, and video and aduio come back up..

so if some good programer are intereted , I will provide STB sample for testing purpose..

thanks,. sorry about my spell.

LinuxTV vs. video4linux

Why did someone feel the need for 2 wiki? What is the difference between them ?

video transmitter

I see lots of good information here about receiving the through-the-air signal, demodulating, decoding, recording, viewing, etc.

Is there any information on the other end of things? Given a camera, what else do I need to start transmitting video through the air? What sorts of common mistakes do people who transmit need to avoid, in order not to cause problems downstream at the reciever?

My understanding is that one needs to license spectrum from the FCC (directly or indirectly), to avoid interfering with other people who may be using those frequencies.

My understanding is that the standard for video transmission is MPEG-4, which requires some sort of license to use. Are there any alternatives? Is Theora ( wikipedia:Theora ) usable ?

--DavidCary 15:30, 3 August 2006 (CEST)

PB : no grabber device available

Hi everybody !

What do we have here :

- hardware working well : devices'files : /dev/dvb/adapter0/demux0 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/net0

But impossible to capture any kind of streaming data : I prepared a faked /root/.tzap/channels.conf file as said in the last wikies :

  1. cat channels.conf

"

TERRESTRISCH_17.08.2006

M6:714000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:120:130:1025 TF1:730167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:120:130:1537

17.08.2006

"

I've tried :

  1. scantv -c /dev/dvb/adapter0/demux0

no grabber device available

  1. scantv -c /dev/dvb/adapter0/dvr0

v4l2: open /dev/dvb/adapter0/dvr0: Operation not supported v4l2: open /dev/dvb/adapter0/dvr0: Operation not supported v4l: open /dev/dvb/adapter0/dvr0: Operation not supported no grabber device available

  1. scantv -c /dev/dvb/adapter0/frontend0

ioctl: VIDIOC_QUERYCAP(driver="";card="";bus_info="";version=0.0.0;capabilities=0x0 []): Operation not supported no grabber device available

  1. scantv -c /dev/dvb/adapter0/net0

ioctl: VIDIOC_QUERYCAP(driver="";card="";bus_info="";version=0.0.0;capabilities=0x0 []): Inappropriate ioctl for device no grabber device available

(My system : Mandriva 10.1, KDE 3.2, Xorg server, Hauppauge WinTv Nova T Usb2, location : Toulouse, France)

DO YOU KNOW WHY ?

Pb with Hauppauge Nova T USB 2, under Linux kernel 2.6.13.2 or 2.6.17.7 tested too :

udev service first recognize my card and makes directories : /dev/dvb/adapter0/dvr0, frontend0, demux0, et net0 but juste after (I think when entering KDE level 5) udev scan again my plugs and disconnect my Nova T nodes

Files samples : " dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 32). dvb-usb: MAC address: 00:0d:fe:02:ca:13 dvb-usb: schedule remote query interval to 100 msecs. dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully initialized and connected. usbcore: registered new driver dvb_usb_nova_t_usb2 dvb-usb: bulk message failed: -110 (2/0) dvb-usb: bulk message failed: -110 (2/0) dvb-usb: bulk message failed: -110 (2/0) dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully deinitialized and disconnected. dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge WinTV-NOVA-T usb2). dvb-usb: MAC address: 00:0d:fe:02:ca:13 dib3000: Found a DiBcom 3000P. DVB: registering frontend 0 (DiBcom 3000P/M-C DVB-T)... dvb-usb: schedule remote query interval to 100 msecs. dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully initialized and connected.

Aug 22 22:40:33 pcnew udev[2668]: configured rule in '/etc/udev/rules.d/dvb.rules' at line 1 applied, 'dvb0.dvr0' becomes '%c' <30>Aug 22 22:40:33 udev[2668]: creating device node '/dev/dvb/adapter0/dvr0' Aug 22 22:40:33 pcnew udev[2753]: removing device node '/dev/dvb/adapter0/dvr0' Aug 22 22:40:33 pcnew udev[2667]: configured rule in '/etc/udev/rules.d/dvb.rules' at line 1 applied, 'dvb0.demux0' becomes '%c' <30>Aug 22 22:40:33 udev[2667]: creating device node '/dev/dvb/adapter0/demux0' Aug 22 22:40:33 pcnew udev[2741]: removing device node '/dev/dvb/adapter0/frontend0' Aug 22 22:40:33 pcnew udev[2746]: removing device node '/dev/dvb/adapter0/net0' Aug 22 22:40:33 pcnew udev[2761]: removing device node '/dev/dvb/adapter0/demux0' "

  1. tzap M6

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 714000000 Hz status 00 | signal ff3f | snr 0001 | ber 001fffff | unc 0000ffff | status 00 | signal ff3f | snr 0001 | ber 001fffff | unc 0000ffff | status 00 | signal ff3f | snr 0001 | ber 001fffff | unc 0000ffff | ...

  1. scandvb -c

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x0000 dumping lists (0 services) Done.

Who could take me out off hell ?