Difference between revisions of "ISDB-T Devices"

From LinuxTVWiki
Jump to: navigation, search
 
(45 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Supported Hardware ==
+
*[[ISDB-T PCI Cards]]
 +
*[[ISDB-T PCIe Cards]]
 +
*[[ISDB-T USB Devices]] (Pensticks, Boxes, etc)
 +
*[[ISDB-T_IEEE1394_Devices|DVB-T IEEE1394 / Firewire / iLink Boxes]]
 +
*[[ISDB-T PCMCIA Cards]] (PC Card/CardBus, ExpressCard)
  
Currently, There are three drivers that support ISDB-T:
+
== Temporary Section ==
=== Open Source ===
+
Support for ISDB-T devices is currently in its infancy under Linux, having only been added to the [[S2API|Linux DVB S2API]] in September 2009.  The number of drivers and supported devices will surely grow in time. 
** the dibcom dib0700 and pt1 drivers. The dib0700 implements the new DVBS2API to allow finer control at the ISDB-T parameters.
+
=== Closed Source ===
+
** the commercially bundled drivers from [[Sundtek]] for USB devices based upon [[EMPIA_Technology|Empia]] chipsets.  The Sundtek solution support both the S2-API as well as the Legacy DVBv3 API
+
  
== How to make it work with the current dvb-apps version? ==
+
===How do I make ISDB-T devices work with the current dvb-apps version? ===
 
+
Currently, some changes are needed within the [[LinuxTV dvb-apps|dvb-apps]] in order to support the new DVBS2API parameters for ISDB-T. Until those changes are implemented there, and within  userspace apps, you will need to use the DVB-T format.
Some changes are needed at dvb-apps in order to support the new DVBS2API parameters for ISDB-T. While those changes aren't implemented there and at the userspace apps, you need to use the DVB-T format.
+
  
 
In the case of ISDB-T, the current implementations (Brazil and Japan) use 6 MHz bandwidth with the same [[ISDB-T Frequency Table]]. In the future, this is likely to change.
 
In the case of ISDB-T, the current implementations (Brazil and Japan) use 6 MHz bandwidth with the same [[ISDB-T Frequency Table]]. In the future, this is likely to change.
Line 18: Line 18:
 
Then, a DVB-T userspace application can be used to play the stream. In the case of Brazil, the application needs to support H.264 for video, HE-AAC for audio, and PMT tables at the mpeg-ts. Currently, only vlc and the newest development versions of mplayer are known to support. However, some stream types are known to not work with none of those two applications, due to some existing bugs.
 
Then, a DVB-T userspace application can be used to play the stream. In the case of Brazil, the application needs to support H.264 for video, HE-AAC for audio, and PMT tables at the mpeg-ts. Currently, only vlc and the newest development versions of mplayer are known to support. However, some stream types are known to not work with none of those two applications, due to some existing bugs.
  
== ISDB-T Boards ==
 
=== Leadership ===
 
 
==== lsusb - vendor/product id ====
 
  eb1a:2875 eMPIA Technology, Inc.
 
  
==== I2C devicelist hash table ====
+
[[Category:Hardware| ]]
  0x6b800080
+
[[Category:ISDB-T| ]]

Latest revision as of 22:54, 3 October 2009

Temporary Section

Support for ISDB-T devices is currently in its infancy under Linux, having only been added to the Linux DVB S2API in September 2009. The number of drivers and supported devices will surely grow in time.

How do I make ISDB-T devices work with the current dvb-apps version?

Currently, some changes are needed within the dvb-apps in order to support the new DVBS2API parameters for ISDB-T. Until those changes are implemented there, and within userspace apps, you will need to use the DVB-T format.

In the case of ISDB-T, the current implementations (Brazil and Japan) use 6 MHz bandwidth with the same ISDB-T Frequency Table. In the future, this is likely to change.

For the device to work, the first step is to seek for the existing channels. This is done by running the 'scan' application:

 scan FrequencyTable >channels.conf

Then, a DVB-T userspace application can be used to play the stream. In the case of Brazil, the application needs to support H.264 for video, HE-AAC for audio, and PMT tables at the mpeg-ts. Currently, only vlc and the newest development versions of mplayer are known to support. However, some stream types are known to not work with none of those two applications, due to some existing bugs.